By Standard: your IICRC, LEAN, OSHA, EPA, and state library

What By Standard is

Restoration work runs against a stack of outside rules: IICRC technical standards, LEAN process discipline, OSHA safety requirements, EPA environmental rules, and whatever your state adds on top. Most operators know these exist. Almost none of them can put a hand on the actual text when a carrier program manager asks "which version are you certified to" or a new hire asks "what does S500 actually require here."

By Standard is that library, built into Processes. It is a searchable catalog of standard references, Verinode's structured read of IICRC, LEAN, OSHA, EPA, and state-level requirements, filtered down to the frameworks that apply to your business and the jurisdiction you operate in. Every entry can be turned into a working SOP draft in one click, so the standard stops being a PDF you half-remember and becomes a documented process you can edit, assign, and run.

Verinode does not certify you against these standards and does not decide which ones you must follow. It surfaces what each standard requires, in your state, and lets you adopt the ones that matter to your business.

Where to find it

Open Processes from the sidebar, under Operations (/processes). Processes is a horizontal card slider with six tabs across the top: Findings, Flow, All Processes, By Standard, Coverage, Benchmarks. Click By Standard.

Inside the tab, from top to bottom:

1. A search bar: "Search standards by name, framework, category, or jurisdiction…"
2. A row of framework pills: All, IICRC, LEAN, OSHA, EPA, State, each with a live count in parentheses.
3. When you have a state on file and the State pill is active, a small note on the right: "Showing [your state] regs only."
4. The results list: one row per standard, each with an inline Adopt button.

The framework pills

The pills are quick filters over the same underlying catalog, not separate tabs:

• All counts every standard reference in scope for your account.
• IICRC covers IICRC's technical standards (the framework token starts with "iicrc," so this pill can span more than one IICRC document, for example S500 for water and S520 for mold, once your catalog has both).
• LEAN covers process-efficiency standards, the discipline behind the LEAN score you see elsewhere on SOPs.
• OSHA covers workplace safety requirements.
• EPA covers environmental handling and disposal requirements.
• State covers anything scoped to a specific state rather than to "Global" or "Federal."

Click a pill to filter the list to it; click All to clear the filter. The count beside each pill updates as your catalog and jurisdiction scope change, it is not a fixed number, it reflects exactly what is loaded for your account right now.

Jurisdiction scoping

By Standard only shows you standards you are actually in scope for. Verinode loads three jurisdiction buckets:

• Global references (framework-level requirements with no geography attached, most IICRC and LEAN content lives here).
• Federal references (OSHA and EPA rules that apply everywhere in the U.S.).
• Your state, if you have one on file. This is where state-specific amendments and add-on requirements show up.

Your state comes from your operator profile. If you have not set it, the State pill still works but with nothing state-specific behind it, and the results list explains why (see Empty states below). Add it under Settings → Profile to unlock jurisdiction-specific regulations.

Jurisdiction values display as plain words: Global, Federal, or your state's two-letter code (for example CA, TX), never a raw lowercase database token.

The results list

Each row is a standard reference. Left to right:

• A small steel-blue dot, the same accent color used for Standards throughout Processes, so a standard reads as a standard even before you read the label.
• The title: the standard's name (for example a named IICRC document) when Verinode has one on file, or a generic "[FRAMEWORK] reference" label when it does not.
• A subtitle line: "Standards" (the kind label), followed by the category this standard applies to (for example Water Mitigation, Fire & Smoke), followed by a short excerpt of the standard's description where one exists.
• A relative timestamp on the right ("3d ago," "Jun 12"), the date this reference entered Verinode's catalog.
• An Adopt button on the far right of the row.

Click anywhere on the row except the Adopt button to open the standard's full detail card. Type in the search bar to filter by name, framework, category, or jurisdiction, search runs across whatever pill is active.

Opening a standard's detail card

Clicking a row (not the Adopt button) opens the standard's full detail view. At the top, four stat fields summarize it:

• Framework, the standard's framework in full caps (IICRC, LEAN, OSHA, EPA).
• Target Score, the standard's quality bar out of 100, the score an SOP built to this standard is expected to hit.
• Required Steps, how many of the standard's steps are locked in as required by citation, versus steps that are informative but not mandatory.
• Programs, how many carrier or TPA programs in your book require an SOP in this category at or above this standard's target score. When that count is above zero, the field is tagged "require this."

Below the stats, the card lays out:

• Adopt as your SOP: the same one-click adoption available from the row, with the exact count of pre-populated steps and a note that the framework's citations are already attached, so you are not starting from a blank page.
• Standard Overview: Framework, Jurisdiction (in the same plain-word format as the list), Source (the named document, where one exists), Version (where tracked), Description, and Target Score expressed as "X / 100."
• Your SOP: if you already have a documented, non-archived SOP in this category, its title, step count, and LEAN score, with a note that comparing it against this standard surfaces drift between what the framework requires and what your SOP actually says. If you do not have one yet, a prompt that drafting one against this standard is the cleanest starting point.
• Carrier Programs Requiring This: only appears when at least one carrier or TPA program in your book requires this category at or above this standard's score. Each program lists its name, a confidence label on how certain Verinode is about that requirement, and the minimum target score the program expects.
• Required Steps: only appears when the standard has citation-backed required steps. Each one shows its position in the sequence, its citation (for example a clause reference), the step description where Verinode has matched it to the standard's own steps, and the rationale for why it is required.

The Adopt button, what it actually does

Clicking Adopt (either inline in the row, or Adopt as draft SOP on the detail card) does one thing: it copies the standard's steps and citations into a brand-new SOP in your own library, in draft status. Specifically:

• The new SOP's title becomes the standard's name followed by "(draft)," or "[FRAMEWORK] [category] SOP (draft)" if the standard has no named source.
• Its category matches the standard's category.
• Its work type is set to apply to both residential and commercial work, so an adopted framework template is not accidentally scoped too narrowly. Narrow it yourself once you have reviewed it.
• Its steps and framework tag come straight from the standard, exactly as cataloged.
• It is tagged internally as adopted from this specific standard, so Verinode can later diff your live SOP against the source and flag drift.

Nothing is activated automatically. A success toast confirms: "Draft SOP created. Open the All tab to refine the steps and activate." Open the All Processes tab, filter to Standards if you want to find the source again or to My SOPs to find your new draft, edit the steps to match how your crews actually work, and only then move it out of draft.

If adoption fails (a category mismatch between the standard and your SOP categories is the most common cause), the button surfaces an error toast asking you to try again rather than silently doing nothing.

Empty states

• No standards match a search inside a pill: "No standards match '[your search]' in [pill name]."
• A pill has nothing in scope at all: "No [pill name] references in scope yet."
• The State pill with no state on file: the empty message above is followed by "Add your state in Settings → Profile to see jurisdiction-specific regs."

None of these are errors. They mean the catalog has not yet accumulated a reference for that combination of framework and jurisdiction, or your profile is missing the state that would unlock state-specific results.

Best-practice example

A water mitigation operator in Georgia opens By Standard and clicks the IICRC pill. The list narrows to IICRC references in scope: global technical standards plus anything Georgia-specific. Clicking the water mitigation reference opens its detail card: Target Score, a handful of Required Steps each tied to a citation, and one carrier program in the operator's book flagged as requiring this category at or above that score. The operator has no documented SOP in this category yet, so the card recommends adopting this one as a baseline. One click on Adopt as draft SOP creates a draft in My SOPs with the standard's steps and citations already in place. The operator opens All Processes, filters to My SOPs, edits the steps to match how the crew actually runs a water loss, and activates it, closing a gap the Coverage tab had flagged for that service line.

Related reading

• Processes: Findings, your open process decisions
• Processes: Flow, your process-mining metrics
• Processes: All Processes, your SOPs, patterns, and standards in one list
• Processes: Coverage, your service-line × SOP × standard matrix
• Processes: Benchmarks, your SOPs against peer cohorts
• The decision workspace
• Benchmarks overview