GuideMergers & Acquisitions

Clean teams and gun-jumping: what deal teams may share before closing

When buyer and target compete, two separate legal risks shape what can happen before closing: exchanging competitively sensitive information, and integrating the businesses before clearance. A clean team lets a small, walled-off group examine sensitive data and pass only safe outputs to the deal team. This guide explains both risks, how to design the team and its agreement, and the technology issues that standard protocols often miss.

Reviewed 6 min read

On this page
  1. Information exchange and premature integration are separate risks
  2. Information that usually counts as competitively sensitive
  3. Setting up a clean team, step by step
  4. How sensitive data moves through a clean team
  5. Provisions a clean team agreement should contain
  6. Pre-closing integration work: generally allowed or wait for clearance
  7. Technology issues standard protocols miss
  8. A hypothetical overlap analysis between two software competitors
  9. Questions and answers
  10. Sources

Information exchange and premature integration are separate risks

Teams often treat these as one rule. They are not, and a protocol that handles only one leaves the other open.

AspectUnlawful information exchangeGun-jumping (premature integration)
What it isCompetitors sharing sensitive information that could reduce competition between themThe buyer taking control of, or coordinating with, the target before clearance
Main rulesSection 1 of the Sherman Act in the US; Article 101 TFEU in the EU, explained in the Commission's guidelines on horizontal cooperation3The Hart-Scott-Rodino Act waiting period in the US1; the standstill obligation in Article 7 of the EU Merger Regulation2
When it can ariseAt any point, including if the deal never closesBetween signing (or filing) and clearance or the end of the waiting period
Typical exampleThe buyer's sales team receives the target's customer-level pricesThe buyer approves the target's customer bids or migrates its systems before clearance
ConsequencesCompetition-law liability for both partiesUnder the EU Merger Regulation, fines of up to 10% of aggregate turnover2; in the US, civil penalties

Information that usually counts as competitively sensitive

The Commission's guidelines treat pricing information as generally sensitive and list costs, capacity, production, quantities, market shares, customers and plans to enter or exit markets as potentially sensitive3. In deal work this typically covers:

0 of 6 checked

Setting up a clean team, step by step

  1. Decide what needs clean-team treatment

    With counsel, sort requested information into what the deal team can see, what only the clean team can see, and what nobody sees before clearance.

    Output
    Information classification
    Owner
    Antitrust counsel

  2. Choose the members

    Use outside advisers, buyer employees with no pricing, sales or strategy role, or both. Members should not be people who will make competitive decisions if the deal fails.

    Output
    Approved member list
    Owner
    Counsel and deal lead

  3. Sign the clean team agreement

    Every member and their employer signs before receiving access, and new members are added only through the approval process.

    Output
    Signed agreements
    Owner
    Counsel

  4. Configure the data room

    Create segregated folders, grant access by named individual, disable downloads where practical and keep access logs.

    Output
    Restricted data-room area
    Owner
    Data-room administrator

  5. Review outputs before release

    Clean-team reports are aggregated, anonymized or redacted, then reviewed by counsel before the deal team receives them.

    Output
    Released summaries
    Owner
    Clean team, then counsel

  6. Close down properly

    On closing, or if the deal fails, return or destroy raw materials and confirm in writing, as the agreement requires.

    Output
    Destruction certificates
    Owner
    Each member

How sensitive data moves through a clean team

Uploads raw dataNamed-user accessDraft aggregated reportRedaction requestsApproved summaryWider release01Target02Restricted dataroom03Clean team04Antitrustcounsel05Buyer deal team
  1. Target

    Uploads sensitive material only to the restricted area.

  2. Restricted data room

    Named-user access with logs.

  3. Clean team

    Analyzes raw data and drafts aggregated findings.

  4. Antitrust counsel

    Reviews every output before release.

  5. Buyer deal team

    Sees only approved outputs until clearance.

  1. Target to Restricted data roomUploads raw data
  2. Restricted data room to Clean teamNamed-user access
  3. Clean team to Antitrust counselDraft aggregated report
  4. Antitrust counsel to Clean teamRedaction requests
  5. Antitrust counsel to Buyer deal teamApproved summary
  6. Restricted data room to Buyer deal teamWider release
Conceptual flow of information through a clean team. The final release of raw data to the deal team happens only after clearance and closing.

Provisions a clean team agreement should contain

0 of 7 checked

Pre-closing integration work: generally allowed or wait for clearance

The dividing line is between planning and implementing. Counsel sets the exact boundary for each deal.

  • If

    You want to design the future organization, system architecture or migration plan on paper.

    Then

    Generally allowed, using information the deal team or clean team may lawfully see.

    Planning does not change how either business competes today.

  • If

    The buyer wants to approve the target's prices, bids or customer contracts.

    Then

    Wait. Interim covenants may require consent for extraordinary actions, but not for ordinary-course commercial decisions.

    Controlling the target's commercial conduct before clearance is the classic form of gun-jumping.

  • If

    Sales teams want to visit customers together or announce joint offers.

    Then

    Wait until closing.

    Joint selling coordinates the two businesses in the market.

  • If

    IT wants to connect networks, give the buyer admin access or start migrating the target's systems.

    Then

    Wait, or limit work to preparation that can be reversed and does not give the buyer operational control.

    System control is a form of operational control.

Technology issues standard protocols miss

Customer datasets are the most common problem. Integration teams want CRM exports to measure overlap; a clean team can match records and report overlap by segment without revealing named accounts. Pricing algorithms are another: model parameters, feature weights or training data can reveal pricing strategy as clearly as a price list, so treat them as sensitive.

Shared system access needs explicit rules. Pre-closing accounts in the target's systems, even read-only, can expose live commercial data and look like operational control. AI tools add a new route for leakage: uploading clean-team material to a general-purpose AI service may store it outside the agreed controls. The protocol should name approved tools, as ColdAI's work on AI-assisted diligence assumes.

A hypothetical overlap analysis between two software competitors

Questions and answers

Can a clean team include the buyer's own employees?

Often yes, if they have no role in pricing, sales, marketing or strategy and will not move into one for an agreed period. Many deals combine outside advisers, who handle the most sensitive analysis, with a few internal specialists such as integration or IT architects. Counsel approves each member against the agreed criteria.

What happens to clean-team information if the deal does not close?

The agreement should require members to return or destroy the materials and confirm this in writing, and should restrict members from using what they learned. This matters most when the deal fails, because the buyer and target remain competitors and any later use of the information could raise competition-law concerns.

Is integration planning itself a form of gun-jumping?

Generally no. Planning the future organization, systems and processes is normal and expected before closing. The risk lies in implementation: transferring control, coordinating commercial decisions, or merging operations before clearance or before the waiting period ends. Keep plans on paper and ask counsel where the line falls.

When can the full deal team see the clean team's raw data?

Usually only after the required clearances are received and the transaction closes, when the two businesses are under common ownership. Before then, the deal team works from approved summaries. Plan integration so that the most detailed work can start immediately after closing, using the clean team's preparation.

Sources

  1. Premerger notification and the merger review process — US Federal Trade Commission · checked 10 October 2026
  2. Council Regulation (EC) No 139/2004 on the control of concentrations between undertakings (EU Merger Regulation), Articles 7 and 14 — EUR-Lex · checked 10 October 2026
  3. Guidelines on the applicability of Article 101 TFEU to horizontal co-operation agreements (2023/C 259/01) — European Commission via EUR-Lex · checked 10 October 2026

More in Mergers & Acquisitions

Back to Mergers & Acquisitions

Next step

Plan integration work your counsel can sign off before closing

Tell us what the integration team needs to know and what counsel has ruled out. We will suggest aggregation methods, data-room controls and a planning sequence that fit inside those limits.

Discuss clean-team planning