A regional health insurer acquires a 420,000-member plan carved out of its parent company, and has eighteen months of transitional services to become independent of the seller. This suite is the full program record: 72 documents covering governance, planning, execution, control and closeout — written as point-in-time artifacts, each true only as of its own date.
The program does not go smoothly, and that is the point. Antitrust law bars an acquirer from examining member-level records before closing, so the estimate for resolving two member databases into one was made blind — and six months after close the first lawful measurement returned a manual review population three times the model. The risk register had scored it Critical ten weeks earlier, with an owner and a mitigation already running. It happened anyway.
What follows is a program that spent negotiated schedule margin rather than breaching a contractual maximum, deferred scope to named owners rather than absorbing everything into cost, and finished inside its authorized funding while carrying a permanent shortfall in cumulative synergy capture. Both of those last two are true at once, and the closeout report says so.
Where to start. If you read one document, read the Application Disposition Matrix — it is where the integration strategy is actually decided, system by system. If you read three, add Data Profiling Results (the crisis) and Lessons Learned (why it was structurally guaranteed). How to Read This Suite explains the annotation colors and the point-in-time convention that makes these documents disagree with one another on purpose.
Consulting SOW & Engagement Model
The contracting model for the whole program: three tiers of paper, and why the engagement lead can sign neither side of his own SOW.
Issued Feb 20, 2023
Deal Summary & Investment Thesis
The integration extract of the deal model — the $85M commitment decomposed by source, and the assumptions this program is now accountable for testing.
Issued Feb 24, 2023
Integration Charter
The highest-authority document: what the program may spend, decide and bind — and the Class 5 estimate it was legally forced to carry.
Issued Feb 27, 2023
Clean Team Protocol
You may not integrate before you close. This is the protocol that lets planning proceed without anyone seeing what they must not see.
Issued Mar 6, 2023
IMO Governance
The operating structure for a program whose manager employs nobody in it — decision rights written to work without line authority.
Issued Mar 6, 2023
RACI Matrix
Fifteen deliverables against eight functions, exactly one Accountable each — and the paired counterpart rows that are joint across two employers.
Issued Mar 6, 2023
Stakeholder Register
Nine groups whose interests actively conflict, with influence and engagement approach stated rather than assumed.
Issued Mar 10, 2023
Due Diligence Findings
Fourteen findings that survive the transaction and become integration work, each with an owner rather than a note.
Issued Mar 13, 2023
Regulatory Tracker
Two gates the program cannot start without, tracked with the conditions regulators may attach and what each would cost.
Issued Mar 13, 2023
Program Kickoff Deck
A 19-slide pre-close deck that states plainly its own budget rests on an estimate nobody is legally allowed to verify yet.
Issued Mar 20, 2023
Integration Management Plan
How the program is actually run when half the information is legally unavailable until close.
Issued Apr 17, 2023
Application Disposition Matrix
The centerpiece decision: absorb, preserve, or best-of-both, argued system by system rather than declared.
Issued Jun 26, 2023
Vendor & Contract Disposition Matrix
The vendor twin of the application matrix: the fastest synergy on the program and its most immediate Day 1 legal exposure.
Issued Jul 17, 2023
Synergy Realization Plan
Converts one committed number into five owned sources with dated profiles and rules for when a saving may be counted.
Issued Aug 7, 2023
Change & Culture Plan
Managing people who know with reasonable certainty that some portion of their jobs will not survive the integration.
Issued Aug 14, 2023
Communications Plan
Written six weeks before close, when the most urgent question anybody has cannot yet be answered and some things may not be said.
Issued Aug 14, 2023
TSA Schedule & Exit Plan
A TSA obliges the seller to provide a service, not to make you capable of it. Exiting one is the integration.
Issued Aug 28, 2023
Vendor Management Plan
The eight terms a vendor drops to win on price, made mandatory — warranty from acceptance, not delivery.
Issued Aug 28, 2023
Retention & Key Talent Plan
Retention buys time to transfer knowledge, not loyalty — sixteen roles, all at the target, and why that is the point.
Issued Sep 5, 2023
Cloud Migration Strategy
A first-time cloud organization evacuating an acquired estate in twelve months — rehost to hit the date, optimize afterward.
Issued Sep 11, 2023
Data Migration & EMPI Strategy
Resolving 420,000 members against 1,800,000 when very few are recorded identically in any two places.
Issued Sep 18, 2023
Integration Architecture
Two claims platforms, two enrollment systems, one membership — and regulators, providers and members must not be able to tell.
Issued Sep 25, 2023
Legal Entity Consolidation
A book of business cannot be moved the way a company is — statutory merger or assumption reinsurance, against a hard year-end.
Issued Nov 13, 2023
Quality Plan
Not validating new functionality against a specification: proving existing functionality still behaves the same way after it moves.
Issued Dec 18, 2023
Test Strategy
How you test a migration whose specification is the system being retired: reproducing a known error is a pass, and improving on it without a decision is a defect.
Issued Dec 18, 2023
Risk Register
Dated ten weeks before the crisis it correctly predicts. Scored Critical, owned, mitigated — and with no idea what is coming.
Issued Feb 5, 2024
Work Breakdown Structure & Console
The work breakdown structure as a navigable console — 11 control accounts, 54 work packages, with the MS Project and Excel exports beneath it.
Issued Feb 12, 2024
Resource Plan
Eighty-four named people with the contract vehicle each is engaged under — an aggregate is a claim, a roster is evidence.
Issued Feb 19, 2024 · revised
Master Schedule
The dated plan with the critical path named — and honest about where float exists and where it does not.
Issued Feb 26, 2024 · revised
Program Budget
Two baselines rather than one, because the first was produced under a legal prohibition on examining the data that determines cost.
Feb 2023 → rev. Mar 2024
Organization Chart
Eighty-four named people. The roster legally changes shape at close — the Clean Team ends where the data stewards begin.
Issued Mar 11, 2024
Roles & Responsibilities
What each function owns and what it explicitly does not, plus the bodies the program depends on and cannot instruct.
Issued Mar 11, 2024
BRD-01 — Member Identity Resolution
The largest work package on the program, and the one where a false positive merges two people and nothing routine surfaces it.
Issued Jan 29, 2024
BRD-02 — Core Administration
Requirements for equivalence, not correctness — the oracle is not a specification, it is the system being retired.
Issued Feb 6, 2024
BRD-03 — Integration Layer
The only work package whose requirements include the conditions for its own removal.
Issued Feb 13, 2024
BRD-04 — Enterprise Data Warehouse
The one system being built rather than moved — where losing a measurement year cannot be recovered at any RTO.
Issued Feb 20, 2024
BRD-05 — Preserved & Best-of-Both
The capabilities deliberately not consolidated, and the three ordinary ways a preserved system quietly degrades.
Issued Feb 27, 2024
Day 1 Readiness Assessment
The final gate three days before close, certifying that the matching engine works and explicitly refusing to certify the volume.
Issued Sep 26, 2023
Day 1 Go/No-Go Decision
The formal authorization to cut over, with the risk it accepts stated plainly rather than closed out.
Issued Sep 29, 2023
Member Communications & ID Cards
420,000 members need a card in hand before the plan-year boundary; the ordering is the whole plan.
Issued Oct 16, 2023
Cloud Landing Zone Design
Built before the first workload moves, and that sequencing is a hard rule rather than a preference.
Issued Nov 6, 2023
Provider Network Rationalization
The largest single synergy line, written before any renegotiation opens and deliberate about how little leverage the program has.
Issued Nov 20, 2023
Cloud Migration Wave Plan
Five waves against a hard data-center exit, opening with the arithmetic that decides whether the plan is possible at all.
Issued Dec 4, 2023
Day 100 Assessment
The first checkpoint after cutover — and it records that the review population is still unquantified.
Issued Jan 9, 2024
Data Profiling Results
The crisis. Six months after close, the first lawful look at the member file returns a review band three times the deal model.
Issued Apr 15, 2024
EMPI Match Rules
The decision logic issued one day after the profiling result — where uncertainty resolves toward review, never toward merge.
Issued Apr 16, 2024
Steward Standard Operating Procedures
The bridge between the match policy and the actual work: queues, documentation, handoff and escalation.
Issued Apr 18, 2024
Status Report — Period 8
Written eighteen days into the crisis with the change request on the table and the outcome genuinely unknown.
Issued May 3, 2024
Steering Committee Deck
One decision sought: extend the TSA by three months and fund it from reserve — with what the program will not do either way.
Issued May 14, 2024
Steering Committee Deck — Slides
The May 2024 escalation as 21 slides. Slide 9 names the option that costs nothing, breaches no date, and is the one the program most opposes.
Issued May 14, 2024
Integration Dashboard
The standing one-page view: four measures the program is actually run on, and the exposures that do not fit on a tile.
Issued Jul 31, 2024
Synergy Realization Tracker
Two numbers pointing in opposite directions, both true — and reporting only the flattering one is the easiest way to mislead a committee.
Issued Nov 8, 2024
TSA Exit Readiness Report
Assesses whether the last two services can exit on the revised date. The exit has not happened yet.
Issued Dec 13, 2024
Closeout Report
Late but whole. Inside authorized funding, inside the contractual maximum, with the cumulative synergy shortfall stated rather than buried.
Issued Apr 30, 2025
Retrospective Synergy Case — Cost-Benefit Analysis
The synergy case, and it does not resolve cleanly — the Year 3 target is met while cumulative capture finishes behind model.
Issued Apr 30, 2025
Lessons Learned
Not a blame list. The estimate was constrained by law, the register got the risk right ten weeks early, and the overrun happened anyway.
Issued Apr 30, 2025
SOW-05 — Clean Team Services
Engaged by Legal rather than by the program, because a clean team retained by the party it shields would not be a barrier.
Issued Aug 28, 2023
SOW-02 — Co-Managed Cloud Operations
Co-managed operations with an acceptance-gated step-down: the supplier is not paid for a phase until ACME can demonstrate what it transfers.
Issued Aug 28, 2023
SOW-07 — Cloud Platform Services
An order under a pre-existing enterprise agreement — standard terms, so this records which ones the program is relying on.
Issued Aug 28, 2023
SOW-04 — Data Steward Staff Augmentation
Staff augmentation, so ACME directs the work and owns the outcome — the distinction that creates co-employment exposure if blurred.
Issued Aug 28, 2023
SOW-03 — X12 Transaction Assurance
ACME defines what correct means; the supplier owns demonstrating it.
Issued Aug 28, 2023
SOW-06 — EMPI Platform
The one instrument where a supplier product decision can invalidate work ACME has already accepted.
Issued Aug 28, 2023
SOW-08 — Physical Data Transfer
340 TB that cannot cross the network inside the migration window, and works only because the archive is cold.
Issued Aug 28, 2023
Glossary
The vocabulary this suite uses that the other seven do not — each term defined against this program’s own numbers rather than generically.
How to Read This Suite
Start here. What the annotations mean, why the documents disagree with each other on purpose, and what is fictional.