Checklist
Defines what the review expects, but not whether the room contains it.
Start from a structured diligence template, expose the right sections to each review group, and see which expected materials are present and which gaps remain.

The checklist tracks expected evidence. The folder holds files. Email carries the questions. RoundOS brings the structure, documents and review context into the same room.
Defines what the review expects, but not whether the room contains it.
Stores documents, but cannot expose missing checklist items or contextual questions.
Carries answers, but separates them from the material a reviewer was looking at.
Choose a diligence room template, adjust its sections and add placeholders for evidence that has not arrived yet. RoundOS shows which expected materials are present and which checklist gaps remain.
Create the groups your review uses and decide which room sections each group can open. A group called Lead reviewers might see the whole room; Co-reviewers and Counsel might see narrower scopes.

Name groups the way your process already works: lead reviewer, counsel and specialist. Then choose the sections each group can open.
A reviewer asks from the material they are reading. The answer remains attached to that context and can be shared with the thread, the originating group or the room.
Which assumptions changed in the current version?
Does this schedule include the renewal?
Is the latest audit attached here?
Which assumptions changed in the current version?
Replies stay with this material and can be visible to the thread, the originating group, or the room.
Checklist gaps show missing or unfilled evidence. Named room activity shows who opened each section and when. Together they answer two different questions about the state of the review.
Opened Revenue bridge.xlsx this morning
Last opened four days ago
RoundOS keeps checklist coverage, current evidence, scoped access, contextual Q&A and named activity together.
The checklist can look complete while the expected evidence is still missing.
Tracks expected workDocuments arrive, but missing evidence and review context live somewhere else.
Stores evidenceChecklist gaps, current files, group visibility, Q&A and named activity share one room.
Runs the review surfaceA diligence template gives the room checklist-backed structure. RoundOS can then show which expected materials are present and which template gaps remain.
Yes. Start from a RoundOS room template, adjust its sections, add room items, and use placeholders for evidence that has not arrived yet.
Yes. Create access groups around the review process, then choose which room sections each group can open and add recipient-level exceptions where needed.
Yes. Reviewers submit questions from the material, and answers stay attached to that context instead of scattering across inboxes.
The Diligence gaps panel lists checklist items that are missing or still represented by an unfilled placeholder. When no template gaps remain, the checklist is complete.
No app is required. A reviewer opens the room link and completes any gate you configured, such as email verification, before viewing the room.
Add a new version to the same material. Links using latest open the current file while version history remains attached.
Choose the structure, add the evidence, and expose the right room to each group.