← M&A Integration Suite Pre-Close Control Document · Artifact 5 · how to read this suite

Clean Team Protocol

Download Word

This Protocol governs the handling of competitively sensitive information between ACME Health and Cumberland Valley Health Plan during the period between signing of the definitive agreement (February 13, 2023) and closing (September 29, 2023). During that period the two organizations remain, in law, independent competitors in overlapping Tennessee markets. This document establishes the information barrier, the Clean Team that operates behind it, the categories of data that may not cross it, and the form in which analysis may be released to the integration program. Issued by the Office of the General Counsel, ACME Health; countersigned by counsel for Cumberland Valley. Effective March 6, 2023 and automatically dissolved at closing. Annex A was appended at program close on April 30, 2025 and is dated separately; the Protocol itself is reproduced as issued.

Table of Contents

Part I — Why This Document Exists
  1. Purpose, Authority and Effective Period
  2. The Legal Basis — Why Two Merging Companies Stay Apart
  3. Competitively Sensitive Information: Definitions
Part II — The Barrier
  1. Clean Team Composition and Independence
  2. The Wall: Technical and Physical Controls
  3. Permitted Outputs — Conclusions, Not Data
  4. Request, Review and Release Workflow
Part III — Conduct and Wind-Down
  1. Gun-Jumping: Prohibited Pre-Close Conduct
  2. Dissolution at Close and Handover
  3. Annex A — Program Consequence (added at close)
Part I — Why This Document Exists

1. Purpose, Authority and Effective Period

A signed merger agreement does not make two companies one. Between signing and closing, ACME Health and Cumberland Valley Health Plan continue to operate as separate legal entities, continue to compete for the same employer groups and the same provider contracts, and continue to be treated by antitrust regulators as competitors. Everything the integration program needs to know about Cumberland Valley — its rates, its membership, its provider economics — is precisely the information two competitors are not permitted to exchange.

This Protocol resolves that conflict. It does not resolve it by waiting: a program that learns nothing until closing has no plan on Day 1. It resolves it by routing sensitive information to a small, contractually isolated group that analyzes it and returns conclusions rather than data.

AttributeProvision
Issuing authorityL. Hollingsworth, General Counsel, ACME Health
CountersignedM. Sheffield, General Counsel, Cumberland Valley Health Plan
EffectiveMarch 6, 2023 (three weeks after signing)
ExpiresAutomatically at closing — September 29, 2023
BindsAll personnel of both entities, all advisors, and all vendors engaged on the transaction
Program ownerC. Tyrrell, Program Manager, Integration Management Office
EscalationAny suspected breach goes to both General Counsel within 24 hours — not to the IMO
The Program Manager does not own this document, and that is deliberate. The IMO is the largest single consumer of Cumberland Valley information and therefore has a structural incentive to read the barrier permissively. Authority sits with Legal on both sides; the IMO's role is to comply, to route requests correctly, and to plan around what it is not allowed to know.

2. The Legal Basis — Why Two Merging Companies Stay Apart

Two distinct legal regimes operate in the pre-close window, and they are frequently confused.

2.1 The waiting period

The Hart-Scott-Rodino Act requires notification of qualifying transactions to the federal antitrust agencies and imposes a waiting period before the parties may close. For this transaction the waiting period expired on May 30, 2023 without a second request. Separately, because both parties are regulated insurers, the Tennessee Department of Commerce and Insurance had to approve a Form A change-of-control filing, which it did on September 12, 2023.

Clearance is permission to close. It is not permission to combine early. This is the single most common misunderstanding on an integration program. HSR clearance arrived four months before closing, and the effect on this Protocol was none whatsoever. Until the transaction actually closes, the parties remain competitors and the barrier stands.

2.2 The conduct rule

Independent of any filing, Section 1 of the Sherman Act prohibits agreements between competitors that restrain trade. Two health plans exchanging current premium rates, negotiated provider reimbursement, or forward bid strategy is a per se problem regardless of whether they have a signed merger agreement. The merger agreement is not a defense; if the deal fails to close, the parties have simply exchanged competitive intelligence.

2.3 Gun-jumping

Gun-jumping is the acquirer exercising operational control over the target before it owns it, or the parties behaving as a combined entity before they are one. It is a conduct offense, not a filing offense, and it is what this Protocol is chiefly designed to prevent. Section 8 lists the specific prohibitions that applied to this program.

3. Competitively Sensitive Information: Definitions

Not all target information is restricted. Over-restricting is its own failure — it starves the plan and pushes discovery past close, where it costs far more. The categories below were agreed by both counsel and are the operative list.

CategoryClassificationHandling
Current and forward premium rates, rating factors, bid strategyRestrictedClean Team only. No release in any form that permits reconstruction of a rate.
Negotiated provider reimbursement rates and fee schedulesRestrictedClean Team only. Aggregate variance bands may be released (see 6.2).
Employer-group-level membership, pricing and renewal termsRestrictedClean Team only. No named accounts to ACME personnel.
Member-level enrollment, claims and clinical dataRestrictedClean Team only, and additionally protected as PHI under HIPAA.
Sales pipeline, competitive win/loss, broker compensationRestrictedClean Team only.
System inventories, architecture diagrams, interface catalogsOpenDirect to IMO. Technical topology is not competitively sensitive.
Vendor contracts, license terms, change-of-control clausesLimitedTo Legal and Vendor & Contract workstream. Pricing redacted where the vendor also serves ACME.
Org charts, headcount by function, role descriptionsOpenDirect to IMO. Required for Day 1 planning and retention design.
Individual compensation and performance recordsLimitedHR and Legal only. Not a competition issue — an employment-privacy one.
Aggregate financial statements, statutory filingsOpenAlready public or already diligence-disclosed.
Two different reasons appear in the same table, and conflating them causes errors in both directions. Provider rates are restricted because of antitrust. Member data is restricted because of antitrust and HIPAA. Compensation records are restricted for employment privacy and are not an antitrust matter at all. A control designed for one does not discharge the other — which is why the member-data rows survived closing as HIPAA controls even after the antitrust barrier dissolved.
Part II — The Barrier

4. Clean Team Composition and Independence

The Clean Team is provided by Harpeth Clean Team Services under a fixed-price statement of work. No member is an employee of either party.

MemberRoleAccess
P. MarchettiClean Team LeadFull restricted set; sole signatory on release memoranda
K. OyelaranAnalyst — pricing and provider network economicsRates, fee schedules, network composition
B. SandovalAnalyst — membership and claims volumeEnrollment, claims volumetrics, employer group detail
H. TillinghastClean Team Counsel (outside)Full restricted set; reviews every release before issue

4.1 Why a third party rather than ACME employees

A Clean Team may be staffed with employees of the acquirer who are walled off from commercial decision-making. That model works where the acquirer is large enough to have people with no line responsibility in the overlapping market. It was rejected here for three reasons:

The cost of the third-party choice was real and was accepted knowingly. Harpeth's analysts learned Cumberland Valley's book in detail and then, by design, walked away at closing. Their knowledge did not transfer to the people who had to execute the integration — only their written conclusions did. Section 10 describes what that meant for the program.

5. The Wall: Technical and Physical Controls

ControlImplementation
Segregated data roomSeparate virtual data room instance, provisioned by Cumberland Valley's counsel. Access list is four named individuals. No ACME or Cumberland Valley operational personnel hold credentials.
No download, no printView-only rendering, watermarked with viewer identity and timestamp. Bulk export disabled at the tenant level.
Analysis environmentHarpeth-controlled workspace, not connected to either party's network. Working files never leave it.
Access loggingEvery document view logged and retained. Log reviewed monthly by both counsel.
Individual undertakingsEach Clean Team member signs a personal confidentiality undertaking naming the restricted categories and surviving the engagement by five years.
No reverse flowClean Team members receive no ACME rate, bid or provider-economics data either. The barrier runs both directions.
Communication channelRequests and releases move through counsel-managed channels only. Direct email between Clean Team analysts and workstream leads is prohibited.
The bidirectional rule is the one most often missed. A Clean Team that holds Cumberland Valley's rates and also holds ACME's rates has not eliminated the exchange — it has centralized it in four people. The undertaking is that neither party's competitively sensitive data reaches personnel holding the other's.

6. Permitted Outputs — Conclusions, Not Data

The Clean Team's product is a numbered Release Memorandum. What may appear in one is defined by form, not by topic.

6.1 The general rule

A release may state a conclusion, a range, a rank order, a variance, or a directional finding. It may not state, or permit arithmetic recovery of, an individual rate, an individual account's terms, or a named provider's reimbursement.

6.2 Worked examples

Not permittedPermitted equivalent
"Cumberland Valley reimburses Sumner Regional at 118% of Medicare for inpatient medical.""Across the top ten facilities by volume, target inpatient reimbursement sits in a band moderately above ACME's, with the widest variance in inpatient medical."
A spreadsheet of the 40 largest employer groups with membership and renewal dates."Group business is concentrated: the ten largest accounts carry approximately a third of commercial membership. Renewals cluster in the fourth quarter."
"Target's small-group rates run 6.2% below ACME's in Davidson County.""Target small-group pricing is below ACME's in the shared counties. Post-close rate convergence will require an actuarial workplan; treat as a Day 100+ item."
Member-level extract for duplicate analysis against ACME's enrollment file."Internal duplicate rate within the target's own membership is materially higher than the deal model assumed. Cross-entity overlap cannot be measured pre-close."
Watch the fourth row — it is the origin of this program's central problem. The Clean Team could see Cumberland Valley's data quality and did report a concern. What it could not do was match Cumberland Valley members against ACME members, because that requires member-level data from both sides in one place, which is exactly what the barrier forbids. The true scale of the identity-resolution problem is therefore unknowable until after closing, and the program plans on the basis that post-close profiling may return materially worse figures than the deal model assumed.

6.3 Release register

Fourteen Release Memoranda were issued between March and September 2023. Selected entries:

RefIssuedSubjectDisposition
CT-0012023-03-20Membership composition by segment and countyReleased to IMO, Actuarial
CT-0032023-03-28Provider network overlap — count and directional rate varianceReleased to Provider Network workstream, redacted form
CT-0052023-04-19Core administration platform — transaction volumes and batch windowsReleased in full; volumetrics deemed non-sensitive
CT-0062023-05-02Enrollment data quality — preliminary indicatorsReleased with qualification — internal duplicates only; cross-entity overlap not assessable
CT-0082023-06-14Vendor spend overlap by categoryReleased to Vendor & Contract workstream, pricing bands only
CT-0092023-06-27Request: employer-group renewal calendar with named accountsRefused — named accounts not releasable; reissued as CT-010
CT-0102023-07-11Renewal seasonality, unnamed, quarterly bucketsReleased to IMO
CT-0142023-09-22Closing handover index — catalog of restricted holdingsHeld by counsel; released to ACME at closing

7. Request, Review and Release Workflow

  1. Raise. A workstream lead submits a Clean Team Information Request to the IMO stating the decision the information will support. Requests that cannot name a decision are returned — curiosity is not a basis for release.
  2. Triage. The IMO checks the request against the Section 3 categories. Open-category items are routed directly to Cumberland Valley and never reach the Clean Team.
  3. Counsel review. Both General Counsel review restricted-category requests. Either may refuse.
  4. Analysis. The Clean Team performs the work inside the walled environment.
  5. Form review. H. Tillinghast reviews the draft release for reconstruction risk — whether the stated conclusion, combined with what the recipient already knows, would permit recovery of a restricted figure.
  6. Release. Issued as a numbered memorandum to a named distribution list. Onward circulation is prohibited.
  7. Register. Logged in the release register, which is retained as the evidentiary record.
Reconstruction risk is the step that requires judgment rather than rules. Two individually permissible releases can combine into an impermissible one: a release stating aggregate network spend and a later release stating member counts by facility may together yield an average rate. This is why a single reviewer sees every release, and why the register exists — the question is never "is this memo acceptable" but "is this memo acceptable given the thirteen before it."
Part III — Conduct and Wind-Down

8. Gun-Jumping: Prohibited Pre-Close Conduct

The following were prohibited to both parties until closing. Each was a live question raised by a workstream during the pre-close period.

ProhibitedPermitted alternative
ACME directing Cumberland Valley operational decisions, staffing or spendConsultation rights under the merger agreement for out-of-ordinary-course actions above defined thresholds
Joint pricing, coordinated bids, or allocating accounts or territories between the partiesNothing. Both parties bid independently through closing, including against each other.
Migrating data, connecting networks, or provisioning cross-entity system accessDesign, document and stage the work. Build the landing zone in ACME's own tenant. Execute nothing that touches target data.
Making offers to, or terminating, Cumberland Valley employeesDesign retention structures and Day 1 org models. Communicate them only after closing.
Terminating or renegotiating Cumberland Valley vendor contractsInventory contracts, identify change-of-control clauses, prepare consent requests for post-close execution
Joint customer or provider communication implying a combined entitySeparate, factually accurate transaction announcements approved by both counsel
The permitted column is what makes an aggressive Day 1 possible. The barrier restricts execution, not preparation. This program used the seven-month pre-close window to complete the Integration Management Plan, the Day 1 Readiness Plan, the cutover runbook, the Azure landing zone design, and the full vendor contract sweep — none of which required a single restricted data element. A program that treats the pre-close period as dead time arrives at closing with seven months of work still ahead of it.

9. Dissolution at Close and Handover

At closing on September 29, 2023 the antitrust basis for the barrier disappeared: the parties became one entity and could no longer conspire with themselves. The Protocol terminated automatically. The wind-down sequence:

Two restrictions did not dissolve, and the workstreams had to be told so explicitly. HIPAA controls on member data survived closing untouched — the merger changed the covered entity, not the obligation. And the Tennessee DOI's conditions attached to the Form A approval, including limits on where member-level data may be processed, remained binding. The IMO issued a standing note to all workstreams on October 2, 2023 stating that "the Clean Team is dissolved" does not mean "the data is open." Any proposal to process member-level data outside the United States is therefore barred by the Form A conditions regardless of the antitrust position.

10. Annex A — Program Consequence: What the Barrier Cost Us

This annex was added at program close on April 30, 2025. It is not part of the Protocol as issued on March 6, 2023. The Protocol above is reproduced unchanged, including judgments that later proved incomplete. This annex is appended because a control document is most useful to the next program when it carries an honest account of what the control cost, written by people who know how it turned out. Everything above this line was written without that knowledge.

The barrier was correctly designed and correctly operated. It also imposed a cost, and that cost shaped the entire program. This annex records both.

10.1 The deal-model estimate was built blind, by law

The integration estimate carried in the deal model — a base of $42.0M with 15% contingency — was prepared without any ability to inspect member-level data or to test Cumberland Valley's records against ACME's. In estimating terms it was an AACE Class 5 estimate: concept screening, expected accuracy roughly −20% to +50% at best. The high contingency was not conservatism; it was the arithmetically correct response to a legally imposed information deficit.

This is the point an interviewer should press on, and it has a clean answer. The pre-close estimate was not wrong because the estimators were careless. It was wrong within its stated tolerance because the estimators were forbidden to look. Antitrust law required the acquirer to commit $1.2B to a transaction while barred from examining the data that would determine the cost of integrating it. Once that is understood, the post-close re-baseline of January 22, 2024 stops being an embarrassment and becomes what it actually was — the first estimate produced with the data in hand, moving the base to $51.8M and the contingency down to 8% because the uncertainty it covered had been resolved rather than assumed away.

10.2 What could not be known, and when it surfaced

Unknowable pre-closeSurfacedConsequence
Cross-entity member overlap and duplicate rateData Profiling Report, 2024-04-15Drove CR-004 — three-month TSA extension, $3.45M, 13 weeks
True condition of target address and identifier fieldsData Profiling Report, 2024-04-15Clerical review band widened; data steward staffing increased
Provider contract detail sufficient to model network rationalizationPost-close, October 2023Network workstream replanned; no cost impact
Account-level renewal exposure during transitionPost-close, October 2023Member Services retention plan revised before Day 100

Two change requests trace directly to constraints recorded in this Protocol. CR-003, which proposed staffing data stewards offshore to relieve the clerical review queue, was rejected on the Form A processing conditions described in Section 9 — the standing note issued on October 2, 2023 was the basis. CR-004, the three-month TSA extension, followed from the identity-resolution scale that Section 6.2 records as unknowable before closing.

10.3 What we would do differently

The defensible summary. The barrier worked: no restricted information reached operational personnel, no gun-jumping allegation arose, and the Form A and HSR processes completed without incident. The barrier also guaranteed that the program's largest risk could not be quantified until six months after the money was committed. Both statements are true, and a program that can hold both is describing what actually happened.

Related artifacts: 1 — Integration Charter · 6 — Regulatory Approval Tracker · 7 — Due Diligence Findings · 31 — Data Profiling Report · 44 — Change Control Log