Inside an SOP: LEAN score, steps, waste, and links

What this card is

Every documented standard operating procedure your team runs, water mitigation, fire and smoke, mold, reconstruction, or contents, gets its own detail card inside Processes. This is the "My SOPs" kind of card, one of three kinds that share the same shell (the other two are agent-inferred Pending Confirmations and the reference Standards catalog; see processes-overview for how all three fit together, and their own detail articles at Confirming an observed pattern and Inside a reference standard).

Open one of your SOPs and Verinode lays out everything it knows about it in one place: its LEAN score and the frameworks it's been checked against, whether field crews are actually running it the way it's written, the credentials it implies your team should hold, which carrier or TPA it's tied to, which vendors, team members, and equipment it references, the specific waste sitting inside its steps, and its own inline step editor.

Verinode does not write your SOP for you and it does not grade your crew. It reads the steps you, your team, or an uploaded document gave it, scores them against LEAN and any frameworks you've attached, watches how jobs actually run against it once it's active, and lays out what's worth tightening. You decide what changes.

Where to find it

Open Processes from the sidebar, under Operations, at /processes. Under the My SOPs kind, click any SOP tile to open its detail card. (Processes is a Premier feature; on other memberships the section still renders with a summary line and an upgrade prompt over the SOP library, see processes-overview.)

The eyebrow: kind label and stance

At the top of the card, an eyebrow line reads My SOPs next to a stance pill: HEALTHY, DRIFT, or EXPOSED. This is the same three-state vocabulary used everywhere on the platform, and for an SOP it works out roughly like this:

• EXPOSED when an open process signal is flagging this specific SOP and its LEAN score is either missing or below 60. This is the "a problem is active right now" state.
• DRIFT when the LEAN analysis hasn't run yet, or the score is below 60, or the SOP hasn't been updated in over a year. Nothing is on fire, but it needs a pass.
• HEALTHY when the SOP is analyzed, scoring 60 or above, and was updated recently.

The subtitle underneath the title is a single sentence naming the specific action Verinode recommends for this SOP right now, for example refreshing a stale score or re-triggering a stalled analysis, never a generic nudge.

Hero stats

Four numbers sit in the hero band:

• LEAN Score. The current score out of 100, or "Pending" while the first analysis is still running. When a target standard exists for this category, a delta line under the score reads "Target N", colored green if you're at or above it and red if you're below.
• Steps. The count of documented steps.
• Jobs Using. How many jobs in this SOP's category currently reference it, carrying the same healthy, drift, or exposed tone as the stance pill.
• Updated. The date the SOP was last edited.

Above the kind-specific content, a short synthesis paragraph weaves the stance, the recommended action, what you gain by acting, and the cost of not acting into a few plain sentences written for this specific SOP. It's regenerated as the underlying signals change and cached for a week; it's Verinode naming what it sees and what it would do next, not a decision made for you.

Draft, active, and the activation flip

A new SOP, whether built from a chat, an upload, a video walkthrough, or adopted from a reference standard, starts life with status Draft. A draft doesn't count toward peer benchmarks and doesn't surface as a match on jobs in its category.

While a SOP is a draft, or was adopted from a standard, a Status section sits at the top of the card:

• If the SOP was adopted from a standard, it names the source standard (or the framework, if the standard has no name) and, when the standard locks specific steps by citation, how many required steps are locked in.
• If the SOP is still a draft, a short line explains that activating it makes it contribute to peer benchmarks and surface in job process matches, next to an Activate this SOP button.

Click Activate this SOP and Verinode confirms the SOP now contributes to peer benchmarks and links to jobs.

Adherence (90 days)

This panel answers one question: is the field actually running the SOP the way it's written, or has the documented procedure drifted from what crews do? It looks at the last 90 days of jobs in this SOP's category that closed out through the closeout webhook.

With data, you see:

• A large followed/total count (for example "18/24") with the percentage next to it.
• A cohort label in a pill: Verified, Observed, Indicative, or Early signal. More closed-out jobs against this SOP strengthen the label; the label tells you how much to trust the number without spelling out the sample size behind it.
• A 13-week sparkline, one dot per week plotted at that week's adherence ratio. Weeks with no closed-out jobs render as a faint dot on the baseline so you can see where the data thins out, not just where adherence dipped. Hover a dot for that week's exact followed/total and percentage.
• A variance line comparing actual time spent against what the SOP's steps estimated, phrased as on plan, over plan, or under plan by a percentage.
• A closing note that changes with the overall ratio: below 50%, it tells you crews are deviating on more than half the window's jobs and suggests walking a few jobs end to end before assuming the SOP itself is wrong, since teams not following an SOP is more common than the SOP being wrong. Between 50% and 80%, it notes adherence is trending up but not consistent, and points you to the Jobs tab's deviation captures to see which steps crews skip most. Above 80%, it confirms crews are running the SOP step for step, and that it's the sparkline's dips worth investigating, not the average.

Empty state. Before any jobs have closed out against this SOP: "No execution data yet. When jobs in this category close out and link to this SOP, adherence + drift signal land here." (If the SOP has no category on file, the second sentence instead reads "When jobs close out and link to this SOP, the adherence rate lands here.")

Credentials this SOP implies

Only appears when the SOP was adopted from a reference standard that declares required or preferred credentials. An intro line explains that the source standard declares these credentials as implied, and that Verinode tracks how many of your active team members currently hold each one.

Each credential row shows:

• The certification code in uppercase (an IICRC code like WRT or ASD, for example).
• A pill reading "N of M needed," green when you already meet the minimum, red when it's required and you fall short, yellow when it's only preferred and you fall short.
• The requirement level, Required or Preferred.
• A rationale line, when one is on file, explaining why the standard calls for it.
• An Open → link to /certifications to see or add holders.

LEAN Score, Framework Scores, Recommendations, and Waste Signals

These four sections come from the same underlying analysis and sit one after another once it's run.

LEAN Score shows the full number out of 100, a colored progress bar (green at 80 and above, copper from 60 to 79, amber from 40 to 59, red below 40), and, when a comparison exists, a line reading how many points above or below the LEAN standard this SOP sits. While the very first analysis is still running, the section shows a pulsing amber dot and a note that analysis is running and to check back shortly.

Framework Scores appears when the SOP has been checked against one or more named frameworks (IICRC S500, S520, S770, OSHA, and so on): one row per framework, its name, its score out of 100, and the same colored bar.

Top Recommendations is a numbered list of the analysis's specific, concrete suggestions for this SOP, ordered by impact. These reference actual steps and section numbers where relevant, not generic advice, so read them in order.

Waste Signals appears when the analysis flags waste in one or more steps, with a count in the section title (for example "Waste Signals (3)"). Each flagged step shows:

• A pill naming the waste type: one of the eight LEAN waste categories, waiting, transportation, motion, defects, over-processing, overproduction, inventory, or skills.
• Which step number and step type triggered the flag.
• A description of what the analysis is seeing.
• A suggestion line, prefixed with an arrow, naming specifically what to change.

Process Rating

A three-dimension rating panel, separate from the LEAN score, that asks whether this SOP actually works in practice:

• Effectiveness (owner rating, 1 to 5)
• Usability (staff rating, 1 to 5, averaged across every team member who's rated it)
• Compliance (system analysis, 1 to 5, derived directly from the LEAN score)

Each dimension shows a bar and a number, or "Not rated" until someone rates it. A peer median can appear next to the LEAN score line, but peer benchmarking for SOPs hasn't shipped yet, so that field stays empty for now.

Once at least one job has run against this SOP, an Outcome Correlation line appears below the three dimensions: how many jobs are using the process and, when margin data exists on both sides, how the average net margin on jobs that used it compares to jobs that didn't, colored favorably when the SOP's jobs kept more and unfavorably when they kept less. This is a correlation inside your own book of business, not a claim of cause and effect, treat it as a prompt to look closer rather than a verdict.

Link to Carrier or TPA

A single-select dropdown lets you attach this SOP to one carrier or TPA client. The list combines your active carriers and TPAs, each name tagged (Carrier) or (TPA). Changing the selection, including clearing it back to "No carrier linked," reveals a Save link button; nothing writes until you click it.

Once a carrier is linked and Verinode has requirements on file for that carrier and this SOP's category, a Carrier Requirements list appears underneath: each requirement's plain-language description, plus its SLA timer and penalty when those are specified. See Clients and carriers for how carrier and TPA records get set up in the first place.

Link to Vendors, Team, or Equipment

A short explainer sits above three pickers: tagging a vendor, team member, or piece of equipment here helps IQ reach for this SOP whenever you ask about that vendor, team member, or equipment elsewhere on the platform.

Each of the three pickers, Vendors, Team, and Equipment, works the same way:

• Currently linked items render as removable chips; click the × on a chip to unlink it.
• A dropdown below the chips lists everything not yet linked ("Add a vendor…", "Add a team member…", "Add a piece of equipment…"). Picking an item links it immediately, no separate save step.
• Every add or remove saves right away. If a save fails, the chip change rolls back and an inline message explains the link couldn't be saved.

Empty states. With nothing linked yet, each picker reads "No vendors linked yet.", "No team members linked yet.", or "No piece of equipments linked yet." for its section. If you have no vendors, team members, or equipment on file at all, the dropdown is replaced with a prompt to add one in the Vendors, Team, or Equipment section first. If every candidate is already linked, it reads "All available vendors are already linked." (or the equivalent for team and equipment).

The step editor and required-step locking

Below the analysis sections, every documented step renders read-only: a two-digit step number, a pill for the step type (inspection, extraction, setup, containment, demo, drying, monitoring, sanitization, documentation, or completion), a description, the assigned role, the equipment used, and estimated minutes when one is set.

Steps locked in by a source standard's citation carry a copper Required · [citation] pill next to the type pill; hover it to see the rationale on file for why that citation requires the step.

Click Edit steps to switch the whole section into an editable form:

1. 1Click Edit steps. Every row flips into a form for type, description, role, equipment (a comma-separated field), and estimated minutes.
2. 2Adjust any field on any row. Nothing persists yet, the section is working from a local draft.
3. 3Click + Add step to append a blank row at the end of the list. There's no way to insert a step in the middle or drag-reorder, so add it and then adjust the surrounding rows if it belongs earlier in the sequence.
4. 4Click Remove on a row to drop it. If the row is marked Required, you'll be prompted first (see below).
5. 5Click Save steps to persist the draft and trigger a fresh LEAN analysis in the background, or Cancel to discard the draft and revert to the last saved version.

Empty state. An SOP with no steps recorded shows "No steps recorded. Click Edit steps to add some."

For the full walkthrough of every field in edit mode, see Editing SOP steps.

Feedback and archive

The bottom of the card carries the SOP's community sentiment, a free-text feedback box, and a Quick Survey button, alongside the archive control.

Click Archive SOP to retire it: it stops appearing in your active list but isn't deleted, and a confirmation explains it won't appear in your active list and that you can restore it from the archived view. Once archived, the same button reads Restore SOP; clicking it flips the status back to active and it reappears in your active list.

Open Tips and Findings tabs

Alongside the main Details tab, two tabs appear only when they have content:

• Open Tips, open process-domain signals tied specifically to this SOP: a headline, the rationale behind it, and, when present, a recommended action.
• Findings, active items in your feed that link back to this SOP, each with its action title and cost-of-inaction summary. See The decision workspace and Acting on decisions for how those get worked once you click through.

Both tabs stay hidden entirely, not shown empty, when there's nothing to display, and each carries a numeric badge on its tab label when it does.

Related reading

• Processes: your SOPs, standards, and how work actually flows
• Editing SOP steps
• Confirming an observed pattern
• Inside a reference standard
• Understanding your margin
• The decision workspace
• Acting on decisions
• Clients and carriers