What Day One is, and is not
Day One is legal completion: the moment ownership transfers and the two companies become one in law. It is not the day integration finishes, and it should not be the day anything irreversible happens to systems, brands or org charts. The standard to hold it to is deliberately modest and completely unforgiving: every employee is paid on time, can log in, knows who they report to, and knows what to say to a customer. Every customer hears the right story before the market does. Nothing breaks.
That modest standard fails more often than it should, because it depends on a dozen small workstreams converging on a single date with no slack.
The checklist, workstream by workstream
People and payroll. The single highest-stakes line on the list. Confirm the payroll cutover date against Day One, run a parallel pay cycle if the dates are close, and confirm benefits continuity in writing. Prepare a manager pack: the announcement, a Q&A, and clear guidance on the questions managers cannot answer yet and how to say so honestly.
IT and access. Email continuity, single sign-on or a documented interim, laptop and account provisioning for anyone changing entity, and security monitoring across the joined estate. The rule that prevents most Day One IT incidents: no forced migrations on Day One itself. Access first, change later.
Legal and regulatory. Change-of-control notices on key contracts, licences and permits that reference ownership, insurance continuity, and the regulatory notifications the deal terms require. Most of this is preparable weeks ahead; it fails when nobody owns the list.
Customers and commercial. A named-account call plan for the top relationships, executed on the day by the people who own those relationships, with a consistent one-line answer on pricing and contracts (usually: nothing changes today). Sales teams on both sides need the same script; the first week after an announcement is when competitors call your customers.
Suppliers, banking and finance. Bank signatories, payment approvals and purchase-order authority under the new structure, so the business can keep spending money legally on day two. Confirm the first combined month-end close is planned, even though it is weeks away.
Facilities and brand. Signage, badges, and what the reception desk says when they answer the phone. Deferring the brand decision is fine; failing to tell anyone it has been deferred is not.
Communications. The sequence matters more than the copy: employees of the acquired company first, then the acquirer's employees, then customers, then the market, ordered across timezones so nobody in one region reads the press release before their own manager has spoken. Write down who says what, when, in which channel, and rehearse the first two hours.
The go or no-go mechanism
A checklist without a review is a wish list.
The mechanism that works is two formal readiness reviews: one at roughly T-14 days, one at T-2. Every line has a named owner and a RAG status, and the T-14 review exists precisely to find the reds while there is still time to fix them. At T-2 the question changes from “how is it going” to “are we go”, and anything still red needs either a fix, an accepted workaround, or in extremis a conversation about the completion date. The review is chaired by the integration lead, not delegated, because the authority to say no-go has to sit in the room.
The failures that recur
Across deals, the same four problems account for most Day One incidents: a payroll cutover nobody stress-tested, laptops and multi-factor authentication not provisioned for transferred staff, managers ambushed by questions with no pack, and announcement timing that leaked sideways across timezones. None of them is difficult. All of them are omissions, which is the argument for the checklist being boringly exhaustive rather than elegant.
After the day
Whatever went wrong, and something will, goes into the issues log with an owner rather than into folklore, and the first week's issues feed the Day 30 review. Day One competence buys the integration team credibility; how the first week's problems are handled decides whether they keep it.
The templates that implement this
The toolkit's 100-Day Integration Plan, Day 1 Readiness Checklist, Risk Log and Board Dashboard follow the structure described here, pre-populated with a worked example. One-time purchase from £199.
See what is inside ›Related guides: building the 100-day plan and running the IMO.