> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryscott.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reviews and approvals

> Request feedback and approval on a specific planspace document version.

Reviews bring an approval workflow to design intent. Instead of waiting for code review to discover misalignment, a team can approve the plan while it is still cheap to change.

Reviews are attached to a specific document version. Reviewers see the exact content they are approving, including comments and relevant context.

## When to request a review

Request a review when:

* the planspace has a clear proposal or prototype direction
* open comments have been answered or intentionally left as decisions for reviewers
* the author wants a formal approval before delegating implementation
* a PR will later need to link back to the approved design intent

## Request a review

1. Open the planspace version you want reviewed
2. Click **Share**
3. Choose **Review**
4. Select one or more reviewers
5. Add a short note about what they should focus on
6. Send the request

Reviewers receive the request in [For You](/collaboration/notifications).

## Reviewer states

| State       | Meaning                                            |
| ----------- | -------------------------------------------------- |
| Pending     | The reviewer has not engaged yet                   |
| In progress | The reviewer is reading, commenting, or discussing |
| Approved    | The reviewer agrees with this version              |
| Rejected    | The reviewer requested changes                     |

Reviewers can approve, reject, or withdraw their decision if they need to reopen the review.

## Agent-assisted design review

Scott can also request review from agent reviewers in supported environments. Agent reviewers are useful for architecture checks, edge cases, security questions, or consistency with connected source context.

Human approvals still matter. Agent review is a way to broaden coverage and catch issues earlier, not a replacement for team ownership.

## Approval and execution

An approved version becomes the trusted reference for execution:

* [Pull](/developer-tools/pull) can load the reviewed context into a fresh agent thread
* [Scott GitHub App](/developer-tools/scott-ci) can link pull requests back to the approved plan
* the team can compare what shipped against what was approved

That is the shift Scott is designed for: review design intent before the diff, then use the diff to verify execution.