Questions answered
- How should an SME VDR be structured?
- Who should access what?
- How should Q&A and revocation work?
Outcome
Build a VDR that enables diligence without turning confidentiality into operational chaos.
The target state is a workspace where every document has an owner, version, access tier and traceable usage history.
1. Workflow
Classify -> Prepare -> NDA -> Grant -> Review -> Q&A -> Update -> Revoke/Expire -> Evidence export
| Gate | Question | Output |
|---|---|---|
| V0 | What information exists? | T0/T1/T2 classification |
| V1 | Is the file ready? | index + owners + versions |
| V2 | Can this counterparty access? | NDA + qualification + permission |
| V3 | Is scope proportionate? | ACL + expiry + download policy |
| V4 | Is diligence traceable? | Q&A + logs + issues |
| V5 | Can access close cleanly? | revoke + evidence pack |
2. Structure folders around diligence questions
A useful architecture may cover corporate, finance, tax, commercial, contracts, people, assets/operations, technology/cyber, permits/compliance and transaction documents.
Do not create 100 empty folders. Structure should reflect the real complexity of the file.
3. Minimum document index
Each row: document_id, title, domain, owner, source_date, version, evidence_status, tier, download_allowed, access_group, expiry, supersedes.
4. Permissions
Use deny by default.
Typical groups: seller core team, buyer core team, buyer advisers, scoped expert, clean team, compliance. A technical administrator does not receive business-document read access by default.

