On the day the deal closes, everyone working at either organization wants to know the same thing: does anything change for me, and if so, when. That is the core of Day 1 communication. Not the strategic rationale for the deal, not the synergy plans for the coming years. Only what is actually different that day and that week.
The groups who hear something on Day 1 are not interchangeable in what they need. Employees want to know whether their contract, their manager, or their work location is changing. Customers want to know whether their point of contact, their contract, or their invoicing stays the same. Suppliers want to know who they now deliver to and who they invoice. Regulators and permit-issuing authorities want to know whether a notification or transfer is underway. Each group needs a different message, at a different moment, through a different channel. Whoever lumps this together into one general announcement fully answers no one's questions. The question of who decides what on Day 1 is directly related to this: before anything is communicated, it must be established who has the authority to decide exactly what is said and when.
The content of Day 1 communication falls into a limited number of categories, and these are to be filled in per situation, not invented.
The legal facts: which entity is the owner, what legal form is the contracting party, and does that change for the recipient of the message. This connects to the legal form steps that must be taken on Day 1 — if those have not yet been completed, that is not something to conceal or exaggerate in the communication, but to report exactly as it is.
The operational facts: does the point of contact stay the same, does the invoicing address change, does the support phone number change. In an acquisition with a cross-border component, an additional layer comes into play that does not apply without an international dimension: what needs to be arranged on Day 1 in a cross-border acquisition directly affects what you can say that day. Without that in order, any statement about invoicing, delivery, or services abroad is a guess.
The contractual facts: do existing agreements continue, is there a change-of-control clause requiring notification, does a customer or supplier need to sign something. This is exactly why the contracts that require Day 1 attention in a cross-border acquisition must be mapped out first: communicating that nothing changes, while a contract contains a notification obligation that has not been fulfilled, is a promise that won't hold.
The financial facts: does the payment instruction stay the same, does the account number change, is there a transition period in which old and new details coexist. This is connected to what happens to payments in a cross-border acquisition: a message to customers about invoicing can only be sent once it is established what actually happens, not what is intended.
The accessibility facts: can everyone still log in, does email work, is the building accessible. This relates to which access rights need to be correct on Day 1 in a cross-border acquisition — a message stating that systems keep working can only responsibly be sent once that has actually been verified, not assumed.
Day 1 communication is not the place for synergy targets, reorganization plans, or future scenarios. As soon as these creep in, the message shifts from factual reassurance to speculation, and that raises more questions than it answers. What changes on day one hundred is a different message with a different occasion — the two should not run into each other.
Not every part of the organization deserves the same speed or the same level of detail in communication. Some teams, customers, or systems remain so untouched that an extensive message creates more unease than it removes. The question of whether something should be communicated because it can be, or only because it needs to be, is to be asked afresh for each part — here too, combining or announcing is not automatic, but a choice made anew case by case.
The generators for the synergy baseline, the Day 1 plan, and the Day 100 plan, together with the integration office for benefit tracking and the decision list of what to integrate and what not to, are still under construction. Anyone who wants to use these once available can sign up for the waiting list.
Drafting Day 1 messages for every target audience, in every language and for every region, is exactly the kind of repeatable, checklist-like work where the question is how much a team still needs to do itself. FTE TO AI's work scan calculates, per task, what portion of it can be taken over by AI, making it clear where human time genuinely remains necessary and where it does not.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.