Plumbing company Data-room index

What decision should a data-room index help reviewers make?

Readers need correct proof, covered facts and permitted use. A bare file list cannot show them. Record scope and version before using totals for a decision.

The selling hub, document guide and confidentiality guide frame preparation and staged access. This page provides manifest fields and controls linked to actual review purpose.

Record coordinator, date, deal and authorized roles. Keep files and permissions in the repository. Reference sensitive proof without exposing unnecessary contents through the manifest.

These fields are original workflow design, not a prescribed tax index or required product. Adapt them to actual review, contract and retention needs.

Which fields belong in the evidence manifest?

Use stable IDs despite filename changes. Record entity, dates and population first. Different branches can produce valid totals that answer different questions.

Exclude passwords, unrestricted bank details and unnecessary personal data. References can point to protected files. Check the manifest itself for sensitive detail before release.

Mark current, superseded, received, clarification needed or accepted for this purpose. Describe actual review. Keep open limits and the next required response visible.

Which eight index controls should be checked?

1. 1.
   Create stable document identifiers.

   Give each file a stable reference, named owner and category. Link duplicates to their common origin where appropriate. An ID should survive renaming. Numbering cannot create a legal filing duty or certify truth, confidentiality or retention. Keep the reference consistent so later reviewers can trace the exact proof and its related questions.

2. 2.
   State entity, period, and reporting population.

   Name entity, relevant branch or service, dates, accounting basis and filters. Record exclusions and limits. A regional total differs from one location's result. Show those boundaries before using the file for earnings, customers, staff or working capital. Check that the population matches the conclusion, rather than assume identical report titles mean comparable records.

3. 3.
   Record origin and reconciliation references.

   Identify original statements, vendor exports, adviser reports and seller summaries. Link supporting records and name who explains differences. Preserve filters and sample checks. A tidy filename cannot reconcile a summary with books or source transactions. Record what has actually been tested and which differences need a response before readers rely on the total.

4. 4.
   Separate sensitive detail from general review files.

   Inventory personal, bank, customer, staff and sensitive commercial fields. Decide what may be masked or grouped for this review stage. Name restricted copies and permitted readers without repeating their contents. Masking should preserve useful scope and explain its limits. Check the version actually released, rather than assume the blank template protects all details.

5. 5.
   Map and test minimum necessary access.

   List user roles, permitted files and the responsible administrator. Test real settings, including inherited rights and share links. Record date and open issues. The index states a plan; the repository must enforce it. Keep passwords and tokens out of the manifest. Review access again when people leave or their role in the deal changes.

6. 6.
   Control current and superseded versions.

   Record revisions, dates, reasons and the current copy. Preserve evidence used in an earlier review when corrections change facts. Name the correction approver and affected conclusions. Do not silently overwrite for a tidy room. Readers need to see what changed and which previous findings must be checked again before using the new version.

7. 7.
   Connect each file to requests and reviewer outcomes.

   Link files and requests both ways. Several files may answer one request, and one file may serve several reviews. Separate receipt from adequacy. Record purpose, exceptions and next owner. Upload cannot close license, finance, tax or earnings questions that still need other proof or professional judgment. Keep the acceptance finding limited to its stated use.

8. 8.
   Assign backup, recovery, and incident responsibilities.

   Assign recovery checks, permitted restore tests, access review and incident response to real people. Keep contacts and proof in restricted process records. Backups, hashes and NDAs cannot guarantee truth, lawful disclosure or freedom from loss. Check the actual control and its limits. A recorded plan cannot replace the administrator's test or the required response to an incident.

Which source boundaries should the manifest preserve?

The FTC guide supports inventories, limited access, protected transmission and response plans. It is general guidance, not a universal acquisition-room rule.

NIST's guide covers inventories, duties, access, backups and recovery. It is voluntary, not certification or guarantee. Record tested controls rather than framework labels.

IRS Publication 583 explains receipt and expense support. It cannot prescribe this manifest or every retention period. Ask about actual duties and permitted disposal timing.

ServiceTitan's instructions explain filters, permissions and formats. Record export scope. Reporting access cannot establish database transfer or verified accounting. Reconcile permitted samples before relying on totals.

What does a worked version correction look like?

Assume hypothetical file F-012 contains January–September jobs. Version 1 includes canceled records; version 2 excludes them. The count changes from 600 to 500. These invented figures show how a filter correction affects the manifest.

Keep F-012 stable while naming each version separately. Record date, filters, reason, preparer and affected requests. Mark the first copy superseded for current analysis. Preserve it as evidence of the earlier conclusion and what its reviewer saw.

Reconcile the new population and affected comparisons. A count change cannot prove changed revenue until records are checked. Name who reviews the unresolved effects.

Explain corrections for someone who missed the first upload. Identify replaced proof, reason and affected findings. A shared filename cannot supply that history.

How should the access map follow review stages?

List each role's required categories. Early review may use grouped concentration; later authorized specialists may need detail. Match purpose and stage before permitting broader disclosure.

Record stage, recipient, purpose and access-test owner. An NDA cannot grant rights to all personal files. Confirm settings and date before wider release.

Use the pre-sale checklist for gaps, buyer request list for decisions and earnings guide for financial proof. Link documents to those review purposes rather than treat their presence as acceptance.

When reviewers leave or change role, reassess access through the administrator. Keep the process record restricted. Public examples should not expose real permissions or findings.

How should an owner maintain the index over time?

1. Identify the original evidence and assign its ID, scope, and owner.
2. Prepare appropriate versions for the authorized release stage.
3. Test access settings before the intended reviewer receives access.
4. Link requests and record receipt, exceptions, and review outcomes.
5. Preserve correction history and review access when files or roles change.

Actual law, contracts, providers and retention rules govern. A chosen review date cannot replace them. Assign unresolved use, storage and disposal questions to the right adviser.

How should the working index be printed?

Print fields and checks for controlled review. Record IDs, versions, scope, status and reviewer separately. Reference contents without repeating them. Keep purpose and date visible.

Print removes navigation and conversion panels. Protect filenames and notes as appropriate. Share only with authorized readers and keep references aligned with current restricted versions.

Which mistakes make an evidence room unreliable?

Common problems include anonymous files, missing dates, open links, duplicate current copies and requests closed on receipt. Compare the manifest with real files and settings. Preserve missing proof and name who resolves each gap.

Maintain origin, access and purpose as the deal develops. The first upload is not completion. Preserve corrections and role changes so reviewers can trace remaining work.