Gun-Jumping Risk in M&A: How to Integrate Safely Before Closing

Every signed M&A transaction involves a period during which two legally separate and, in most cases, still-competing companies must cooperate on diligence, integration planning, and transaction logistics while maintaining the competitive independence that antitrust law requires until the deal actually closes. That period, the time between signing and regulatory clearance and closing, is governed by a set of antitrust rules that are widely misunderstood, inconsistently applied, and actively enforced by the Federal Trade Commission and the Department of Justice. The concept of "gun-jumping" refers to conduct during this pre-closing window that prematurely transfers operational control, eliminates competition, or coordinates competitive behavior between the parties before they have legal authority to operate as a combined entity.

The consequences of gun-jumping are not theoretical. Both the FTC and DOJ have brought enforcement actions resulting in civil penalties against parties whose pre-closing conduct, whether through aggressive interim operating covenants, operational integration before clearance, or unstructured information exchange, crossed the line from permissible deal execution into prohibited pre-merger coordination. Those actions have involved buyer-directed price changes at the seller, joint customer solicitation, shared sales teams, coordinated hiring decisions, and overly broad consent requirements that gave the buyer effective veto power over the seller's ordinary-course business decisions.

This sub-article is part of the HSR Act Filings and Antitrust Merger Review in M&A: A Deal Lawyer's Field Guide. It covers the two legal theories under which gun-jumping liability arises, the categories of information that require clean team handling, how to structure integration planning workstreams that stay within permissible boundaries, the specific risk areas around customer and vendor outreach, hiring, board observer arrangements, and interim operating covenant drafting, the penalty structure for violations, the enforcement history that defines the outer limits of permissible conduct, and the compliance infrastructure that protects parties during the pre-closing period.

Acquisition Stars advises buyers, sellers, and their boards on pre-closing antitrust compliance, clean team design, integration planning protocols, and gun-jumping risk assessment. Nothing in this article constitutes legal advice for any specific transaction.

Two Gun-Jumping Theories: HSR Section 7A and Sherman Section 1

Gun-jumping liability flows from two independent legal frameworks that operate in parallel during the pre-closing period. Understanding the distinction between them is foundational to structuring a compliant integration program, because the analysis, the prohibited conduct, and the enforcement mechanisms differ in material ways.

The HSR Act Section 7A theory prohibits the acquisition of voting securities or assets before the applicable waiting period has expired or been terminated. The HSR Act requires that parties to qualifying transactions file premerger notification and wait for the agencies to complete their initial review before closing. Gun-jumping under this theory occurs when one party effectively acquires "beneficial ownership" of the target's assets or business before filing is made or before the waiting period expires. The concept of beneficial ownership in this context extends beyond formal legal title: it includes arrangements that give the buyer operational control over the target's business decisions, the right to direct the target's competitive conduct, or the economic benefit of the target's operations before the legal transfer of ownership. Overly broad interim operating covenants, shared operational resources, and buyer-directed pricing changes at the seller have each been found to constitute premature acquisition of beneficial ownership.

The Sherman Act Section 1 theory applies a different framework. Section 1 prohibits agreements between competitors that unreasonably restrain trade. When two competing businesses agree to coordinate their competitive conduct, whether on pricing, output, customer allocation, or market strategy, that agreement is potentially a Section 1 violation regardless of whether it occurs in the context of a pending merger. The merger agreement itself is not the problem: agreeing to sell and buy a business does not violate Section 1. What violates Section 1 is the ancillary conduct that the parties engage in during the pre-closing period if that conduct constitutes competitive coordination: sharing pricing information that affects current bids, jointly allocating customers, coordinating sales team activities, or agreeing to hold prices steady in a way that eliminates the competitive pressure each party would otherwise face from the other. The critical distinction is that Section 1 liability can arise even in transactions that are not HSR-reportable, because Section 1 applies to any agreement between competitors regardless of deal size.

The two theories can apply to the same conduct simultaneously. A buyer who directs the seller's pricing decisions before closing may violate Section 7A (by exercising operational control before HSR clearance) and Section 1 (by coordinating competitive pricing between two companies that remain competitors until closing). Counsel must analyze proposed pre-closing conduct under both frameworks before advising that it is permissible.

Permissible vs. Impermissible Pre-Closing Conduct

The line between permissible pre-closing conduct and gun-jumping is not always bright, and it is drawn differently depending on the competitive relationship between the parties, the nature of the information exchanged, and the operational effect of the conduct at issue. The general framework distinguishes between conduct that is reasonably necessary to preserve the value of the transaction and conduct that eliminates competition between the parties before the legal authority to do so exists.

Permissible pre-closing conduct includes due diligence information exchange through properly structured clean teams, internal integration planning that does not involve the exchange of competitively sensitive information or operational coordination, customer and employee notifications that describe the pending transaction without coordinating on pricing or competitive terms, and the ordinary administration of the transaction including regulatory filings, third-party consent solicitations, and legal and financial advisory work. Seller employees may continue to operate their business in the ordinary course. Buyer employees may plan for integration. The two groups may not coordinate on pricing, customer strategy, bidding, sales activity, or competitive positioning.

Impermissible pre-closing conduct includes any operational coordination that treats the two entities as a combined business before closing. Sharing live pricing decisions between the seller's sales team and the buyer's sales team is impermissible. Having buyer employees accompany seller sales personnel on customer calls is impermissible, except in narrowly defined transition contexts with appropriate restrictions. Allowing buyer management to direct or approve seller operational decisions beyond the scope of legitimate consent rights is impermissible. Combining sales pipelines or customer databases for joint prospecting is impermissible. Coordinating hiring decisions or compensation adjustments between the two entities in a way that affects the competitive labor market is impermissible in many circumstances.

The key analytical question for any proposed pre-closing activity is whether it could affect competitive behavior between the parties before closing. If the answer is yes, the activity requires clean team structuring, deferral to post-closing, or agency guidance before it proceeds. If the answer is no because the activity is purely administrative or involves information that is not competitively sensitive, the activity can generally proceed with appropriate documentation.

Interim Operating Covenants in the Purchase Agreement

Interim operating covenants in the purchase agreement are the contractual mechanism by which the buyer protects the value of the acquisition target during the pre-closing period. Standard covenants require the seller to operate in the ordinary course of business consistent with past practice and prohibit the seller from taking significant actions outside that ordinary course without the buyer's consent. These covenants serve a legitimate purpose: they protect the buyer from value destruction between signing and closing by preventing the seller from making material changes to the business that the buyer did not underwrite in its valuation.

The gun-jumping risk in interim operating covenants arises when the consent rights granted to the buyer are so broad that they effectively give the buyer operational control of the seller's business before HSR clearance. Courts and agencies evaluate whether the buyer has, through the combination of affirmative operating covenants and consent rights, become the de facto operator of the seller's business during the pre-closing period. Consent rights that require buyer approval for ordinary-course decisions, that give the buyer authority to direct specific competitive choices such as pricing responses to customer requests, or that allow the buyer to veto routine employee compensation decisions are the category most likely to be found to constitute premature acquisition of beneficial ownership.

Drafting interim operating covenants for gun-jumping compliance requires identifying which categories of seller action are sufficiently material to warrant buyer consent and which are ordinary-course decisions that the seller should retain full authority to make. Material contract thresholds, capital expenditure limits, acquisition and disposition restrictions, and debt incurrence caps are standard and generally defensible. Pricing approval rights, customer negotiation consent requirements, and hiring approval rights for below-senior-management positions are more problematic and should be avoided or narrowly cabined. Where the parties are direct competitors, counsel should review the full covenant package specifically for gun-jumping risk before the purchase agreement is executed.

The standard should be that the seller retains genuine authority to make day-to-day operational decisions affecting competition, with the buyer's consent reserved for decisions that are material to the value of the enterprise and that cannot reasonably be deferred to post-closing. Any consent right that the buyer intends to use to direct the seller's competitive behavior should be removed from the agreement or restructured to require only notification rather than approval.

Competitively Sensitive Information: Categories and Handling

Identifying which categories of information are competitively sensitive is the first step in designing a clean team protocol and in evaluating whether any proposed information exchange during the pre-closing period presents gun-jumping risk. The analysis is market-specific: information that is competitively sensitive in a market with few competitors and rapid price movements may be less sensitive in a fragmented market with slow-moving commodity pricing. Counsel must assess sensitivity in the context of the specific competitive dynamics of the relevant market.

The core categories of competitively sensitive information that require clean team handling in most transactions are: current and forward-looking pricing information at the customer-specific, product-specific, or transaction-specific level; discount structures, rebate schedules, and promotional pricing terms; customer identity and customer-specific contract terms; active and pending bid or proposal information, including bid strategies and win-loss data; production capacity and output levels; cost structures at a level of detail that would enable the receiving party to predict pricing or competitive responses; supply chain and vendor pricing arrangements that affect competitive positioning; and R&D pipeline information that reveals product strategy or competitive positioning in future markets.

Information that is generally permissible to share without clean team restrictions includes: aggregated financial statements that do not reveal customer-specific, product-specific, or transaction-specific data; headcount by function without compensation detail; real estate leases and facilities information; general insurance and benefits program terms; corporate governance documents; public regulatory filings; and environmental and compliance records that are not competitively sensitive. The dividing line is not the format of the document but the competitive use to which the information could be put by the receiving party's operational personnel.

Handling procedures for competitively sensitive information should include: access limited to clean team members identified by name; physical and electronic access controls; marking of documents shared under the protocol; written restrictions on use and disclosure; prohibition on disclosure to operational personnel, sales personnel, or anyone responsible for competitive decisions at either party; and a process for destroying or returning materials at the end of the pre-closing period for any personnel who do not transfer to the combined entity.

Clean Teams: Structure, Rules, and Documentation

A clean team is a group of individuals, typically drawn from each party's legal, financial, and strategic advisory teams, who are designated to receive and analyze competitively sensitive information during the pre-closing period. Clean team members are prohibited from disclosing the information they receive to their colleagues who remain responsible for competitive decisions. The clean team serves as a firewall: it allows the deal team to conduct thorough due diligence on the target's competitive position without exposing that information to the people who could use it to compete more effectively against the target before closing.

Clean team membership should be defined at the outset of due diligence and documented in a written clean team agreement signed by each member. The agreement should specify the information categories subject to the protocol, the access controls applicable to clean team materials, the permitted uses of the information (due diligence and integration planning only, not operational decision-making), the restrictions on disclosure to non-members, and the obligations upon termination of the pre-closing period. Outside counsel and financial advisors who receive clean team information should also execute the agreement or be subject to equivalent restrictions under their engagement terms.

The clean team structure must be enforced in practice, not just on paper. Clean team meetings should be logged. Access to the clean team data room should be restricted by user credential and monitored. Documents produced in clean team analysis should be marked as clean team restricted. If a clean team member transfers to a role with competitive responsibilities at either party, their continued access to clean team materials should be reviewed. Clean teams that are created at signing but whose access restrictions erode over the course of a long regulatory review period provide diminishing protection as the pre-closing period extends.

The documentation of the clean team protocol, including the agreement, the member list, the access logs, and any counsel guidance on the scope of the protocol, should be retained after closing. If the agencies subsequently investigate pre-closing conduct, the existence of a well-documented clean team is material evidence of the parties' good-faith effort to comply with the applicable antitrust restrictions.

Integration Planning Workstreams That Are Safe

Integration planning is one of the most valuable activities that parties can undertake during the pre-closing period, and it is also one of the areas most prone to inadvertent gun-jumping if not properly structured. The goal of pre-closing integration planning is to enable the combined entity to realize synergies and operate effectively from day one of combined operations. The constraint is that integration planning must not require the exchange of competitively sensitive information or the operational coordination of competitive activities before closing.

Safe integration planning workstreams are those that operate at a level of abstraction that does not require the parties to share the specific competitively sensitive information in the core restricted categories. Systems integration planning can proceed by identifying the technical requirements for connecting the two entities' IT infrastructure without sharing customer databases or pricing systems. Organizational design planning can proceed by identifying the reporting structure and functional responsibilities of the combined entity without specifying individual compensation decisions. Real estate and facilities planning can proceed by identifying which locations will be retained, consolidated, or exited without sharing specific lease terms or negotiating jointly with landlords. Finance and accounting integration can proceed by identifying the accounting systems, reporting cadences, and policy alignment required without sharing disaggregated financial data at the customer or product level.

Integration planning workstreams that require competitive information should be routed through the clean team. Synergy analysis that requires understanding the target's customer-specific pricing or the buyer's competitive win rates requires clean team handling. Product line rationalization planning that requires understanding the competitive overlap at the SKU or customer level requires clean team handling. Any workstream that involves personnel from both parties discussing how the combined entity will compete in the market after closing requires clean team structuring or should be deferred until closing is imminent and the regulatory outcome is certain.

Each integration workstream should designate a legal lead who is responsible for assessing whether proposed activities require clean team handling. That assessment should be documented. Decisions to defer specific integration planning activities to post-closing should also be documented so that the parties can demonstrate that they were deliberately managing gun-jumping risk rather than proceeding without awareness of the constraints.

Customer and Vendor Outreach Coordination

Customer and vendor outreach during the pre-closing period is a necessary component of every significant transaction: key customers want to understand what the transaction means for their relationship, vendors want to know whether the combined entity will honor existing commitments, and many contracts require notification or consent in connection with a change of control. Managing this outreach without creating gun-jumping liability requires careful attention to who is communicating, what is being communicated, and whether the outreach is coordinating the parties' competitive positions rather than simply informing counterparties of the pending transaction.

Permissible customer outreach is limited to notifying customers that the transaction is pending, explaining the anticipated timeline for regulatory review and closing, describing the general strategic rationale for the combination, and addressing transaction-specific logistics such as change-of-control consent requirements and assignment procedures. These communications should come from the seller, not from the buyer on the seller's behalf, and should not include representations about post-closing pricing, service levels, or contract terms that have not been finalized between the parties. Buyer personnel who join customer calls during the pre-closing period should not discuss competitive terms, pricing, or post-closing strategy for that customer.

Joint customer outreach by buyer and seller personnel is a particular risk area. When both parties attend a customer meeting, the customer is effectively meeting with the combined entity before the combination has occurred. If the parties discuss the customer's competitive situation, pricing expectations, or contract renewal terms in that joint meeting, they risk being found to have coordinated their competitive approach to that customer in violation of Section 1. Joint outreach should be limited to introductory transition meetings with appropriate legal preparation and should not include substantive competitive discussions.

Vendor outreach presents similar issues when the vendors are also counterparties in competitive markets. If the buyer and seller share a significant vendor and that vendor is used as a competitive input, coordinating vendor negotiation strategy before closing can constitute impermissible coordination. Each party should continue to manage its vendor relationships independently during the pre-closing period, and joint vendor negotiations should be deferred to post-closing unless required for transaction-specific purposes such as obtaining assignment consents.

Joint Bidding and Market Coordination Risks

Joint bidding between two companies that are competitors in a procurement market is one of the clearest examples of gun-jumping under the Sherman Act Section 1 framework. If the buyer and seller are both currently qualified bidders on an active procurement and they coordinate their bid responses, pricing, or strategy after signing but before closing, that coordination is a horizontal agreement between competitors that eliminates the competitive constraint each party would otherwise face from the other in that procurement. The fact that the parties have a signed merger agreement does not legalize conduct that would otherwise be a Section 1 violation.

The risk is not limited to formal joint bids where both parties appear as a single bidding entity. Coordination that stops short of formal joint bidding can also constitute impermissible market coordination. If the parties share their respective bid pricing with each other before the bids are submitted, that information exchange allows each party to calibrate its bid in light of the other's, eliminating the competitive uncertainty that makes independent bidding valuable to the procurement customer. If the parties agree that one will withdraw from a procurement to allow the other to win, that is a market allocation that violates Section 1 regardless of whether the merger ultimately closes.

The practical consequence is that in markets where the buyer and seller are active bidders, each party's bidding decisions must remain genuinely independent during the pre-closing period. Bid pricing, bid strategy, and bid decisions must not be shared between the parties' operational teams. If a bid requires information about the combined entity's capabilities or pricing, that bid may need to be deferred or handled by a single party until closing, with legal guidance on how to represent the transaction status to the procuring entity.

In government procurement contexts, the rules are even more stringent. Federal procurement regulations and the False Claims Act create additional layers of liability for false representations in bids. If the parties have announced a pending merger and are separately bidding on the same government contract, the contracting officer may inquire about the competitive independence of the bids. Counsel should be involved in evaluating how to respond to such inquiries and how to structure the bidding process to maintain genuine competitive independence until closing.

Hiring Freezes, Non-Solicits, and Post-Signing Talent Moves

Employment-related conduct during the pre-closing period presents gun-jumping risk in three distinct categories: hiring freezes that may affect the labor market, non-solicitation agreements between the parties that may constitute impermissible market allocation in the market for labor, and individual talent moves that may have the effect of coordinating the parties' competitive positions before closing.

Hiring freezes at the seller, implemented at the buyer's direction or with the buyer's involvement during the pre-closing period, can constitute an impermissible exercise of operational control if they go beyond what the seller would independently implement in the ordinary course. More significantly, if the buyer and seller agree not to recruit from each other's employee base during the pre-closing period, that agreement is a no-poach arrangement between two competing employers. The DOJ and FTC have taken the position that no-poach agreements between competing employers, including those negotiated in the context of M&A transactions, are subject to antitrust scrutiny and may be per se unlawful depending on their scope and duration.

Non-solicitation provisions in purchase agreements, which are standard features of M&A transactions, must be evaluated carefully. A non-solicitation provision that prevents the buyer from actively recruiting the seller's employees during the pre-closing period serves a legitimate purpose related to deal protection and is generally defensible. A broader provision that prevents the seller from recruiting from the buyer's workforce, or that restricts recruitment activity in ways that affect the broader labor market rather than just protecting the target's employee base, requires more careful analysis.

Individual talent moves during the pre-closing period present gun-jumping risk when they have the effect of giving the buyer operational influence at the seller before closing. If a key seller executive begins reporting to buyer management or taking direction from buyer personnel before closing, that creates a de facto integration that may constitute premature acquisition of control. Transition roles for seller executives that involve both parties before closing should be structured carefully with clear reporting lines and legal review.

Board Observer Seats and Information Access Limits

It is common for a buyer to negotiate the right to send a board observer to seller board meetings during the pre-closing period. This arrangement serves a legitimate purpose: the buyer wants visibility into material decisions made at the seller level that could affect the value of the acquisition. However, a board observer arrangement that gives the buyer access to the seller's full board information package, including competitively sensitive pricing data, customer information, and competitive strategy, can constitute gun-jumping if it effectively gives the buyer operational visibility over the seller's competitive decision-making before HSR clearance.

The structuring of board observer rights for gun-jumping compliance requires matching the observer's information access to the specific legitimate purpose the observer serves. If the observer's role is to monitor for decisions that require buyer consent under the interim operating covenants, the observer's access should be limited to the information necessary to evaluate those specific decisions. The observer does not need access to the seller's full board package, which typically includes detailed competitive information, customer status reports, and sales pipeline data. Restricting the observer's access to agenda items and board materials relevant to consent-required decisions, while excluding competitive operating data from the observer's information package, is a defensible structure.

Board observer arrangements should also address the observer's participation in board deliberations. An observer who actively participates in discussions about the seller's competitive strategy, pricing decisions, or customer approach is not functioning as a passive observer but as a participant in the seller's operational decision-making, which creates gun-jumping risk. Observer rights should be limited to observation without participation, except in cases where participation is required to address specific consent rights issues.

The observer's confidentiality obligations with respect to information received at board meetings should be specified in the purchase agreement. Competitively sensitive information received by the observer in their observer capacity should be subject to the same clean team restrictions that apply to other competitively sensitive information exchanged during the pre-closing period. The observer should not be permitted to share competitive information received in the observer role with the buyer's operational teams before closing.

Enforcement History and Penalty Exposure

The FTC and DOJ have brought a series of gun-jumping enforcement actions that collectively define the outer limits of permissible pre-closing conduct and establish the range of penalties that parties face for violations. These actions are instructive not because they identify a single bright-line rule but because they illustrate the types of conduct that the agencies regard as sufficiently clear violations to merit public enforcement.

The FTC's action against Qualcomm and NXP Semiconductors involved allegations that Qualcomm used the pre-closing period to impose conditions on NXP's licensing business and to delay NXP's execution of licensing agreements in ways that benefited Qualcomm's competitive position, effectively directing NXP's competitive conduct before the transaction had received regulatory clearance. The transaction ultimately did not close, but the investigation established that the agencies scrutinize buyer conduct that influences the seller's competitive decisions during the pre-closing period regardless of whether the merger closes. The FTC's $5.5 million civil penalty against Qualcomm in related proceedings illustrated the magnitude of the financial exposure.

The DOJ's action against Gemstar-TV Guide International and Tribune Company involved allegations that the parties began integrating their businesses, including sharing sales personnel and coordinating competitive operations, before the HSR waiting period expired. The DOJ assessed a $5.7 million civil penalty. Similarly, the DOJ's action against Computer Associates and Platinum Technology involved allegations that Computer Associates exercised operational control over Platinum Technology before HSR clearance, resulting in a consent decree and a $638,000 civil penalty, which at the time represented the maximum available. Civil penalty amounts have increased substantially since that period as Congress has raised the per-day penalty levels.

Current civil penalties for HSR Act violations are assessed at a per-day rate for each day of violation, with the maximum rate adjusted annually for inflation. The per-day penalty rate means that violations that persist over weeks or months can generate penalty exposure that dwarfs the administrative cost of implementing a compliant pre-closing protocol. Beyond civil penalties, Sherman Act Section 1 violations can support private litigation by competitors or customers who claim that the pre-closing coordination harmed them, with treble damages available to prevailing plaintiffs.

Training, Firewalls, and Closing-Day Handoff

The compliance infrastructure that protects parties from gun-jumping liability is only as effective as the training that personnel receive and the enforcement mechanisms that ensure the protocols are followed in practice. Most gun-jumping violations arise not from deliberate decisions to violate antitrust law but from operational personnel who do not understand the applicable constraints and proceed with integration activities that seem efficient without recognizing the legal risk.

Effective gun-jumping training should be delivered at signing, before any integration planning begins, and should be tailored to the specific roles of the personnel receiving it. Sales, marketing, and business development personnel need training focused on the restrictions on customer outreach, competitive coordination, and information sharing with the other party's commercial teams. Operational and IT personnel need training focused on the restrictions on systems integration and operational consolidation. Finance and accounting personnel need training focused on the clean team protocol and the categories of financial information that require restricted handling. Senior executives need training focused on the restrictions applicable to board observer arrangements, consent right exercises, and senior management interaction with the other party.

Firewalls during the pre-closing period should be implemented both organizationally and technically. Organizational firewalls separate clean team members from operational personnel and establish clear protocols for escalating compliance questions to legal counsel. Technical firewalls restrict access to shared data rooms, limit the distribution of clean team documents, and create audit trails for information access that can be reviewed if a compliance question arises. The combination of organizational and technical controls is more robust than either alone.

Closing-day handoff is the point at which many of the pre-closing restrictions lift and the parties can begin operating as a combined entity. The handoff should be structured to ensure that integration activities that were deferred to post-closing are activated on a coordinated basis immediately upon closing. Legal sign-off on the closing-day integration plan should confirm that the activities being initiated on day one are consistent with the now-combined entity's legal authority and do not require any additional regulatory approvals or transition periods. Personnel who were subject to clean team restrictions should be formally released from those restrictions upon closing, with appropriate documentation, and should be briefed on the information they are now authorized to access and use in their combined-entity roles.

Frequently Asked Questions