M&A communications: before, during and after the announcement
M&A communications begin before the press release and continue after the announcement. They should explain the rationale, protect the reliability of information and answer each audience’s practical questions without presenting unresolved issues as decisions.
Before: establish information governance
Set up a tight preparation group combining the functions involved: direction, transaction, legal, human resources and communication. Define who confirms the facts, validates the formulations and authorizes their dissemination. Confidentiality must be organized, 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 respect to the applicable obligations, particularly in relation to financial reporting and social dialogue. A project communication must not present as acquired a transaction still conditional.
One project, different audiences
The central narrative explains why the transaction is being considered, what it allows and the elements that support it. It serves as a basis for different responses depending on the audience. Employees ask what changes in their work; customers are interested in continuity of service; investors look at strategic coherence and risks.
Consistency does not mean that all receive exactly the same text. It requires that no version contradicts the facts or commitments of others.
- Employees: decisions taken, open subjects, interlocutors and next point of information.
- Clients and partners: continuity, contracts, contacts and handling of issues.
- Media: the logic of the operation, relevant steps and spokespersons.
- Investors: assumptions, risks and information validated in the applicable framework.
Prepare for leaks and delays
Prepare a response to premature information, delay or misinterpretation. The document must specify the level of confirmation possible, the persons to be reached and the channels allowed. A useful wait message recognizes the question and indicates what can be confirmed, without feeding a rumor with unvalidated details.
Teams in both organizations need to know the climbing circuit. It is also necessary to anticipate differences in languages and time zones: a hasty translation can turn an intention into commitment or a condition into certainty.
During: coordinate the announcement
On the day of the announcement, use a date reference version of the facts, a FAQ and a contact list. The release takes into account local obligations and validated calendar. Managers must be able to explain what is known and pass on the questions they cannot answer yet.
Watch for factual errors and recurring misunderstandings. Correcting a date or perimeter is more useful than multiplying enthusiastic messages. A team must be responsible for keeping the FAQ up to date, with a clearly identified official and validation time.
After: make integration progress visible
The announcement does not solve organizational, cultural or operational issues. Prepare a pace of information adapted to real decisions: governance, tools, interlocutors, identity and modes of cooperation. Promises of integration must be followed, including when the timetable changes.
A dashboard can bring together team questions, client misunderstandings, coverage errors and commitments that remain to be clarified. It must not turn any concerns into resistance to change: some issues reveal an operational gap to be corrected.
An illustrative scenario and useful deliverables
Two companies announce a rapprochement before its realization. They prepare a common narrative, but separate responses for the teams of each organization. Undecided topics are explicitly included 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 note, an audience matrix, a broadcast schedule, a FAQ, managers' messages and a follow-up process. Success is due to the reliability of the information and the continuity of the relationship, not just the coverage of the day of the announcement.
Frequently asked questions
When to start preparing communication of an acquisition?
As soon as the project requires structure of the information, in a group adapted to the level of confidentiality. The distribution then follows the calendar validated by the relevant functions.
Should we announce the same to the teams of both companies?
The facts and commitments must be consistent, and explanations may differ to respond to the specific concrete consequences of each organization.