Merger remedies: test whether the divested business can operate
A completed divestiture transfers a package of rights and assets. It does not by itself establish that the buyer can operate the business independently after transition support ends. Research should connect the remedy package to the actual functions required to supply customers and compete.
The FTC Bureau’s 2012 merger-remedies statement discusses autonomous businesses, necessary components and viable buyers. The FTC’s 2019 divestiture-package discussion emphasizes assets, rights and personnel. These are dated background materials, not a determination about any current transaction. Read the particular order and agreements for binding obligations.
Turn assets into an operating dependency map
List the products, geography and customer obligations covered by the divested business. For each essential function, identify assets, employees, intellectual-property rights, input supply, data, distribution and working capital. A factory building is not a functioning business if the necessary license or specialist team is unavailable.
Record whether each component is transferred, supplied temporarily, licensed, replaced by the buyer or unresolved. Match the scope: a license for one territory or product cannot automatically support all historic sales. Rights to use technology and practical access to know-how are also different questions.
For retained dependencies, save service scope, price, duration, extension rights, exit conditions and responsible party. A transition-services agreement, TSA, can support continuity while replacements are built. Its existence alone does not show that a workable exit plan exists or that the buyer can absorb the eventual standalone cost.
Hypothetical transition gap
Assume a fictional divested manufacturer closes on day zero. Its production assets transfer, but order processing continues on the seller’s IT platform under a TSA ending on day 90. The buyer’s separately evidenced plan schedules replacement order processing for day 120.
| Dependency | Hypothetical evidence | Remaining question |
|---|---|---|
| Production assets | Transfer completed | Can supporting inputs reach the line? |
| Order-processing TSA | Ends day 90 | Is extension available and agreed? |
| Replacement system | Planned ready day 120 | Has end-to-end testing passed? |
| Critical employees | 40 of 50 accepted offers | Are missing specialist roles covered? |
The unmitigated schedule has a 30-day gap between day 90 and day 120. It is a scenario risk, not proof that an outage will occur. A verified extension, another tested system or an earlier replacement could resolve it; a general statement that the buyer is ready cannot.
Employee acceptance is 80%, but that is not an 80% operational-readiness score. If missing employees include an essential quality-signoff team, the unresolved function can constrain the entire business. Counting all components as equally important can conceal the binding dependency.
Trace transition economics and execution
Compare historical allocated expenses with temporary TSA charges and eventual standalone costs. Assume a fictional month includes 0.20 million of seller service charges plus 0.35 million of parallel replacement operations. The transition subtotal is 0.55 million, not a permanent 0.20 million run rate or two alternative costs from which the analyst can choose.
Keep implementation spending, inventory funding and customer-transfer costs separately visible. A buyer may have the legal right to operate while lacking sufficient working capital or completed customer onboarding. Financial capability and the mechanics of operations require different evidence.
Check acceptance and performance milestones: supplier qualification, employee transfer, license activation, shipping, invoicing and successful TSA exit. A signed agreement is evidence of a commitment; a completed operational milestone needs its own record. Do not infer final success from regulatory approval or closing alone.
Preserve confidential or unavailable schedules as limits rather than assuming their contents. The worksheet cannot determine legal compliance, predict the regulator’s judgment or prove competitive outcomes from public materials alone. Its output is a dependency map, a dated milestone schedule and specific unresolved operating questions. Recheck when TSA terms, staffing, supply access or customer transitions change.
Test dependencies in sequence rather than treating every completion date as interchangeable. A replacement system may be installed before employees are trained or customer master data passes validation. The operating milestone is the complete required path, not the earliest finished component.
FAQ
Does regulatory approval prove the buyer is operating independently?
No. Approval and operating execution are distinct evidence objects. Verify the transition and subsequent functions.
Is a TSA necessarily a sign the remedy failed?
No. Temporary support can be part of the plan. Its scope, exit path and actual replacement determine the operating question.