Reviewing documents
Run Review to grade a document on a four-dimension scorecard in one pass, fix the ranked findings with inline accept, check the citations behind grounded findings, and track the score in your document library.
A finished draft is the record of decisions you already made. Review grades that draft like a coach would: it scores the decisions and assumptions it rests on, grounded in your own context, and shows you what to fix first. Open a document, click Review, and ForceVue checks it in a single pass, then hands back a scorecard and a ranked list of findings you can act on in place.
The scorecard
Every review grades your draft on four dimensions and gives it an overall score from 0 to 100:
- Strategy: is the work arguing for the right thing, with goals and evidence behind it?
- Structure: is the draft organized to be used, with the sections a reader expects?
- Clarity: is the prose specific enough to build from, with testable conditions and measurable claims?
- Completeness: could a team start tomorrow, or are details and open questions still unnamed?
The grades sit at the top of the review panel as soon as the run finishes. There is nothing to expand: the overall grade and score, a one-line summary, and all four dimension grades are right there. Hover a dimension to read the one-sentence reason behind its grade.
Your latest overall score also shows on the document's card in the initiative's Documents list, so you can see at a glance which drafts have been reviewed and how they hold up. Edit the document and run Review again to refresh the score.
Run a review
- Open a document.
- Click Review. It sits in the editor toolbar, and there is a Review button on the document view page too.
- Watch the panel narrate what it is doing, from reading your document to grading the four dimensions and ranking the fixes.
- The scorecard and findings appear in a side panel next to the document.
The whole scorecard comes from one pass over the document, not a back-and-forth and not one call per dimension.
Fix these first
Findings come back ranked, with the most consequential gap at the top and polish at the bottom, under a Fix these first header. Each finding names the dimension it counts against, so you can see which grade it is dragging down.
You get two kinds of feedback:
- Inline findings tied to a specific passage. Some propose a concrete change you can accept in place, others are notes to act on.
- Document-level findings about the draft as a whole, shown as a banner at the top.
From the side panel:
- Click a finding to jump straight to the passage it refers to.
- Accept applies the proposed change to your document.
- Accept all applies every proposed change in one click.
- Dismiss drops a finding you disagree with. Dismiss all clears the list. Dismissed findings stay gone if you re-run the review on the same unedited text; edit the document and a fresh review looks at it with clear eyes.
A finding whose passage you changed after the review drops its Accept button, so an edit is never applied to the wrong place. Re-run the review to refresh it.
Grounded findings and reviewer judgment
ForceVue generated your draft from the context you gave it, so a good review should check the draft against that context, not just against generic rules. Findings that draw on your own material say so: a Grounded in your context item (or goal, uploaded source, or prior document) marker sits under the finding with a citation you can click to preview the exact passage it rests on, without leaving the document.
Findings with no such link are labelled Reviewer judgment. They are still worth reading, especially for wording and clarity, but they are the reviewer's own call and they are never dressed up as if they came from your sources.
Accept or Comment only
You can tell the two kinds of finding apart by the button on the row:
- Accept appears when the finding comes with a specific edit, so ForceVue can make the change for you. Click it and the suggested text replaces the passage. Nothing changes until you do.
- Comment only appears when the finding is something to act on rather than a one-click edit, for example "add success-metric targets to your goals" or "validate the integration assumption with a quick spike." There is no text to swap in, so these point you to something to add to your context or goals, or an action to take outside the document.
Review only runs when you ask
Review never fires on its own. It runs when you click the button, and a keyboard shortcut only opens the panel, it does not start a review. You stay in control of when an AI pass happens.
The six advisors
Under the hood, Review draws on a set of advisors, each tuned for a different job:
| Advisor | What it looks at |
|---|---|
| PRD Critic | Structure, acceptance criteria, and measurable success metrics |
| Assumption Map | The unstated assumptions a draft is leaning on |
| Launch Readiness | Whether an initiative is ready to ship |
| Prioritization | How the work stacks up against other work |
| Stakeholder Update | A clear status summary for the people watching |
| Competitive Battlecard | How you compare against a named competitor |
The in-editor Review button blends the document-focused advisors (PRD Critic and Assumption Map) into one pass and adds the scorecard on top, so a single click grades the draft and surfaces both kinds of findings.
The three initiative-level advisors (Launch Readiness, Prioritization, and Stakeholder Update) run from the initiative's Advisors tab rather than the editor, because they reason across the whole initiative, not one document.
Competitive Battlecard creates a new document for you rather than annotating an existing one.
Include in AI retrieval
Every document has an Include in AI retrieval toggle in its header.
When it is on, the document can be used as context when ForceVue generates new documents, answers questions in chat, and runs search. That is usually what you want, since a richer context produces better drafts.
Turn it off to exclude a document. Use this for outdated drafts, scratch notes, or anything you do not want feeding into AI results. The document stays in your workspace and you can read and edit it as normal. It just stops being pulled in as background context.
Where to go next
- Refining with AI to rewrite a passage or the whole draft.
- How generation works for what AI retrieval feeds into.
- Generating documents to create the draft you review.