How to track conditions precedent with source references for Business Merger Transactions

Track merger conditions precedent by converting each operative condition into a source-linked record of its beneficiary, satisfaction standard, timing, evidence, dependencies, and waiver route. For the acquirer, distinguish a contractual condition to its closing obligation from an independent legal restriction and from a supporting deliverable. The resulting tracker should let closing counsel reconstruct each status decision from the executed agreement and evidence package, identify outstanding closing-time checks, and present unresolved matters to the authorized decision-maker before the acquirer gives its closing instruction.

When to use this workflow

Use this workflow after signing, when acquirer counsel and the in-house deal team need to determine what remains outstanding before closing. Establish the tracker before collecting completion confirmations; update it as evidence arrives and immediately before the closing decision.

The scope is conditions precedent, not the entire closing checklist. Include corporate approvals, regulatory restrictions, specified third-party consents, representation bring-downs, covenant compliance, and certificates where the agreement makes them conditions. Cross-reference related requirements without converting every diligence issue or deliverable into a closing condition.

This guide uses a US baseline focused on Delaware corporate mergers and federal HSR review. Other formation jurisdictions, entity types, regulated businesses, and foreign investment regimes require separate analysis. Contractual conclusions depend on the operative documents, governing law, facts, and merger structure.

What you need

Start with the executed merger agreement, amendments, applicable disclosure schedules, and incorporated documents. Include definitions and cross-referenced covenants: a condition may depend on a defined material adverse effect, a specified consent list, or an exception outside the conditions article.

Obtain the proposed closing sequence and current evidence package: corporate approvals, regulatory correspondence, consent instruments, compliance confirmations, certificates, and counsel’s issue reports. Distinguish preparation copies from executed documents and documents held pending release.

Establish who confirms factual compliance, interprets disputed wording, authorizes a permitted waiver, and gives the acquirer’s closing instruction. Identify the parent, merger subsidiary, target, and proposed survivor separately; their obligations and approval requirements may differ.

Maintain a document index with stable IDs, versions, execution status, and storage locations. The tracker should refer to those records rather than rely on changing filenames.

Use the template

Use the Business Merger Transactions — Conditions precedent tracker below. You can copy this table into your working document or spreadsheet. Create one row per independently assessable condition; use linked subrows when one provision contains different substantive tests.

In Condition source, record the document ID, operative version, section, and relevant schedule or definition. Use clause references, supplemented by PDF pages where useful. Keep the source establishing the obligation separate from the evidence supporting satisfaction.

In Beneficiary / waiver, identify the benefiting party and the provision governing waiver. Record the authorized decision-maker or an unresolved authority question. For an independent legal requirement, state that contractual waiver does not remove it.

In Test / timing, preserve qualifiers and identify whether satisfaction is required before closing or tested at closing. Evidence reference should pinpoint the supporting record, its date, and the latest review time where freshness matters.

Use controlled Status / rationale descriptions: open, evidence received, under review, satisfied subject to a specified closing confirmation, satisfied, or waived with authority documented. These are working conventions, not self-proving conclusions. Retain reasons and reviewer approval for any item classified as inapplicable.

Step by step

1. Extract the operative conditions and preserve their structure

Read the conditions article with definitions, amendments, schedules, closing provisions, and cross-referenced covenants. Separate conditions benefiting both parties, the acquirer, and the target. Identify obligations of the merger subsidiary rather than subsuming them under the parent’s name.

Do not compress a representation bring-down into “representations true.” Different groups of representations may have distinct accuracy thresholds, materiality treatment, specified-date exceptions, or closing-date tests. Split them into linked rows where separate analysis is necessary. Capture any no-material-adverse-effect condition separately from the representation tests.

Record: A source-cited row for each distinct test, with the cross-references needed to reconstruct its meaning and the affected entity identified.

2. Separate contractual conditions from independent requirements

Classify each row as a contractual condition, an independent legal requirement, or supporting evidence. Cross-link overlaps without treating them as interchangeable.

For mergers governed by Delaware §251, subsection (b) requires each constituent corporation’s board to approve the agreement and declare its advisability. Subsection (c) generally requires adoption by a majority of outstanding stock entitled to vote, subject to statutory exceptions. Check the charter, voting classes, and merger structure, including potentially applicable exceptions such as §251(f) or (h). Delaware Code §251(b)–(c), (f), and (h).

A prepared certificate of merger does not establish contractual readiness. Section 251(c) permits filing a certificate instead of the agreement and specifies its contents; the merger agreement supplies the separate contractual closing tests. Delaware Code §251(c).

Record: The category, affected entity, approval evidence, and relationship to an express condition. Keep statutory filing preparation distinct from permission to release the filing.

3. Define evidence for each substantive test and certificate

Specify the evidence needed and who evaluates it. A customer-consent condition may require an executed instrument covering the correct contract, entities, and transaction. A covenant-compliance condition may require confirmations from several business owners before an officer can certify compliance.

Keep the certificate requirement separate from its underlying tests. In the historical Dayforce/Dawn agreement, §6.02(d) requires Parent and Merger Sub to receive a company certificate executed by a duly authorized executive officer, confirming satisfaction of §6.02(a)–(c). This is negotiated wording, not a statutory certificate requirement. SEC-filed agreement, §6.02(d).

Record: Required evidence, expected signatory or reviewer, precise source location, and missing factual support. Receipt alone should not move a row to satisfied.

4. Map timing and dependencies before assigning completion status

Distinguish conditions completed in advance from closing-time tests. Link dependent rows: an officer certificate may await final compliance confirmations; a consent may await agreement on scope. Read the contractual closing trigger and outside-date provisions rather than assuming completion of the tracker determines when closing must occur.

For HSR, obtain transaction-specific reportability advice. The FTC explains that only certain transactions require notification, thresholds change annually, and exemptions exist. A reportable transaction cannot close before the applicable waiting period expires or is terminated early; a Second Request extends the waiting restriction. HSR expiration is not universal regulatory approval. FTC merger-review guidance.

Record: The operative event, counsel’s timing analysis, prerequisite rows, and verification owner. Do not substitute a generic waiting-period calculation for supported transaction-specific analysis.

5. Reconcile evidence against the actual satisfaction standard

Review evidence against the whole condition, including exceptions and qualifications. Confirm names, transaction descriptions, signatories, versions, and limitations. A consent limited to an assignment may not address the merger-related event specified in the condition; assign that scope question rather than infer coverage.

Preserve conflicting confirmations and diligence findings. “No issue reported” is not necessarily affirmative support for a specified test. Conversely, a disclosed issue does not automatically fail a condition: apply the negotiated threshold and any relevant exception.

For closing-time tests, identify facts that could change after preliminary review and arrange a targeted recheck.

Record: The reviewer’s conclusion, reasoning, review date, contrary evidence, and remaining gap. Use a conditional satisfaction status only when the outstanding confirmation and owner are explicit.

6. Document waiver decisions without rewriting the record

For an unsatisfied contractual condition, identify the options: obtain evidence, cure, consider an authorized waiver, or escalate. Review the waiver and amendment provisions, beneficiary, applicable law, and internal authority before proposing a route.

Do not treat commercial acceptance as removal of an independent legal restriction. Preserve the original condition and failure analysis. Link written waiver documentation and record its scope, any limitations, approval authority, and delivery requirements under the agreement.

A condition-waiver decision should also identify whether related covenant, remedy, or termination questions need separate resolution; do not assume the waiver answers them.

Record: The authorized decision, supporting document, revised status, and unresolved consequences assigned to counsel.

7. Prepare a source-linked closing decision snapshot

Before the acquirer’s closing instruction, review every open or conditional row. Confirm completed items, closing-time events, and the person responsible for each remaining verification. Distinguish execution, delivery, release, closing, and legal effectiveness in the proposed sequence.

Produce a dated snapshot linked to the evidence package. State blockers and conditional instructions plainly. A completion percentage cannot convey the significance of one outstanding legal restriction or a disputed bring-down test.

Record: Final review time, responsible closing lawyer, remaining checks, and decision references. Preserve subsequent changes as updates rather than overwrite the record supporting the instruction.

Worked example

Fictional scenario: Alder Harbor Acquisition Corp. will acquire Cedar Vale Systems, Inc. through its wholly owned Delaware merger subsidiary, which will merge into Cedar Vale, the survivor. All parties, documents, and provisions below are fictional.

Executed agreement MA-01 requires a specified customer’s written consent under §7.2(c). Section 7.2(a) contains the representation bring-down; §7.2(d) separately requires an officer certificate confirming it. Section 7.1(b) addresses expiration or termination of the applicable HSR waiting period. The table shows three representative entries, not every condition.

The team receives an unsigned consent, a draft certificate, and an email calling regulatory review “done.” FACT-06 records that a business owner’s updated representation confirmation has not been supplied. No missing confirmation is assumed to exist.

The decision changes from “three documents received” to three targeted evidence requests. CP-01 requires execution and scope review. CP-02 depends on the separately tracked bring-down analysis and certificate delivery; neither replaces the other. CP-03 requires supported regulatory verification, not an assumed date.

If the acquirer considers waiving CP-01, counsel must document the authorized decision and consider related contractual consequences. That discussion does not resolve CP-03 or the closing-time representation test.

Common mistakes

• Copying headings instead of tests. Preserve qualifiers, dates, exceptions, and defined terms; split independently assessable tests.
• Treating every consent as a condition. Identify the provision making it closing-critical, or retain it in the appropriate linked covenant or diligence record.
• Treating a certificate as conclusive despite contrary information. Track certificate compliance and underlying substantive tests separately; assign discrepancies.
• Relying on superseded evidence. Link operative versions and amendment relationships so replaced drafts cannot support current decisions.
• Calling an unresolved item waived. Retain authorized documentation and distinguish the condition from independent legal restrictions and related obligations.

Final quality check

• Every condition traces to the executed agreement and operative amendments.
• Necessary definitions, schedules, and cross-references are linked.
• Beneficiaries, waiver authority, and independent legal requirements are distinguished.
• Evidence references identify the correct version and supporting text.
• Draft, executed, delivered, and pending-release statuses remain distinct.
• Closing-time confirmations have named owners and verification points.
• Open issues are resolved or assigned for an express decision, with blockers visible.
• The dated snapshot preserves conclusions, contrary evidence, and waiver records.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use contract review with acquirer-specific instructions to examine condition wording; findings can quote clauses, locate text, rank severity, and identify missing language as not present. Tabular review supports work across multiple documents, while due diligence classification can organize supporting materials for human review. The tracker remains your work product, and counsel determines satisfaction, waiver authority, and closing readiness. Book a demo to discuss this workflow.

Frequently asked questions

Should the tracker include conditions benefiting the target?

Yes. Identify them separately because the acquirer or merger subsidiary may need to perform obligations or supply evidence. Maintaining the tracker does not give the acquirer authority to waive the target’s conditions.

Can a condition be marked satisfied before closing?

Follow its wording. Record completed evidence review separately from an outstanding closing-time test. Identify changed facts requiring rechecking and the owner who will confirm them before the closing instruction.

What if a condition refers to an unavailable schedule?

Record a source gap. Do not infer required consents or exceptions from diligence summaries. Obtain the operative schedule or assign the uncertainty for resolution before relying on the analysis.

Should post-closing obligations remain in this tracker?

Usually move them to a linked post-closing work product. Retain references needed to explain a condition, but keep later tasks separate from requirements that must be satisfied before or at closing.

Sources

• Delaware Code, Title 8, §251 — merger approvals, statutory exceptions, and certificate provisions.
• FTC, Premerger Notification and the Merger Review Process — federal HSR overview; transaction-specific analysis remains necessary.
• SEC-filed Dayforce/Dawn merger agreement, §6.02(d) — historical negotiated certificate condition, not evidence of market standards.

Scope: General professional workflow guidance using the supplied research cutoff of October 13, 2026; not advice for a particular transaction.

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.