Careless teams collapse two different dates into one, and nothing else about the first day matters as much. Legal Day 1 is the moment the transaction actually closes. Signing and closing conditions are satisfied, regulatory clearances are obtained (or a hold-separate order governs what can't combine yet), and change of control takes effect. Operational Day 1 is what actually, visibly changes for employees, customers and systems on the ground. In any deal of real size it's deliberately not the same day as legal close, because payroll systems, IT environments, customer contracts and regulatory licenses can't all be re-plumbed at once. Interim arrangements bridge the gap. Most often that's a Transition Services Agreement, covered on its own page. In antitrust-sensitive deals there's also a formal hold-separate order that legally forbids combining certain functions (sales forces, pricing, product roadmaps) until a regulator signs off. Break it and you've committed a "gun-jumping" violation.
Advertisement
What does a Day 1 readiness checklist cover?
A usable Day-1 readiness checklist runs across four axes, and every item on it belongs to one of them. The legal and regulatory axis checks that the entity structure is effective, that licenses and permits are transferred or under interim cover, and that antitrust clearance is obtained. If it isn't, a hold-separate order should be in force, and both leadership teams should understand it. The people axis checks that the announcement and town-hall communication have happened, and that retention agreements cover the people you can't afford to lose in the first ninety days. It also checks that the go-forward org structure is named, even if it isn't fully staffed yet.
Customer and supplier continuity means key contracts are novated or otherwise legally unaffected, and supplier payment terms carry on uninterrupted. It also means a customer communication plan has gone out, so nobody hears about the deal from a news alert before hearing it from you. Systems and finance covers payroll, which must run continuously with no missed or duplicated pay cycle. It covers financial reporting too. That has to be integrated or bridged so the combined entity can close its books. The axis also needs a cybersecurity and access-control plan for the new entity's systems.
None of this is optional ceremony.
A missed payroll cycle or an un-novated customer contract on Day 1 is the kind of failure that turns a well-modeled deal into a public embarrassment inside the first week. You can avoid it entirely with a checklist built and rehearsed before close. Improvising one afterward is how the failure happens.
What is an integration management office?
Governance has to exist before Day 1. It can't spring up afterward. Stand up an Integration Management Office (IMO), a small cross-functional team with named workstream leads for systems, people/culture, customer and finance, plus a synergy-tracking lead. Give it a fixed steering cadence and a single shared synergy tracker that everyone reports into. Ideally that tracker is signed off in diligence. It should definitely be operating by the moment the deal closes. The mechanics of actually running the steering cadence come later in the transformation and program-governance work: agenda design, pre-wiring so nobody's surprised in the room, facilitating to a decision, minutes and actions. What you need here is the content those mechanics serve, which is what the PMI steering committee should be governing and tracking.
The 100-day plan and the discipline of tracking synergy capture honestly
A hundred days is a recognizable horizon that creates urgency. There's nothing magic about the number, and it's worth saying so plainly. A team that treats "Day 100" as a hard deadline for everything will rush structural changes that deserved more care, and it'll declare victory early on work that's only just beginning.
A usable plan sequences three categories of work, so you're not trying to do everything at once. Quick wins are low-risk, fast, often symbolic moves (vendor-contract consolidation, decommissioning an obviously duplicate tool, a joint town hall). They build momentum and credibility while the harder work is being planned. Structural moves are the higher-risk, higher-value changes (org design, systems migration, facility consolidation), and they take real time and real governance. People and culture means keeping the specific individuals the deal's thesis depends on. It also means a communication rhythm that doesn't go silent between the announcement and the first real milestone, because silence is when rumor and attrition set in.
How do you track synergy capture?
A synergy case becomes real only if you keep a tracker at the initiative level. An aggregate number won't do. For each initiative separately (procurement consolidation, facility closure, cross-sell enablement and so on), the tracker reports a baseline, a run-rate target and its phasing, and actuals. The phasing matters because most synergy programs ramp on an S-curve. A straight line is the wrong shape, and the phasing point from the synergy case now gets run month by month.
Why go to this trouble? Bookkeeping tidiness has nothing to do with it.
When the blended actual comes in below plan, the only useful next question is which initiatives are behind because of timing and which because of true leakage. A timing miss is real work that will land, just later than modeled, like a lease-break clause that takes longer to negotiate than expected. Leakage means the initiative isn't going to happen as modeled. Think of a cross-sell push that collapses because of channel conflict between the two sales forces, with named accounts that actually churned. Blend those two causes into a single aggregate number and you get the wrong management response either way. You panic over what's merely delayed. Or you grow complacent and paper over synergies that are never coming. Worked Example 5 diagnoses this kind of shortfall, initiative by initiative, and shows the right response to each cause.
What are dis-synergies and how do you monitor them?
Then there are dis-synergies, the mirror-image risk you met at the modeling stage: customer attrition from overlapping accounts, culture clash slowing decisions, management distraction from the base business. Once the deal closes, they stop being a one-time modeling adjustment. The 100-day plan has to actively monitor for them (named at-risk accounts, employee-sentiment pulses, a watchlist of key people) and have a response ready. A dis-synergy that shows up unmonitored in month four looks, to an outside observer, like ordinary post-merger friction. It keeps looking that way until it's already cost you the account or the engineer.
{
"skill": "Drafting a first-pass 100-day plan, TSA service schedule, or synergy tracker template before an Integration Management Office exists to build one from scratch",
"use": "Use AI to generate a structured starting scaffold — a workstream list, a draft Day-1 checklist across the four axes, a TSA service schedule template, or a synergy-tracker spreadsheet skeleton with baseline/target/actual/variance columns by initiative — that a real IMO then edits, staffs, and defends, never a plan that ships unedited.",
"tools": ["Chat assistants — Claude, ChatGPT, Gemini, for structured drafts", "Spreadsheet/code tools — for building the actual synergy-tracker template with real formulas"],
"prompt": "Draft a 100-day PMI plan skeleton for <DEAL TYPE/INDUSTRY>, organized into quick-wins / structural-moves / people-culture workstreams, with a Day-1 checklist split into legal, people, customer, and systems items, and a synergy-tracker table template with columns for initiative, baseline, month-by-month target (phased, not linear), actual, and a timing-vs-leakage variance note. Do not invent specific dollar or rupee figures for our deal — leave those as placeholders.",
"verify": "Every placeholder figure in the draft must be replaced with your own diligence-sourced or internally modeled number before the plan is used — never let an AI's illustrative filler number survive into a real tracker. Recompute every total; date-check that any 'standard PMI timeline' the tool asserts matches your deal's actual regulatory and systems constraints (Guardrail 1-5).",
"diy": "You must already know what a synergy tracker needs to separate (timing vs. leakage), what a Day-1 checklist must cover, and why the archetype decision precedes the plan — everything this section teaches — before you can tell a good AI-drafted scaffold from a generic, unusable one.",
"market": "IN"
}