← M&A Integration Suite Plan · Artifact 14 · how to read this suite

Resource Plan

Download Excel

Eighty-four named people across two companies and five outside firms. This plan records who they are, which of four contract vehicles each one is engaged under, when they join and leave, and which roles the program cannot afford to lose. It also reconciles honestly against the work breakdown structure, where 53 of the 84 carry a named row and 31 do not. Revision 2, issued February 19, 2024, following the post-discovery re-baseline.

Eighty-four is a roster, not a room. It is the right number for onboarding, system access, background checks and business associate agreements — every one of those is per person. It is the wrong number for capacity planning, because the roster spans two years, changes shape at closing, and includes people whose involvement is a monthly meeting. A plan that treats a headcount as a workforce will be short of hands and unable to say why.

Table of Contents

Part I — Composition
  1. Four Labor Categories
  2. Contract Vehicle Per Person
  3. The Roster Changes Shape at Closing
Part II — Cost and Constraint
  1. Rate Card
  2. Constraints That Are Not Negotiable
  3. Retention and Key Person Concentration
Part III — Honesty Checks
  1. Reconciliation Against the WBS
  2. Attrition and Churn
  3. The Roster — all 73 named
Part I — Composition

1. Four Labor Categories

OrganizationPeopleCategoryRole on the program
ACME Health31EmployeeWorkstream leads, IMO analysts, target-state design, all decision authority
Cumberland Valley Health Plan21EmployeeWorkstream counterparts — how the acquired business actually operates
Arrington Advisory Group17ConsultingProgram management and the three specialisms ACME's bench is thinnest on
Arrington Advisory Group (offshore)4ConsultingInterface regression testing against de-identified data
Harpeth Clean Team Services4Specialist vendorPre-close information barrier. ⚠ Dissolves at closing.
Two Rivers Talent Partners4Staff augmentationClerical review of identity matches
Gallatin EDI Assurance3Specialist vendorX12 transaction assurance
Total roster84Across the full program window
Fifty-two of the eighty-four are employees of the two merging companies, and that ratio is deliberate. A program staffed predominantly by consultants can move quickly and leaves nothing behind — the capability walks out with the invoice. Outside help is concentrated where ACME genuinely lacks depth: identity resolution, integration architecture, cloud engineering, and program management itself. Everywhere else the work is done by people who will still be here when the program closes.

2. Contract Vehicle Per Person

The plan records a vehicle for every named individual, not merely a rate. The distinction determines who owns the outcome, who directs the work, and what the program is legally permitted to ask.

VehiclePeopleWho owns the outcomeWho may direct the work
FTE52ACME / Cumberland ValleyTheir line manager
Deliverable SOW21Arrington — against accepted deliverablesArrington. ACME defines "done", not "how".
Fixed-price SOW7The vendor — against a defined resultThe vendor
Staff aug (T&M)4ACME — hours are rented, not outcomes⚠ ACME — see the guardrail below
The staff augmentation row is the one that creates legal exposure, and it does so precisely because the vehicle is working as intended. ACME rents hours and directs the work — that is why the vehicle was chosen for clerical review. But directing the work is not managing the person: the Program Manager may set which queue a steward works and what quality standard applies, and may not conduct their performance review, approve their leave, or place them on the ACME organization chart. Recording the vehicle per individual is what makes that line visible rather than remembered, and it is the reason this column exists at all.

3. The Roster Changes Shape at Closing

PopulationPre-closePost-closeReason
Clean Team40The antitrust basis for the barrier ends at closing. Nobody crosses into the program.
Data stewards04⚠ Member-level data is not lawfully available before closing. The work cannot begin earlier.
Migration, cloud and build engineers014Execution against the target is prohibited pre-close
EDI assurance03Testing requires production transaction flow
TSA management01There is no TSA until there is a transaction
Total on the program5880Different populations, not the same one grown
This is the only resource plan in the portfolio where the shape of the team is set by law rather than by budget. The Clean Team exists because two competitors may not exchange certain information before they combine, and it dissolves the moment they do. Data stewards cannot start early no matter how much the schedule would benefit, because the records they review may not lawfully be examined yet. Neither constraint responds to money, escalation or urgency — which makes them different in kind from every other resourcing problem on the program, and it is why the pre-close and post-close rosters are maintained as two states rather than one list with start dates.
Part II — Cost and Constraint

4. Rate Card

Blended hourly rates, inclusive of benefits, overhead and supplier margin. Deliverable fees are priced from this table against an agreed effort estimate; time-and-materials hours bill against it directly.

CategoryRateVehicle
Engagement lead / Program Manager$265Deliverable SOW
Principal consultant$245Deliverable SOW
Architect — integration, cloud$230Deliverable SOW
Senior engineer / senior analyst$195Deliverable SOW
Analyst — PMO, data quality, FinOps$155Deliverable SOW
Offshore delivery manager$95Deliverable SOW
Data steward supervisor$92Staff aug
Offshore test lead$80Deliverable SOW
Data steward$68Staff aug
Offshore QA engineer$65Deliverable SOW

5. Constraints That Are Not Negotiable

ConstraintEffect on resourcing
No member-level data outside the United States⚠ Tennessee DOI conditions and ACME privacy policy. Clerical review, data stewardship and anything touching the member file must be staffed onshore. The obvious lever for a queue overrun does not exist.
Offshore work is de-identified onlyThe four offshore staff test interface regression against synthetic and de-identified datasets. Their scope is bounded by what can be done without a real member record.
Clean Team is walled offFour people who see restricted information and return only conclusions. They may not be redeployed onto the program afterward.
Employee continuation periodCorporate function consolidation cannot begin until the merger agreement's continuation period expires, regardless of readiness.
Steward throughput is fixed⚠ A steward working faster is a steward spending less time on the hard cases, which is where false positives originate. Capacity scales by adding people, and onboarding runs several weeks.
Read the first and last rows together, because they combine into the program's tightest corner. If the clerical review queue proves larger than modeled, the three obvious responses all fail: offshore capacity is barred by regulation, throughput cannot be pushed without producing the error type that does not surface, and recruiting takes weeks the schedule may not have. The only remaining lever is time — and time is the constraint the Charter ranks hardest.

6. Retention and Key Person Concentration

Sixteen roles carry retention agreements. Every one is at Cumberland Valley.

The asymmetry is the point: retention risk sits where the system knowledge is, and that is the side of the transaction whose people are least certain of their futures. The staff who understand how the target's claims platform is actually configured — as opposed to how it is documented — are the same staff most able to find another job, and they know some of their colleagues will not be here in a year. The program depends on their knowledge for twelve months and cannot offer most of them twelve months of certainty in return. That is not a problem retention payments solve; it is a problem they buy time against.
ConcentrationExposure and response
Core administration configurationA small number of long-tenured staff hold undocumented platform knowledge. Knowledge transfer is a deliverable with named receivers, not an assumed by-product of the TSA.
Member data structuresConcentrated in one Cumberland Valley manager. ⚠ Single point of knowledge for the program's largest risk.
Provider contract historyHeld by the target's contracting director; material to network rationalization
Data steward supervisionOne supervisor owns the queue service level. Deputy identified and cross-trained.

⚠ Retention cost is funded separately by Human Resources and does not sit in the program budget. The program identifies the roles; it does not price them.

Part III — Honesty Checks

7. Reconciliation Against the WBS

The work breakdown structure names an owner on every row. Fifty-three of the eighty-four appear there. Thirty-one do not, and the reasons matter more than the number.

PeopleGroupWhy they carry no work package
5Steering CommitteeGovernance, not delivery. They approve, decide and escalate; a control account owner reports to them. ⚠ Putting an executive on a work package would misrepresent who does the work.
4Clean TeamPre-close only. Dissolved before the WBS window opens.
22Workstream members⚠ Their work sits inside a package owned by a colleague. See below.
31Not on the WBS53 + 31 = 84
The third row is a genuine limitation of single-owner assignment, and it is better named than papered over. A WBS row carries one accountable owner. A workstream of two or three people therefore shows one name, and the counterpart or second analyst appears nowhere — not because they do nothing, but because the structure has no place to record them. A reader who counts names on the WBS and concludes the program runs on 53 people would be wrong by more than a third. That is what this reconciliation exists to prevent, and it is why the roster rather than the plan is the source of truth for who is on the program.

8. Attrition and Churn

The program runs nineteen months from Day 1 to close. Nobody should plan on the same 73 people being present throughout.

RealityHow the plan absorbs it
Consultants rotateDeliverable SOW means Arrington owns continuity, not ACME. ⚠ Named-personnel continuity is contracted for the roles where transfer depends on the same individual.
Target-side staff leaveRetention on 14 roles; knowledge transfer specified as a deliverable so a departure after transfer is a staffing problem rather than a program one
Acquirer staff are reassignedWorkstream leads are named and their release requires the Sponsor's agreement, not their line manager's alone
Stewards turn overStaff augmentation absorbs this by design — the supplier replaces, ACME retrains. Onboarding time is in the queue forecast, not assumed away.
The MSP steps downCloud operations transfer to ACME across four contracted phases; capability is measured at each boundary rather than assumed
The defensible summary if someone asks whether the program is adequately resourced. Fifty-two of the people are permanent employees who remain after the program ends. Outside help is concentrated in four specialisms and contracted so the supplier carries continuity. Sixteen critical roles are retained, and every one of them owes a knowledge transfer with named receivers and an acceptance test. The plan does not assume the team is stable; it assumes the team turns over and buys the specific continuity the program cannot survive losing.

9. The Roster — All 84 Named

Grouped by workstream. Vehicle is the contract instrument each person is engaged under; window is when they are on the program; R marks a role covered by a retention agreement.

An aggregate is a claim; a roster is the evidence for it. Saying the program has four data stewards and thirteen consultants invites the only question that matters — who are they, what are they engaged to do, and under what paper. This table answers that for every person, and it is generated from the same source the headcounts in Section 1 are derived from, so the two cannot disagree.
NameRoleOrganizationVehicleWindowR
Steering Committee · 6
D. AshmoreEVP & Chief Financial Officer, ACME — Executive SponsorACMEFTEThroughout
R. VillanuevaChief Operating Officer, ACMEACMEFTEThroughout
M. KessingerPresident & CEO, Cumberland ValleyCumberland ValleyFTEThroughoutR
T. BroadnaxSVP Corporate Development, ACMEACMEFTEThroughout
L. HollingsworthGeneral Counsel, ACMEACMEFTEThroughout
S. AchebeChief Information Officer, ACMEACMEFTEThroughout
Integration Management Office · 5
C. TyrrellProgram Manager, Integration (engagement lead)ArringtonDeliv. SOWThroughout
N. FarnsworthPMO AnalystArringtonDeliv. SOWThroughout
J. PetrosyanSynergy & Financial AnalystACMEFTEThroughout
A. WinterbourneChange & Communications LeadArringtonDeliv. SOWThroughout
G. ThreadgillTSA Manager — owns exitACMEFTEPost-close
Clean Team · 4
P. MarchettiClean Team LeadHarpethFixed pricePre-close only
K. OyelaranClean Team Analyst — pricing & network ratesHarpethFixed pricePre-close only
B. SandovalClean Team Analyst — membership & claims volumeHarpethFixed pricePre-close only
H. TillinghastClean Team Counsel (outside)HarpethFixed pricePre-close only
Claims & Core Administration · 11
R. SedgwickBusiness Analyst — benefit configurationACMEFTEThroughout
D. HalloranBusiness Analyst — enrollment & eligibilityCumberland ValleyFTEThroughoutR
M. PrideauxConfiguration Analyst, Core AdministrationACMEFTEPost-close
J. WhitfieldConfiguration Analyst, Claims — retiring platformCumberland ValleyFTEPost-closeR
S. CoventryQA Analyst — parallel run reconciliationACMEFTEPost-close
T. CallowayQA Analyst — parallel run reconciliationCumberland ValleyFTEPost-close
W. FerridayVP Claims Operations, ACME — Workstream LeadACMEFTEThroughout
E. NakagawaDirector, Core Admin Platform, ACMEACMEFTEThroughout
R. LattimoreVP Claims, Cumberland Valley — CounterpartCumberland ValleyFTEThroughoutR
D. OkparaManager, Claims Configuration, Cumberland ValleyCumberland ValleyFTEThroughoutR
V. CastellanosPrincipal Consultant, Core Admin MigrationArringtonDeliv. SOWPost-close
Data & EMPI · 11
P. RamaswamySenior Data Engineer, EMPI BuildArringtonDeliv. SOWPost-close
Dr. A. RavindranDirector, Enterprise Data Management, ACME — Workstream LeadACMEFTEThroughout
M. ThibodeauxData Architect, ACMEACMEFTEThroughout
C. BhattacharyaManager, Member Data, Cumberland ValleyCumberland ValleyFTEThroughoutR
S. WrenfieldPrincipal Consultant, Identity ResolutionArringtonDeliv. SOWPost-close
I. DuvernaySenior Data Engineer, Matching & SurvivorshipArringtonDeliv. SOWPost-close
Y. AbegundeData Quality AnalystArringtonDeliv. SOWPost-close
L. PembertonData Steward — clerical review queueTwo RiversStaff augPost-close
F. GuerreroData Steward — clerical review queueTwo RiversStaff augPost-close
N. OjukwuData Steward — clerical review queueTwo RiversStaff augPost-close
T. VandiverData Steward Supervisor — SLA ownerTwo RiversStaff augPost-close
Application Integration · 11
K. BalasubramanianBusiness Analyst — interface requirementsArringtonDeliv. SOWThroughout
A. FeldsteinSenior Engineer, Interface BuildArringtonDeliv. SOWPost-close
B. NkemdirimTest Manager — equivalence testing (onshore)ArringtonDeliv. SOWPost-close
K. StallworthDirector, Enterprise Integration, ACME — Workstream LeadACMEFTEThroughout
J. AmonettManager, Interfaces, Cumberland ValleyCumberland ValleyFTEThroughoutR
R. DelacroixIntegration Architect — canonical modelArringtonDeliv. SOWThroughout
O. HargraveSenior Engineer, Integration LayerArringtonDeliv. SOWPost-close
V. KrishnamoorthyOffshore Delivery ManagerArrington (offshore)Deliv. SOWPost-close
P. DevarakondaTest Lead, IntegrationArrington (offshore)Deliv. SOWPost-close
S. MahadevanQA Engineer, Interface RegressionArrington (offshore)Deliv. SOWPost-close
A. VaidyanathanQA Engineer, Interface RegressionArrington (offshore)Deliv. SOWPost-close
Cloud & Infrastructure · 7
C. LarkspurRelease & Environment ManagerACMEFTEThroughout
B. TrammellVP Infrastructure, ACME — Workstream LeadACMEFTEThroughout
H. SandiferManager, Platform Engineering, ACMEACMEFTEThroughout
G. WhitmireDirector, IT Operations, Cumberland ValleyCumberland ValleyFTEThroughoutR
E. KalinowskiCloud Architect — landing zoneArringtonDeliv. SOWThroughout
D. FontenotSenior Cloud Engineer, Migration WavesArringtonDeliv. SOWPost-close
R. IlesanmiFinOps Analyst — tagging, showback, reservationsArringtonDeliv. SOWPost-close
Provider Network · 2
J. KirkendallVP Network Management, ACME — Workstream LeadACMEFTEThroughout
A. BoudreauxDirector, Provider Contracting, Cumberland ValleyCumberland ValleyFTEThroughoutR
Care Management · 2
Dr. M. EllsworthChief Medical Officer, ACME — Workstream LeadACMEFTEThroughout
Dr. P. NwachukwuVP Care Management, Cumberland ValleyCumberland ValleyFTEThroughoutR
Member Services · 2
T. RuffaloVP Member Experience, ACME — Workstream LeadACMEFTEThroughout
C. HollifieldDirector, Member Services, Cumberland ValleyCumberland ValleyFTEThroughoutR
Finance & Accounting · 2
S. BeauregardVP Financial Planning & Analysis, ACME — Workstream LeadACMEFTEThroughout
N. ApplewhiteController, Cumberland ValleyCumberland ValleyFTEThroughoutR
HR & Talent · 2
D. MarchbanksSVP Human Resources, ACME — Workstream LeadACMEFTEThroughout
K. OsterhoutDirector, HR Business Partner, Cumberland ValleyCumberland ValleyFTEThroughout
Legal & Regulatory · 3
F. UnderhillAssociate General Counsel, M&A, ACME — Workstream LeadACMEFTEThroughout
R. CadwalladerDirector, Regulatory Affairs, ACME — DOI Form A ownerACMEFTEThroughout
M. SheffieldGeneral Counsel, Cumberland ValleyCumberland ValleyFTEThroughoutR
Compliance & Privacy · 2
L. BraithwaiteChief Privacy Officer, ACME — Workstream LeadACMEFTEThroughout
J. FerrandinoCompliance Director, Cumberland ValleyCumberland ValleyFTEThroughoutR
Security · 2
A. QuintanillaChief Information Security Officer, ACME — Workstream LeadACMEFTEThroughout
P. HasenfratzManager, Information Security, Cumberland ValleyCumberland ValleyFTEThroughout
Actuarial & Underwriting · 2
E. WetherbyVP Actuarial Services, ACME — Workstream LeadACMEFTEThroughout
C. AdeyemiChief Actuary, Cumberland ValleyCumberland ValleyFTEThroughoutR
Communications · 2
B. LundquistVP Corporate Communications, ACME — Workstream LeadACMEFTEThroughout
R. TomlinsonDirector, Communications, Cumberland ValleyCumberland ValleyFTEThroughout
Vendor & Contract Management · 3
H. CastellowVP Procurement, ACME — Workstream LeadACMEFTEThroughout
D. AchterbergDirector, Vendor Management, Cumberland ValleyCumberland ValleyFTEThroughoutR
M. RousseauContracts Consultant — change-of-control sweepArringtonDeliv. SOWThroughout
Facilities · 2
W. PickeringDirector, Corporate Real Estate, ACME — Workstream LeadACMEFTEThroughout
S. GrimsleyFacilities Manager, Cumberland ValleyCumberland ValleyFTEThroughout
EDI Transaction Assurance · 3
N. ReinhardtEngagement Lead, X12 AssuranceGallatinFixed pricePost-close
T. Osei-BonsuSenior EDI Analyst — 834 enrollment, 820 premiumGallatinFixed pricePost-close
L. MarchesiSenior EDI Analyst — 837/835 claims & remittanceGallatinFixed pricePost-close
Two patterns in this table are worth reading across rather than down. Every R sits on a Cumberland Valley row — retention risk is entirely on the acquired side, because that is where the system knowledge is. And the window column is not a schedule convenience: the four Harpeth rows end at closing and the data stewards begin there, because an information barrier dissolves the moment two companies combine and member-level data cannot lawfully be reviewed until they have.

Related artifacts: 8 — Consulting SOW & Engagement Model · 9 — Integration Management Plan · 10 — Work Breakdown Structure · 19 — Retention & Key Talent · 23 — Data Migration & EMPI Strategy · 24 — Cloud Migration Strategy · 28 — Risk Register