Mergers and acquisitions: communications before, during and after the announcement
Communication about a merger and acquisition begins before the press release and continues after the announcement. It must explain the logic of the operation, protect the reliability of the information and give each audience a useful response, without anticipating the decisions which remain open.
Before: building information governance
Form a tight preparation group bringing together the functions concerned: management, transaction, legal, human resources and communication. Define who confirms the facts, who validates the formulations and who authorizes their dissemination. Confidentiality must be arranged, not assumed.
Distinguish the stages of the operation: discussions, signature, possible authorizations, implementation and integration. These steps are not interchangeable. The public calendar must be validated with regard to applicable obligations, particularly in terms of financial information and social dialogue. A project communication must not present an operation that is still conditional as acquired.
Prepare several readings of the same project
The central story explains why the operation is planned, what it allows and the elements that support it. It serves as a basis for different responses depending on the audience. Employees ask what is changing in their work; customers are interested in continuity of service; investors examine strategic coherence and risks.
Consistency does not mean that everyone receives exactly the same text. It requires that no version contradicts the facts or the commitments of others.
- Employees: decisions taken, open topics, contacts and next information point.
- Customers and partners: continuity, contracts, contacts and handling of questions.
- Media: logic of the operation, stages and competent spokespersons.
- Investors: assumptions, risks and information validated within the applicable framework.
Predict leakage and lag scenarios
Prepare a response to premature information, delay or misinterpretation. The document must specify the level of confirmation possible, the people to contact and the authorized channels. A helpful hold message acknowledges the question and indicates what can be confirmed, without fueling a rumor with unverified details.
Teams from both organizations must be familiar with the climbing circuit. It is also necessary to anticipate differences in languages and time zones: a rushed translation can transform an intention into a commitment or a condition into certainty.
During: synchronize without standardizing
On the day of the announcement, use a dated reference version, an FAQ and a contact list. The broadcast schedule takes into account local obligations and the validated schedule. Managers must be able to explain what is known and convey questions they cannot yet answer.
Watch for factual errors and recurring misunderstandings. Correcting a date or a scope is more useful than multiplying enthusiastic messages. A team should be responsible for keeping the FAQ up to date, with a clearly identified manager and validation time.
After: make the integration observable
The announcement does not resolve questions of organization, culture or operation. Prepare a pace of information adapted to real decisions: governance, tools, contacts, identity and modes of cooperation. Integration promises must be followed, including when the schedule changes.
A dashboard can bring together team questions, customer misunderstandings, coverage errors and commitments that remain to be clarified. It should not turn any concern into resistance to change: certain questions reveal an operational gap that needs to be corrected.
Illustrative example and deliverables
Two companies announce a merger before its completion. They prepare a common story, but distinct responses for the teams in each organization. Undecided topics are explicitly listed in the FAQ with the next planned milestone. This example does not describe a transaction accompanied by Belief System.
The useful deliverables are a decision brief, an audience matrix, a distribution schedule, an FAQ, messages from managers and a monitoring system. Success depends on the reliability of the information and the continuity of the relationship, not just the coverage on the day of the announcement.
Frequently asked questions
When to start preparing the communication of an acquisition?
As soon as the project requires structuring the information, in a group adapted to the level of confidentiality. The distribution then follows the schedule validated by the competent functions.
Should we announce the same thing to the teams of both companies?
Facts and commitments must be consistent. Explanations may differ to respond to the concrete consequences specific to each organization.
Our accompaniments
Sources and benchmarks
- OECD — Principles of Corporate Governance (2023) [1]
Let's talk about your issue
↗India–France–Europe: make financial technology accountability explicit
Indian technology companies serving European financial institutions should distinguish supplier and regulated-customer responsibilities. Document the legal entities, service locations, subcontracting dependencies and incident contacts before announcing the relationship. ESMA’s DORA guidance distinguishes ICT providers designated as critical from suppliers generally; working for a bank alone does not establish that designation. Communications should accurately reflect the supplier’s status and the commitments contained in the actual contract. Customers need delivery evidence, distinguishing tested or independently assessed arrangements.
Illustrative scenario: an Indian software company supports a French financial institution’s customer portal. The announcement identifies the service delivered and avoids suggesting that the supplier holds the bank’s authorisations. Prepare consistent answers about escalation, continuity and support across the Indian delivery centre and French account team. During an interruption, distinguish known customer effects from unresolved technical questions and use an agreed update schedule. Afterward, track corrective actions with named owners. A credible resilience account rests on these operating arrangements; a broad promise of uninterrupted service would go beyond what the evidence can support.
This edition retains the French and European context of the analysis. The market note addresses its use by Indian headquarters and their French or European teams.
Local edition ·
Read the French source