Three weeks is not enough time to run due diligence the normal way. That is the point of this guide: you should not try. A 21-day window, whether forced by a bid procedures order, a DIP milestone, a liquidity cliff, or simply an aggressive buyer with leverage, requires a different operating model, not a faster version of the standard one.
I have watched compressed processes succeed and fail, and the difference is never effort. Both winning and losing teams work weekends. The difference is that winning teams make three structural decisions early: they launch an imperfect room fast, they tier access instead of curating, and they run a daily operating cadence with named owners. Here is the full playbook, day by day.
The Three Structural Decisions
Decision 1: Live Beats Complete
In a normal process, the room opens when it is ready. In a compressed process, the room opens on day 2 or 3 with whatever exists, and completeness is achieved in public, on a posted schedule. Bidders in fast processes expect gaps; what they punish is silence and surprise. A dated document status log ("cure cost schedule: expected day 9") converts missing documents from a red flag into a calendar item.
Decision 2: Tier Access, Do Not Curate
There is no time to hand-review every document for every audience. Instead, define two or three access tiers up front and sort documents into tiers as they are uploaded:
- Tier 1 (all NDA-signed parties): business overview, summary financials, asset registers, org structure
- Tier 2 (parties that submit indications of interest): detailed financials, material contracts, customer data with names redacted, forecasts
- Tier 3 (finalists or winning bidder): unredacted contracts, employee detail, sensitive litigation and pricing
Sorting into tiers takes seconds per document. Curating a bespoke view per bidder takes hours you do not have.
Decision 3: Named Owners and a Daily Cadence
Compressed processes fail through dropped handoffs, not missing effort. Assign four named roles on day 1:
| Role |
Owner |
Daily Duty |
| Room admin |
FA analyst or associate |
Uploads, permissions, index log, status log |
| Q&A marshal |
FA VP |
Triage questions, draft answers, chase SMEs |
| Counsel gate |
Deal counsel |
Approve every Q&A answer and new sensitive upload |
| Process lead |
FA MD / banker |
Read engagement analytics, decide escalations |
Then hold one 20-minute call every morning: overnight questions, today's uploads, bidder engagement readout, blockers. Every day, no exceptions.
The Day-by-Day Plan
Days 1-2: Stand Up the Room
- Select the platform if not already standing. Speed disqualifies most enterprise onboarding tracks; you need same-day or next-day deployment. Subscription platforms like Papermark go live in hours; if the mandate warrants an enterprise platform, Datasite can move fast when you tell them the court deadline. Platform selection criteria for distressed work are covered in our guide to the best data room for restructuring and bankruptcy.
- Clone your standard index. Do not design a folder structure from scratch under time pressure; adapt a template.
- Bulk upload everything that exists today, into the template, imperfectly. Target: 70 percent of expected volume uploaded by end of day 2.
- Configure tiers and user groups, including invisible walls between bidder organizations. Verify with two dummy accounts before any external user activates.
- Post the document status log as document 0.1 in the root folder.
Days 3-5: Open Tier 1 and Absorb the First Wave
- Activate NDA-signed parties into Tier 1 as counsel confirms each NDA.
- Expect the first Q&A wave to be about process, not substance: bid deadlines, cure schedules, access requests for colleagues. Template these answers.
- Continue uploading toward completeness; update the status log daily with actual dates, not aspirations.
- Start the engagement report: one page, every party, last login, documents viewed, trend. The process lead reads it every morning from day 3 onward.
Days 6-10: Deep Diligence Begins
- Open Tier 2 to qualifying parties.
- Q&A volume peaks here. Enforce the discipline: every question logged, answered once, reused for duplicates; counsel approves everything; 24-hour turnaround target, 48-hour hard limit. A single unanswered question aging past three days becomes a bid-deadline extension request.
- Schedule management access deliberately. In a three-week process, management can support perhaps 4-6 bidder calls total. Use the engagement analytics to allocate them: the bidder who has opened 400 documents gets a call; the one who logged in once does not.
- Mid-process index freeze: after day 10, add documents but never renumber or restructure folders. Bidders' internal trackers reference your index numbers.
Days 11-15: Separate Signal from Noise
- By day 12, engagement data tells you who is real. Typical pattern in a well-run process: of 15 parties in Tier 1, 6-8 enter Tier 2, and 3-4 show the sustained daily activity that predicts a bid.
- Push remaining document gaps to closure. Anything still missing at day 15 should be disclosed as permanently unavailable, priced in rather than hoped for.
- For the likely finalists, pre-stage Tier 3 so it can open within an hour of finalist designation.
- Counsel begins assembling the process record: NDA list vs activated users, access log export, Q&A log, index change log. Do not leave this for day 21.
Days 16-19: Finalist Sprint
- Open Tier 3 to finalists. Expect a second Q&A spike focused on contracts, cure costs, employees, and whatever the status log admitted was missing.
- Turnaround target drops to same-day. The Q&A marshal and counsel gate need cleared calendars this week.
- Watch for the late-arriving bidder. Fast processes often flush out a party who ignored the process until day 16. Have a policy decided in advance (usually: Tier 1 and 2 access immediately, no timeline extension) rather than improvising.
Days 20-21: Close the Record
- Bid deadline. Export the complete audit log the same day and deliver to counsel.
- Freeze the room: no uploads, no permission changes without counsel sign-off, until the process concludes.
- Archive plan confirmed: full export of documents plus logs, retained per your matter retention policy (seven years is the standard floor in distressed matters).
Where Compressed Processes Actually Break
Five failure modes account for most blown timelines:
- The room launches late. Every day of setup delay compresses bidder diligence further and generates extension requests. This is why deployment speed is a primary platform selection criterion, not a nice-to-have; our restructuring advisor's guide to choosing a VDR covers how to test it before you are on the clock.
- Q&A becomes a swamp. No marshal, no log, duplicate answers that contradict each other. In a court-supervised process, contradictory answers to different bidders are worse than slow answers.
- A wall fails. One bidder learns another's identity through a visible user list or a mis-routed answer. Test walls with dummy accounts on day 1; enforce a two-admin rule on permission changes thereafter.
- Management becomes the bottleneck. Unallocated management access means the loudest bidder consumes the calendar. Ration by engagement data.
- The record is assembled after the fact. If the audit trail, NDA reconciliation, and Q&A log are first compiled the night before a sale hearing, gaps surface at the worst moment. Build the record weekly.
What to Tell Bidders Up Front
A one-page process letter posted in the room's root folder prevents half the friction. It should state: the tier structure and how to advance; Q&A turnaround targets and the submission channel; the document status log's location and update cadence; management access policy; the index freeze date; and the bid deadline with the governing time zone. Bidders forgive a hard process; they do not forgive an opaque one.
The Bottom Line
A three-week deal room is a process design problem. Launch imperfect on day 2, tier instead of curate, name four owners, meet every morning, freeze the index at day 10, and build the court record as you go rather than at the end. Teams that follow that structure routinely close diligence in 21 days without extension requests. Teams that try to run a normal process faster do not.
Related Resources