Benchmarks: how your SOPs compare to peers

What the Benchmarks tab shows

The Benchmarks tab answers one question your own paperwork can never answer: is the SOP you wrote actually complete, compared to what operators like you are running in the field? Every other tab in Processes looks inward, at your own SOPs, your own standards library, your own coverage. Benchmarks is the one tab that looks outward. It takes the SOPs you've already documented, groups them by service category and work type, and lines each one up against an anonymized cohort of peer operators running the same kind of job. You see how your LEAN score and step count stack up, and, most usefully, which specific steps your peers commonly run that your SOP is missing.

Nothing here is a peer's actual SOP text. Verinode never shows you another operator's step descriptions, job notes, or anything a peer typed. What crosses the cohort boundary is aggregated shape only: step types, step counts, framework scores, and adoption percentages, the same kind of anonymized structural signal that powers every other benchmark on the platform (see How benchmarks work).

Where to find it

Open Processes from the sidebar (/processes). The card slider across the top has six tabs: Findings, Flow, All Processes, By Standard, Coverage, and Benchmarks, the last one. Tap it to open the peer-SOP comparison.

Which SOPs get a card

Verinode doesn't benchmark every SOP you own individually. It groups your active SOPs (archived ones are excluded) by category and work type, for example water mitigation, residential. Within each group, it picks one representative SOP, the one with the highest LEAN score if you have more than one for the same category and work type, and shows a single card for it. The tab caps out at three cards so the view stays scannable even if you have SOPs across many categories.

If none of your documented SOPs have any steps typed (every step needs a recognized step type to be counted), there's nothing to show. In that case the tab reads:

Peer SOPs Document at least one SOP and peer comparisons unlock once your cohort has enough contributing operators to protect anonymity. Verinode never sells operator process data to carriers, insurers, or any third party. Your data sharpens the peer picture for operators like you.

That second line isn't boilerplate, it's the actual trade the tab is built on: your SOP's shape helps sharpen the cohort other operators see, and their contributions sharpen yours. None of it is ever sold, and none of it ever reaches a carrier.

Reading a bucket card

Each card is headed by its category and work type, in plain language (for example "Water Mitigation · Residential & Commercial," not the raw database tokens underneath). Below the heading, a small line reads Your SOP: N steps, plus · LEAN N if your SOP has been scored. LEAN score is a 0-100 read on how efficiently a SOP's steps are structured against the LEAN standard; a SOP that hasn't been scored yet just shows a dash instead of a score.

To the right of the heading, once a cohort loads, a small label shows the cohort scope and its size, formatted like "National · N=…" The scope tells you how Verinode had to widen the search to find enough peers to compare against:

• State Size, operators in your state and in your size band, the tightest, most relevant read.
• State, your state, any size.
• Size, your size band, any state.
• National, the widest fallback, any state or size.

Verinode always tries the most specific cohort first and only widens when it has to. A "National" label isn't a downgrade you did anything wrong to cause, it just means your state-and-size slice of operators running that exact SOP shape hasn't grown large enough yet to publish on its own.

While it loads, or if it fails

The card briefly reads "Resolving peer cohort…" while the comparison loads. If the request fails, it reads "Couldn't load peer cohort ([error detail])." Reload the page or try again in a moment.

Still learning

If your cohort, at every scope from State Size all the way out to National, hasn't reached the number of contributing operators Verinode requires before it will publish a comparison, the card reads:

Still learning, peer cohort needs at least [a minimum number of] contributing operators in your [Category] · [Work Type] bucket. Once the cohort fills in, this card unlocks.

This is a hard privacy floor, not a data quality choice. Verinode won't show you a cohort built from too few operators, because a tiny cohort risks echoing one identifiable peer's process back to you as "the peer standard." As more operators in your category and work type contribute SOPs, the bucket fills and the comparison unlocks on its own. There's nothing to configure to speed this up beyond documenting your own SOPs, which is exactly what grows the cohort for everyone.

The two comparison numbers

Once a cohort resolves, the card shows two side-by-side reads:

LEAN vs cohort. Your SOP's LEAN score, with the cohort's median score beside it (for example "74 · cohort median 68"). If your SOP hasn't been scored, this reads a dash. Underneath, a plain-language placement label tells you where you land:

• Top quartile, at or above the cohort's 75th percentile.
• Above median, at or above the cohort median but below the 75th percentile.
• Below median, at or above the cohort's 25th percentile but below the median.
• Bottom quartile, below the cohort's 25th percentile.

Step count vs cohort. Your SOP's raw step count, with the cohort's median step count beside it. Underneath, a similarly plain read:

• More steps than 75% of peers
• Above median peer step count
• Below median peer step count
• Fewer steps than 75% of peers

Neither number by itself is a verdict. A high step count with a low LEAN score usually means bloat, steps that don't add rigor. A low step count with a high LEAN score usually means a tight SOP that hits the essentials without padding. Read the two together.

Steps your peers run that you don't

This is the part of the tab worth acting on. Below the two headline numbers, Verinode compares every step type your cohort commonly runs against the step types already in your SOP. Any step type that at least half the cohort runs, and that your SOP doesn't have, shows up under the heading "Steps your peers run that you don't."

Each gap lists:

• The step type, in plain language (for example "Moisture Mapping," not moisture_mapping).
• What share of your cohort runs it (for example "78% of peers run this").
• A rough typical duration, if the cohort has enough timing data (for example "~45min"). If timing data isn't available for that step, the duration is simply omitted.

If your SOP already covers every step your cohort runs at that adoption level, the card instead shows a plain confirmation: "Your SOP covers every step your cohort runs at ≥50% adoption." That's the version of this tab you want to see, but it's also the quieter, less common outcome. Most SOPs have at least one gap the first time they're compared.

Capture as gap

Each gap row has a Capture as gap button. Clicking it:

1. 1Sends the step type, the peer adoption percentage, and the cohort scope to Verinode as a new pending item, no peer text is ever copied, because peer descriptions are stripped before they ever reach the cohort. There's nothing to copy back.
2. 2The button changes to Capturing…, then to Captured once it lands, and stays disabled so you can't double-capture the same gap.
3. 3A new entry appears in Pending Confirmations (find it in the All Processes tab, under the Pending Confirmations pill), pre-filled with a note like "Add a Moisture Mapping step, most peer operators in your cohort run this in their Water Mitigation Residential SOP."
4. 4Open it from Pending Confirmations and write your own version of the step. Verinode never had a peer description to hand you, so this is genuinely your call on wording, sequencing, and who owns it.

The evidence attached to that pending item records which cohort scope and how many peers it was drawn from, so if you come back to it later you can see the basis for the suggestion. See Confirming patterns Verinode spots for how the confirm-or-dismiss flow works once a captured gap lands there.

How to use this tab well

Work it bucket by bucket, starting with whichever category and work type covers the most job volume for you. Check the LEAN and step count reads first for a quick sense of where the SOP stands, then scan the gap list. A step that a large majority of your cohort runs and you don't is worth a look even if your overall LEAN score is strong, a high score with a real gap usually just means your existing steps are tight but something's missing outright, not padded.

Not every gap is worth adopting. A step at just over half adoption might be regional, seasonal, or specific to a job mix that doesn't match yours. Use judgment on whether it fits your work before you capture it, and even more judgment when you write your own version in Pending Confirmations, because Verinode surfaces the pattern and the adoption rate, it never tells you what to write or whether to add it. That call is yours.

Related reading

• The Processes section: how SOPs, Pending Confirmations, and Standards fit together across all six Processes tabs.
• By Standard: the IICRC, LEAN, OSHA, EPA and state library: adopt a standard as a starting SOP before you have one to benchmark.
• Confirming patterns Verinode spots: what happens after you capture a gap, or after Verinode spots a pattern in your own job history.
• How benchmarks work: the anonymization and cohort mechanics behind every benchmark on the platform, not just Processes.
• Benchmarks overview and Reading a benchmark: the same percentile and cohort-scope language used elsewhere in Verinode.

Data sources