How to track conditions precedent with source references for SAFE Financing Transactions

Track SAFE financing conditions precedent by tying each proposed closing requirement to the operative instrument, approval, or identified legal requirement. Record the relevant event, whose protection the requirement serves, what proves satisfaction, and who can resolve an exception. Separate contractual conditions from representations, covenants, internal controls, and future conversion obligations. For company counsel, the deliverable is an investor-specific closing tracker showing whether the company can proceed, what remains unresolved, and where the supporting evidence sits—not merely a document-receipt checklist.

When to use this workflow

Use this workflow when company counsel prepares an initial SAFE issuance, coordinates staggered investor closings, or reconciles negotiated side letters before accepting funding. It is particularly useful when investors sign different forms or require additional deliveries.

The scope is initial signing, company acceptance, and funding—not the later equity financing at which a SAFE may convert. Identify which event each tracker decision addresses.

This is a general workflow for US practice, with Delaware corporate authorization discussed specifically. Other formation jurisdictions, state securities requirements, and negotiated governing law require separate analysis. Contractual conclusions depend on operative wording, facts, and deal context; the process recommendations below are not independent legal requirements.

What you need

Assemble a controlled source set:

• Each investor’s SAFE, execution pages, amendments, side letters, and incorporated schedules, distinguishing operative versions from drafts.
• The charter, relevant corporate approvals, capitalization records, outstanding convertibles, and delegated signing authority.
• Debt documents and investor agreements potentially restricting issuance or requiring consent.
• Negotiated closing instructions, correspondence concerning conditions, and company acceptance records.
• Verified payment instructions, funds evidence, and the offering’s exemption analysis.

Assign stable document IDs and a custodian for missing material. “Not supplied” differs from “confirmed not to exist.” Request additional diligence only where it informs an identified condition or approval question; do not import a priced-round checklist without checking relevance.

Use the template

The companion template is SAFE Financing Transactions — Conditions precedent tracker. You can copy this table into your working document or spreadsheet. Use one row per independently resolvable requirement; split investor-specific variations.

“Requirement / class” distinguishes an express condition, covenant, representation, statutory prerequisite, or internal recommendation. An unresolved authorization inquiry can be identified as such without prematurely declaring a statutory violation.

“Source / locator” identifies the document ID, version, and clause or page—not merely a folder. For missing material, cite the available source establishing the gap, such as a resolution referencing an absent exhibit.

“Trigger / beneficiary” identifies the relevant event and protected party; for legal prerequisites, record the applicable authorization requirement rather than inventing a contractual beneficiary. “Evidence / gap” identifies the satisfaction record or missing proof.

Use statuses such as open, evidence received, satisfied, exception proposed, or deferred outside initial closing. Explain the basis. The final column records decision authority and disposition. A blank waiver field is not permission to proceed. Target dates are operational unless a source establishes a deadline.

Step by step

1. Fix the closing event and operative sources

Identify the investor, SAFE version, purchase amount, and event being assessed: signing, company acceptance, or funding. Keep separate timestamps in a linked transaction index when those events differ. Do not infer acceptance or satisfaction solely from a signature or incoming wire.

Freeze a review set with document IDs. Preserve superseded versions separately and reconcile each side letter against the SAFE it modifies. If an executed copy differs from the approved draft, reopen affected rows.

Record: investor scope, operative version, relevant event, and unresolved document conflicts.

2. Extract requirements without making every clause a condition

Read for conditional language, required deliveries, approval dependencies, and funding mechanics. Preserve a short excerpt or precise source note with an exact locator. Separate the document’s requirement from counsel’s recommended control.

Do not classify an authority representation as an independent delivery condition without supporting language. Likewise, check whether an information covenant operates before funding or afterward. When wording is ambiguous, assign the interpretation to counsel rather than defaulting to the most restrictive classification.

Record: the narrow requirement, classification, beneficiary where applicable, source, and interpretive uncertainty.

3. Separate issuance from conversion and later events

Test every extracted item against its actual trigger. Similar document-delivery language can address different events.

For example, the SEC-filed CapCO2 form provides for automatic conversion at the initial Equity Financing closing and qualifies investor execution of financing documents with specified protections. That wording concerns conversion, not an initial SAFE funding condition. This crowdfunding-context form illustrates contractual wording; it is not a Regulation D checklist, evidence of customary terms, or SEC approval. See Exhibit A, §1(a). (sec.gov)

Record: each row’s applicable event. Transfer later obligations to a linked follow-up record, preserving their source and the reason they do not block initial closing.

4. Verify corporate and contractual approval dependencies

Match the proposed issuance against approvals: instrument form, decision-maker, authorized parameters, and execution authority. Check charter and contractual restrictions separately. Compare approved economics with each execution version, including purchase amount, cap, discount, and negotiated side-letter departures where relevant.

For Delaware corporations, DGCL §157(a)–(b) addresses stock-acquisition rights or options, subject to the charter, and the resolutions specifying issuance and acquisition terms. Counsel must determine its application to the particular SAFE and additional approval requirements. Section 157 alone does not establish authorization for this issuance. See Delaware Code, Title 8, §157. (delcode.delaware.gov)

Record: approval sources, covered parameters, and mismatches requiring supplemental approval or a legal determination.

5. Define satisfaction evidence before requesting it

Translate each requirement into an evidence test. For a countersignature condition, identify the required version, signatories, and delivery recipient. For an approval inquiry, obtain the complete executed consent and incorporated exhibits. Funds evidence answers a different question from authority to accept funds.

Assign a custodian and target for each gap. Common evidence may support several investors, but verify its coverage separately. Do not close multiple rows merely because one file arrived. Preserve the verification date and reviewer in the status note or linked record.

Record: required evidence, received document ID and locator, remaining gap, owner, and verification result.

6. Resolve exceptions through the correct authority

For an unsatisfied contractual condition, identify its beneficiary and examine waiver and amendment mechanics. Have counsel confirm who can decide, the required form of consent, and possible effects on other investors. Distinguish waiver of a condition from an amendment changing the bargain.

Keep legal compliance questions separate from commercial exceptions: investor willingness to proceed is not a substitute for resolving a statutory prerequisite. Likewise, permission to relax an internal control does not establish waiver of an investor’s protection.

Record: proposed disposition, counsel-confirmed authority, decision evidence, and residual issue. Keep unresolved rows open or exception proposed.

7. Decide readiness and hand off later tasks

Review investor by investor, checking for cross-investor or aggregate-financing dependencies. Prepare a short decision summary separating satisfied requirements, documented exceptions, blockers, and nonblocking follow-up. Readiness is an event-specific conclusion, not an assertion that every financing obligation is complete.

Keep applicable filings distinct from contractual closing conditions. SEC guidance requires Form D for offerings under Rules 504 or 506 or Securities Act §4(a)(5), within 15 days after the first investor becomes irrevocably contractually committed; a weekend or holiday deadline moves to the next business day. Determine the exemption and commitment date rather than substituting wire receipt. See SEC, Filing a Form D Notice. Analyze state notices separately. (sec.gov)

Record: the event-specific company decision, supporting evidence, and named recipients for deferred tasks. Do not assume every filing can wait until the entire raise ends.

Worked example

Fictional scenario: Alder Signal, Inc., a Delaware corporation, plans separate SAFE issuances to Birch Harbor Ventures for $400,000 and Mesa Lantern Capital for $250,000. All parties, documents, amounts, and provisions below are fictional.

Birch’s final closing letter expressly conditions funding on receipt of a countersigned participation side letter. Mesa has no equivalent requirement. Neither investor’s supplied documents makes its closing dependent on the other investor’s closing.

A signed board consent approves the SAFE form attached as Exhibit A, but the supplied PDF omits that exhibit. Birch’s SAFE separately addresses executing financing documents upon future conversion. Counsel records:

The missing Birch countersignature does not block Mesa on these supplied terms. The incomplete approval record affects both issuances because counsel cannot compare the approved and execution forms; it is an evidence gap, not proof that approval never occurred. The conversion clause creates no present delivery task on these facts.

Counsel seeks the complete approval record before clearing either issuance and obtains Birch’s countersigned side letter before clearing its funding condition. If the exhibit remains unavailable, the authorization inquiry stays open pending an appropriate decision. The tracker neither invents the exhibit’s contents nor treats recollection as the missing document.

Common mistakes

• Treating every open task as a condition. Classify the task and explain whether it blocks the particular event.
• Importing conversion deliveries into initial funding. Check the trigger and transfer future obligations with their source references.
• Using one status for the entire raise. Separate investors where forms, side letters, or dependencies differ.
• Closing a row on receipt alone. Verify version, signatures, content, and coverage before marking satisfaction.
• Recording “waived by company” without authority. Identify the beneficiary and mechanics; distinguish contractual waiver from internal permission.

Final quality check

• Every blocker has an operative source or an assigned legal-analysis question.
• Document IDs, versions, clauses, and pages lead to the cited text.
• Initial issuance requirements are separated from conversion and exit obligations.
• Common approvals cover each relevant investor and execution version.
• Satisfaction rests on verified evidence, not file receipt alone.
• Exceptions identify authority, decision evidence, and residual issues.
• Open issues and deferred tasks have owners, targets, and explicit handoffs.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support review of SAFE terms and side letters, while tabular review supports work across documents. Due diligence classification can organize the source set and prioritize human review. The tracker remains the legal team’s work product; counsel determines classification, satisfaction, authority, and readiness. To assess this workflow with your documents, book a demo.

Frequently asked questions

Does every SAFE have a conditions precedent section?

Do not assume one exists. Examine the SAFE and related agreements for operative requirements. The tracker can record approval inquiries and internal controls without inventing contractual conditions.

Can we close when an investor has signed but not funded?

Identify the event being called closing and examine its requirements. Record signing, company acceptance, and funding separately; signature alone does not answer the funding question.

Should a pro rata side letter always block initial funding?

Determine whether delivery is required for this closing and who must sign. Distinguish a present delivery condition from the later participation right the letter grants.

What if a source reference points to a superseded draft?

Recheck the requirement against the operative version and update the locator and analysis. Preserve history, but reopen conclusions that relied on changed language, including satisfaction and waiver decisions.

Sources

• Delaware Code, Title 8, §157 — rights and options provisions; application to the particular SAFE requires analysis.
• SEC, Filing a Form D Notice — covered exemptions and filing trigger.
• CapCO2 Solutions, SEC-filed Exhibit A, §1(a) — illustrative conversion wording, not general law or evidence of customary terms.

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.