Documentation menu

// How-to

Review agent changes

When an agent wants to change a governed document, it sends a proposal. You review the result before it becomes the version everyone uses next. Working documents allow direct agent edits; see How approval works.

1. ProposeThe agent prepares a bounded change.
2. ReviewYou see the new text and what it replaces.
3. DecideAccept, reject or request changes.
4. ContinueAccepted work becomes the next version.

Review a proposal

  1. Open the proposal from Inbox or its direct link.

    The preview shows the document as it will look if you accept.

  2. Read the change, not only the summary.

    The diff shows what was removed and what was added.

  3. Choose the outcome.

    Accept it, reject it, or request a revision with the feedback the agent needs.

The important boundary

An agent proposing a change is not the same thing as changing the shared document. Your review is the boundary between those two events.

Request a useful revision

  1. Open the proposal and compare it with the current document.
  2. Anchor feedback to the relevant text when inline comments are available.
  3. State the required change and its reason.
  4. Use Request changes to send the work back. A discussion comment alone is not the same decision.
  5. Review the revised proposal before accepting it.
Example revision request
Keep the date from the approved plan and cite that plan. The proposal uses a different date without supporting evidence. Revise only the date and its source reference; leave the rest unchanged.

Understand each decision

  • Accept: applies the reviewed proposal as a new document version.
  • Reject: closes the proposal without applying its changes.
  • Request changes: returns the proposal for revision with your feedback.

The decision applies to the proposal you reviewed. Read the body and source evidence as well as the summary. An agent review can supply advice; it does not replace your approval.

When the document changed during review

A proposal can become stale when another change reaches the document first. Check its relationship to the latest version. If the app offers Apply change to current version, review the merged result. If the changes conflict, request a revision against the current document. Do not assume an old preview includes another reviewer’s later changes.

Review returned Word files

A redline is a Word document with tracked changes. Use Add redline to select the returned .docx and identify which document or version it applies to.

  1. Inspect every extracted edit.
  2. Accept an edit, reject it with a comment, or acknowledge an edit outside the main text when that is the offered action.
  3. Decide every edit, then accept the overall proposal to publish the result.
  4. Use Download .docx for the reply file and copy the decision summary when you need to send a response.

Downloading prepares the file. You still send it to the other party yourself. Check the reply file before sending, especially for formatting or changes outside the main text.

Document comments and proposal comments

A document comment concerns the document. A proposal comment concerns the proposed change. Reply in the existing thread to keep the discussion together. When an agent’s revision addresses a document thread, linking the proposal lets its acceptance resolve the linked discussion. Provider-origin comments follow the source’s workflow.