Day 1 is the day on which the deal legally becomes a fact and the organization must function as one whole for the first time, or at least must not grind to a halt. That is a different question than the synergy baseline or the Day 100 plan. Day 1 is not about creating value, but about preventing value from leaking away because of something simple that was not arranged: an invoice that cannot be paid, an employee who no longer has access, a customer whom no one has informed.
The temptation exists to fill Day 1 with ambition: the first steps toward synergy, the first organizational change, the first joint initiative. That belongs in the Day 100 plan, not in Day 1. Day 1 is about continuity. The question is not what can be improved, but what breaks if nothing happens. Whoever mixes these two lists risks that on the first day energy goes into things that can wait, while something that cannot wait is left undone.
There is a limited number of domains where Day 1 problems concentrate, and they are roughly the same for every deal, even though the content differs per situation.
Contracts with suppliers, customers and financiers often contain provisions that a change of control affects. Which ones these are and what they require differs per contract, and that is exactly what which contracts require Day 1 attention addresses.
Payments continue, independent of the legal structure. Salaries, invoices, collections: if the underlying bank structure or approval chain has not been tested through, the risk arises that on Day 1 something is due that no one can execute. What is often underestimated in this regard is described in what happens to payments on Day 1.
Access to systems, buildings and accounts must be correct on the day itself, not a week later. This is a domain where the damage is often not financial but operational: people who cannot work, customer data that is unreachable, an IT department that has to reactively solve what could have been figured out in advance. Which access this concretely concerns differs per organization and is worked out in which access must be right on Day 1.
Communication to employees, customers and sometimes the market is a separate domain, with its own timeline and its own risk: saying too early what is not yet certain, or staying silent too long about something that is already leaking. What is told that day and to whom is explained in what you communicate on Day 1.
Decision rights is the domain that is most easily skipped because it does not seem like a concrete action, but without an explicit answer to who may decide on Day 1 about expenditures, personnel and customer contact, delay arises at the moment when speed is most needed. That question is addressed in who decides what on Day 1.
Legal form steps, such as formally putting board changes into effect or adjusting powers of attorney, often have a statutory deadline that does not coincide with the date the deal teams themselves use. Which steps these are is worked out in which legal form steps are required on Day 1.
Here too the question applies that belongs with every part of an integration: does this really need to be combined, and does it need to happen by Day 1. Not every contract requires immediate action, not every system needs to be linked that very day, and not every department is in a hurry. A Day 1 list that contains everything that ever needs to be arranged is no longer a Day 1 list, but a disguised integration plan with the wrong label. The distinction between what must be on the Day 1 list and what can wait until Day 100 or later is itself a decision that must be recorded, not something self-evident.
The Day 1 generator from mergerintegration.net structures these domains into a list that fits the specific deal: which contracts, which systems, which communication moments, which decisions. The integration office keeps track of what has been completed per point, which dependencies exist between the points, and which choices have been deliberately made not to do something. It is a tool that delivers structure and asks questions about what should and should not happen; it is not a track record and no guarantee that an integration runs smoothly.
The tool is under construction. Anyone who wants to use it as soon as it becomes available can sign up for the waiting list.
A Day 1 list consists of tasks: reading through contracts, testing payments, checking access, formulating messages, recording decisions. Some of those tasks are largely human work, others largely consist of searching and structuring information that is already available. Which part of that work can be accelerated with AI, and which part cannot, differs per task. The work scan from FTE TO AI calculates that per task, so that it becomes clear where time can be gained and where it cannot.
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.