Reviewing documents

Run Review to audit a document in one pass, jump to inline suggestions and accept them, the six advisors, and the Include in AI retrieval toggle.

Review reads a finished draft the way a sharp reviewer would and tells you what to fix. Open a document, click Review, and ForceVue audits it in a single pass, then hands back inline suggestions you can jump to and accept.

What Review does

Review checks the things a strong version of that document type actually needs. For a PRD, that means clear structure, acceptance criteria, measurable success metrics, and the unstated assumptions worth surfacing before they bite you later. It is one pass over the whole document, not a back-and-forth.

You get two kinds of feedback:

  • Inline suggestions 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.

Run a review

  1. Open a document.
  2. Click Review. It sits in the editor toolbar, and there is a Review button on the document view page too.
  3. Wait a few seconds while ForceVue reads the draft.
  4. Suggestions appear in a side panel next to the document.

From the side panel:

  • Click a suggestion to jump straight to the passage it refers to.
  • Accept applies the proposed change to your document.
  • Skip anything you disagree with. Nothing changes until you accept it.

Document-level findings (the broader notes that do not attach to one passage) show up as a banner so you see them without scrolling the panel.

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.

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.

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:

AdvisorWhat it looks at
PRD CriticStructure, acceptance criteria, and measurable success metrics
Assumption MapThe unstated assumptions a draft is leaning on
Launch ReadinessWhether an initiative is ready to ship
PrioritizationHow the work stacks up against other work
Stakeholder UpdateA clear status summary for the people watching
Competitive BattlecardHow you compare against a named competitor

The in-editor Review button blends the document-focused advisors (PRD Critic and Assumption Map) into one pass, so a single click gives you both.

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