Skip to main content

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.

​
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

Inspect model content

Browse model structure, filters, properties, and measurements.

Compare changes

See what changed between versions.

Combine models

Load multiple models in one view.

Track feedback

Create issues, assign owners, and close them when done.

Add markups

Add drawings and notes directly on the view.

Save views

Save camera position, visibility, and filters for reuse.

Prepare presentations

Set up clear visuals for meetings and reviews.

Share and embed

Send links or embed models in external tools.

​
Common paths by role

​
Coordinator or reviewer

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

Inspect the current state

Open the relevant models and review them in Exploration.
2

Identify what changed

Use Compare Versions to find recent changes.
3

Create follow-up tasks

Capture findings in Issues, assign owners, and add due dates.

​
Discipline lead

Use this path when validating work before handover:
1

Focus the view

Use filtering and visibility controls in Exploration.
2

Mark key points

Add markups to highlight important points with Markups.
3

Save checkpoints

Store repeatable checkpoints as Saved views for later review rounds.

​
Project manager or client lead

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

Set clear visuals

Configure output in Presentation.
2

Share access

Create links or embeds in Share your Models.
3

Track open work

Use Issues to track progress.

​
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

Use Issues when you need assignment, due dates, and status tracking. Use Markups for visual notes and drawing-based context.
No. Saved views preserve camera and visibility state. Issues track action ownership and completion.
Yes. Most teams inspect in Exploration, capture actions in Issues, and then communicate outcomes through Presentation or Sharing.
Start with Inspect model content, then pick either Track feedback or Prepare presentations based on whether the goal is coordination or communication.
Last modified on May 4, 2026