A review round sends an issued release to a reader — a client, a co-investor, the target's management — and collects their markup against it.
What a reviewer can do
- Raise a thread anchored to a specific block, so a comment is attached to the sentence or table it concerns rather than floating in an email.
- Record a verdict on a finding: accepted, disputed, or needs clarification.
- Reply, back and forth, until the point is closed.
What you do with it
Each thread lands beside the block in the compose view. You reply, revise the block, or record that the point was considered and not changed. A revision made during a review round is a Revised block like any other, so the trail shows the report changed because a reviewer pushed back.
Rounds are bounded
A round is opened against a specific release and closed when you close it. That gives you a clean answer to "what did they object to, and what did we do about it" — per round, rather than an unbounded comment stream across the life of the project.
Reviewers are not billed
An external reviewer is not a licensed user. Their access is scoped to the release you shared and ends when the share does.
Availability
Part of the plans that include review rounds, and requires an issued release — you cannot send a live draft out for markup.