Post-Closing Integration: A Plan, or a Tracker?
Liam explains why a one-time integration plan written the day an M&A deal closes cannot catch workstreams that quietly stall, and why a phased tracker with task, owner, phase, and status fields does.
The instinct on the day an M&A deal closes is to write an integration plan, a single document laying out everything that has to happen next. Liam walks through why that instinct is only half right, and why the thing that actually closes the gap after closing day is a living, phased tracker rather than a static plan.
Why a plan alone falls short
A plan captures one moment in time. The day after closing, several workstreams start moving in parallel at once, IT systems, HR and benefits, finance consolidation, vendor contracts, and a document written on day one has no way to tell you six weeks later which of those workstreams are on schedule and which have quietly stalled. The plan only lists what was named at the moment it was written; it can't track what happens after.
The four fields that make a tracker work
What closes that gap is a tracker built around four fields applied to every workstream: the task itself, the owner responsible for it, the target phase, whether that's day-one, day-thirty, or day-one-hundred, and today's status. Every workstream goes through the same four fields, which is what makes gaps visible instead of assumed away.
The anchor example
Consider a vendor-contract workstream marked for day-thirty on the org chart, with no owner ever formally assigned to it. Run through the same four fields as everything else, and that gap becomes visible immediately, since "owner" comes up blank. A one-time plan written on closing day would never have caught that, because nothing about the org chart itself flags a missing owner. The tracker does, simply by forcing every workstream through the same structure.
Tracked is not the same as cleared
Being tracked doesn't mean a workstream is actually on schedule. A status field is a snapshot at a point in time, not a guarantee that everything is fine. The reverse is also true: a fully staffed tracker on day one doesn't mean nothing else will surface later. New workstreams turn up as an integration proceeds, and the tracker's job is to keep catching them as they appear, not to lock in a complete picture at the start.
Applying it
The practical version of this is straightforward: list the workstreams for a post-closing integration, IT systems, HR and benefits, finance consolidation, vendor contracts, and for each one assign an owner and a target phase, then mark today's status. Any workstream that comes up blank on owner is exactly the kind of gap a one-time plan would never have surfaced.
Key takeaways
- A static integration plan written on closing day captures only what was known at that moment and can't show which workstreams later stall.
- A phased tracker applies four fields, task, owner, target phase, and status, uniformly across every workstream.
- A vendor-contract workstream with a phase assigned but no owner is a concrete example of a gap the tracker catches automatically.
- Being tracked is not the same as being on schedule; status is a snapshot, not a guarantee.
- New workstreams surface as integration proceeds, so the tracker needs to keep working past day one, not just at the start.
Who this is for
This is for anyone responsible for post-merger or post-acquisition integration who wants a concrete, repeatable structure for tracking parallel workstreams, rather than a single document that goes stale the day after it's written.
Chapters
Full transcript(auto-generated, with timestamps)
Do we need a plan for after the deal closes?
[0:00]Someone whose deal just closed asks if they need a master integration plan. Wrong first word. What they actually need is a tracker of phased work plan. Lay them take them through it. You could
A plan only lists what's named
[0:10]Write an integration plan the day the deal closes a single document listing what has to happen, but a plan captures one moment. The day after closing work streams start moving in parallel IT, HR, finance, contracts and a static document can't tell you which ones are on schedule and which have quietly stalled. What actually closes that gap isn't a plan, it's a live tracker. Four things
Four fields — the anchor
[0:30]Go in for every work stream on that tracker. The task, the owner, the target phase day one, day 30, day 100 and today's status. Watch the anchor. The vendor contract work stream marked day 30 on the org chart with no owner ever assigned to it. That work stream gets the same four fields as everything else owner assigned, phase set, status tracked and
Tracked, not cleared
[0:50]Now it's visible instead of silently late. But in progress doesn't mean on schedule. Status is a snapshot, not a guarantee and a fully staffed tracker on day one doesn't mean nothing else surfaces new work streams turn up as integration proceeds. You can't manage an integration you're not tracking. Build the phase tracker, not a single plan. The plan only holds for day one. Your turn. Here's the prompt, read it with me. List the work streams for a hypothetical post closing integration IT
Carry-out
[1:16]Systems, HR and benefits, finance consolidation, vendor contracts. For each one assign an owner and a target phase day one, day 30 or day 100. Mark
Your turn
[1:25]Today's status. If any work stream has no owner, that's the gap the tracker just found. Lay them in for bare. Post closing integration, a plan or a tracker? Lay them in for bare.
