How to track conditions precedent with source references for Private Company Acquisitions

Track conditions precedent by translating the executed acquisition agreement into a buyer-side decision record: one row per independently testable condition, linked to its operative clause, supporting evidence, beneficiary, and waiver authority. Separate contractual conditions from external closing restrictions and routine deliverables, while linking related entries. Update each row as evidence arrives, but reserve closing-time tests for the closing decision. The resulting tracker should explain why each condition is satisfied, remains open, requires escalation, or has been validly waived—not merely report that a document was received.

When to use this workflow

Use this workflow after signing a private-company acquisition agreement, or prepare a provisional tracker during final drafting. It is intended for buyer’s deal counsel, in-house legal teams, and closing coordinators managing stock purchases, equity purchases, asset acquisitions, or mergers.

The scope is conditions readiness, not the entire closing checklist. Include a deliverable when the agreement makes its delivery or effectiveness part of a condition; otherwise, cross-reference the deliverables list.

This guide uses a US transactional orientation. Entity type, transaction structure, governing law, industry, and negotiated wording determine the requirements. For HSR-reportable acquisitions, the applicable waiting period must expire or be terminated before closing. Thresholds and exemptions require transaction-specific analysis; HSR status does not establish satisfaction of other restrictions. See the FTC’s merger-review guidance.

What you need

Start with an authoritative document set:

• The executed acquisition agreement, amendments, disclosure schedules, exhibits, and incorporated documents.
• Definitions, conditions, covenants, closing-deliverables, waiver, and termination provisions, including the outside date.
• Executed underlying contracts and amendments for required consents, together with consent forms.
• Approval records, regulatory correspondence, officer certificates, and evidence of delivery or effectiveness.
• Buyer instructions identifying reviewers, commercial decision-makers, waiver approvers, and release authority.

Assign stable document IDs and record execution status and version in a source index. Distinguish drafts from executed documents. An email saying “consent obtained” is a lead to evidence, not a substitute for examining the consent.

Establish the actual document hierarchy. Section 13.11 of the Molina–Bright Health stock purchase agreement incorporates schedules and related agreements but gives the agreement body precedence over inconsistent provisions, subject to specified disclosure exceptions. That is a drafting example, not a hierarchy governing other acquisitions.

Use the template

The companion template is Private Company Acquisitions — Conditions precedent tracker. Copy this table into your working document or spreadsheet. Use one row per independently testable condition, with sub-IDs for components of an aggregate test.

In Source / test, record the executed document ID, section, relevant schedule or definition, and a faithful summary. Preserve materiality qualifiers, specified-date exceptions, and cross-references rather than writing “reps accurate.”

Beneficiary / waiver identifies whose obligation is conditioned and who may authorize contractual waiver. For an external restriction, record the legal question separately; do not imply contractual waiver power.

Evidence / locator identifies the evidence document and clause, page, or dated message. Link stable IDs to the source index. Reference related rows by CP ID because cell references alone can break when sorted.

Use statuses such as open, evidence received, verified for current date, closing recheck required, waiver pending, waived, and satisfied. Put the next action date and dependency in Owner / test time or Action / decision. The Closure record captures reviewer, date, rationale, and any waiver reference. Receipt and satisfaction are different states.

Step by step

1. Fix the controlling document set

Confirm which signed agreement governs and whether amendments, side letters, or permitted schedule updates affect conditions. Preserve superseded documents, clearly marked, without treating every later upload as controlling.

Record the agreement ID and version in each source entry. If an amendment changes one condition, update that row and retain the previous test in its history. Assign unresolved hierarchy questions rather than selecting the version that makes closing easier.

Output: source-linked rows tied to an identified controlling document set, with conflicts assigned for resolution.

2. Extract conditions without flattening their tests

Read the conditions article alongside definitions, referenced covenants, and closing deliveries. Preserve distinct standards for fundamental representations, other representations, covenant performance, and any material-adverse-effect condition. Capture exceptions for representations made as of a specified date.

Use subrows for separately required consents or approvals. Retain a parent row showing the aggregate test so completed subitems do not conceal a missing component.

Article X of the Molina–Bright Health agreement distinguishes mutual conditions from additional buyer and seller conditions. Its structure illustrates why one undifferentiated list can misstate whose obligation is affected.

Output: an inventory retaining operative references, qualifiers, and aggregate tests.

3. Identify beneficiaries and decision authority

Classify each row as a buyer condition, mutual condition, seller condition relevant to coordination, or external restriction. Where a contractual condition addresses an external restriction, link the entries rather than treating them as unrelated requirements.

Record the contractual waiver holder and the internal buyer approver separately. Check any restriction on relying on condition failure. For example, § 10.4 of the Molina–Bright Health agreement restricts reliance where the relying party’s breach caused the failure. Inspect the actual agreement before applying that reasoning.

Output: beneficiary, waiver holder, internal approver, and any reliance question recorded independently of status.

4. Specify evidence addressing the actual test

Work backward from the condition. If a consent must remain effective, examine execution, transaction scope, delivery, effectiveness triggers, and limiting terms. Read the underlying contract and amendments rather than relying only on a seller’s consent summary.

Section 2.4 of the Granite Southeast–Roberts Family equity purchase agreement separately identifies specified contract consents in full force and an executed insurance change-of-control letter. These are agreement-specific delivery requirements; their placement alone does not establish a condition in another transaction.

For bring-down conditions, map certificate paragraphs and supporting review to the negotiated standards. Flag contrary information rather than treating a certificate as conclusive.

Output: required evidence, received-document locators, and precise evidentiary gaps.

5. Assign timing and dependencies

Identify whether each test can be verified now or requires closing-time confirmation. A signed consent may await a payment trigger; a continuing absence-of-restraint condition requires an appropriately current check.

For regulatory entries, obtain responsible counsel’s assessment of the restriction and supporting evidence. The FTC guidance explains that a second request extends the waiting period until substantial compliance and the subsequent waiting period have been addressed. A filing receipt alone therefore does not establish HSR readiness.

Record dependencies such as payment, delivery, or release. Distinguish internal target dates from contractual deadlines. Flag outside-date implications for counsel rather than treating an open condition as an automatic termination right.

Output: owner, test time, dependency, and next action for every open row.

6. Resolve gaps through evidence, escalation, or waiver

Describe the mismatch precisely: “consent excludes acquired subsidiary” is more useful than “consent issue.” Assign corrective action and identify who decides if correction is unavailable.

Separate commercial risk acceptance from contractual waiver. Check authority, required form, and scope before recording waiver; distinguish waiver of a condition from amendment or release of an underlying obligation. Refer external restrictions to responsible counsel rather than marking them waived.

Record the resolving evidence or authorized waiver document. Preserve unresolved questions instead of converting them into optimistic status labels.

Output: a documented resolution route, decision-maker, and supporting reference for each exception.

7. Verify conditions at closing

Before recommending release, revisit timing-sensitive conditions against current information. Reconcile the tracker with the deliverables list so signed, delivered, released, and effective documents are not confused.

Prepare an exception summary covering unresolved conditions, proposed waivers, external restrictions, and evidence expected at release. Record the authorized decision and its basis. An assigned issue is not necessarily a cleared issue.

Preserve a dated closing version and accessible evidence links. Retain earlier uncertainty and the record explaining its resolution.

Output: a closing-time report with traceable satisfaction, waiver, and unresolved-blocker decisions.

Worked example

Fictional scenario: Alder Quay Holdings is buying all equity in Brookglass Components under SPA-01. All parties, documents, and clauses are invented. Section 8.2(c) requires a specified customer consent to be effective. Section 8.2(a) requires closing-date bring-down of representations under differentiated standards, subject to specified-date exceptions. Section 8.1(b) requires expiration or termination of any applicable HSR waiting period. Section 11.4 permits written buyer waiver of buyer-only conditions.

The seller reports readiness. Buyer’s counsel receives a signed consent, a draft certificate, and a filing acknowledgment. Each leaves a different question unresolved.

The tracker changes the decision from collecting signatures to resolving three distinct gaps. CP-01 needs proof of effectiveness. CP-02 needs corrected wording and the underlying closing-date assessment. CP-03 needs regulatory counsel’s determination, not a generic statement that “approval” arrived. No supplied evidence supports closing any row, and the tracker does not invent missing facts.

Common mistakes

• Tracking certificates instead of tests. Link each certificate paragraph to the condition and investigate known inconsistencies.
• Treating all consents alike. Preserve counterparty, transaction scope, required form, and effectiveness requirements for each consent.
• Assuming buyer conditions are freely waivable. Verify contractual authority and form; analyze external restrictions separately.
• Using stale source references. Reconcile amendments and preserve the history of changed tests.
• Closing rows on seller assurances. Obtain evidence or document the authorized decision addressing the gap without mislabeling uncertainty as satisfaction.

Final quality check

• Every condition traces to the controlling executed documents.
• Definitions, qualifiers, specified dates, and aggregate tests remain intact.
• Beneficiaries, waiver holders, and internal approvers are distinguished.
• Evidence links resolve to the correct document, version, and location.
• Signed, delivered, effective, and satisfied states remain separate.
• Closing-time tests have current verification records and named reviewers.
• Open issues are resolved or expressly assigned and escalated; unresolved blockers remain visible.
• The dated closing report records the decision basis and preserves evidence.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review supports buyer-side, deal-specific instructions in Word, with findings that quote and locate clauses, rank severity, and identify missing language as not present. Lawyers control tracked changes and can dismiss findings with reasons. Due diligence classification and tabular review can support organizing and reviewing acquisition documents. The tracker remains your work product; counsel retains satisfaction and waiver decisions. Book a demo to discuss this workflow.

Frequently asked questions

Should every closing deliverable appear as a condition?

No. Include it as a condition where the agreement makes it part of the test. Otherwise, cross-reference the deliverables list and identify any dependency affecting readiness.

Can one officer certificate support several conditions?

Yes, if it addresses their respective requirements. Cite the relevant paragraph in each row and separately record contrary information or additional verification needed.

How should a condition checked before closing be recorded?

Use “verified for current date” where continued validity matters. Record what must be rechecked, by whom, and when. Apply final satisfaction status at the contractual test time.

What if the buyer wants to close despite missing evidence?

Distinguish uncertain proof from known condition failure. Escalate to counsel and authorized decision-makers, documenting the assessment and any permitted waiver. Do not imply that contractual waiver removes an external restriction.

Sources

• FTC, Premerger Notification and the Merger Review Process.
• Molina–Bright Health stock purchase agreement, Article X and § 13.11.
• Granite Southeast–Roberts Family equity purchase agreement, § 2.4.

General workflow guidance, not advice for a particular acquisition. Filed agreements illustrate wording, not market standards; apply current law and the operative transaction documents.

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.