Outcome: a reviewed data-room inventory that makes four evidence states visible for every requested item: present, missing, unverified, or not applicable. Sharing approval is recorded separately.
This workflow helps a team find gaps before it shares a room. It does not certify completeness, accuracy, legal sufficiency, security, or diligence readiness. The final request list and disclosure decisions belong to the company, its investor or counterparty, and the relevant legal, finance, tax, privacy, security, and operating reviewers.
Inputs
- The intended recipient or audience
- The fundraising or diligence stage
- The investor's actual request list, if one exists
- The current Documents folder and approved source systems
- Named owners for legal, finance, people, product, security, and commercial material
- A review date and decision owner
Use a four-state inventory
| State | Meaning | Required next step |
|---|---|---|
| Present | A candidate file or source was located and its identity, version, and source were recorded | Route it to the accountable owner for a separate sharing decision |
| Missing | The requested item is not present or cannot be located | Assign an owner and date, or explain why it will not be provided |
| Unverified | A candidate exists, but its version, accuracy, scope, or source remains unresolved | Route it to the appropriate owner or qualified reviewer |
| Not applicable | The item does not apply to this company or transaction | Record the reason and reviewer |
Do not use a single green check to collapse “present” and “approved.” Track approval in a separate field with the accountable owner, decision date, intended audience, and any restriction. A file can exist and still be stale, inaccurate, unsigned, duplicative, overbroad, or inappropriate for the recipient.
Start with the actual request
If an investor or counterparty supplied a request list, make it the primary checklist. Preserve the wording and source so the team does not silently reinterpret the request.
When no request list exists, use Finta's documents to include in your data room for due diligence as the canonical starting checklist. Do not reproduce it here. Add, remove, or narrow items based on the company, stage, industry, jurisdiction, and professional advice.
Run the workflow
1. Freeze the review scope
Record the audience, stage, request source, room owner, reviewers, and review date. A broad internal archive and an investor-facing room are not the same thing.
2. Reconcile files to checklist items
For each requested item, record:
- exact request;
- file or source link;
- version date;
- accountable owner;
- inventory state;
- sharing scope;
- unresolved issue;
- next action and due date.
Use file hashes or other version identifiers when the team's systems support them. Do not claim version certainty from a file name alone.
3. Ask Aurora for a source-linked first pass
Aurora can work with supported indexed Documents and available workspace context. Use a prompt that preserves uncertainty:
Compare the supported documents in this folder with the attached request list. For each request, cite the file or source you found and propose one evidence state: present, missing, unverified, or not applicable. Never treat presence as approval. Identify conflicting numbers, stale dates, duplicates, and unsupported assumptions. Add a separate approval field for an accountable human owner to complete. Prepare a review table only. Do not publish, share, or send anything.
Aurora can accelerate matching and gap identification. It cannot know whether an absent document exists outside Finta, whether a source is legally sufficient, or whether confidential information may be disclosed.
4. Review by domain owner
Each accountable owner confirms the relevant rows. Finance should reconcile key numbers to the source of truth. Counsel should review legal and disclosure questions. Product and security owners should verify technical material. People leaders should review employee and personal information.
5. Resolve conflicts visibly
When two files disagree, keep both sources and assign resolution. Do not let AI select the more plausible number. When a requested item is not applicable, explain why rather than leaving the row blank.
6. Build the approved room only after review
Move only items that are present and separately approved into the intended Share Page. Keep missing, unverified, and unapproved items in the internal inventory. If the team chooses to disclose a known gap, write an accurate explanation and name the follow-up owner.
Use Create an Investor Data Room With AI after the inventory has been reviewed.
Completeness review table
| Request | Source | Owner | Evidence state | Approval | Sharing scope | Next action |
|---|---|---|---|---|---|---|
| Monthly financials | Finance folder, August close | Controller | Present | Approved September 14 | Named investor diligence team | Add approved PDF and model |
| Customer concentration | CRM export | Revenue lead | Unverified | Not approved | Pending confidentiality review | Aggregate and review with counsel |
| IP assignments | Legal folder | Counsel | Missing | Not approved | Not shareable yet | Complete assignment and confirm |
| Physical inventory | None | COO | Not applicable | Not needed | Explain if asked | Record company has no physical inventory |
Worked example
A Series A company has 46 files and a 28-item investor request. Aurora finds likely matches for 22 items, flags two files with inconsistent revenue figures, and finds no source for four requests. The team does not report “79 percent complete.” Instead, each owner reviews the proposed matches.
Finance resolves the conflicting revenue files, marks the selected source present, and approves one version. Counsel keeps two contracts unverified because they contain sensitive terms. The COO records two requests as not applicable. Four items remain missing with named owners and dates. Only items that are both present and separately approved move to the external room.
The result is a truthful inventory, not a readiness score.
Completion checks
- Every checklist row has a source or an explicit missing state.
- Every present row has a source, version identifier, and accountable owner.
- Every approved row has a separate approval decision, audience, owner, and review date.
- Conflicting numbers and duplicate versions are resolved or visibly open.
- Sensitive information has an explicit sharing decision.
- Not-applicable decisions include a reason.
- Missing items include an owner, next action, and date.
- Only approved materials appear in the visitor-facing room.
- The room has a future review date for freshness.
Human approval boundary
Aurora may search supported documents, compare them with a supplied checklist, identify possible gaps, and prepare a review table or tasks. People determine whether the sources are correct, complete, current, and appropriate to disclose.
What this workflow does not replace
- Legal, finance, tax, audit, privacy, or security diligence
- A counterparty's formal request list
- Systems of record for finance, ownership, contracts, people, or security
- Independent verification of statements or documents
- Specialist VDR administration or transaction management
- Human approval of the final room and recipient access
