The Carve-Out Day 1 Checklist: What 'Ready' Actually Covers

By the MeridianCogent team — drawing on published carve-out and Day 1 readiness frameworks, with our own view on how execution readiness should actually be evidenced and measured.

---

Most carve-out checklists fail in one of two directions. They're either generic enough to apply to any deal, which makes them useless for a specific one, or they're so long — some published templates run past 500 line items — that nobody actually works through them in order, and the list becomes documentation of intent rather than a tool anyone uses.

Day 1 readiness spans far more than cutover day itself. Established industry frameworks, including Deloitte's, consistently spread readiness across functional areas ranging from HR and finance to IT, procurement, real estate, shared services and legal. What follows is our synthesis of that body of work into seven areas particularly relevant to a carve-out, organised by function and by how far out each item needs to start — plus the distinction we think matters more than any individual line item: a completed task is not the same as an unblocked one.

Seven core carve-out readiness areas

Deloitte's Day One readiness guidance spans a broader set of functional areas than any single article can usefully cover. Seven of those are worth examining in detail for a carve-out specifically:

Procurement — contract readiness for separation, and service alignment for continuity. In practice this means every vendor contract has to be classified: inside the new entity's perimeter, migrating to a new agreement, or excluded entirely. Volume-dependent contracts are the trap here — an enterprise agreement priced at the parent's scale is a different, worse deal once the standalone entity is negotiating alone.

HR — organisational design, payroll setup, employee migration, and benefit plan rationalisation. A more detailed HR-specific readiness checklist adds concrete acceptance criteria worth adopting directly: a roster freeze signed off by HR and Finance together, transfer contracts with a real return-rate threshold rather than "sent," employee-representation and consultation processes carrying statutory timelines in relevant jurisdictions identified and tracked early rather than treated as an ordinary project-plan activity, and a payroll parallel run reconciled to a defined variance tolerance before go-live — not just "tested."

Real estate — security and badging deployment for the separating entity, IT access consolidation for what's migrating, and location strategy. Frequently underweighted relative to its actual Day 1 risk: badge access and physical security are binary on Day 1 in a way that most systems work is not.

IT — application and infrastructure integration or rationalisation, cutover planning and asset integration, and user acceptance testing. UAT is particularly vulnerable to compression when timelines tighten, and it's the item most likely to catch whether the other IT work actually functions rather than merely having been completed on schedule.

Finance (including Tax, Treasury and Controllership) — financial close, opening balance sheet, banking strategy and cash management, data retention and audit, financial valuations, and carve-out financials specifically. Worth separating two things that get conflated: carve-out financial reporting and standalone finance readiness are related but different problems. Historical carve-out financial statements can often be derived from the parent's records and cost allocations. Day 1 operational readiness is a separate question — whether the new entity can actually close its books, manage cash, process payables and receivables, retain required data, and produce management information without leaning on processes that are disappearing along with the parent.

Shared services — optimisation of shared services specifically for the separation, which is really a polite name for the stranded-cost problem: services sized for the combined organisation don't shrink just because part of the organisation left.

Legal — entity structuring, licence and permit transfer, and the consent and novation work covered in its own right elsewhere in this library.

One practical way to sequence the work

Exact timing varies by deal, jurisdiction and transaction perimeter — there's no universal T-minus schedule that fits every carve-out. But the latest sensible point at which each category of work should already be underway follows a consistent pattern:

Well before close — entity structuring and permit work, procurement contract classification, the TSA scoping that depends on knowing what's actually shared, and carve-out financial statement preparation. These take months, not weeks, and starting them at signing rather than at the decision-to-sell stage is a recurring, avoidable source of compressed timelines later.

In the final months before close — payroll and HRIS cutover testing, IT infrastructure cutover planning, banking and cash management setup, and any employee-representation or consultation processes that carry statutory timelines in the relevant jurisdictions.

In the final weeks — UAT, badge and facility access deployment, manager toolkits and communications materials, and the payroll parallel run.

At Day 1 itself — cutover execution, and the shift from planning mode to the first live day of operating independently.

Start with whichever activities have externally constrained lead times — entity formation, regulatory approvals, permits, employee consultation, and third-party consents often contain waiting periods that additional project resource cannot simply compress. Identify those constraints first; everything else is easier to accelerate if it turns out to be running late.

A working checklist

Not five hundred rows. A reasonable starting set of readiness gates, each needing an owner and real evidence rather than a checkbox:

This is our own synthesis of the categories above into a working list, not a reproduction of any single source's proprietary checklist.

Why "complete" and "ready" are different questions

Every item above can be checked off as "done" by the team that owns it, and Day 1 can still fail, if the thing that item was supposed to unblock for someone else hasn't actually been unblocked. Payroll parallel run reconciled is a real, checkable fact. Whether that reconciliation used final employee master data, or provisional data because the HRIS cutover hadn't actually finished yet, is a different fact — and it's the one that determines whether the first real payroll run works.

We think about this as four separate questions, not one:

Is it complete? Has the task itself been performed.

Is it evidenced? Can someone actually demonstrate that it works, rather than asserting that it does.

Is it unblocked? Are the things it depends on genuinely available, not just scheduled to be.

Has it unblocked downstream work? Has whoever needs what this produced confirmed it has actually landed.

Most checklists only ever get built to answer the first question, because it's the easiest one — a task is either done or it isn't. The other three require knowing what depends on what across functional lines, which is exactly the kind of visibility a flat checklist, however long, doesn't provide on its own.

What the delay actually costs

Two figures worth having in view while working through a list like this.

PwC's own analysis of successful carve-outs found that exiting TSAs early is associated with roughly a year of additional business value capture, contributing an estimated 5 to 7 percent value uplift as part of a broader combination of factors PwC has observed driving 8 to 11 percent uplift overall. Every checklist item completed before the TSA clock starts running is time not rented from the seller afterward.

Separately, BCG's analysis of separation cost data across more than fifty divestitures found one-time separation costs typically ranging from 1 to 5 percent of the divested business's revenue, with complex or large carve-outs reaching or exceeding 10 percent. Because the effort involved in separating a business is often similar in absolute terms regardless of deal size, smaller divestitures tend to land at the higher end of that percentage range — a smaller business absorbs roughly the same separation cost as a larger one, against a smaller revenue base. That scale makes separation readiness economically material, not a program-management nicety.

Lessons learned

Identify the externally constrained items first. Entity formation, regulatory approvals, permits, and statutory consultation periods may contain waiting periods that no amount of additional resource compresses. Everything else has more flexibility; these set the actual floor on your timeline.

A checklist tells you what's done. It doesn't tell you what's actually unblocked. Track both, or the list will show green while a downstream dependency is still waiting on data that technically exists but hasn't landed where it's needed.

Carve-out financial reporting and standalone finance readiness are different problems. One is about constructing historical statements from parent records. The other is about whether the new entity can actually run finance operations independently. Assuming the first solves the second catches finance teams out.

The stranded-cost line item is really a separate workstream wearing a checklist item's clothes. "Shared services optimisation" on a Day 1 list undersells how much ongoing work sits behind it — worth reading in full elsewhere in this library rather than treating as one row among many.

---

Sources: Deloitte, "Day One Readiness: Enabling Business Continuity Through Effective Operational Readiness" (functional category framework); Umbrex, "Checklist: HR-Related Actions for Day 1 Readiness" (HR acceptance-criteria detail); PwC, "How expediting transition service agreement exits can unlock deal value" (TSA exit value uplift analysis); BCG, "The 2021 M&A Report: Mastering the Art of Breaking Up" and "6 Technology Due Diligence Imperatives in Carve-outs" (separation cost analysis across 50+ divestitures).