Meaning and transaction use
PwC describes Day-one readiness as pre-close integration planning that identifies priorities, allocates responsibilities and prepares teams for operational integration from the first day. [S1]
PwC's integration approach connects due-diligence findings to governance, operating-model, finance, systems, people and execution plans extending through the first 100 days. [S2]
Day-one scope should reflect the transaction perimeter, regulatory restrictions before close, transition-service agreements, separation dependencies and the target operating model.
Worked example
Illustrative readiness dashboard only. Assume 120 critical actions across eight workstreams. Ninety-six are complete with evidence, 18 have approved and tested fallback plans, and six remain open. Thirty actions are classed as highest criticality, with four unresolved. Owners are assigned to 118 actions and 28 of 30 required communications are approved.
Scroll the table horizontally to view all columns.
| Measure | Calculation | Result |
|---|---|---|
| Completed-action rate | 96 / 120 | 80.0% |
| Fallback-ready rate | 18 / 120 | 15.0% |
| Illustrative operational coverage | (96 + 18) / 120 | 95.0% |
| Open-action rate | 6 / 120 | 5.0% |
| Unresolved highest-criticality rate | 4 / 30 | 13.3% |
| Owner coverage | 118 / 120 | 98.3% |
| Approved-communication rate | 28 / 30 | 93.3% |
The illustrative dashboard shows 95.0% operational coverage, while four highest-criticality actions and two owner gaps remain unresolved. The deal team should assess each gap and fallback before treating the business as ready for legal close.
Proposed transaction review process
Define the Day-one perimeter
Translate the deal structure, diligence findings, regulatory conditions, operating model and separation needs into critical outcomes.
Mobilise governance
Set the integration management office, workstreams, decision rights, owners, cadence, evidence standards and escalation routes.
Build and test plans
Prepare cutover, access, controls, communications, treasury, people, customer, supplier, technology and continuity actions with fallbacks.
Approve and execute
Run readiness reviews, close critical gaps, confirm legal-close timing, execute the cutover and monitor stabilisation through the transition period.
Evidence checklist
Transaction perimeter
Closing conditions, legal entities, assets, employees, contracts, regulatory approvals and separation requirements.
Operating readiness
Process maps, systems, access, data, treasury, controls, facilities, licences and business-continuity tests.
Stakeholder readiness
Employee, customer, supplier, lender, regulator and market communications with approvals and timing.
Governance and cutover
Owners, decisions, dependencies, issue log, fallback plans, command centre, escalation and acceptance evidence.
Decision framework
| Situation | Proposed action |
|---|---|
| A critical system will not be ready | Activate an approved fallback or transition service with capacity, access, controls and exit timing. |
| A closing condition changes the timetable | Rebaseline dependent actions and communications before confirming the cutover date. |
| An action lacks an accountable owner | Assign authority and due date or escalate the gap as a readiness blocker. |
| Pre-close coordination is legally restricted | Apply clean-team and legal protocols and defer prohibited integration activity until authorised. |
Common errors to check
- Treating checklist completion as proof that critical operations can run.
- Planning only the first day without stabilisation, Day-100 and transition-service exit dependencies.
- Leaving customers, employees, suppliers or regulators without approved communications.
- Starting prohibited integration activity before legal close or required approval.
Close the Day-one readiness gaps
Bring the transaction perimeter, integration plan, transition services, critical-action register, communications and cutover evidence to a Day-one review. Confirm ownership, fallbacks and escalation for every outcome required at legal close.
Discuss the transactionPrimary references and editorial scope
- PwC, M&A Mergers and Acquisitions
Day-one readiness, integration priorities, responsibilities and pre-close planning. Reference checked 17 September 2026. - PwC, Integrations
Integration management, pre-close planning, operating model and first-100-day execution. Reference checked 17 September 2026.
General post-merger-integration education. Counts are hypothetical. Day-one requirements depend on the transaction perimeter, jurisdictions, regulatory approvals, employment rules, contracts, data restrictions and integration or separation model.
General business information. Obtain advice appropriate to the legal, tax, accounting and financing facts. No offer, lender commitment or transaction outcome is represented. All worked examples use expressly assumed figures. Editorial draft date: 17 September 2026.
