Integration Day After Company Merger in 2026

We look at how to turn a post-merger meeting into a working transition point: aligning facts, working through new interfaces, gathering questions, and assigning next steps.

After a merger, employees rarely need another ceremonial presentation. They need to understand what has already been decided, what is not changing yet, where new work routes have appeared, and who will provide the next answer. At Aventura, we view the integration day as a managed transition point. It links top-level communication, function-specific work, and follow-up actions. HR, legal, and organizational processes run separately.

If the task is already in the plan, request a quote for the integration day. We will clarify audiences, format, number of tracks, and set of materials before developing the scenario.

What is an integration day and what problem does it solve?

An integration day is an in-person or hybrid working meeting for employees of two merging companies. Its goal is to provide a shared version of confirmed facts, show the upcoming changes for different groups, collect questions, and create the necessary working connections. Such an event shows where and when employees will receive the next answers. Decisions by management, human resources (HR), and process owners remain outside the program.

After the deal, people look at the integration from their own perspective. Finance cares about approvals, sales cares about customer routes. Information technology (IT) teams clarify systems and access, and production monitors business continuity. One generic slide does not answer these questions. That is why we start not with the stage, but with a map of audiences and changes.

Preparation can be conducted as a business event for employees, if the core of the program focuses on decisions, questions, and working dependencies. An entertainment part is acceptable as a short addition, but it should not overshadow the conversation about the consequences of the merger.

An integration day differs from a Welcome Day. Most participants already know their jobs, have established connections, and have experience in their previous organization. From the Welcome Day agenda, navigation and a contact map are useful, but addressing experienced employees as newcomers is not appropriate.

Goals and boundaries of the format after the merger

A good goal for an integration day describes an observable work outcome: employees have an updated map of changes, know the owners of answers, identified gaps between functions, and agreed on next points of contact. Formulations about instant culture merging or creating a single team are too broad. They provide neither a scenario solution nor an honest criterion for the outcome of a single event.

Before preparing the program, we divide four types of content:

• confirmed decisions that need to be explained to everyone in the same way;
• changes that affect specific functions, cities, or management levels;
• open questions for which verification owners have already been assigned;
• personal and confidential topics that cannot be discussed on the general stage.

This framework protects managers from improvisation, and employees from mixing facts and assumptions. If a decision is still under consideration, we say so directly. Instead of a presumed answer, we indicate the responsible person and the event after which an update will appear.

The general part of the program can use the mechanics of town hall for the company: a unified message, moderated questions, and a final package. But the integration day is broader. After the general block, participants move to working interfaces where the two former organizations must begin to act jointly.

What should be prepared before developing the program?

Before the script, a coordinated basis is needed: audience map, list of announced changes, decision owners, disclosure boundaries, and update channel. Without this preparation, directing will only beautifully package uncertainty. At Aventura, we ask the client to first gather facts and roles, and then we translate them into the participant's journey, materials, program flows, and question mechanics.

Preparation is sequential:

1. We define audiences. We separately note functions, managers, branches, shifts, remote employees, and groups with different levels of change impact.
2. We build a decision map. For each change, we record the status, affected roles, owner, and location of the next update.
3. We check boundaries. HR, legal, security, and process owners mark what can be said publicly, what requires a separate channel, and what cannot yet be confirmed.
4. We prepare managers. Speakers receive one version of facts, a list of difficult questions, and a rule for responding when confirmed information is absent.
5. We design participation channels. We decide in advance where the microphone, chat, form, small groups, and protected personal inquiries work.
6. We assign recording. For each question, decision, and commitment, there must be an owner, status, and publication location.

GSA in M3 Playbook recommends before large-scale change to identify affected groups, communication purpose, channels, timelines, and feedback mechanism. For the program, this is a practical guideline: one audience and one way of participation is not enough if the merger affects roles and locations differently.

For sensitive consequences, we plan in advance meetings of management with individual teams. The general scenario answers general questions. A local meeting allows discussing a specific process or group without disclosing personal details in front of the entire company.

We publish analyses of business and corporate formats on the Telegram channel of Aventura.

Unified fact base and change map

The unified fact base stores confirmed decisions, unknowns, answer owners, and update history. The change map shows how these decisions affect specific roles, processes, systems, and locations. Together they give participants a foundation for conversation: employees compare working reality with the official version, and the integration team receives a list of discrepancies for verification.

We suggest keeping the fact base in one accessible place and using the same structure for every decision.

Color can aid navigation, but the status must be written in words. W3C recommends not conveying important meaning only visually. Therefore, "approved", "open", and "not changing" must be readable without color, and the on-screen scheme should have a text explanation.

We divide the change map into working layers: decision structure, processes, systems and access, roles, client obligations, locations, dependencies, and open risks. The client confirms the content. Our task is to make it clear, accessible, and suitable for discussion in different program streams.

How to build an integration day program?

The program moves from the general framework to specific work and ends with commitments. First, the leadership names the confirmed decisions and the boundaries of the event. Then participants analyze the change map according to their roles, align cross-functional interfaces, and pass questions to owners. At the end, the team records what will be done next, where answers will appear, and how employees will see the updated version of the materials.

The working framework looks like this:

1. Opening and framework. Leadership explains the reason for the meeting, confirmed decisions, unknowns, and boundaries of public discussion.
2. Fact base. Participants receive one version of key messages and understand where the current version is stored.
3. Change map. Functions see what is changing now, later, not changing yet, or still requires a decision.
4. Working interfaces. Mixed groups compare the routes for transferring tasks, data, and decisions between former organizations.
5. Role streams. Separate teams analyze implications for their work, location, or management level.
6. Questions and validation. The moderator assigns topics to public answers, owner review, and secure channels.
7. Closing. Organizers repeat decisions, owners, channels, and next checkpoints.

This is a sequence of tasks, not a universal minute-by-minute script. Duration, number of streams, and list of speakers depend on the scope of confirmed changes, number of audiences, and participation format. If some information is not ready yet, we reduce the content rather than filling gaps with assumptions.

When the merger includes a new name or visual system, a separate stream can be the internal brand launch. The brand block makes sense only with ready materials and application rules. It does not replace the map of processes, roles, and contacts.

General Session, Working Groups, and Local Meetings

Each format serves its own purpose. The general session provides a unified context, working groups identify gaps between functions, and local meetings address sensitive implications for specific teams. We don't force one format to do everything at once. This separation helps maintain a shared version of the facts while also hearing details that get lost in a large hall.

Mixed groups are assembled based on work dependencies, not randomly. For example, participants can align on a single end-to-end process: who receives the input, in what form the task is handed off, where a decision is required, and what to do until a permanent procedure is approved. The outcome is a route or a question for the owner, not a set of generic wishes.

A complex conversation requires a business program moderator who maintains the boundaries of the blocks, brings the discussion back to observable consequences, and protects the time of different groups. The moderator does not answer on behalf of decision owners and does not turn an uncomfortable question into a neutral wording if that loses its meaning.

Employee Questions, Feedback Sessions, and Answers

Employee questions should be collected in several ways and the route for answers should be explained in advance. Acas describes consultation as a two-way conversation where participants can express their views, and the employer considers suggestions and concerns. For an integration day, this means dedicated time for listening, capturing topics without arguing with personal experience, and a transparent status for each question after the meeting.

Before the feedback session, we name three boundaries: what has already been decided, what employees can still influence, and which topics require a separate channel. Then the facilitator asks questions that provide working material:

• which change currently hinders task completion;
• where the two companies use the same words for different processes;
• which dependency on another function has no owner;
• which risk to the client or business continuity might be invisible to the central team;
• what is useful to preserve from each organization's practices.

After the list, the facilitator repeats the themes heard and explains their further route. CIPD notes that employee voice requires multiple channels and visible actions on feedback. Therefore, an open microphone alone is not enough: we add chat, a form, and the opportunity to reach out after the session.

For questions and answers, a status register is useful:

Microsoft Forms allows disabling name capture in some settings, but this does not prove full anonymity. The content of the question, a small group, the time of submission, or a combination of details can reveal the author. We describe to participants the specific mode: what data is collected, who sees the export, how questions are anonymized, and where personal cases are directed.

How to connect teams in in-person and hybrid formats?

Connections between employees are built around a common work task. We connect people from two former organizations if they need to transfer data, make joint decisions, or maintain a single process. In a hybrid format, this requires a single fact base, a dedicated online moderator, and equal access to questions, materials, and outcomes. A regular broadcast from the room leaves remote participants as observers.

A study indexed by Europe PMC examined communication ties during a specific corporate merger. The authors found a link between increased contacts between employees of the two former organizations and lower subsequent turnover. This observation does not prove the effect of a single technique in the program, but it supports the practical conclusion: it is useful to tie acquaintance to real joint work.

We use several techniques:

• paired review of one end-to-end process;
• a map of dependencies between functions;
• short meetings 'who can I help and from whom do I need a decision';
• mixed working groups with a first follow-up contact;
• a catalog of process owners and experts.

For branches and remote teams, we design the hybrid format as a separate participation route. The online moderator monitors the chat and the question queue. Remarks from the room are repeated into the microphone. Materials are available via a link, and remote participants get the floor in each meaningful block, not in the remaining time.

The hybrid preparation process includes four steps:

1. Check the platform, accesses, subtitles, chat, forms, and backup channel.
2. Conduct a rehearsal with real materials and representatives of different roles.
3. Assign separate facilitators for the room, online, and decision capture.
4. Save questions during a technical failure and give them written status after the event.

Confidentiality, data, and accessibility

Registration, questions, polls, recording, and adaptation requests require a separate data map. We define in advance the purpose of each dataset, access scope, public part, and the rule for review or deletion. NIST and ICO provide useful risk management principles for privacy and data minimization, but they cannot be presented as Russian legal norms. Applicable requirements are confirmed by the client's specialists.

For each dataset, we ask five questions:

1. Why is the information needed for the program or participant?
2. Which fields are necessary for this purpose?
3. Who will see the raw data and the aggregated result?
4. Which details cannot be displayed on the public screen or included in the protocol?
5. When will the owner review the need for storage?

We do not show raw anonymous questions without moderation. Names, unique details, and personal stories are removed from the public version. Medical information, individual HR situations, performance appraisals, and agreement terms remain in the client's protected processes.

Meeting recording also requires a predefined purpose. Before the event, the client determines the legal basis for recording and further use of materials, notifies participants, and obtains consent where required. If the recording is needed for employees who were not present, the client also determines the access scope, the content of published materials, and the retention period according to its own rules and applicable law. Recording "just in case" creates an unnecessary dataset and does not solve the problem of subsequent communication by itself.

Accessibility is built in before the invitation. W3C and Section508.gov recommend providing a way to request adaptation in advance, preparing accessible materials, using microphones, voicing significant visual information, and providing subtitles as needed. We also provide for participation without a personal smartphone, breaks, a quiet place, and a text summary after the event.

What should remain after the integration day?

After the event, what remains are an updated fact base, a register of questions and actions, a map of work connections, and a single address for current materials. These artifacts are more important than a group photo and an emotional finale. The employee should know the next action, the owner of the response, and the location of the next update. Managers receive a list of discrepancies that require resolution outside the program.

We assemble the final package in the following sequence:

1. We consolidate questions, decisions, and identified gaps without unnecessary personal details.
2. We return to the owners the topics that require verification or a confidential response.
3. We update the fact base and note the change history.
4. We publish an accessible summary, open questions, and checkpoints for updates.
5. We check whether the assigned work contacts took place and which dependencies remain unresolved.
6. We start the next meeting with the status of previous commitments: closed, in progress, or cancelled with an explanation.

The result can be evaluated without invented percentages. Suitable indicators are the presence of owners for commitments, a transparent status of issues, the number of corrections in the change map, completed follow-up contacts, and the clarity of the next work route. OPM and CIPD link employees' willingness to provide feedback to visible management actions, so publishing the status is no less important than collecting questions.

If you need to combine a common framework, work streams, hybrid participation, and a materials package into one program, discuss the task with us. We will start with an audience map and confirmed decisions, and then prepare a concept, script, and estimate.

Sources

• GSA M3 Playbook: Define Stakeholders and Develop Communications Plan
• GSA M3 Playbook: Execute Communications Plan
• Acas: Holding a consultation
• CIPD: Employee voice
• Microsoft Support: Set up a survey so names are not recorded
• Europe PMC API: Turnover during a corporate merger
• ICO: Data minimisation
• NIST Privacy Framework
• W3C WAI: Making Events Accessible
• Section508.gov: Create Accessible Meetings
• Microsoft Learn: Hybrid meeting principles
• OPM: 2024 Federal Employee Viewpoint Survey memorandum