This document establishes the contracting model for the entire integration program. It contains the engagement statement of work under which Arrington Advisory Group provides program management to ACME Health, and it defines the three tiers of contracting paper through which every non-employee resource on the program is engaged — consulting, technology vendors, and staff augmentation. It also sets the rules for a problem specific to transactions: paper signed before closing binds an entity that will not exist in the same form afterward. Executed February 20, 2023.
Table of Contents
- Parties, Term and Instrument
- Scope of Services and Deliverables
- Acceptance, Fees and Invoicing
- Independence, Conflicts and the Clean Team Boundary
- Three Tiers of Contracting Paper
- Deliverable SOW versus Staff Augmentation
- Rate Card and Vehicle Selection
- Co-Employment Guardrails
1. Parties, Term and Instrument
| Attribute | Provision |
|---|---|
| Client | ACME Health |
| Supplier | Arrington Advisory Group |
| Instrument | Statement of Work No. ARR-2023-01, issued under the Master Services Agreement between the parties dated April 2021 |
| Vehicle | Deliverable statement of work — fees tied to accepted deliverables, not to hours worked |
| Engagement lead | C. Tyrrell, Program Manager, Integration |
| Client relationship owner | D. Ashmore, EVP & CFO, ACME Health |
| Effective | February 20, 2023 |
| Term | Through exit of the final Transition Services Agreement and formal program close. Extension by written amendment only. |
| Not-to-exceed | Set per phase; the pre-close phase authorization does not carry into the post-close phase without amendment |
2. Scope of Services and Deliverables
Arrington provides program management, and specialist capability in the three areas where ACME's internal bench is thinnest — identity resolution, integration architecture, and cloud platform engineering. Seventeen Arrington personnel are engaged across the program: thirteen onshore and four offshore.
| Service area | Arrington role | Principal deliverables |
|---|---|---|
| Program management | Program Manager; PMO Analyst | Integration Charter, Integration Management Plan, WBS and schedule, RAIDD log, status and steering reporting, change control administration, closeout |
| Change and communications | Change & Communications Lead | Communications Plan, Change & Culture Plan, Day 1 and Day 100 communications |
| Identity resolution | Principal Consultant; Senior Data Engineer; Data Quality Analyst | Data Migration & EMPI Strategy, match rules and survivorship specification, data profiling, steward SOPs |
| Integration architecture | Integration Architect; Senior Engineer | Integration Architecture & Interface Plan, canonical model, interface build and cutover |
| Cloud platform | Cloud Architect; Senior Cloud Engineer; FinOps Analyst | Cloud Migration Strategy, landing zone design, wave plan, FinOps foundation |
| Core administration migration | Principal Consultant | Platform consolidation approach, migration and decommissioning plan |
| Contracts | Contracts Consultant | Change-of-control sweep, Vendor & Contract Disposition Matrix, consent and novation packages |
| Test execution (offshore) | Offshore Delivery Manager; Test Lead; two QA Engineers | Interface regression suite, execution and defect reporting |
2.1 Explicitly excluded from this engagement
- Decision authority. Arrington recommends; ACME decides. Nothing in this SOW confers authority to approve a disposition, accept a risk, or commit funds.
- Line management. No Arrington personnel manage ACME or Cumberland Valley employees.
- Clean Team services. Contracted separately to a firm with no other role in the transaction — see Section 4.2.
- Transaction advisory. Valuation, diligence and deal negotiation are outside scope and were performed by others before this engagement began.
- Any activity constituting pre-close operational control of the target.
3. Acceptance, Fees and Invoicing
3.1 The acceptance mechanism
Each deliverable in Section 2 carries a named ACME acceptor, a defined acceptance period, and written acceptance criteria agreed before work begins. Deliverables are invoiced on acceptance. Where a deliverable is rejected, the rejection must state which criterion is unmet; Arrington remediates at its own cost and resubmits.
3.2 Fee structure
| Component | Basis |
|---|---|
| Deliverable fees | Fixed fee per accepted deliverable, priced from the rate card in Section 7 against an agreed effort estimate. Overrun against the estimate is Arrington's risk. |
| Ongoing program management | Monthly fixed fee for the duration of each authorized phase, covering the standing program management function that is not deliverable-shaped |
| Expenses | Reimbursed at cost against ACME's travel policy. No markup. Pre-approval required above a per-trip threshold. |
| Rate escalation | Fixed for the first twelve months; thereafter by written amendment only |
| Invoicing | Monthly in arrears. Deliverable fees invoiced in the month of written acceptance. |
3.3 Termination
- For convenience by ACME on 30 days' written notice, with fees payable for accepted deliverables and work in progress at the point of notice.
- For cause by either party on material breach uncured after 30 days.
- On transaction failure. If the transaction does not close, the engagement terminates automatically at the point of abandonment. This clause exists because a signed merger agreement is not a closed transaction, and an engagement structured as though it were would leave ACME paying for integration management of a company it did not buy.
4. Independence, Conflicts and the Clean Team Boundary
4.1 Conflict representation
Arrington represents that it holds no engagement with Cumberland Valley Health Plan, no engagement with a competing bidder, and no financial interest in the transaction outcome. Arrington's fees are not contingent on closing, on synergy attainment, or on any transaction metric.
4.2 Why Arrington is not the Clean Team
Arrington personnel are integration advisors with broad access to ACME's planning. That access is incompatible with the information barrier. The Clean Team is therefore engaged separately from Harpeth Clean Team Services, which has no other role in the transaction, and no Arrington personnel hold Clean Team credentials or receive restricted-category information in any form other than issued Release Memoranda.
5. Three Tiers of Contracting Paper
Twenty-eight of the seventy-three people on this program are not employees of either party. They reach the program through three distinct kinds of paper, and the distinction is not administrative — it determines who owns the outcome when the work goes wrong.
| Tier | Instrument | People | Who owns the outcome |
|---|---|---|---|
| Tier 1 | Consulting engagement SOW — Arrington Advisory Group | 17 | Supplier for named deliverables; ACME for all decisions |
| Tier 2 | Technology and specialist vendor SOWs — fixed price | 7 | Vendor, against a defined result |
| Tier 3 | Staffing firm SOWs under MSA — time and materials | 4 | ACME — the firm supplies capacity, not outcomes |
5.1 Tier 2 — technology and specialist vendors
| Vendor | Instrument | Scope and why fixed price |
|---|---|---|
| Harpeth Clean Team Services | Fixed-price SOW, pre-close | A defined analytical service with a defined end date. Fixed price is right because the scope is bounded by law and the engagement dissolves at closing. |
| Gallatin EDI Assurance | Fixed-price SOW, post-close | X12 transaction assurance across 834 enrollment, 837 claims, 835 remittance, 270/271 eligibility and 820 premium. A specialist result ACME cannot produce internally. |
| Microsoft Azure | Enterprise agreement plus BAA | Consumption-based platform, not a services engagement. Contracted by IT under the program's cloud strategy; requires an executed Business Associate Agreement before any protected health information reaches the platform. |
| Rutherford Cloud Operations | Managed service agreement, co-managed model | ⭐ Operations of the Azure estate during and after migration, on a contracted step-down from vendor-operated to ACME-operated. Requires a BAA, a three-party responsibility matrix as an exhibit, and transition-out terms — the exit is designed at signature, not discovered at renewal. |
5.2 Tier 3 — staff augmentation
Two Rivers Talent Partners supplies four data stewards under time-and-materials SOWs issued against a master services agreement. This is the one population on the program where ACME rents hours rather than buying a result, and Section 6 explains why that is the correct choice here and Section 8 explains what it obliges ACME to do.
6. Deliverable SOW versus Staff Augmentation
| Dimension | Deliverable / fixed-price SOW | Staff augmentation (T&M) |
|---|---|---|
| What is bought | A defined result | Qualified capacity |
| Who directs the work | Supplier | ACME |
| Who carries overrun | Supplier | ACME |
| Payment trigger | Written acceptance of a deliverable | Hours worked, approved on a timesheet |
| Right fit when | Scope is definable in advance and the result is separable from ACME's own work | Scope is continuous, volume-driven or unpredictable, and the work is inseparable from internal operations |
| Failure mode | Endless change orders when acceptance criteria were vague | Cost drifts with no deliverable to point at; co-employment exposure |
6.1 Why the data stewards are staff augmentation and not a fixed-price service
Clerical review of identity matches is continuous, volume-driven queue work whose size cannot be known until profiling is complete. It also requires the reviewers to work inside ACME's systems, against ACME's data governance rules, under an ACME supervisor's quality standards. Fixed-pricing that means pricing an unknown volume of an activity ACME must control — which produces either a padded price or a vendor incentivized to close the queue rather than to close it correctly.
7. Rate Card and Vehicle Selection
7.1 Rate card
Rates below are the blended basis on which deliverable fees are priced and against which time-and-materials hours are billed. They are inclusive of benefits, overhead and supplier margin.
| Category | Rate / hour | Applies to |
|---|---|---|
| Engagement lead / Program Manager | $265 | Tier 1 |
| Principal consultant | $245 | Tier 1 — identity resolution, core admin migration |
| Architect — integration, cloud | $230 | Tier 1 |
| Senior engineer / senior analyst | $195 | Tier 1 |
| Analyst — PMO, data quality, FinOps | $155 | Tier 1 |
| Offshore delivery manager | $95 | Tier 1 offshore |
| Offshore test lead | $80 | Tier 1 offshore |
| Offshore QA engineer | $65 | Tier 1 offshore |
| Specialist EDI analyst | Fixed price | Tier 2 — priced as a result, not an hour |
| Data steward | $68 | Tier 3 |
| Data steward supervisor | $92 | Tier 3 |
7.2 The offshore boundary
Offshore personnel work interface regression testing against de-identified and synthetic datasets. No member-level data leaves the United States, per Tennessee Department of Commerce and Insurance conditions and ACME privacy policy. This constraint is inherited, not negotiated, and it is the reason the offshore population is concentrated in interface testing rather than distributed across the program: interface testing is the substantial body of work that can be performed correctly without ever touching a real member record.
7.3 Vehicle selection rule
| If the work is… | Then contract it as… |
|---|---|
| A definable result, separable from ACME operations, with agreeable acceptance criteria | Deliverable or fixed-price SOW |
| A specialist capability ACME does not have and does not intend to build | Fixed-price SOW — buy the result |
| Continuous, volume-driven, or inseparable from internal operations and governance | Staff augmentation — and accept that ACME owns the outcome |
| Permanent capability the combined entity will need after the program ends | Neither — hire |
8. Co-Employment Guardrails
Staff augmentation personnel are employees of the staffing firm. Treating them as ACME employees creates worker-classification and co-employment exposure — a risk that lands on HR and Legal, and one a program manager should raise before Procurement discovers it.
| Prohibited | Required instead |
|---|---|
| Placing contractors on the ACME organization chart | Shown on the Resource Plan with contract vehicle and supplier named |
| Assigning ACME job titles or business cards | Supplier titles retained; access badges identify contractor status |
| Including contractors in employee performance review cycles | Performance feedback routed through the supplier's engagement manager |
| Direct participation in employee benefits, bonus or equity programs | Compensation is entirely the supplier's concern |
| Open-ended engagement with no defined end | Each SOW carries a term and an end date; extension is a decision, not a default |
| ACME managers approving contractor time off or setting personal work schedules | Supplier manages its own personnel; ACME specifies coverage requirements |
9. Contracting Across the Close
9.1 Who is the contracting party
| Instrument | Contracting party | Rationale |
|---|---|---|
| Arrington engagement SOW (this document) | ACME Health | ACME is the surviving entity and the buyer of the service. No transfer required at closing. |
| Harpeth Clean Team SOW | ACME Health, with Cumberland Valley counsel as a named beneficiary | The service protects both parties; the engagement ends at closing so no transfer arises. |
| Gallatin EDI Assurance SOW | ACME Health | Signed post-close. No transaction complication. |
| Two Rivers staffing SOWs | ACME Health | Signed post-close, because the work cannot lawfully begin before it. |
| Azure enterprise agreement and BAA | ACME Health | Pre-existing ACME relationship, expanded. The BAA must be confirmed to cover the enlarged member population. |
| Cumberland Valley's inherited contracts | Determined case by case | The material problem. Addressed in the Vendor & Contract Disposition Matrix, not here. |
9.2 The rule this program applied
Where a program instrument could be signed by ACME alone, it was — because ACME survives the transaction and a contract with the surviving entity needs no action at closing. Where the work could not lawfully begin until after closing, the paper was dated after closing rather than signed early in anticipation. Both choices trade a little speed for the elimination of a novation requirement.
9.3 What this program deliberately did not do
- Did not sign vendor consolidation agreements before closing. Consolidating Cumberland Valley's vendors onto ACME's contracts before ACME owned Cumberland Valley would be operational control of the target. Consents were prepared and held for post-close execution.
- Did not novate inherited contracts in anticipation. A novation executed before closing binds an entity that may never merge, and the counterparty consent obtained for it may not survive a changed closing date.
- Did not contract the data stewards early to secure availability. Tempting, and rejected: the work is unlawful before closing, and a staffing contract with nothing to do is either idle cost or an invitation to start early.
10. Register of Program Contracting Instruments
| Ref | Instrument | Tier | Vehicle | People | Status at Day 1 |
|---|---|---|---|---|---|
| ARR-2023-01 | Arrington Advisory Group — integration program management | 1 | Deliverable SOW | 17 | Active |
| HAR-2023-01 | Harpeth Clean Team Services — pre-close clean team | 2 | Fixed price | 4 | Dissolved at close |
| GAL-2023-01 | Gallatin EDI Assurance — X12 transaction assurance | 2 | Fixed price | 3 | Active |
| TWO-2023-01 | Two Rivers Talent Partners — data stewardship capacity | 3 | Staff aug (T&M) | 4 | Active |
| MSFT-EA | Microsoft Azure enterprise agreement and BAA | 2 | Consumption | — | BAA scope confirmation required |
11. Execution
This statement of work is not effective until executed by an authorized signatory of both parties and endorsed by ACME Legal. ⚠ Work performed before execution is performed at Supplier's risk and is not payable.
Related artifacts: 1 — Integration Charter (§8.2, delegated authority) · 5 — Clean Team Protocol · 14 — Resource Plan · 21 — Vendor & Contract Disposition Matrix · 33 — Data Steward SOPs & SLA