Document Review

Verification reads a deliverable unit by unit (PDF pages, PowerPoint slides or Word pages), pulls out the factual assertions, and checks each one against the project knowledge base and its cited sources. Every claim is anchored to the exact span it applies to and given a verdict, shown as a coloured highlight you can click to see the reasoning and the sources behind it.

Where a claim can't be settled from your documents alone, verification can also research the web and trusted knowledge bases where appropriate, but your project's own sources always take precedence.

• Traceable. Click any highlight to see the verdict, the reasoning, and the verbatim source excerpts it rests on.
• Editable. Advisors can adjust a verdict, re-anchor it, flag it, or delete it; human decisions are pinned and preserved across edits.
• Self-healing. Re-running verification re-cites claims; your manual highlights and verdicts are never overwritten.

Verification checks whether claims are true; feedback agents check whether the deliverable is good. A panel of expert agents reads the whole deck in parallel and leaves structured findings, each pinned to the slide it concerns, from four distinct perspectives:

Each agent sees every slide before it finishes and submits comments you can work through, accept, or dismiss: a second pair of expert eyes on the deck before it goes out.

Beyond the four built-in agents, you can define your own feedback personas in the library: a name, title, and the focus areas they should care about (for example, a sector specialist, a risk officer, or a fussy partner). Add a persona to a feedback run and it joins the panel with its own perspective, so the critique reflects how your firm actually pressure-tests work.

Verification and feedback agents are a machine second opinion; sometimes you want a human one. Open the Reviews panel in the viewer or editor toolbar and choose Request to ask another member of the project to look over the deliverable. Pick the reviewer, add an optional note, and they receive an email, “so-and-so has requested your review”, with a link that opens the document straight into their review.

You can also review a document yourself. Start review in the same panel opens a review assigned to you, with no email sent, and takes you straight into it. Picking yourself as the reviewer on a final request is how you sign your own work off once every open issue is addressed.

A review isn't a checklist you go hunting for. As the reviewer you get Work through N issues, and the Reviews panel turns into the review itself, taking you through them one at a time: it turns the document to the slide or page, rings the claim there, and puts that claim in the panel ready to work on — its verdict, reasoning and sources, with Save, Approve and Delete always in the same place at the bottom. Deal with it and the next one comes up; Next moves on without touching it, so you can leave one and come back to it later.

The panel keeps count of where you are and what's left, and once nothing is outstanding it offers the sign-off itself: Mark complete. Leave the walkthrough at any point and the review stays open where you left it, back in the list of requests.

Some organizations require that a second pair of eyes signs a document off. An owner or admin can turn self-review off under Allow self-review in organization settings, and members then see only the option to request a review from a colleague.

There are two kinds of request:

• Standard. An informal “please take a look”. The reviewer can walk the outstanding issues the same way, and mark it complete whenever they're satisfied.
• Final. A formal sign-off. A final review can only be marked complete once every open issue on the document, contradictions, citation issues, and anything else still unresolved, has been addressed, whether that's by fixing it, dismissing it, or approving it as-is. Sign-off waits at the end of the walkthrough, so the only way to complete one is to have been through everything.

The Reviews panel keeps the full history for every deliverable, whether it's a slate or a PDF. Requests still in progress and completed reviews alike, with who reviewed and when. Either the requester or the reviewer can retract a request that's no longer needed. “Final” is simply the name for the gated kind of review, and a document can go through as many final reviews as its life requires.

When you're ready to put a reviewed deliverable in front of someone outside the project, use Share in the deliverable header. Choose Create share link to mint a Public share link, then Copy link. Anyone with the link gets a read-only view of the claims overview: verdicts and citations, but no comments, review tools or source files. Click Revoke link to switch it off immediately.