Process

Running a diligence Q&A thread without losing the answers

Multi party Q&A is the feature that separates a document store from a deal room. It also fails in predictable ways.

Vault Index desk / 14 August 2026 / 7 min read

Why email loses

Diligence questions arrive faster than anyone expects and touch documents that keep being revised. In an inbox, an answer given on Tuesday about version two of the lease schedule becomes a liability by Friday when version three is uploaded, because nothing connects the two.

A room thread attaches the question to the document and keeps the version history alongside it. When somebody later asks what the buyer was told, there is one place to look.

The roles that make it work

Give each side a single gatekeeper who owns triage. On the seller side that person routes each question to the right subject matter owner, checks the draft answer against what has already been said, and releases it. On the buyer side it stops four advisers asking the same question three different ways.

Set a service level in the kick off note, typically two working days, and publish the count of open questions weekly. Visible ageing is the cheapest way to keep a process honest.

Separating bidders

In a competitive process, an answer released to everyone tells each bidder what the others are worried about. Rooms built for auctions let you answer privately, or publish to all where fairness requires it. Decide the default before the first question arrives and write it into the process letter.

Closing the thread

At completion, export the full question and answer log with timestamps and attach it to the closing record alongside the document index. Buyers ask for it, counsel expects it, and it costs nothing if the platform supports export. Confirm that it does before the process starts rather than in the final week.

Sources and further reading

Vendor figures rechecked 1 September 2026