> ## 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.

> ## Agent Instructions
> These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence.
> Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page.
> Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described.
> Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone.

# Combine capabilities into outcomes

> End-to-end workflows that combine Speckle capabilities for design review, validation, transformation, extraction, and reconstruction.

Documentation status: impacted for the changes in Speckle 2026.9 (from 2026-09).

Affected guidance: Changed viewer and connector steps; existing workflow patterns remain applicable.

For these changes, read [2026.9 guidance](/next/workflows/overview).

For Speckle 2026.9, prefer the linked guidance only for the affected topics. This page remains applicable to earlier experiences and unchanged guidance. Do not treat the whole page or feature as deprecated.

These guides show how Speckle capabilities fit together to produce real outcomes. Capabilities describe what Speckle can do; the pages in this section show how to combine them in practice.

<Note>
  The [Speckle website](https://speckle.systems) also uses **Workflows** for high-level solution
  areas—for example [project dashboards and progress
  tracking](https://speckle.systems/project-dashboards-and-progress-tracking), [present and review
  models](https://speckle.systems/present-and-review-models), and [exchange design
  data](https://speckle.systems/exchange-design-data). **Here**, each page is a detailed, repeatable
  workflow you can follow in the product.
</Note>

## Common foundation

All workflows in this section assume a shared baseline for how data is stored and evolved:

<Note>
  **Foundation:** Data lives in [Projects](/workspaces/projects), [Models](/workspaces/models), and
  [Versions](/workspaces/versions). Versions are immutable and form a complete history. Work
  proceeds by reading data, transforming it as needed, and publishing new versions.
</Note>

## What is a workflow?

A workflow in this section is not a single feature or connector. It is a repeatable pattern that combines multiple capabilities to achieve a specific outcome in a defined context.

Each workflow answers:

* **What outcome** does this achieve?
* **What capabilities** are composed?
* **In what context** is this used?

## Workflow guides

Start from the **outcome** you want, not only the tool you use. Each guide below follows a **pattern** (observation, evaluation, transformation, extraction, or reconstruction): the first sentence describes the pattern; the rest is what that guide walks through. These are composable—you might chain evaluation into reconstruction, or transformation before extraction.

<CardGroup cols={2}>
  <Card title="Design review" icon="messages-square" href="/workflows/design-review-workflow">
    **Observation** — Understand and review model data without modifying it. Saved views,
    federation, markups, and issues for structured design reviews.
  </Card>

  <Card title="Model validation" icon="shield-check" href="/workflows/model-validation-workflow">
    **Evaluation** — Assess model data against rules or criteria to produce signal. Intelligence
    dashboards with Property Checker and Model Validation against your rulesets.
  </Card>

  <Card title="Grasshopper componentised pipeline" icon="workflow" href="/workflows/grasshopper-componentised-workflow">
    **Transformation** — Modify, restructure, or derive new data from existing models. Split large
    definitions into modules that hand off data through Speckle models.
  </Card>

  <Card title="Revit room data extraction" icon="table" href="/workflows/revit-room-data-extraction-specklepy">
    **Extraction** — Use model data outside Speckle for reporting, analytics, or integration. Pull
    room data from Revit with SpecklePy for Pandas, Power BI, or other systems.
  </Card>

  <Card title="SpecklePy model analytics" icon="database" href="/workflows/specklepy-model-data-analytics">
    **Extraction** — Load model datasets into local DuckDB with SpecklePy and run repeatable
    analytics queries.
  </Card>

  <Card title="Mapping to native systems" icon="boxes">
    **Reconstruction** — Reinterpret Speckle data into native elements in a target system. Map
    geometry and data to native families and types. Coming soon.
  </Card>

  <Card title="Grasshopper design explorer" icon="sliders" href="/workflows/grasshopper-design-explorer">
    **Evaluation** — Compare parametric design alternatives from Grasshopper across 3D geometry and
    numeric performance metrics in an interactive dashboard.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.