> ## Documentation Index > Fetch the complete documentation index at: https://docs.roboticks.io/llms.txt > Use this file to discover all available pages before exploring further. # Pinning Standards > Bind a project or organisation to a specific edition of a standard. The difference between "derive from" and "conform to" — and how to bulk-pin from a template. # Pinning Standards A **pinned standard** is a project's (or organisation's) declaration: *we author requirements that derive from this edition of this standard, and we expect to receive amendment alerts and diff views when it changes.* Pinning is the gate that unlocks derivation, the feed, and amendment diffs. Until a standard is pinned, you cannot link a requirement to its clauses. **Roboticks is audit-readiness tooling, not a certified toolchain.** We assemble the evidence your notified body, certification body, or QA process ingests. We do not replace tool qualification (DO-178C, ISO 26262-8 TCL) and we do not issue conformity assessments. Verify the regulatory interpretations on this page against the standard text and your accredited assessor. ## Two scopes | Scope | When to use | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Organisation-wide** | Standards that apply to every product the org ships (e.g., ISO 12100 risk-assessment basics, ISO 9001 quality processes). Inherited by every project. | | **Project-scoped** | Standards specific to the product family — ISO 10218-1:2025 for an industrial-robot project, ISO 3691-4 for an AMR project. | A project inherits every org-wide pin and can add its own project-scoped pins. A project cannot un-pin an org-wide pin — that decision lives at the org level. ## How to pin ### From the dashboard **Organisation Settings → Standards** for org-wide pinning, or **Project → Standards** for project-scoped. Filter by family (machinery safety, functional safety, AI, etc.), by issuing body (ISO, IEC, EN, ANSI, EU), or by free-text search. The catalog shows every available standard, its latest edition, and any pinned amendments. Most standards have multiple editions. **Pick the edition you actually certify against** — typically the latest harmonised edition, or the latest at your last conformity assessment. Roboticks supports pinning past editions for legacy products. First standards subscription is included on Team. Additional are \$99 / standard / month. The confirmation modal shows the exact monthly delta. The pin is effective immediately. Existing requirements can now reference clauses; new requirements can be derived from clauses. ### From the CLI ```bash theme={null} # Project-scoped rbtk standard pin iso-10218-1-2025 \ --project acme-robotics/firmware # Organisation-wide rbtk standard pin iso-12100-2010 \ --org acme-robotics ``` ### Bulk-pin from a template For organisations that want every new project to start with the same standards stack, **Templates** are a one-shot bulk pin: ```bash theme={null} rbtk standard template apply industrial-robot-eu \ --project acme-robotics/firmware ``` Built-in templates: | Template | Pins | | --------------------- | ----------------------------------------------------------------------------------------- | | `industrial-robot-eu` | ISO 10218-1:2025, ISO 10218-2:2025, ISO 12100, EN ISO 13849-1, IEC 62061, EU MR 2023/1230 | | `cobot-eu` | Above + ISO/TS 15066 | | `amr-eu` | ISO 3691-4, ISO 12100, EN ISO 13849-1, IEC 62061, EU MR 2023/1230, IEC 61496 | | `amr-us` | ANSI/RIA R15.08, ANSI B11.0 family | | `medical-adjacent` | (Curated; consult [hello@roboticks.io](mailto:hello@roboticks.io)) | Custom templates can be defined per org. See **Org Settings → Standard Templates**. ## "Derive from" vs "conform to" These are two distinct claims, and Roboticks tracks them differently. **Derive from** is a Roboticks model concept. A requirement says: *I exist because clause X of standard Y says these things. If clause X changes, I may need to change.* The derivation link is what powers amendment diffs. **Conform to** is the regulatory determination. *Our product, in this configuration, meets the requirements of standard Y.* Roboticks does not make this determination. The evidence pack provides the inputs (requirement coverage, test results, MCAPs, coverage); the conformance call is made by your QA team, your notified body, or your certification body. The implication: a project can be **pinned** to ISO 10218-1:2025 without claiming **conformance** to it. The pin enables derivation and alerting; the conformance is a separate, off-platform decision. Many customers pin a standard a year before they intend to claim conformance, to build a derivation backlog gradually. ## The pinned-standard view For each pinned standard, the dashboard shows: * **Edition and amendment level** — the exact version the project derives from. * **Last pull** — when the platform last verified the publication feed for this standard. * **Open amendments** — any amendment published since the pin that has not been triaged. * **Derived requirement count** — how many of your requirements link to this standard. * **Coverage roll-up** — of the derived requirements, how many are confirmed by at least one passing test. Use it as a posture summary: at a glance, do we have an open amendment to deal with, and is our derived-requirement coverage healthy. ## Unpinning Unpinning a standard: * **Stops the feed** for that standard at the project level. * **Does not delete** historical derivation links — they remain in place, marked as "from unpinned standard." * **Does not refund** the in-month subscription; pro-ration is end-of-billing-cycle. Unpinning is a deliberate action. It does not affect prior releases — their pinned-standards snapshot is immutable. Future releases simply will not show this standard in their conformance section. To re-pin, re-run the pin flow. The historical derivation links automatically re-attach to the freshly pinned standard, and the feed resumes. ## Multi-edition projects Some projects need to maintain conformance to multiple editions simultaneously — typically when an older edition is still grandfathered for products in the field while a new edition applies to new builds. Roboticks supports pinning the same standard at multiple editions concurrently. Each pin is independent: separate feeds, separate derivation links, separate amendment diffs. Requirements explicitly reference an `{edition, clause}` tuple, so the lineage is unambiguous. This is the dominant pattern in the run-up to EU MR 2023/1230 (applies January 20, 2027): legacy products under Machinery Directive 2006/42/EC, new products under MR 2023/1230, both pinned, both with active feeds. ## Pricing reminder | Tier | Standards subscription | | ---------- | ------------------------------------------- | | Free | Catalog browse only (cannot pin) | | Team | 1 included; \$99 / standard / mo additional | | Enterprise | Bundled | | Sponsored | Bundled | See [Pricing](/pricing) for the full grid. ## Next steps What we poll, how often, how alerts route. The 12 standards Roboticks ships with deep coverage of.