How to track conditions precedent with source references for Corporate Carve-Out Transactions

Track buyer-side conditions precedent by linking each contractual satisfaction test to the operative agreement, its exceptions, and evidence establishing completion. For a carve-out, separately identify separation dependencies—shared contracts, transferred assets, employee arrangements, and transition services—that may be operationally essential without being closing conditions. The deliverable is a source-linked tracker distinguishing satisfied conditions, unresolved evidence, documented waivers, and operational escalations. It should support buyer counsel’s closing recommendation while showing which conclusions remain contingent on closing-time events or outstanding decisions.

When to use this workflow

Use this workflow after signing, when the purchase agreement establishes the closing framework, and update it as amendments, separation documents, and completion evidence arrive. It serves buyer’s deal counsel, in-house legal teams, and closing coordinators evaluating readiness to close.

Keep the scope narrower than the integration program. Include separation tasks that support a condition or expose a critical operational dependency requiring a buyer decision.

This is a US-oriented legal-workflow guide, not advice for a particular transaction. Assess federal premerger requirements separately from state, foreign, and sector-specific requirements. Read contractual conditions under the actual agreement, governing law, transaction structure, and facts; the recommendations below are workflow controls, not independent legal requirements.

What you need

Start with the executed purchase agreement, amendments, disclosure schedules, definitions, closing-deliveries provisions, and agreed certificate and ancillary-agreement forms. Request missing schedules expressly rather than assuming the conditions article is self-contained.

For a carve-out, assemble:

• The separation perimeter identifying entities, assets, employees, IP, permits, premises, and liabilities moving to the buyer.
• Shared-contract and consent lists, including parent-level arrangements supporting the business.
• Reorganization steps, transfer instruments, lien-release materials, and completion evidence.
• The transition services agreement (TSA), service schedules, standalone supply or licensing agreements, and relevant readiness records.
• Regulatory counsel’s transaction-specific analysis and supporting status documents.
• Buyer approval and signatory instructions for closing decisions and possible waivers.

Assign stable document IDs. Maintain execution status, version, amendments, and repository location in a source index. Distinguish unavailable, redacted, draft, and executed records. A missing document establishes an evidence gap, not necessarily failure of the underlying condition.

Use the template

Use the Corporate Carve-Out Transactions — Conditions precedent tracker below. You can copy this table into your working document or spreadsheet. Create one row per independently assessable condition or expressly labeled operational dependency; link supporting deliveries rather than treating every delivery as a condition.

In Source / version, record the document ID, executed version, section, schedule, and page where useful. Link to the indexed document. Cross-reference stable IDs such as CP-04, not changeable spreadsheet row numbers.

Test / beneficiary should preserve thresholds and timing. Exceptions / waiver captures qualifications, the contractual waiver route, and necessary approval—not a presumed right to waive.

Separate evidence from uncertainty in Evidence / gap. In Owner / next action, distinguish an internal target date from a contractual deadline. Use statuses such as awaiting evidence, under legal review, ready for closing-time confirmation, satisfied, waiver proposed, waiver documented, and operational escalation. Add reviewer and review time to the decision entry.

Step by step

1. Establish the operative closing framework

Read the conditions article with definitions, termination provisions, closing deliveries, relevant covenants, and amendment and waiver provisions. Identify conditions benefiting the buyer, seller, or both; do not infer the beneficiary from who supplies evidence.

Establish which executed version controls. Where an amendment changes a condition, retain the original reference alongside the amendment citation. Identify closing-time conditions separately from those capable of earlier satisfaction.

Record: a provisional row for each condition, its beneficiary, operative sources, timing, and unresolved cross-references. Assign interpretation questions to a lawyer.

2. Separate conditions from deliveries and business dependencies

Classify each candidate as a condition, delivery, or operational dependency. A delivery may support a condition, but trace that relationship to the agreement.

For example, Section 3.02 of the Emergent–BTG agreement lists seller deliveries including specified ancillary agreements, share-transfer evidence, tax forms, and lien releases, with qualifications. It illustrates negotiated deliveries, not a universal conditions checklist. (sec.gov)

Trace parent-owned software, procurement, payroll, and premises into this exercise. Ask whether title, access, consent, or interim support is needed and whether the agreement makes it a closing condition.

Record: classification and linked condition ID. Keep critical nonconditions visible without automatically labeling them contractual blockers.

3. Translate each clause into a faithful satisfaction test

Retain materiality qualifications, specified dates, exceptions, and incorporated definitions. Split compound conditions into linked subrows where evidence or owners differ, while retaining the parent condition.

For representation bring-down conditions, identify the referenced representations and applicable qualifications rather than writing only “representations accurate.” For covenant compliance, identify the relevant pre-closing obligations and contractual compliance standard. Avoid turning an efforts obligation into a guaranteed result.

Record: the test, cross-references, timing, and required evidence. Distinguish receipt of a certificate from assessment of known information that may contradict it.

4. Map separation dependencies to the correct legal question

Identify upstream steps: an asset transfer before an entity sale, release of a parent guarantee, employee transition, or TSA execution covering retained systems. Check the correct entities and acquired perimeter.

Do not automatically treat missing consent as condition failure. Matthews–Duravant Section 5.5(e) generally excludes specified missing consents and transfer arrangements from determining satisfaction of closing conditions, except to the extent of a breach of Section 3.4 or 5.5. Read those provisions with Article VIII; this is agreement-specific drafting. (sec.gov)

Record: the upstream dependency, relevant cross-references, and operational consequence. Assign legal and business follow-up separately where their conclusions may differ.

5. Attach evidence proving the relevant event

Match evidence to the test, not its document title. An executed TSA may establish signatures without establishing delivery, effectiveness, required service coverage, or a separately specified readiness test.

Capture each evidence item’s document ID, date, execution status, relevant passage, and reviewer. Distinguish drafts, signatures held pending release, released counterparts, and effective instruments. For releases, reconcile covered entities and asset identifiers against the acquired perimeter.

Record: what the evidence establishes and what remains unproved. Request confirmation of the missing event rather than treating silence as satisfaction or failure. Retain the supporting version, not just a link to a replaceable file.

6. Evaluate regulatory status separately from contractual waiver

For covered acquisitions, the FTC explains that parties cannot close before the applicable HSR waiting period expires or is terminated early. Not every acquisition requires filing; exemptions may apply and thresholds change annually. Use transaction-specific advice, not this overview, to determine filing obligations and timing. See the FTC premerger review guidance. (ftc.gov)

Obtain regulatory counsel’s conclusion and supporting record, including any other identified restraint. Assess contractual waiver separately; an internal waiver decision does not establish regulatory compliance.

Identify the contractual beneficiary, waiver mechanism, approval authority, and documentation required. Do not mark a proposed waiver resolved merely because commercial personnel favor closing.

Record: regulatory evidence or the precise open question; separately record any waiver proposal, approving authority, scope, and documented outcome.

7. Prepare an evidence-based closing recommendation

At the agreed review time, reconcile new amendments, evidence, and material updates. Recheck timing-sensitive conditions when their wording requires. Use “ready for closing-time confirmation” where final satisfaction depends on an event still to occur.

Group unresolved rows into missing evidence, disputed interpretation, potential condition failure, proposed waiver, and operational escalation. Distinguish a recommendation to proceed subject to identified events from confirmation that those events occurred.

Record: review time, reviewer, rationale, outstanding decision, and person responsible for final confirmation. Preserve the tracker snapshot and supporting sources so the recommendation can be reconstructed.

Worked example

Fictional scenario: Alder Quay Holdings is buying Beacon Ridge Industries’ laboratory-equipment division through an asset and subsidiary acquisition. All parties, documents, clauses, and facts below are invented.

The fictional purchase agreement requires the buyer to receive an executed TSA covering scheduled payroll support and effective releases of listed equipment liens. Its shared-contract provision excludes missing vendor consent alone from the conditions analysis, subject to a covenant-breach exception. Section 11.4 permits written buyer waiver of the two buyer conditions; buyer instructions require general counsel approval. The seller’s completion email says all three items are complete, but the records differ.

CP-01 requires the operative schedule before counsel can assess payroll coverage; its absence from the supplied copy does not prove no schedule exists. CP-02 requires asset reconciliation and effective release evidence, not merely a lender signature.

OP-01 produces a different decision. The refusal establishes a consent problem, not necessarily condition failure. Counsel must assess the covenant exception while IT evaluates continuity. No replacement arrangement is assumed. The buyer receives three distinct assessments rather than one misleading “complete” or “not ready” label.

Common mistakes

• Treating every consent as a condition. Read conditions, consent covenants, and exceptions together; separately escalate operational exposure.
• Equating signatures with effectiveness. Identify the required event and obtain evidence of delivery, release, or effectiveness as applicable.
• Citing only the conditions article. Add definitions, schedules, amendments, and incorporated qualifications that change the test.
• Checking the wrong perimeter. Reconcile release annexes, transfer instruments, and service schedules to acquired assets and entities.
• Marking closing-time tests satisfied early. Record readiness provisionally and assign final confirmation at the contractually relevant time.

Final quality check

• Every condition identifies its beneficiary and operative clause-level sources.
• Thresholds, exceptions, definitions, and timing remain intact.
• Deliveries and operational dependencies are distinguished from conditions.
• Evidence links resolve to reviewed versions and relevant passages.
• Transfer, service, and release evidence matches the acquired perimeter.
• Satisfaction, provisional readiness, and documented waiver have distinct statuses.
• Regulatory status is assessed separately, and each open issue has an owner and stated effect on the recommendation.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review supports represented-party selection and deal-specific instructions in Word; findings quote and locate clauses, rank severity, and identify missing language as not present. Tabular review supports cross-document work, while due diligence classification can organize sources and prioritize human review. The tracker remains the team’s work product; lawyers determine satisfaction, waiver, and readiness. Book a demo to discuss applying these capabilities to carve-out closing review. (decover.ai)

Frequently asked questions

Should the tracker include every separation task?

No. Include tasks supporting conditions and critical operational dependencies requiring a closing decision. Cross-reference the broader separation plan rather than duplicating integration work.

Can one seller certificate support several conditions?

Yes, where its wording addresses their tests. Cite the relevant passage for each row and assess separate evidence requirements or known inconsistencies. Do not let one certificate obscure different thresholds.

How should a missing schedule be recorded?

Identify the schedule, incorporating clause, requested version, and conclusion it prevents. Use “awaiting evidence,” assign an owner, and avoid inferring that the schedule or underlying arrangement does not exist.

What happens to a consent issue that does not block closing?

Preserve its contractual classification and operational significance. Assign follow-up before closing and cross-reference any continuing efforts, interim support, or delayed-transfer provisions. Do not assume those arrangements exist or solve the continuity problem.

Sources

• FTC — Premerger Notification and the Merger Review Process: federal premerger overview.
• Emergent–BTG Stock and Asset Purchase Agreement, §3.02: negotiated closing deliveries.
• Matthews–Duravant Equity Purchase Agreement, §5.5(e): qualified treatment of missing consents and transfer arrangements.

The contractual examples illustrate wording, not generally applicable law or market standards.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.