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
Build the checklist from the operative financing documents, not a generic signature list. Give each approval, condition, signature, filing, payment, conversion, and issuance record its own entry, tied to a document version and applicable closing. Assign preparation, signature, delivery, and verification responsibilities; then record dependencies and completion evidence. The resulting company-side checklist should identify what prevents closing, what can be released together, who can authorize an exception, and which obligations require a documented post-closing handoff.
When to use this workflow
Use this workflow when company counsel and the in-house team have sufficiently settled Series A documents to identify closing requirements, but before signatures or funds are released. Start earlier when charter amendments, convertible securities, missing invention assignments, or additional closings create dependencies.
The scope is a U.S. private-company equity financing involving a Delaware corporation. Securities notice discussion assumes Regulation D. Other incorporation jurisdictions, offering exemptions, state requirements, and regulated businesses require separate analysis. Actual language, governing law, facts, and deal structure control. The checklist is a verification tool, not an independent determination that the financing may close.
Keep diligence analysis outside this checklist unless it generates a deliverable, affects a condition or disclosure, or requires assigned follow-up.
What you need
Collect these inputs before assigning completion status:
- Current purchase agreement, disclosure schedules, restated charter, investor rights agreement, voting agreement, and right-of-first-refusal and co-sale agreement, as applicable.
- Term sheet and resolved issues list, including decisions not yet reflected in operative documents.
- Existing charter, bylaws, board and stockholder records, and agreements potentially requiring financing consents.
- Stock ledger, capitalization model, option records, SAFEs, convertible notes, amendments, and proposed conversion calculations.
- Investor purchasing entities, allocations, authorized signatories, closing sequence, and funding instructions.
- Diligence remediation items, proposed certificates, negotiated opinion requirements, and relevant employee or consultant agreements.
Create a document index with stable IDs, versions, dates, and execution status. Identify missing schedules and amendments expressly. Maintain sensitive payment details separately with appropriate access controls; the checklist can reference their controlled location.
Use the template
Use the Series A Financing Rounds — Closing deliverables checklist below. You can copy this table into your working document or spreadsheet. Add rows rather than combining independently verifiable deliverables.
| ID / category | Deliverable / source | Closing / beneficiary | Prepare / sign / deliver / verify | Dependency / trigger | Due / release gate | Evidence / status | Exception / next action |
|---|---|---|---|---|---|---|---|
Separate approvals, signatures, conditions, filings, funds, conversions, and issuance records in the first column. In “Deliverable / source,” include document ID, version, section, and page where useful. Reference model cells for allocations or conversion amounts, but retain the underlying instrument citation: a spreadsheet cell is not the obligation.
“Closing / beneficiary” identifies the applicable closing and whose condition or deliverable is involved. Name individuals in the responsibility column, using role labels before each name. A verifier should know what evidence establishes completion, not merely who last handled the document.
Use statuses such as missing, in preparation, awaiting signature, held for release, verified complete, waived, or not applicable. Date the verification entry. Preserve waived and not-applicable rows with reasons and supporting authority.
Step by step
1. Establish the document baseline and closing structure
Identify purchasing entities, securities, the initial closing, and any additional-closing mechanism. Record the documents governing each closing and schedules still provisional. Resolve term-sheet discrepancies through the issues list rather than silently choosing one version.
Separate execution, release, funding, charter effectiveness, and issuance as events. For additional investors, identify allocation limits, admission documents, and conditions requiring renewed review under the actual agreement. Do not assume an initial-closing signature package covers later purchasers.
Record: Document versions, applicable closing, allocation references, and an owner for each structural question. When a document changes, identify affected checklist rows and recheck their requirements.
2. Extract conditions and identify their beneficiaries
Read both investor and company conditions alongside delivery, waiver, and additional-closing provisions. Create one row per independently testable condition. Distinguish a required certificate from the underlying facts it certifies, and preserve contractual qualifications in the requirement description.
The historical RPX agreement applies investor conditions at each closing and makes a waiver ineffective against an investor who does not consent. Sections 4.1–4.3 separately address representation bring-down, performance, and an officer’s compliance certificate. These illustrate drafting choices, not default Series A requirements. RPX purchase agreement, §§4–4.3. (sec.gov)
Record: Source, beneficiary, applicable closing, satisfaction evidence, and waiver authority. Include company-side conditions such as agreed payment requirements; do not build an investor-only checklist.
3. Map approvals and charter dependencies
Separate statutory and charter approvals, board action, and contractual investor consents. Have counsel identify applicable authority, eligible voters, thresholds, and approved document versions. A signed purchase agreement is not a substitute for approval evidence.
For Delaware corporations, DGCL §151(a) permits differing stock powers, preferences, rights, and restrictions when stated in the certificate or issuance resolutions adopted under express charter authority. It does not itself supply negotiated Series A rights or establish that this financing’s approvals are sufficient. DGCL §151(a). (delcode.delaware.gov)
Reconcile charter terms, authorized shares, issuance figures, option-pool changes, and approval materials. Where an effective filed charter is a closing requirement, distinguish submission from effectiveness and check any specified effective time.
Record: Approval source, required signers, approved version, execution evidence, and filing dependencies. Escalate mismatched versions before release.
4. Reconcile conversions, allocations, and funding
Connect every SAFE or note to its executed instrument, amendments, and conversion-model cells. Verify holder identity, principal, accrued amounts where applicable, conversion triggers, discounts or caps where present, and required notices or consents. Identify missing inputs rather than accepting the workbook as conclusive.
Reconcile cash subscriptions separately from converted amounts. Check purchase prices, share counts, rounding, and post-closing capitalization. Assign issuance-record preparation and verification; an updated model alone should not be treated as the completed stock ledger.
Finance should verify payment instructions through an independently established channel. Distinguish a wire initiated from the receipt or release standard agreed by the parties, and reconcile any expense payments or deductions contemplated by the documents.
Record: Instrument IDs, model cells, reviewer, conversion documents, cash amounts, receipt evidence, and issuance-record tasks.
5. Assemble signatures, certificates, and remediation evidence
Assign preparation, signature, delivery, and verification separately. Check entity names, signing capacities, counterparts, exhibits, and version consistency. Track authorization to release signed pages rather than treating possession as permission.
RPX §§4.6–4.8 illustrate distinct deliverables: a secretary’s certificate with organizational documents and resolutions, a filed restated certificate remaining in effect, employee proprietary information and inventions agreements, and consultant agreements. These are negotiated conditions, not universal requirements. RPX purchase agreement, §§4.6–4.8. (sec.gov)
For a bring-down certificate, obtain current confirmations from responsible business owners against the actual representation standards. Escalate changed facts and determine any required disclosure or waiver treatment. If an opinion is negotiated, track its agreed form, supporting certificates, and delivery separately.
Record: Executed documents, attachments, confirmation sources, remediation evidence, and release restrictions. Drafted certificates remain incomplete.
6. Conduct a release-readiness review
Review each closing gate with company counsel, the company decision-maker, and relevant finance personnel. Classify it as verified complete, ready for coordinated release, unresolved, or covered by an authorized documented exception.
Check the sequence: which event must precede another, which releases are coordinated, and who confirms each event. Avoid circular instructions that require both parties to act only after the other has completed performance.
For exceptions, identify beneficiaries and applicable waiver mechanics. A lead investor’s commercial agreement to proceed does not establish authority to waive another purchaser’s condition. A contractual waiver also does not, by itself, satisfy a statutory requirement or cure the underlying defect.
Record: Verifier, final evidence, release sequence, exception authority, and residual risk. Preserve a closing-specific snapshot and obtain confirmation that assigned release instructions were followed.
7. Hand off notices and unfinished follow-up
Separate permitted follow-up from unsatisfied closing gates. Assign notice filings, issuance-record completion, additional-closing preparation, and agreed remediation to named owners. Confirm filing access and review arrangements before the deadline becomes urgent.
SEC guidance states that Form D is due within 15 calendar days after first sale—the first investor’s irrevocable contractual commitment. A Saturday, Sunday, or holiday deadline moves to the next business day. The wire date is not necessarily the trigger. SEC Form D FAQs, question 1. (sec.gov)
The guidance also addresses amendments for material errors, specified information changes, and annually while an offering continues, subject to exceptions. Rule 506 offerings may retain state notice and fee requirements; state timing requires separate review. SEC Form D FAQs, questions 6–8. (sec.gov)
Record: Verified trigger and evidence, calculated deadline, filer, reviewer, and receipt. Give additional-closing tasks their own applicability checks.
Worked example
Fictional scenario: Cedar Signal, Inc., a Delaware corporation, plans a $7.2 million cash Series A led by Harbor Lantern Ventures, plus conversion of a $450,000 note. A second investor may join later. Fictional SPA-07 requires an effective restated charter and assignments from listed personnel at the initial closing.
Counsel has signature pages, a filing-service submission email, CAP-06, and most personnel agreements. No complete note-amendment history has been provided. The team initially calls the package ready. These three representative rows show why release remains unresolved. Every party, document, amount, and contractual requirement in this example is fictional.
| ID / category | Deliverable / source | Closing / beneficiary | Prepare / sign / deliver / verify | Dependency / trigger | Due / release gate | Evidence / status | Exception / next action |
|---|---|---|---|---|---|---|---|
| F-01 / Filing | Effective charter; SPA-07 §5.2 | Initial / purchasers | Prepare: Maya, counsel; sign: Owen, CEO; deliver: filing service; verify: Maya | Approved charter version | Before release | Submission email only; unverified | Maya to obtain effectiveness evidence; submission alone insufficient |
| C-02 / Conversion | Conversion reconciliation; NOTE-03 §3; CAP-06 D18 | Initial / company and holder | Prepare: Leah, finance; sign: parties if required; deliver: Maya; verify: Leah and Maya | Complete operative note terms | Before issuance reconciliation | Model uses $450,000 principal; amendment history missing | Maya to obtain history; Leah to recheck calculation; amount not yet approved |
| R-03 / Condition | Consultant assignment; SPA-07 schedule 5.4 | Initial / purchasers | Prepare: Maya; sign: consultant; deliver: Owen; verify: Maya | Consultant signature | Before release unless validly waived | Unsigned form; missing | Owen to obtain signature; Maya to assess waiver authority and remaining IP exposure |
The filing row changes “filed” to “awaiting verification.” The conversion row does not prove a calculation error; it identifies insufficient support for approving the conversion amount. No interest, discount, or amendment terms are assumed from missing evidence.
The assignment row requires a closing-condition decision and assessment of the underlying IP exposure. Waiver would not create an assignment. Counsel keeps release on hold pending satisfaction or authorized exceptions; later purchasers receive separate condition checks rather than inheriting an unqualified completion status.
Common mistakes
- Copying a prior deal’s conditions. Retain useful categories, but replace requirements and citations with this financing’s documents.
- Tracking only investor deliverables. Include company conditions, payment evidence, conversion requirements, and issuance records.
- Equating signatures with release. Distinguish execution, custody, delivery, and release authorization where closing arrangements require it.
- Treating the capitalization model as authority. Link conversions to complete instruments and verify calculation inputs.
- Moving missing items to post-closing. First establish whether they are closing gates, who can authorize an exception, and what risk remains.
Final quality check
- Each gate cites the operative document version and provision.
- Initial and additional closings identify their conditions and beneficiaries separately.
- Corporate approvals, charter terms, allocations, and issuance figures reconcile.
- Completion claims link to evidence reviewed by a named verifier.
- Conversions distinguish cash proceeds from converted amounts and support their inputs.
- Exceptions identify authority, affected parties, written evidence, and residual risk.
- Release instructions specify dependencies and responsible confirmers.
- Filing triggers are verified; open issues have owners, due dates, and explicit closing treatment.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use contract review and tabular review to examine requirements across financing documents. In Word, choose the company as represented party and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present; lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name. Due diligence classification can organize supporting documents and prioritize human review. The checklist remains your work product, and counsel retains verification and release decisions. Book a demo to discuss this workflow.
Frequently asked questions
When should the company circulate the first checklist?
When operative drafts reveal likely conditions and deliverables. Mark provisional rows clearly and update them when negotiations change approvals, signatures, allocations, or release dependencies.
Should every diligence issue appear in the checklist?
No. Include issues that produce deliverables, affect conditions or disclosure treatment, or need assigned follow-up. Reference the diligence tracker rather than duplicating its analysis.
Can the lead investor waive every outstanding condition?
Do not assume so. Identify the affected condition and beneficiary, then read the applicable waiver provisions. RPX’s investor conditions illustrate why consent must be checked investor by investor. RPX purchase agreement, §4. (sec.gov)
Is funding the Form D deadline trigger?
Not necessarily. SEC guidance uses the first investor’s irrevocable contractual commitment. Counsel should determine that event from the documents and facts, then record evidence and calculate the deadline. SEC Form D FAQs, question 1. (sec.gov)
Sources
- Delaware General Corporation Law, §151: Delaware stock-rights provisions.
- RPX Corporation Series A and A-1 Preferred Stock Purchase Agreement, §4: historical contractual example, not market-standard evidence.
- SEC Frequently Asked Questions and Answers on Form D: federal notice timing, amendments, and state-requirement guidance.
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.
