vdr-management
VDR Management
The genesis of any M&A transaction involves the population of a Virtual Data Room. Sellers or their investment bankers dump thousands of poorly labeled files into a centralized repository — scanned PDFs of decades-old leases, raw Excel trial balances, unformatted payroll ledgers. The administrative burden of organizing these files represents a massive loss of analytical bandwidth.
When to Use
- A seller has uploaded unstructured documents to a VDR
- Buy-side teams need to organize incoming data room files for diligence
- Files need standardized naming conventions and folder hierarchies
- Deal teams need to transition from document discovery to analysis immediately
The /vdr-classify Protocol
How It Works
- Ingest each file's text using NLP and OCR
- Recognize the legal or financial taxonomy of each document
- Map to standard M&A index structures:
- Legal (corporate governance, contracts, IP, litigation)
- Financial (audited statements, tax returns, trial balances, bank statements)
- HR (employee census, benefit plans, org charts)
- Operational (customer lists, vendor agreements, real estate)
- Regulatory (permits, licenses, compliance records)
- Apply standardized naming conventions
- Generate a complete VDR index with document counts per category
Standard M&A Folder Hierarchy
VDR/
├── 01 - Corporate & Governance
├── 02 - Financial Statements & Tax
├── 03 - Material Contracts
├── 04 - Intellectual Property
├── 05 - Real Estate & Assets
├── 06 - HR & Employee Benefits
├── 07 - Insurance
├── 08 - Regulatory & Compliance
├── 09 - Environmental
├── 10 - Litigation & Claims
├── 11 - Technology & IT
├── 12 - Customers & Revenue
└── 13 - Miscellaneous
Output Format
## VDR Classification Report
**Total Files Processed**: [N]
**Auto-Classified**: [N] ([%])
**Requires Manual Review**: [N]
### Classification Summary
| Category | Files | Key Documents Identified |
|----------|-------|-------------------------|
| Corporate & Governance | [N] | Articles of incorporation, bylaws, board minutes... |
| Financial & Tax | [N] | 3-year audited financials, tax returns... |
| Material Contracts | [N] | Customer MSAs, vendor agreements... |
| ... | ... | ... |
### Flagged Items
- [Files that couldn't be classified]
- [Duplicate documents detected]
- [Missing expected documents (e.g., no audited financials found)]
Operating Guidelines
- Prioritize accuracy over speed — misclassified documents create downstream diligence errors
- Flag documents that appear to be duplicates or multiple versions
- Identify missing categories — if no tax returns are found, flag immediately
- Apply consistent date formatting in file names (YYYY-MM-DD)
- Preserve original file names in a mapping table for audit trail
- Never delete or modify original files — classification is additive
Time Savings
Saves 10+ hours per VDR drop. Eliminates the administrative friction of organizing misfiled or poorly named seller documents, creating a diligence-ready environment instantly.
More from lauraflorentin/skills-marketplace
multi-agent-collaboration
A structural pattern where multiple specialized agents communicate and coordinate to solve a problem that is too complex for a single agent. Use when user asks to "build a multi-agent system", "agents working together", "agent collaboration", or mentions team of agents, distributed agents, or swarm.
21reflection
A recursive pattern where an agent evaluates and critiques its own output to iteratively improve quality and catch errors. Use when user asks to "add self-reflection", "agent introspection", "self-critique", or mentions self-evaluation, meta-cognition, or quality self-assessment.
18human-in-the-loop
A hybrid pattern where the system pauses execution to request human approval, input, or disambiguation before proceeding with critical actions. Use when user asks to "add human approval", "require human review", "human-in-the-loop", or mentions approval workflows, human oversight, or escalation.
16planning
A high-level cognitive pattern where an agent formulates a structured sequence of actions (a plan) before executing any of them, ensuring goal-directed behavior. Use when user asks to "add planning to my agent", "task planning", "agent planning", or mentions plan generation, plan execution, or step-by-step planning.
14parallelization
A concurrency pattern where multiple agent tasks are executed at the same time to speed up processing or gather diverse perspectives. Use when user asks to "run agents in parallel", "parallelize tasks", "concurrent execution", or mentions parallel processing, fan-out, or batch execution.
13routing
A control flow pattern where a central component classifies an input request and directs it to the most appropriate specialized agent or tool. Use when user asks to "route between agents", "agent routing", "task dispatch", or mentions classifier routing, intent detection, or agent selection.
12