← Portfolio Mergers & Acquisitions · Program Management Suite

ACME Health / Cumberland Valley Health Plan Integration

A complete health plan acquisition, charter through closeout — annotated with the reasoning behind each decision.

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: 67 documents covering governance, planning, execution, control and closeout — written as point-in-time artifacts, each true only as of its own date.

67
Documents
$1.2B
Transaction
2,220,000
Combined members
$59,400,000
Program outturn
$85M
Synergy target
84
Named people
19 mo
Charter to close

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.

Initiation — before the deal closes
1

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.

2

Integration Charter

3

Deal Summary & Investment Thesis

4

Stakeholder Register

5

IMO Governance

6

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.

7

Regulatory Tracker

8

Due Diligence Findings

9

Consulting SOW & Engagement Model

Planning — the decisions everything else inherits
10

Integration Management Plan

11

Work Breakdown Structure & Console

12

Master Schedule

13

Program Budget

14

Synergy Realization Plan

15

Resource Plan

16

Organization Chart

Eighty-four named people. The roster legally changes shape at close — the Clean Team ends where the data stewards begin.

17

RAIDD Log

18

Communications Plan

19

Change & Culture Plan

20

Retention & Key Talent Plan

21

Application Disposition Matrix

The centerpiece decision: absorb, preserve, or best-of-both, argued system by system rather than declared.

22

Vendor & Contract Disposition Matrix

23

Vendor Management Plan

24

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.

25

Data Migration & EMPI Strategy

26

Cloud Migration Strategy

27

Integration Architecture

28

Quality Plan

29

Legal Entity Consolidation

30

Risk Register

Dated ten weeks before the crisis it correctly predicts. Scored Critical, owned, mitigated — and with no idea what is coming.

Business Requirements
31

BRD-01 — Member Identity Resolution

32

BRD-02 — Core Administration

33

BRD-03 — Integration Layer

34

BRD-04 — Enterprise Data Warehouse

35

BRD-05 — Preserved & Best-of-Both

36

Requirements Traceability Matrix

Execution — Day 1, the crisis, and the recovery
37

Day 1 Readiness Assessment

38

Day 1 Go/No-Go Decision

39

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.

40

EMPI Match Rules

41

Steward Standard Operating Procedures

42

Cloud Landing Zone Design

43

Cloud Migration Wave Plan

44

Day 100 Assessment

45

Provider Network Rationalization

46

Member Communications & ID Cards

47

Interface Build & Cutover Log

Monitoring & Control
48

Integration Dashboard

49

Synergy Realization Tracker

50

Status Report — Period 8

51

Steering Committee Deck

52

Change Control Log

Twelve requests, six approved. The log reconciles the baseline to the outturn exactly — and names the constraint each request protected and spent.

53

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.

54

TSA Exit Readiness Report

Closeout
55

Closeout Report

Late but whole. Inside authorized funding, inside the contractual maximum, with the cumulative synergy shortfall stated rather than buried.

56

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.

57

Cost-Benefit Analysis

The synergy case, and it does not resolve cleanly — the Year 3 target is met while cumulative capture finishes behind model.

58

Total Cost of Ownership

What the estate costs to run once the program is gone. Every disposition decision was a claim about this number.

Vendor Statements of Work
59

SOW-02 — Co-Managed Cloud Operations

60

SOW-03 — X12 Transaction Assurance

61

SOW-04 — Data Steward Staff Augmentation

62

SOW-05 — Clean Team Services

63

SOW-06 — EMPI Platform

64

SOW-07 — Cloud Platform Services

65

SOW-08 — Physical Data Transfer

66

Business Associate Agreement Register

67

How to Read This Suite

Start here. What the annotations mean, why the documents disagree with each other on purpose, and what is fictional.