The board approved a $1,200,000,000 transaction on a commitment of $85,000,000 run-rate synergy by the end of Year 3. This plan converts that single number into five sources, each with a named owner, a dated realization profile, a defined measurement baseline, and rules for when a saving may be counted. It is the document that makes the commitment auditable rather than aspirational. Approved August 7, 2023, before closing.
A synergy target with no owner is a forecast. A synergy target with an owner, a baseline and a recognition rule is a commitment. The difference matters at Year 3, when someone asks whether the savings arrived. Programs that never did this work cannot answer — not because the savings failed, but because nobody was ever in a position to know. The purpose of this plan is to make the question answerable, including in the event that the answer is unwelcome.
Table of Contents
Part I — The Commitment
Part II — Measurement
Part III — Governance
1. Decomposition, Owners and Dates
| Ref | Source | Run-rate | Confidence | Owner | Gated by |
|---|---|---|---|---|---|
| SY-01 | Platform & IT consolidation | $24,000,000 | High | S. Achebe, CIO | Core admin cutover; target platform decommissioning. Largest and slowest. |
| SY-02 | Provider network rationalization | $19,000,000 | Medium | J. Kirkendall, VP Network | Contract renewal cycles. Cannot be pulled forward by effort. |
| SY-03 | Vendor & contract consolidation | $18,000,000 | High | H. Castellow, VP Procurement | Notice periods and migration dependencies. Fastest to land. |
| SY-04 | Corporate function consolidation | $16,000,000 | High | S. Beauregard, VP FP&A | Employee continuation period in the merger agreement |
| SY-05 | Facilities & other | $8,000,000 | Medium | W. Pickering, Dir. Real Estate | Lease expiry dates. Governed by calendars, not decisions. |
| Committed run-rate | $85,000,000 | The figure the board approved the transaction on |
Read the "gated by" column and notice what is missing: effort. Not one of these five sources accelerates because people work harder. Platform savings arrive when a migration completes; network savings when contracts renew; facilities savings when leases expire; corporate savings when a contractual continuation period ends. Synergy realization is almost entirely a sequencing problem, which is why the plan is dated rather than merely owned — and why a delay anywhere upstream translates directly into savings that were never banked.
2. The Realization Curve
| Period | Cumulative capture | Shape | What lands |
|---|---|---|---|
| Year 1 | $22,000,000 | Vendor consolidation, executive and corporate overlap, early facilities | |
| Year 2 | $58,000,000 | TSA exit, platform decommissioning begins, network renewals cycle | |
| Year 3 | $121,000,000 | Full platform retirement; run-rate reaches the committed $85,000,000 |
Two different numbers are reported every month, and confusing them is the most common failure in synergy reporting.
Run-rate answers "what is the annualized saving in effect right now." It is the number the board committed to and the number that appears in the Year 3 test.
Cumulative capture answers "how much money did we actually not spend." It is the number the CFO sees in the general ledger.
A program can hit its run-rate target on schedule and still be materially behind on cumulative capture, because a saving that arrives three months late is never banked for those three months. That shortfall is permanent — no subsequent overperformance recovers money that was already spent. Reporting both from month one means a timing problem is visible as a timing problem, months before it looks like a shortfall.
Run-rate answers "what is the annualized saving in effect right now." It is the number the board committed to and the number that appears in the Year 3 test.
Cumulative capture answers "how much money did we actually not spend." It is the number the CFO sees in the general ledger.
A program can hit its run-rate target on schedule and still be materially behind on cumulative capture, because a saving that arrives three months late is never banked for those three months. That shortfall is permanent — no subsequent overperformance recovers money that was already spent. Reporting both from month one means a timing problem is visible as a timing problem, months before it looks like a shortfall.
3. The Baseline — the Hard Part
The difficulty in synergy tracking is not tracking. It is defining what you are tracking against. A saving is only a saving relative to something, and the something has to be fixed before the savings start arriving — because once they do, every party to the measurement has an incentive to remember the baseline differently.
| Baseline component | Definition |
|---|---|
| Baseline period | The twelve months ended at closing, for both entities separately |
| Baseline cost | Actual spend in that period, at the account level, per source |
| Normalization | Adjusted for one-time items, known volume changes, and contracted price escalations that would have occurred anyway |
| Membership adjustment | ⚠ Per-member-per-month where the source scales with membership, absolute where it does not |
| Frozen | Baseline is fixed at closing and does not move. Restatement requires Steering Committee approval and is disclosed. |
3.1 Why per-member-per-month matters for some sources and not others
Claims processing cost scales with membership; a data center lease does not. Measuring a volume-driven cost in absolute dollars credits the program with savings that are really just membership decline — or penalizes it for growth. Measuring a fixed cost per member does the reverse. The unit of measurement is chosen per source and recorded, because choosing it after the results are in is how a number gets manufactured.
The "frozen baseline" rule is the one that will be tested, and it will be tested by people acting in good faith. Eighteen months in, someone will observe correctly that the baseline included an unusual item, or that a price increase was always coming, or that a comparison is unfair for a reason that is genuinely true. Each individual adjustment will be defensible. The cumulative effect of a baseline that moves whenever it is inconvenient is a synergy number that means nothing — which is why restatements require Steering approval and are disclosed alongside the result rather than absorbed into it.
4. Recognition Rules
A saving is recognized when the action producing it is complete and irreversible — not when it is decided, approved, or forecast.
| Source type | Recognized when | Not recognized when |
|---|---|---|
| Vendor termination | Notice served, term expired, no residual obligation | Decision taken; notice drafted; contract in renegotiation |
| Platform decommissioning | System off, license terminated, hosting cost ceased | Migration complete but the old system still running "just in case" |
| Role elimination | Position removed from the establishment and not backfilled | ⚠ Vacancy unfilled; incumbent on notice; work absorbed informally |
| Network rate improvement | Amended contract executed and effective | Rate agreed in principle; renewal in negotiation |
| Facility exit | Lease terminated or expired; no holdover | Space vacated but lease still running |
The distinction between "vacated" and "lease terminated" is the whole of this section in miniature. A team can move out of a building, report the space as consolidated, and the organization still pays rent on it for two more years. The operational action is complete; the saving does not exist. Recognition tracks the cash, not the activity — and the gap between them is where optimistic synergy reporting lives.
5. Synergy Versus Business-as-Usual
Not every cost reduction after a merger is a merger synergy, and the difference is not academic — it decides whether the deal is judged to have worked. If a function would have renegotiated its contract anyway, that saving was coming with or without the transaction. Counting it as synergy inflates the result and, worse, means the transaction gets credit for something it did not cause. The test is counterfactual: would this saving have occurred without the acquisition?
| Counts as synergy | Does not |
|---|---|
| Terminating a duplicate contract that exists only because there were two companies | Renegotiating a contract that was up for renewal regardless |
| Eliminating a role duplicated across the two organizations | A vacancy that was already being held open |
| Volume-based pricing improvement obtained by combining the two books | Market-rate movement that would have applied anyway |
| Retiring a platform because a single one now serves both | Retiring a platform that was already end-of-life on its own roadmap |
Each source therefore carries a documented counterfactual, agreed with the owning function at the time the source was defined — before anyone knew whether the number would be met.
6. Phantom Savings
The most common form of overstated synergy is a saving that moved rather than a saving that happened. Twenty roles are eliminated and reported as a corporate function synergy. Six months later, the same work is being done by contractors, or by an outsourced service, or by overtime in an adjacent team. The headcount line improved; total cost did not. Nothing in a headcount-based measure detects this, because the cost reappeared in a different account under a different owner.
| Phantom pattern | Control |
|---|---|
| Roles eliminated, work reappears as contractor spend | ⭐ Savings measured at total function cost, not headcount — contractor, temporary and outsourced spend included in the same envelope |
| Contract terminated, spend reappears with another vendor | Category-level measurement rather than contract-level |
| Cost pushed into the integration program budget | ⚠ Program spend excluded from synergy measurement entirely — the program cannot save money by paying for it itself |
| Cost deferred rather than removed | Recognition requires the obligation to have ended, not paused |
| Savings claimed in one function, cost absorbed in another | Independent measurement across the combined ledger, not by self-report |
The third row is the one a program manager should be most alert to, because the program is the perpetrator. It is easy, and almost never deliberate, for work that used to sit in a business function to be absorbed into the integration program's own budget — and for the function to then report a saving. The organization has not spent less; it has moved the spending into a temporary envelope that will end. A synergy that disappears when the program closes was never a synergy.
7. Net Position — Cost to Achieve and Dis-Synergies
| Component | Amount | Treatment |
|---|---|---|
| Committed run-rate synergy | $85,000,000 | The commitment |
| Dis-synergy allowance, netted inside the sources | $6,000,000 | Attrition backfill, duplicate running cost, distraction, membership disruption, lost legacy terms |
| Integration program — authorized | $52,500,000 | One-time cost to achieve. Separately authorized in the Charter. |
Stating cost to achieve beside the benefit is not a caveat; it is half the argument, and it is the half deal models routinely omit. Roughly $52,500,000 of one-time program spend establishes $85,000,000 of recurring annual saving. That is a strong return and it is also the shape of the sentence a CFO wants to hear, because they already know the savings did not arrive on their own. A program manager who can only quote the benefit is quoting a brochure.
⚠ Dis-synergies are netted inside the source figures rather than shown as a separate deduction, so the $85,000,000 is already a net commitment. Carrying the allowance explicitly matters because deal models frequently omit it altogether, and a closeout report forced to explain a gap it never budgeted for is describing a surprise rather than a plan.
8. Reporting and Independence
| Element | Provision |
|---|---|
| Measurement owner | J. Petrosyan, Synergy & Financial Analyst, IMO |
| Source owners | The five executives in Section 1. They deliver; they do not measure. |
| Cadence | Monthly against baseline, both run-rate and cumulative |
| Reported to | Steering Committee monthly; Executive Sponsor owns the board commitment |
| Evidence | Traced to general ledger accounts, not to function-reported estimates |
| Restatement | Baseline restatements require Steering approval and are disclosed alongside the result |
Source owners deliver savings; they do not measure them. That separation is the single most important governance provision in this plan. Letting each function self-report its own synergy attainment produces an aggregate that always exceeds what the general ledger shows — not through dishonesty, but because every function counts every favorable variance in its area as integration benefit, and nobody counts the unfavorable ones. Independent measurement against a frozen baseline is duller, less popular, and the only version an auditor or an acquirer's board will believe.
9. Risks to Realization
| Ref | Risk | Effect and response |
|---|---|---|
| SR-01 | Migration slips, delaying platform decommissioning | Highest exposure. SY-01 is the largest source and the last to land. Run-rate may still be reached late; cumulative capture is permanently reduced. |
| SR-02 | Provider contracts do not permit rationalization inside the modeled window | SY-02 slips to later renewal cycles. Timing risk rather than value risk. |
| SR-03 | Vendor consolidation accelerated ahead of migration dependencies | ⚠ The opposite failure. Booking a saving early causes an operational break. Vendor exit dates are outputs of the migration plan. |
| SR-04 | Attrition exceeds the dis-synergy allowance | Backfill cost erodes SY-04 and threatens the knowledge base the TSA exit depends on |
| SR-05 | Savings claimed but not evidenced in the ledger | Managed by independent measurement. Detected as a widening gap between reported and ledger position. |
| SR-06 | Baseline erosion through repeated restatement | Managed by the freeze rule and by disclosing restatements rather than absorbing them |
SR-01 and SR-03 are the same dependency read from opposite ends, and a program can fail either way. Move too slowly and the largest source lands late, permanently reducing cumulative capture. Move too quickly — terminate the clearinghouse before the migration that depends on it — and the saving is real but the operational failure is worse than the money. The synergy curve and the migration plan are the same schedule seen from two directions, and neither may be optimized without the other.
Related artifacts: 2 — Deal Summary & Investment Thesis · 20 — Application Disposition Matrix · 21 — Vendor & Contract Disposition Matrix · 22 — TSA Schedule & Exit Plan · 41 — Synergy Tracker · 46 — Closeout Report