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

# Combine capabilities into outcomes

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

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>
</CardGroup>