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

# Review Workflows

> Choose the right review flow for model checks, feedback, and sharing.

## What are review workflows?

Review workflows are repeatable paths for checking models, sharing feedback, and
tracking follow-up.

Use this page to pick the best review path in the web app.
Each path links to a page with full step-by-step details.

## Start with your review goal

<CardGroup cols={2}>
  <Card title="Inspect model content" icon="compass" href="/3d-viewer/exploration">
    Browse model structure, filters, properties, and measurements.
  </Card>

  <Card title="Compare changes" icon="arrows-rotate" href="/3d-viewer/compare-versions">
    See what changed between versions.
  </Card>

  <Card title="Combine models" icon="cubes" href="/3d-viewer/federation">
    Load multiple models in one view.
  </Card>

  <Card title="Track feedback" icon="comments" href="/3d-viewer/issues">
    Create issues, assign owners, and close them when done.
  </Card>

  <Card title="Add markups" icon="pen" href="/3d-viewer/markups">
    Add drawings and notes directly on the view.
  </Card>

  <Card title="Save views" icon="bookmark" href="/3d-viewer/saved-views">
    Save camera position, visibility, and filters for reuse.
  </Card>

  <Card title="Prepare presentations" icon="display" href="/3d-viewer/presentation">
    Set up clear visuals for meetings and reviews.
  </Card>

  <Card title="Share and embed" icon="share" href="/3d-viewer/sharing">
    Send links or embed models in external tools.
  </Card>
</CardGroup>

## Common paths by role

### Coordinator or reviewer

Use this path when you need to check work across teams:

<Steps>
  <Step title="Inspect the current state">
    Open the relevant models and review them in
    [Exploration](/3d-viewer/exploration).
  </Step>

  <Step title="Identify what changed">
    Use [Compare Versions](/3d-viewer/compare-versions) to find recent changes.
  </Step>

  <Step title="Create follow-up tasks">
    Capture findings in [Issues](/3d-viewer/issues), assign owners, and add due
    dates.
  </Step>
</Steps>

### Discipline lead

Use this path when validating work before handover:

<Steps>
  <Step title="Focus the view">
    Use filtering and visibility controls in
    [Exploration](/3d-viewer/exploration).
  </Step>

  <Step title="Mark key points">
    Add markups to highlight important points with
    [Markups](/3d-viewer/markups).
  </Step>

  <Step title="Save checkpoints">
    Store repeatable checkpoints as [Saved views](/3d-viewer/saved-views) for
    later review rounds.
  </Step>
</Steps>

### Project manager or client lead

Use this path when sharing progress with people who do not author models:

<Steps>
  <Step title="Set clear visuals">
    Configure output in [Presentation](/3d-viewer/presentation).
  </Step>

  <Step title="Share access">
    Create links or embeds in [Share your Models](/3d-viewer/sharing).
  </Step>

  <Step title="Track open work">
    Use [Issues](/3d-viewer/issues) to track progress.
  </Step>
</Steps>

## How pages are separated

Pages are grouped by decision type:

* **Inspect and Compare** for understanding model state and change.
* **Feedback and Tracking** for discussions, markups, and issue ownership.
* **Present and Share** for communication outside technical review sessions.

If your team wants one standard review path, use this page as the entry point
and keep detailed actions in the linked pages.

## FAQ

<AccordionGroup>
  <Accordion title="Should we use Issues or Markups for review feedback?">
    Use **Issues** when you need assignment, due dates, and status tracking. Use
    **Markups** for visual notes and drawing-based context.
  </Accordion>

  <Accordion title="Do saved views replace issues?">
    No. Saved views preserve camera and visibility state. Issues track action
    ownership and completion.
  </Accordion>

  <Accordion title="Can one review use multiple workflows?">
    Yes. Most teams inspect in Exploration, capture actions in Issues, and then
    communicate outcomes through Presentation or Sharing.
  </Accordion>

  <Accordion title="Where should teams start when process is unclear?">
    Start with **Inspect model content**, then pick either **Track feedback** or
    **Prepare presentations** based on whether the goal is coordination or
    communication.
  </Accordion>
</AccordionGroup>