Most data room mistakes are invisible to the person who made them. The admin who built the permission groups sees the room as an admin, with everything visible. Only a user inside a restricted group discovers that a folder meant for the second round is open to everyone, or that the watermark is missing on printed pages. If that user is a real bidder, the mistake has already happened.
A dry run moves that discovery to a safe moment. It takes a few hours, needs a handful of colleagues and costs nothing. It is the single most effective quality check available to a data room admin.
When should the dry run happen?
Timing is a balance. Too early, and the room is not finished, so the test misses the final state. Too late, and there is no time to fix what it finds. Two to five working days before the first invitations go out works for most processes.
By then, the index should be complete, the first-round documents uploaded, the permission groups created and the main settings chosen. Late documents can still arrive after the dry run, but the structure and rules should be final.
Who takes part, and which test groups do you need?
Create one test user for every permission group that will exist on launch day, using colleagues’ email addresses (not shared mailboxes) so that invitations and verification work as they will for real guests.
| Test group | Mirrors | Tester | Main question |
|---|---|---|---|
| Test bidder A | A first-round bidder | Colleague outside the deal team | Do they see only first-round folders? |
| Test bidder B | A second bidder | Another colleague | Can they see anything from bidder A, including questions? |
| Test clean team | A clean team member | Colleague briefed on clean team rules | Do they see the restricted tier, and only that? |
| Test adviser | Seller’s adviser with upload rights | Junior adviser | Can they upload to their folders and nowhere else? |
| Test expert | Company expert answering questions | Finance or legal lead | Do they see assigned questions without bidder names? |
| Admin observer | The real admin | The admin | What does the activity log record? |
Testers outside the deal team are valuable because they know nothing about the room’s structure. They will not unconsciously avoid the folders they should not open.
What should the dry run check?
Running a data room dry run
- Send real invitations
Invite each test user through the platform exactly as bidders will be invited. Note whether any invitation lands in spam or is delayed.
- Complete first login
Each tester signs in, accepts any terms and sets up 2-step verification. Note anything confusing.
- Map what each group sees
Each tester lists the top-level folders they can see and opens one document in each. Compare the lists with the permission plan.
- Test document rights
Testers try to download, print and copy text from a view-only document and from a standard one, and report what happened.
- Check watermarks
Testers print one page to PDF and take a screenshot of one viewed page. Confirm their name and the time are visible and readable.
- Rehearse a Q&A cycle
Each test bidder submits one question. Route it, draft an answer, approve it and release it. Confirm only the asking bidder receives it.
- Test notifications
Upload a new document to a first-round folder. Confirm test bidders get the notification and the clean team does not, unless intended.
- Review the activity log
The admin checks that every test action appears with the right user, document and time, and exports a sample report.
Which platform features does the dry run exercise?
Each check above tests a feature the platform claims to provide. The matrix shows how many of the 18 platforms in our facts file list each one, and the dry run check that proves it works in your room.
Features the dry run tests, and how widely they are listed
| Platforms listing | Dry run check | |
|---|---|---|
| File-level access rights | 15 of 18 | View-only and download behave per group |
| Viewer watermarks | 18 of 18 | Name and time visible on screen and in print |
| 2-step verification | 14 of 18 | Second step requested on first login |
| Q&A workflow | 13 of 18 | One question from submission to release |
| Bulk import | 17 of 18 | Numbering matches the agreed index |
| Activity log | 18 of 18 | Test views appear with user and time |
If your platform does not list one of these features, replace the check with the process that covers the gap. Without a Q&A workflow, for instance, rehearse the question log and approval by email so that everyone knows the routine. The feature comparison shows which features your platform lists.
What usually goes wrong?
Dry runs find problems in a predictable set of places. Knowing them helps testers look in the right corners.
| Finding | Typical cause | Fix |
|---|---|---|
| A test bidder sees a second-round folder | Subfolder inherited rights from a parent, or a group was added to the wrong folder | Correct rights, retest that group |
| Watermark missing on printed pages | Watermark set for viewing only | Enable for print and download |
| Invitation in spam | New sending domain, strict filters | Ask the vendor about sender settings; tell bidders to allowlist |
| Expert sees bidder names | Default Q&A setting shows identity | Hide submitter identity from experts |
| Notification sent to all groups | Notification rule applied at room level | Set notifications per folder or group |
| Activity log shows the admin, not the tester | Admin used view-as instead of a real test login | Repeat with a real test account |
The first row is by far the most common and the most serious. Inheritance rules differ between platforms and catch out experienced admins, which is why every group needs its own tester.
What goes on the go or no-go list?
End the dry run with a short written list, reviewed by the deal lead. Each item is either passed, fixed and retested, or open. Permission items block launch if open; other items can be accepted with a plan.
Data room go or no-go list
- Every test group saw exactly the folders in the permission plan
- No test bidder could see another bidder's questions, answers or activity
- View-only documents could not be downloaded or printed
- Watermarks visible on viewed and printed pages
- 2-step verification required for every test guest
- One question completed the full Q&A cycle and reached only the asking bidder
- Notifications reached the intended groups only
- Activity log recorded every test action and exports cleanly
- Test users disabled, admin list confirmed
Once the list is complete, send invitations in batches and check the first real logins against it. The data room setup hub covers the steps before and after launch, and our beginner’s manual covers the basics of building the room.
How long does a dry run take?
For a room with three to five groups, plan half a day: an hour for invitations and first logins, two hours for the checks, an hour to fix findings and retest. Larger rooms with many groups or a clean team take a full day. Compared with the cost of a bidder seeing the wrong folder, it is cheap insurance.
It also has a side benefit. Testers who have been through the room become useful helpers on launch day, able to answer the routine “how do I” questions from bidders while the admin deals with exceptions.
Frequently asked questions
Can I use view-as instead of real test users?
View-as is useful for quick checks, but it does not test invitations, sign-in, 2-step verification, notifications or the activity log. A dry run needs real test accounts.
Should the seller's advisers take part?
Yes. The sell-side adviser usually runs the process and should see the room as bidders will. A junior adviser makes a good tester for the adviser group.
What if the dry run finds a permission error?
Fix it, then retest that group and any group sharing the affected folders. Do not launch until every permission item on the list has passed.
Do we need a dry run for a small room?
Even a room with one counterparty benefits from a short version: one test guest, one view-only check, one watermark check and one question. It takes under an hour.