Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Track conditions precedent by turning each operative closing condition into a source-linked decision record. For company counsel in a seed equity financing, that means identifying the controlling agreement, beneficiary, applicable closing, required evidence, dependencies, and waiver authority. Separate document preparation and delivery from the assessment of substantive satisfaction. The resulting tracker should explain why each condition is satisfied, open, waived, or inapplicable, with precise references that let another reviewer verify the decision without reconstructing the closing from email.
When to use this workflow
Use this workflow when the seed stock purchase agreement is sufficiently settled to begin closing preparation. It serves company counsel, in-house legal teams, and personnel collecting approvals, signatures, capitalization information, and officer confirmations.
The trigger is a proposed closing—not simply completion of diligence. Scope the tracker to the initial or subsequent closing and its participants. A broader closing checklist contains preparation tasks; this tracker records the contractual basis for proceeding, including conditions protecting the company as well as purchasers.
This is a general US transactional workflow using a Delaware corporation baseline, not advice for a particular financing. Contract rights depend on the actual language, governing law, facts, and deal context. Other entity laws, securities requirements, and regulatory approvals require separate analysis.
What you need
Collect the purchase agreement, disclosure schedules, exhibits, amendments, side letters, and existing waivers. Identify agreed drafts separately from executed documents.
Supporting materials should include:
- Existing and proposed charters, board and stockholder approvals, and filing evidence.
- Signature packets for the purchase agreement and related investor-rights, voting, or stockholders’ agreements.
- Officer certificate forms, representation bring-down support, and unresolved disclosure questions.
- Stock ledger, capitalization models, purchaser allocations, and outstanding SAFE or note instruments.
- Funding requirements, payment evidence, and conversion or cancellation documents, as applicable.
- Closing sequence, participating investors, and assigned company and counsel responsibilities.
Give each document a persistent ID. Maintain an index recording version, execution status, amendment chain, and location. Preserve earlier versions without leaving them in the active source set. “Latest SPA” is not a durable citation.
Use the template
Copy the Seed Equity Financing Rounds — Conditions precedent tracker into your working document or spreadsheet. Use one row per independently assessable condition; split components requiring different evidence or decisions.
| ID / closing | Condition / source | Beneficiary | Evidence / reference | Dependency / gap | Owner / reviewer | Status / decision | Waiver / authority |
|---|---|---|---|---|---|---|---|
In Condition / source, summarize the requirement and cite document ID, version, subsection, and page where useful. Preserve qualifiers and link to the source. Evidence / reference should identify supporting proof by document ID and clause, page, signature block, or spreadsheet tab and cell range—not merely a folder.
Beneficiary identifies whose obligation to close is conditional. Owner / reviewer separates evidence collection from assessment; add a target time where needed. Record dependencies without treating them automatically as additional contractual conditions.
Use controlled statuses: open, evidence received, under review, satisfied, waived, or not applicable. Record the reviewer, date, and short rationale with each disposition. The waiver field identifies contractual authority, required consenting parties, and written support. A blank field means no waiver is recorded.
Step by step
1. Fix the source set and applicable closing
Establish the controlling documents and whether they are executed or still under negotiation. If work begins from an agreed draft, mark decisions provisional until the executed version is reconciled.
Identify the company, participating purchasers, securities, and closing being tested. In the filed Defeye seed agreement, Section 4 addresses purchaser conditions at the initial closing; Section 5 addresses company conditions at initial or subsequent closings. This illustrates why applicability must be read rather than inferred from a generic checklist (Defeye purchase agreement, §§ 4–5).
Read related agreements and side letters for additional conditions or modifications. Filed examples illustrate wording, not market standards or proof of closing.
Record: closing identifier, participating parties, controlling source version, beneficiary, and unresolved execution questions.
2. Extract conditions without broadening them
Read conditions alongside definitions, incorporated exhibits, and cross-referenced obligations. Preserve materiality qualifiers, timing tests, exceptions, and participant limitations. Do not turn a qualified performance test into an absolute requirement.
Distinguish express conditions from supporting tasks and negotiation requests. Drafting a certificate is a task; delivering it and satisfying the conditions it certifies may require separate rows. An investor’s email request is not automatically a contractual condition.
The Defeye example includes representation accuracy, performance, certificates, stockholders’ agreement signatures, and an effective filed restated charter. These are agreement-specific requirements, not a mandatory seed-round checklist (Defeye purchase agreement, §§ 4.1–4.7).
Record: each assessable requirement, exact source, relevant qualifiers, and interpretation questions for counsel.
3. Define satisfaction evidence before collecting it
Describe what would demonstrate satisfaction and who should assess it. For a charter condition, request evidence addressing the required filing and effectiveness, including any stated effective time. For a representation condition, identify factual confirmations and the specified certificate separately.
Tie disclosure support to the agreed mechanism. The Defeye agreement requires corresponding disclosure-schedule sections and permits cross-qualification where applicability is readily apparent; a data-room upload is not itself that specified disclosure mechanism (Defeye purchase agreement, Section 2 introduction).
Distinguish missing evidence from evidence that affirmatively contradicts satisfaction. If proof has not arrived, describe the gap rather than supplying an assumed citation.
Record: expected proof, received-proof references, missing confirmations, and any contradictory evidence.
4. Map approval, funding, and conversion dependencies
Connect issuance conditions to approvals and capitalization support. For Delaware corporations, DGCL § 152(a) addresses issuance in the numbers, at the times, and for the consideration specified in board resolutions. Section 152(b) requires specified share, time, and minimum-consideration limits for delegated issuance authority. Those provisions do not alone resolve charter capacity or approval defects (DGCL § 152).
Check that approvals, purchaser allocations, and the closing model describe the same issuance. Separate new cash subscriptions from SAFE or note conversions; identify instrument-specific conversion triggers, amounts, and required cancellation evidence.
Review company-protective conditions too, including payment or purchaser representations where the agreement requires them. Do not mistake a converting holder for a cash subscriber. Keep reconciliation work linked to the condition it supports rather than inventing additional contractual requirements.
Record: approval and capitalization references, funding or conversion dependencies, sequencing, and mismatch owners.
5. Evaluate substantive satisfaction and changed facts
Use “evidence received” when material arrives. Use “satisfied” only after the reviewer assesses content, execution, timing, and applicable qualifiers. Identify separately whether confirmation from the beneficiary or its counsel remains outstanding.
For bring-down conditions, identify people able to confirm changes since signing and unresolved diligence matters affecting the test. A signed certificate does not resolve a known contradiction in the underlying records. Seek further evidence and a reasoned disposition.
Recheck affected rows after changes to allocations, charter text, investor participation, or disclosures. Preserve the earlier decision and explain why it changed; do not overwrite the history with an unexplained green status.
Record: reviewer, decision date, rationale, beneficiary response where relevant, and matters requiring recheck before release.
6. Resolve waiver requests and release dependencies
When satisfaction is doubtful, distinguish cure, a changed closing plan, amendment, and waiver. Read the condition together with applicable waiver and amendment provisions to determine authority and form. Do not assume a lead investor can act for every purchaser.
Defeye’s purchaser-conditions introduction permits waiver, but does not establish authority for another financing (Defeye purchase agreement, Section 4). For corporate-authority or charter gaps, separately assess the governing statutory framework rather than treating contractual waiver as the complete solution (DGCL § 152).
A proposed post-closing undertaking should not silently replace an outstanding condition. Obtain an express disposition and specify any conditions attached to signature, document, or funds release.
Record: cure or waiver route, consenting parties, authority reference, written evidence, scope, and release restrictions.
7. Preserve the closing decision record
Before release, review unresolved rows with the company’s authorized closing decision-makers and relevant counterpart counsel. Distinguish counsel’s assessment from instructions authorizing release.
Preserve a dated snapshot with accessible evidence links. Reconcile citations against executed documents and retain explanations for satisfied, waived, and inapplicable rows. Where releases occur in sequence, record the event on which each release depends.
Move genuinely surviving tasks to a separate post-closing list only after their contractual treatment is resolved. Keep the source reference, owner, completion evidence, and agreed timing. Do not assume securities filings or other legal tasks are necessarily post-closing; have the responsible lawyer determine their triggers separately.
Record: final disposition, release instructions reference, snapshot date, and separately assigned surviving undertakings.
Worked example
Fictional scenario: Cedar Loom Robotics, Inc., a Delaware corporation, plans an initial seed closing with Alder Basin Ventures and two individuals. All parties, documents, and provisions below are fictional. Executed SPA-07 distinguishes cash subscriptions from note conversion. Company counsel is asked to approve afternoon release.
SPA-07 § 4.4 requires an effective filed charter; § 4.1 requires the company’s representations to be true at closing; and § 4.6 requires all purchasers to execute the stockholders’ agreement. Fictional § 8.3 requires each affected purchaser’s written consent to waive its condition.
The charter folder contains only a filing-service submission receipt. A signed officer certificate has arrived, but an inquiry about a founder’s potentially conflicting IP commitment remains unanswered. One individual purchaser has not signed the stockholders’ agreement.
| ID / closing | Condition / source | Beneficiary | Evidence / reference | Dependency / gap | Owner / reviewer | Status / decision | Waiver / authority |
|---|---|---|---|---|---|---|---|
| CP-01 / initial | Effective filed charter; SPA-07 § 4.4 | Each purchaser | FIL-02 p. 1: submission receipt | Filing and effectiveness unverified | Filing coordinator / counsel | Open: receipt does not establish required effectiveness | None; § 8.3 consent route requires separate legal assessment |
| CP-02 / initial | Representation bring-down; SPA-07 § 4.1 | Each purchaser | CERT-03 p. 2; QUERY-05 item 6 unanswered | Founder IP commitment unconfirmed | CEO / counsel | Under review: certificate leaves known factual gap | None recorded; § 8.3 |
| CP-03 / initial | All purchaser signatures; SPA-07 § 4.6 | Each purchaser | SIG-04 index row 8: missing signature | Obtain signature or evaluate waiver | Company legal / counsel | Open: required execution incomplete | Each affected purchaser’s written consent under § 8.3; none received |
The tracker changes the decision from “packet assembled” to three unresolved requirements. Counsel requests appropriate charter evidence, investigates the founder’s response, and pursues the signature. The IP question is not labeled a proven breach: the evidence is incomplete. Neither satisfaction nor waiver is recorded without support, and a possible charter-condition waiver does not end the corporate-law analysis.
Common mistakes
- Citing a superseded agreement. Reconcile every row against executed documents and reassess changed conditions.
- Treating delivery as satisfaction. Review content, execution, timing, and underlying factual contradictions.
- Combining cash and conversion mechanics. Link each allocation to its payment or instrument-specific conversion requirements.
- Clearing all purchasers together. Test applicability and waiver authority for each affected participant and closing.
- Moving an open condition to “post-close.” Resolve its contractual treatment before assigning a surviving undertaking.
Final quality check
- Each condition cites the controlling version and precise subsection.
- Purchaser and company conditions, and separate closings, are distinguished.
- Evidence references open the correct document and location.
- Decisions address timing, qualifiers, and contradictory evidence.
- Approval, capitalization, funding, and conversion dependencies are resolved or explicitly assigned.
- Waivers identify authority, affected parties, scope, and written support.
- Open issues have owners and explicit dispositions; the snapshot preserves authorized release dependencies.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use contract review with company-specific instructions to examine closing provisions, and due diligence to organize supporting materials for human review. Tabular review supports work across multiple documents; this tracker remains your work product. Lawyers retain satisfaction, waiver, and release decisions. To assess the workflow against your financing documents, book a demo.
Frequently asked questions
Should every closing deliverable have a condition row?
No. Use a condition row for an operative contractual requirement. Link preparation tasks and supporting deliverables to it, or retain them in the broader closing checklist.
Can one officer certificate clear several conditions?
It can support several rows, but assess each condition separately. Reuse its reference while recording distinct requirements, factual support, and unresolved contradictions.
How should subsequent seed purchasers be tracked?
Create a separate closing identifier and read the provisions governing their admission. Reuse documents where appropriate, but do not carry forward initial-closing decisions without checking applicability and timing.
What if the parties disagree about satisfaction?
Record competing interpretations and source references. Identify the decision-maker and proposed cure, amendment, or waiver route. Keep the issue open until a supported disposition is recorded.
Sources
- Delaware General Corporation Law § 152: issuance authority and delegated-authority limits.
- Defeye Series Seed Preferred Stock Purchase Agreement: example conditions, closing applicability, and disclosure wording; not market-standard evidence.
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.
