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.

Use this page for Standards authoring and reuse.
Standards are reusable templates for validation logic. They are intended for cross-check consistency and broader governance workflows.
In the beta release, standards are stored as project standards for reuse within that project. Workspace- and organization-level standards are planned for a later stage. Get in touch with feedback — we actively use it to shape this roadmap.

​
What standards are for

  • Define reusable rule templates once.
  • Apply standards across multiple checks.
  • Keep rule logic consistent across teams and projects.

​
Create first standard

First step: create or import your standard. Use Create standard from project sidebar when you want reusable validation logic before creating checks.
  • First screen can look empty before preview model is loaded. This is expected.
  • Load preview model first to unlock suggested starter rules.
  • Select model/version context for authoring and preview.
  • Define WHERE and CHECK logic. For full rule-construction guidance, use Rule structure in checks.
  • Run preview while authoring to confirm rule behavior before saving standard.
  • If you edit rule after running preview, UI prompts rerun so results stay in sync.
  • For large models, 3D preview can be skipped in this screen.
  • Standard authoring still works, but viewer may not render result state unless model preview is loaded.
  • You are done when standard appears in Standards and can be selected when creating checks.

​
Save or import outcome

  • If you created a new standard from rule authoring, choose Save standard.
  • If you imported a standard (IDS, COBie, or Speckle), import completes directly into project standards.
  • In both paths, your project standard appears in the Project standards list.

​
Build standard with many rules

Single standard can hold list of related rules (for example, handover completeness across multiple object categories).
  • Use Add rule to expand rules list.
  • Keep one requirement per rule so downstream check failures stay actionable.
  • Use per-rule Run while authoring to iterate faster.
  • Use duplicate/copy controls when rules share similar scope logic.
This pattern keeps one reusable standard for topic while preserving clear, rule-level outcomes in checks.

​
Import formats

You can import standards from:
  • IDS: strong fit for IFC-aligned requirements exchange.
  • COBie: strong fit for asset/information delivery requirements.
  • Speckle: migration path from dashboard widget rules or older Speckle Automate Model Checker definitions (JSON/TSV/CSV flows).

​
Standards to checks flow

1

Create or import your standard

Author rules directly (including preview iterations) using the same rule-building pattern as checks. See Rule structure in checks. Or import from IDS, COBie, or Speckle formats.
2

Refine rule logic

Confirm predicates, scope, severity, and message quality before reuse.
3

Create checks from standard

Use standard as base. Configure tracked models and trigger mode for each check. Then review outcomes in Viewing Results. Running Run check from a standard card takes you into the same check-creation flow documented in Checks.

​
Best practices

  • Keep standards focused by purpose (e.g. naming, compliance, handover).
  • Version standards with clear naming so downstream checks remain interpretable.
  • Communicate updates before broad rollout.
Last modified on May 7, 2026