Use case
Preparing a request list before folder creation
Download the CSV, open it in Excel or Google Sheets, customise the rows, then upload the finished index to Data Room Builder. The columns are intentionally simple: Level 1, Level 2, Level 3 and Notes.
| Level 1 | Level 2 | Level 3 | Notes |
|---|---|---|---|
| Corporate | Formation documents | Articles and certificate | Latest filed versions |
| Corporate | Ownership | Cap table | Fully diluted if applicable |
| Finance | Historical financials | Audited accounts | Three years |
| Finance | Forecast | Budget and model | Include assumptions where shareable |
| Contracts | Customers | Top customer contracts | Include amendments and side letters |
| HR | Employees | Employee census | Exclude personal data unless needed |
| Tax | Returns | Filed tax returns | By jurisdiction and year |
| IT | Systems | Core software list | Licences, owners and renewal dates |
Implementation tips
- Add owner, status and confidentiality columns before collecting documents.
- Use consistent folder names in the request list so upload teams do not create duplicates.
- Separate internal preparation notes from the buyer-facing index.
FAQs
What columns should a request list include?
At minimum: category, subcategory, request description, owner, status, notes and target folder path.
When should a request list become a data room?
Once the top-level categories are stable and each request has a target folder, convert the request list into the room structure.