Standard references: adopt a framework as your draft SOP

What it is

A standard reference record is a published process standard, an IICRC, LEAN, OSHA, EPA, or state regulation, that Verinode has already turned into a structured reference: a named source, a jurisdiction, a target score, and (where the source specifies them) a step-by-step outline with citations. It is not something you write. It flows in from Verinode's research library so you always have a defensible baseline to check your own documented process against, without reading the standard yourself.

The standard reference detail card is what opens when you click one of these records. It has one job beyond showing you the standard: let you turn it into your own SOP in one click, so you never start from a blank page. Verinode surfaces the framework, the required steps, and where your own SOP stands against it. It does not decide your SOP for you, the draft, the edits, and the decision to activate it are yours.

Where to find it

Processes lives under Operations in the sidebar, at /processes. Processes is a Premier-tier feature: Contributor and Executive accounts see a preview card summarizing how many processes Verinode is tracking, with an upgrade prompt in place of the full workspace.

Two ways into a standard reference from the Processes home:

• In the Explore row, click the tile labeled with your state (for example, "Texas + Federal") or, if Verinode doesn't have your state on file yet, "Standards." That opens the process slider on the By Standard tab.
• From All Processes, filter to the Standards kind alongside your SOPs and pending confirmations.

The By Standard tab is a searchable standards library:

• A search box across the top: "Search standards by name, framework, category, or jurisdiction…"
• Filter pills with counts beside each one: All, IICRC, LEAN, OSHA, EPA, State. If your state is on file and you select State, a note reads "Showing [your state] regs only."
• Below that, one row per standard: its name, the Standards kind label, its category, a short description snippet, and how long ago it was added, plus an inline Adopt button on the right.

Click anywhere on a row (not the Adopt button) to open the full standard reference detail card.

What the card shows

The header: kind, stance, and the four numbers

At the top of the card, a small label reads Standards next to a stance pill: HEALTHY, DRIFT, or EXPOSED. This pill is not about the standard itself, it reflects your position against it:

• EXPOSED means a carrier program requires an SOP in this category at or above this standard, and you don't have a documented SOP there yet. The subtitle reads something like "Adopt this standard, [N] carrier program(s) require it."
• DRIFT means no carrier program is currently forcing the issue, but you also don't have an SOP in this category. The subtitle reads "Compare to your SOP, start a draft if you don't have one."
• HEALTHY means you already have a documented SOP in this category. The subtitle reads "Already covered, diff your SOP against the latest revision."

Below the title and subtitle, four stat tiles:

• Framework: the standard's framework code in full caps (IICRC, LEAN, OSHA, EPA, or a state code).
• Target Score: the score (out of 100) the framework expects a compliant SOP to reach.
• Required Steps: how many of the standard's steps carry a citation marking them as mandatory, not optional.
• Programs: how many carrier programs require an SOP in this category at or above this standard. When there's at least one, the tile carries a "require this" note in the stance color.

Just under the header, Verinode writes a short synthesis paragraph in plain language: what your stance is, what you'd gain by acting, and what it costs you to wait. It refreshes periodically rather than on every visit, so wording may lag a few days behind the latest numbers on the tiles above it.

Adopt as your SOP

The first section on the card. It reads: "Scaffold a draft SOP from this standard. You start with [N] pre-populated step(s) and the citations from [FRAMEWORK] already attached, no blank page." Below it, a single button: Adopt as draft SOP.

Click it and Verinode creates a new SOP in your account, in draft status, seeded with every step from the standard and the citations that mark which of those steps are required. It does not touch anything else, an existing SOP in the category, a carrier link, an activated process, none of it. You are dropped back on the Processes home with a toast: "Draft SOP created. Open the All tab in Processes to edit it." From there you refine the wording, add or remove steps, and activate it when it's ready, exactly as you would with any hand-written SOP.

If you already have an SOP in this category, the section adds a line under the button: "You already have an SOP in this category ([title]). Adopting will create a separate draft you can compare against." Adopting does not merge into or overwrite your existing SOP, it always creates a new, separate draft.

Standard Overview

A plain field list describing the standard itself:

• Framework: the framework code in full caps.
• Jurisdiction: where the standard applies. National frameworks read "Global," "Federal," "State," or "Local." A specific U.S. state reads as its two-letter postal code (for example, "CA"). Anything else reads as a humanized label.
• Source (when the standard names one): the specific published document, for example an IICRC standard edition.
• Version (when recorded): the edition or revision identifier.
• Description (when recorded): a short summary of what the standard covers, shown in full.
• Target Score: the same number from the header stat tile, shown here as "[score] / 100" for context.

Your SOP

This section tells you where you stand against the standard, without you having to check yourself:

• If you have a documented SOP in this category, it shows the SOP's title, its step count, and its LEAN score if one has been calculated. When a LEAN score exists, a line explains what to do next: "Diff against this standard catches drift between what the framework requires and what your SOP says today."
• If you don't have one yet, it reads: "You don't have a documented SOP in this category yet. Drafting one against this standard is the cleanest baseline for the rest of your work in this category."

Carrier Programs Requiring This

Appears only when at least one carrier program requires an SOP in this category at or above this standard's target score. The intro line: "Programs that need an SOP in this category at or above this standard's target score." Each row shows the program name, a confidence tier (Low, Medium, or High, describing how confident Verinode is in the requirement mapping), and the minimum target score the program expects, shown as "Min [score]." This is the section that turns an abstract standard into a concrete reason a carrier could pull you from a program if you're not documented against it.

Required Steps

Appears only when the standard has at least one citation-backed required step. Each row shows the step's position number, a citation pill (for example, a section reference from the source document), the step's description pulled from the standard's own step list when available, and an italicized rationale explaining why that step is mandatory rather than optional. These are the exact steps the SopStepEditor on an adopted SOP marks with a "Required" pill and warns you before you delete, so this section is the reference copy for that guardrail.

Open Tips and Findings tabs

Two more tabs sit alongside Details, both hidden entirely when there's nothing in them:

• Open Tips shows any open process signal Verinode has raised specifically against this record, each with a headline, a short rationale, and a suggested action. In practice this tab rarely appears on a standard reference card: process signals tend to attach to your own SOP once you've adopted one, not to the published standard itself, so seeing it empty here is expected, not a bug.
• Findings lists any active decision that links back to this standard, each with its action title and the cost of leaving it unresolved.

How to use it

1. 1From /processes, click the state-and-federal tile (or "Standards") in the Explore row to open the By Standard tab.
2. 2Search or filter by framework (IICRC, LEAN, OSHA, EPA, State) to find the standard for the category you care about.
3. 3Click the row to open the full detail card and read the Standard Overview, Your SOP status, and any Carrier Programs Requiring This section.
4. 4If a required-steps list exists, skim it, these are the steps a carrier or auditor would look for first.
5. 5If you don't have an SOP in this category yet (stance reads DRIFT or EXPOSED), click Adopt as draft SOP.
6. 6Open the new draft from the All tab, refine the wording and steps to match how your team actually works, then activate it so it starts contributing to your process record and job matches.

Empty states

• By Standard tab, no matches for a filter or search: "No standards match '[query]' in [group]." (or, with no search text) "No [group] references in scope yet." If you've selected the State filter and haven't recorded your state, an extra line appears: "Add your state in Settings, Profile to see jurisdiction-specific regs."
• Standard Overview fields: Source, Version, and Description each drop out of the field list entirely when the standard doesn't carry that value, rather than showing a blank or a dash.
• Your SOP, no documented SOP in the category: "You don't have a documented SOP in this category yet. Drafting one against this standard is the cleanest baseline for the rest of your work in this category."
• Carrier Programs Requiring This: the whole section is omitted when no carrier program cites this category and framework.
• Required Steps: the whole section is omitted when the standard carries no citation-backed required steps.
• Open Tips / Findings tabs: each tab disappears from the card entirely when there is nothing open against this record.

Best-practice example

Say the standard reads EXPOSED, with the header noting "2 carrier programs require it," and you have no SOP in the category yet. Open Standard Overview to confirm the framework and jurisdiction match what you expected, check Carrier Programs Requiring This to see which programs and their minimum target scores, then click Adopt as draft SOP. You land with a fully structured draft, required steps already flagged, in under a minute. Open it from the All tab, adjust the wording to match your crew's actual workflow (equipment, roles, timing), and activate it. The stance on both the SOP and the standard reference record updates from there, and the next time the framework revises, the Your SOP panel on this card is what tells you your SOP has fallen behind, not an audit.

Related reading

• Processes: your SOPs, standards, and how work actually flows
• By Standard: the IICRC, LEAN, OSHA, EPA and state library
• The SOP detail card
• Editing SOP steps
• Stance, Open Tips and Findings on a process
• Clients and carriers