Fundraising Operations
Equity Document Versions: Keep the Approved Terms Traceable
Keep equity proposals, approved agreements and amendments connected without assuming the newest file always controls.
What you will learn
- Distinguish a file version from an operative amendment.
- Trace which document changes which award terms.
- Preserve an evidence trail without treating filenames as legal authority.
Equity document control is about relationships, not just the newest filename. Keep proposals, executed agreements and amendments connected, with their status and scope visible. If two documents appear to conflict, route the question to the appropriate owner instead of deciding that the latest upload automatically wins.
Use two kinds of history
File history records edits, uploads and versions. Award history records the documents and decisions that apply to a particular award. A recently uploaded copy can contain older terms; a small amendment can change one clause without replacing the entire agreement. Both histories matter.
The ICO’s document-control policy illustrates how one organization distinguishes draft and final documents and traces changes. It supports the operating practice, not a legal rule about which equity agreement controls.
Map documents by relationship and scope
This fictional case contains an executed grant and a later amendment. The company’s authorized reviewer, not the filename, confirms which terms apply.
Original equity document relationship map
| Record | Status and relationship | Scope to confirm |
|---|---|---|
| Plan P, version 1 | Plan referenced by Grant A | Applicable plan and referenced terms |
| Grant A, signed copy | Executed award record under Plan P | Quantity, schedule and other documented terms |
| Amendment B, executed copy | Applies to Grant A as confirmed by reviewer | Changes one specified expiry term; other effects need confirmation |
| Proposal C, draft | Unapproved proposal for another change | Not treated as current award terms |
| Portal summary | Administrative representation of applicable records | Check that affected fields match confirmed sources |
Give each record a stable reference, source date, version, status, owner and access location. Keep the document itself alongside the map; the map is an index, not a replacement agreement.
Do not infer legal precedence from a label
“Final,” “signed” and “approved” should have evidence behind them. A filename such as final-v7-new.pdf does not establish execution, authority or applicability. A document about one grant may not apply to another grant held by the same person.
A historical equity plan filed with the SEC illustrates how a plan and instrument-specific agreements can interact. It does not establish the interpretation of another company’s plan, amendment or recipient record.
Control the working copy without deleting history
- Choose a clear current working packet after the authorized owner confirms its scope.
- Mark superseded or draft materials visibly without destroying them.
- Record what changed and which records may need review.
- Limit access to the appropriate participants and permitted excerpts.
- Keep unresolved conflicts in a questions log rather than silently rewriting the index.
The goal is one traceable explanation of the current packet, not one file left after deleting every awkward earlier version. Retention obligations and legal preservation questions require their actual owner.
Exercise: a new upload versus a scoped amendment
An employee uploads an older signed Grant A after Amendment B has already been stored. The upload timestamp is newer. Should the team discard Amendment B and call Grant A the latest terms?
Answer: No. Upload time alone does not resolve the document relationship. Preserve both, identify the actual execution dates and amendment scope, and ask the authorized owner to confirm the operative packet. The upload may only be a newly received copy of an older record.
Make the index useful during a real handoff
The cap-table checklist explains why source-backed records matter. This lesson adds the narrower document relationship map, not another generic record checklist.
Use Finta Documents to organize permitted files and the questions around them. Do not describe Finta as determining legal precedence, issuing grants or certifying an award record. The human-owned index should make review easier, not pretend review is unnecessary.
General education with fictional examples, not individualized legal, tax, valuation or investment advice. Have the appropriate professional review decisions affecting actual awards or transactions.