Convertible Note Financing Transactions

How to track conditions precedent with source references for Convertible Note Financing Transactions

Track convertible note closing conditions with clause-level sources, evidence, waiver authority, and a copyable company-side conditions precedent tracker.

October 18, 2026  ·  10 min read
Book a Demo →

Track conditions precedent by linking each closing requirement to its controlling clause, identifying whose obligation it conditions, and recording proof of satisfaction or an authorized waiver. Company counsel should distinguish investor funding conditions from company issuance conditions, third-party restrictions, and post-closing obligations. The deliverable is a source-linked closing decision record showing what must happen for each convertible note closing, who must act, which issues remain unresolved, and what evidence supports releasing signatures, issuing notes, and accepting funds under the agreed mechanics.

When to use this workflow

Use this workflow when the convertible note purchase agreement is developed enough to identify closing conditions and counsel must coordinate corporate approvals, investor signatures, existing lender consents, certificates, and funding. It serves company legal teams, outside financing counsel, and finance personnel assembling closing evidence.

The scope is the conditions-to-closing decision, including initial and subsequent closings. It does not replace securities-exemption analysis, conversion modeling, or post-closing compliance tracking.

This is a general US legal-workflow guide, with Delaware corporate-law points identified expressly. Contract rights depend on the instruments, governing law, facts, and financing structure. Historical filed agreements illustrate negotiated wording, not universal requirements for startup notes.

What you need

Start with a controlled document set and a defined closing event:

  • The current purchase agreement, note form, investor schedule, side letters, and any security, subordination, or intercreditor documents.
  • Charter documents, relevant board and stockholder approvals, capitalization records, prior notes and SAFEs, and existing debt instruments, including amendments and waivers.
  • The proposed closing sequence: simultaneous or rolling closings, signature-release arrangements, funding instructions, and any contractual minimum proceeds requirement.
  • Proposed certificates and attachments, third-party consents, and correspondence identifying unresolved deliverables.
  • Company custodians, investor contacts, authorized decision-makers, and a document index assigning stable IDs and version status.

Preserve attachments with their parent instruments. A secretary’s certificate without its referenced resolutions leaves the approval evidence incomplete. Keep investor-specific side letters visible: one investor’s additional condition should not silently become a requirement for every purchaser.

Use the template

Use the Convertible Note Financing Transactions — Conditions precedent tracker below. You can copy this table into your working document or spreadsheet. Use one row per independently verifiable condition; split requirements with different owners, authority, or proof.

ID / closing Source / standard Beneficiary / waiver Trigger / deadline Dependencies Owner / next action Proof / citation Status / decision

Source / standard identifies the document ID, version, clause, and operative test. Preserve materiality qualifications, specified dates, and any named party’s satisfaction standard.

Beneficiary / waiver identifies whose obligation is conditioned and the provision governing waiver. Do not infer waiver authority from beneficiary status alone.

Trigger / deadline states the relevant event and distinguishes contractual timing from the team’s internal target. Proof / citation points to the specific evidence, including its document ID, execution status, section, page, or attachment. Link the precise version rather than a folder of competing drafts.

Use distinct statuses: open, evidence received, under review, satisfied, waived, or not applicable with a reason. Evidence received is not a satisfaction determination. Record the reviewing lawyer and decision date in the final column.

Step by step

1. Define the closing and control the source set

Identify the issuer, participating investors, principal allocation, and intended closing event. Assign separate closing IDs where investors sign or fund at different times. Determine whether later issuances use the same agreement and which joinders or additional documents it requires.

Index the purchase agreement, note, schedules, side letters, and amendments. Mark drafts clearly and reconcile any executed version against the documents currently circulating. Freeze a review baseline, while tracking subsequent changes.

Record: the closing ID and controlling document ID, version, and clause in each row. Flag version conflicts before determining satisfaction.

2. Extract conditions without turning every obligation into one

Read conditions provisions alongside definitions, closing mechanics, representations, covenants, and waiver language. Separate investor funding conditions from conditions to the company’s issuance obligation. Follow incorporated requirements through to certificate attachments and referenced schedules.

A representation may affect closing through a bring-down condition, but its existence alone does not establish the closing test. An administrative request likewise needs classification rather than automatic treatment as a blocker.

One SEC-filed convertible note agreement addresses conflicts with existing agreements separately from purchaser conditions requiring specified consents, certificates, security documents, and subordination. These are negotiated provisions in a secured, subordinated transaction, not requirements for every unsecured note financing (§§ 2.1–2.2 and 4.1(e)–(l)). (sec.gov)

Record: each operative test, beneficiary, and classification as a condition, supporting dependency, or separately assigned obligation.

3. Map approvals and restrictions to the correct event

Review debt, prior notes, SAFEs, and side letters for restrictions affecting additional indebtedness, liens, note issuance, or conversion. Identify whether each provision applies now, at a later equity issuance, or on another event. Preserve exceptions and thresholds instead of summarizing everything as consent required.

For a Delaware issuer, distinguish conversion-share authorization from note economics. Where stock rights are established by board resolutions under charter-granted authority rather than stated in the charter, § 151(g) requires a certificate of designations to be executed, acknowledged, filed, and effective. That conditional procedure is not required for every note issuance or conversion (DGCL § 151(g)). (delcode.delaware.gov)

Record: the dependency’s source, affected event, owner, and unresolved question. Do not label future conversion work a present condition without a supporting basis.

4. Specify acceptable proof before requesting it

Tell each owner what evidence is needed. For resolutions, identify the financing, principal authorization, and note form requiring approval. For a secretary’s certificate, identify required attachments and certification scope. Compare a proposed lender consent against the restriction it must address.

Distinguish preparation, execution, delivery, and effectiveness. A signed consent may remain conditional; an unsigned draft establishes only drafting progress. Check whether representations must be tested at signing, closing, or both, and preserve the actual bring-down qualifications.

Record: requested evidence, custodian, relevant attachment or page, and next action. On receipt, mark evidence received pending substantive review—not satisfied.

5. Sequence deliveries, funding, and repeat conditions

Map dependencies to the agreed mechanics. Determine whether notes are released before funding, against funding, or through another arrangement. Identify who confirms receipt; payment initiation is not necessarily proof of receipt. Reconcile minimum proceeds requirements and each investor’s allocation.

For rolling closings, identify certificates, representations, approvals, and investor-specific deliverables needing refresh. Do not reuse initial-closing evidence without testing its continuing relevance.

Keep subsequent filings separate unless the documents make them closing conditions. For offerings under Rules 504 or 506 or Securities Act § 4(a)(5), SEC guidance requires Form D within 15 days after the first investor becomes irrevocably contractually committed, with weekend or holiday adjustment. Wire receipt need not establish that trigger (SEC, Filing a Form D Notice). (sec.gov)

Record: triggers, internal targets, predecessor row IDs, and any post-closing handoff. Assign separate analysis of applicable state notices.

6. Resolve exceptions through the correct authority

Review open items before requesting investor clearance. Classify each as missing evidence, incomplete performance, interpretation uncertainty, or a requested waiver. Avoid an ambiguous substantially complete status.

Read waiver and amendment provisions, including investor-specific rights and required consent thresholds. Analyze authority under each instrument separately: purchaser clearance under the purchase agreement does not itself answer whether the lender’s debt restriction has been addressed. The filed agreement illustrates why purchase-agreement consent conditions and representations about other agreements require separate review (§§ 2.2 and 4.1). (sec.gov)

Record: the decision-maker, cure or waiver route, governing provision, and supporting evidence. Leave disputed interpretations open with a named owner rather than treating silence as approval.

7. Reconcile the tracker to the closing evidence

Before release, inspect evidence supporting every satisfied or waived row. Check execution, attachments, effectiveness, and changes to the governing standard. Confirm that legal and finance use the same investor schedule and closing allocation.

Prepare a short decision summary separating cleared conditions, express waivers, unresolved blockers, and assigned post-closing work. Assignment alone does not clear a blocker. Where an item is deferred, document the authority and basis for proceeding.

Record: reviewer, decision date, proof location, and disposition. Preserve the closing-specific snapshot so later closings do not overwrite the decision record.

Worked example

Fictional scenario: Cedar Arc Robotics, Inc., a Delaware corporation, plans a $1.8 million unsecured convertible note financing. Two investors will participate in C1; a third is expected at C2. All parties, documents, amounts, and provisions below are fictional.

Purchase agreement PA-04 requires a secretary’s certificate attaching resolutions approving the financing and specified note form. It also requires written lender consent before purchaser funding and tests representations at each closing. Existing debt agreement DEBT-01 separately restricts additional indebtedness.

Certificate draft SECERT-03 attaches resolutions approving N-02, but closing note N-04 changes the conversion discount. The lender’s email expresses comfort with proceeding; the record contains no executed consent addressing DEBT-01. Counsel has not determined whether the email satisfies either instrument.

ID / closing Source / standard Beneficiary / waiver Trigger / deadline Dependencies Owner / next action Proof / citation Status / decision
CP-01 / C1 PA-04 § 5.2; certificate with approving resolutions C1 purchasers; § 9.4 authority unverified Before C1 release Approval covering closing note Counsel: reconcile N-02/N-04; obtain approval evidence SECERT-03 draft, Ex. A ¶ 2; N-04 § 3 Open: draft and version mismatch prevent clearance
CP-02 / C1 PA-04 § 5.4; written lender consent C1 purchasers; § 9.4 authority unverified Before C1 funding DEBT-01 § 7.3 restriction addressed CFO: request consent; counsel: assess scope and authority EMAIL-07 p. 1; executed consent absent Open: email’s legal effect unresolved; separate debt review required
CP-03 / C2 PA-04 § 5.1; representations tested at each closing C2 purchaser; § 9.4 authority unverified At C2 Updated facts and appropriate confirmation Counsel: establish refresh process PA-04 § 5.1; C2 evidence absent Open for C2; not independently a C1 blocker

The evidence changes the release decision. CP-01 requires approval-scope analysis and appropriate documentation, not simply a final certificate signature. CP-02 requires separate resolution of the purchase-agreement condition and debt restriction; purchaser willingness alone does not complete that analysis. CP-03 remains visible without prematurely blocking C1.

The tracker assumes neither missing approvals nor missing consents exist. Any route to closing must identify the actual cure, authorized waiver, or other supported resolution.

Common mistakes

  • Using document names as satisfaction tests. Replace board approval with the relevant approval scope, note version, attachments, and controlling condition.
  • Combining distinct consent authorities. Separate purchaser waiver authority from lender or prior-noteholder consent requirements.
  • Dropping bring-down qualifications. Preserve timing, materiality, and exceptions in the operative test.
  • Treating conversion work as automatically due at issuance. Identify the event and contractual basis before declaring a present blocker.
  • Copying the first closing unchanged. Review changed facts and repeat conditions; preserve separate evidence for each closing.

Final quality check

  • Every condition identifies its controlling document, version, and clause.
  • Each closing and participating investor is identifiable.
  • Standards retain relevant qualifications and timing.
  • Dependencies cite the underlying approval or restriction.
  • Satisfaction rests on reviewed evidence, not document circulation alone.
  • Waivers identify authority, scope, and supporting evidence.
  • Blockers are resolved or remain expressly blocking; other open work has owners and triggers.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review supports deal-specific instructions and findings that quote clauses, locate text, rank severity, and identify missing language as not present. Due diligence classification can organize supporting documents; tabular review supports comparison across documents. The tracker remains your work product, and counsel determines satisfaction and waiver authority. To discuss applying these capabilities to closing-condition review, book a demo.

Frequently asked questions

Should every representation receive its own tracker row?

No. Track the operative bring-down condition, with supporting rows for distinct verification issues. Split rows when different owners, evidence, or exceptions would otherwise disappear inside one status.

Can an email establish satisfaction?

Possibly, depending on wording, applicable formalities, and authority. Record what it establishes and what remains uncertain. Do not classify informal support as effective consent without reviewing the controlling instrument.

How should missing attachments be handled?

Keep the affected determination open. Identify the missing attachment, custodian, and consequence. A certificate referencing resolutions does not supply their contents when the attachment is absent.

Should Form D appear as a closing condition?

Only if the documents make it one. Otherwise, assign the filing handoff separately. The SEC’s first-sale trigger concerns irrevocable contractual commitment, not necessarily wire receipt or the planned closing date (SEC guidance). (sec.gov)

Sources

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo