How to track conditions precedent with source references for Share Purchase Transactions

Track conditions precedent by converting the signed share purchase agreement into a buyer-side decision record: one row for each independently assessable condition, linked to its operative clause, satisfaction standard, supporting evidence, and authorized disposition. Separate contractual conditions from regulatory restrictions, and distinguish documents received from facts established. The resulting tracker should identify satisfied conditions, closing-time dependencies, unresolved evidence, and documented waivers. Every status should lead a reviewer back to both the requirement and the evidence supporting the buyer’s closing decision.

When to use this workflow

Use this workflow after signing, or when preparing the final signing version, when buyer’s counsel must coordinate closing readiness across corporate, regulatory, finance, and business teams. It is particularly useful where several holders will transfer shares, third-party consents remain outstanding, or certificates must confirm facts as of closing.

Cover conditions to the buyer’s obligation to close, shared conditions affecting that obligation, and supporting evidence. Include seller conditions where they create a closing dependency, but keep unrelated closing administration and post-closing obligations elsewhere.

This is a US-oriented workflow guide for professional readers. Actual language, governing law, target jurisdiction, and transaction facts control. Federal regulatory requirements apply only where relevant; foreign-investment, sector-specific, state, and non-US requirements need separate assessment.

What you need

Start with the executed purchase agreement, amendments, disclosure schedules, and incorporated exhibits. Before signing, label the governing draft provisional and reconcile every row against the executed documents afterward.

Collect sources specific to the conditions:

• Bring-down provisions, defined terms, specified representations, and covenant-performance standards.
• Required officer certificates, share certificates, stock powers, and other transfer instruments.
• Seller identities, ownership records, transfer restrictions, and required consents or waivers.
• Regulatory counsel’s assessment, filing records, and evidence supporting the status of applicable closing restrictions.
• Consent requests, responses, ancillary agreements, and records of required preclosing actions.
• Buyer instructions identifying evidence reviewers, escalation routes, and internal waiver decision-makers.

Give each source a stable document ID, version, execution status, and location. Preserve superseded versions without treating them as current evidence. A folder link alone is insufficient: identify the relevant clause, page, paragraph, or other pinpoint.

Use the template

The Share Purchase Transactions — Conditions precedent tracker is the team’s working decision record. You can copy this table into your working document or spreadsheet.

Requirement source identifies the operative agreement and clause, including controlling amendments. Beneficiary / standard preserves relevant accuracy, materiality, knowledge, and timing qualifiers. Link a controlled extract when the test is too lengthy for a cell.

Evidence / pinpoint identifies received evidence and what it establishes. Record expected evidence as “requested” or “not received,” not as an existing source. Status / gap distinguishes missing documents from unresolved facts. Useful statuses are open, evidence received, review pending, satisfied, closing-time verification, and waived.

Owner / next check names an accountable reviewer and date or event. Action / authority records the next step and approval route. Resolution reference links the final assessment, waiver, or release record, including reviewer and assessment time. Leave it blank until that record exists.

Step by step

1. Establish the operative requirement and its beneficiary

Read closing conditions together with definitions, closing deliveries, schedules, waiver provisions, and referenced covenants. Identify shared conditions, buyer-benefit conditions, and seller-side dependencies. Do not assume every required delivery is independently a condition to closing.

The SEC-filed AMD–ZT Group agreement illustrates this structure: § 8.2 subjects the buyer’s closing obligation to satisfaction or buyer waiver of listed conditions. This is negotiated wording, not a universal waiver rule. See the agreement, § 8.2.

Record the CP ID, operative source, beneficiary, and cross-references. Where an amendment changes a condition, identify the controlling language while retaining the superseded reference in the history.

2. Break composite conditions into assessable rows

Separate requirements needing different evidence, reviewers, or decisions. A clause addressing accurate representations, covenant performance, and certificate delivery should not become one row marked “certificate outstanding.”

For bring-down conditions, preserve categories of representations, applicable accuracy tests, signing-date and closing-date requirements, date-specific exceptions, and any instructions to disregard embedded materiality qualifiers. For covenant conditions, identify covered obligations and the required performance standard.

Record linked subrows under a parent CP ID. Where the contractual test aggregates failures, retain a parent-level assessment: separate rows must not conceal the combined effect of several exceptions. Keep certificate delivery distinct from the conditions it certifies.

3. Define evidence for each condition

Write an evidence plan before chasing documents. For customer consent, identify the triggering contract provision, correct counterparty, transaction covered, required scope, and effectiveness conditions. In a share purchase, check the ownership-change language rather than assuming an assignment provision applies.

For transfer instruments, identify each selling holder, shares covered, required form, signatory, recipient, and release dependency. Section 8.2(e)(i)–(ii) of the AMD–ZT Group agreement specifies share-transfer documentation and a CEO certificate addressing designated conditions. It illustrates the need to map documents to particular requirements. See § 8.2(e).

Record requested evidence and the assigned reviewer in the tracker. Treat the certificate’s delivery and the underlying factual assessment as separate review questions.

4. Separate regulatory restrictions from contractual discretion

Create a distinct row for each applicable regulatory restriction and link it to the associated contractual condition. Ask regulatory counsel to identify the assessment and evidence required before closing may proceed.

FTC guidance explains that certain acquisitions require premerger notification and observance of a waiting period; a Second Request extends that period. Filing thresholds change annually, and exemptions can apply. The overview does not determine this transaction’s reportability or permissible closing date. See FTC guidance on premerger notification and merger review.

Record the regulatory reviewer, unresolved facts, and supporting references. Do not use “clearance” as an unexplained status: identify the event counsel relies on. Keep any proposed contractual waiver separate from the assessment of applicable legal restrictions, and escalate uncertain timing rather than supplying an unsupported date.

5. Test received evidence against the actual standard

Confirm identity, scope, version, execution, and effectiveness for each document. A consent addressing an asset assignment may not resolve an ownership-change requirement. An instrument covering one seller’s shares does not establish readiness for every selling holder.

Compare evidence with the plan and contractual standard. For bring-down matters, identify new information that contradicts the proposed certificate or affects an applicable qualifier. Distinguish observed facts, absent sources, and the reviewer’s assessment.

Enter the evidence pinpoint and remaining gap. Use “evidence received” or “review pending” until the assigned reviewer completes the assessment. For “satisfied,” record the reviewer, assessment time, and reasoning. Identify any event requiring renewed verification.

6. Route exceptions and proposed waivers for decision

An unresolved condition may require further evidence, corrective action, a revised closing arrangement, or consideration of a contractual waiver. Present alternatives without disguising commercial risk acceptance as factual satisfaction.

For a proposed waiver, identify the beneficiary, contractual mechanism, internal decision-maker, affected condition, and proposed scope. Ask counsel to assess its interaction with other rights and obligations; do not assume a tracker notation accomplishes the waiver.

Record the recommendation, exposure, and approval route. Use “waived” only when the required decision and documentation are evidenced. Preserve the original defect and link the disposition so later reviewers can distinguish accepted risk from cure.

7. Verify closing-time conditions and preserve the decision record

Identify conditions assessable only at closing, including closing-date certificates and documents held pending release. Record the recheck event and responsible reviewer. An agreed draft, an executed instrument, and an effectively released instrument are different states.

Before the buyer’s closing decision, review outstanding rows and confirm earlier conclusions remain supported. Check the agreement’s closing mechanics before treating condition satisfaction as establishing the closing date; record relevant dependencies rather than assuming immediate closing.

Circulate a dated readiness snapshot showing satisfied conditions, documented waivers, closing-time items, and unresolved restrictions. Record final evidence, release confirmations, and decision references. Preserve the snapshot alongside the live tracker so later updates do not obscure the buyer’s basis for proceeding.

Worked example

Fictional scenario: Harbor Finch Holdings is buying all shares of Alder Quay Systems from two sellers. Their fictional SPA, A01, requires effective consent from customer Bracken Vale under § 7.2(c), executed transfer instruments from both sellers under § 7.2(d), and a closing-date officer certificate under § 7.2(e). Separate bring-down conditions require their own assessment.

The seller’s closing email describes the three document requirements as complete. Buyer’s counsel tests the attachments instead. The customer consent is signed but conditional, the transfer package covers one seller, and the certificate remains a draft. The available record does not establish that the missing steps occurred.

The tracker changes “documents complete” into three distinct dependencies. CP-01 needs effectiveness evidence, not another consent copy. CP-02 needs seller-specific documentation. CP-03 remains a closing-time item without implying verification of underlying representations or covenants. No resolution reference is supplied because no satisfaction assessment or waiver exists in the fictional record. A scheduled closing alone changes none of these conclusions.

Common mistakes

• Treating every deliverable as a condition. Map documents to the agreement’s structure; distinguish supporting deliveries from express conditions.
• Losing qualifiers or aggregation. Preserve the actual test and assess combined exceptions where the condition requires it.
• Using a folder as the citation. Record a stable document ID, version, pinpoint, and supported fact.
• Equating signature with effectiveness. Check attachments, effectiveness conditions, parties, and release arrangements.
• Calling accepted risk “satisfied.” Record an authorized waiver separately from factual cure, with scope and documentation.

Final quality check

Before presenting the buyer’s readiness assessment, confirm that:

• Every condition traces to the operative agreement, schedules, and amendments.
• Composite conditions have assessable subrows and any required aggregate assessment.
• Beneficiaries and satisfaction standards retain relevant qualifiers.
• Source references open the correct versions and support the stated conclusions.
• Regulatory restrictions have separate analysis rather than a contractual-waiver status.
• Closing-time items identify owners, recheck events, and release dependencies.
• Each open issue has an assigned action; each waiver has an approval and source record.
• The dated snapshot distinguishes verified conclusions from outstanding dependencies.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities can support clause identification and review; tabular review supports work across multiple documents. In Word, select the buyer as represented party and provide deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Counsel verifies findings, assesses satisfaction and waiver questions, and maintains the tracker as the team’s work product. To discuss this closing workflow, book a demo.

Frequently asked questions

Should every closing deliverable appear in this tracker?

Include deliveries establishing a condition or creating a dependency for its assessment. Keep unrelated administration in a separate checklist, linked by document ID. This keeps delivery volume from concealing unresolved conditions.

Is an officer certificate enough to mark a condition satisfied?

Review certificate delivery separately from the underlying standard. Check execution, date, required statements, and referenced conditions. Investigate inconsistent information rather than treating the certificate as resolving it automatically.

How should we record seller assurances without documents?

Record the communication’s date, sender, and precise assertion as evidence of the assurance—not necessarily the underlying fact. Identify missing corroboration, assign follow-up, and avoid a status overstating what the communication establishes.

What changes if closing moves?

Recheck date-sensitive conditions, certificate dates, consent effectiveness, and evidence tied to the earlier date. Preserve prior assessments and assign renewed verification. Ask the responsible reviewer whether intervening facts change a conclusion or the applicable contractual timing test.

Sources

• AMD–ZT Group Stock Purchase Agreement, August 17, 2024, § 8.2: negotiated buyer conditions and specified closing documents, not general law or market standards.
• FTC, Premerger Notification and the Merger Review Process: agency overview, not a transaction-specific reportability or timing opinion.

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.