The Benchmarks tab: how your SOPs compare to peers

What the Benchmarks tab shows

Every other tab in Processes looks inward: your own SOPs, your own standards library, your own coverage matrix. Benchmarks is the one tab that looks outward. It takes the SOPs you have already written or adopted, 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 does not have.

Nothing that crosses the cohort boundary is a peer's actual SOP text. Verinode never shows you another operator's step descriptions, notes, or anything a peer typed. What flows across 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 for the mechanics behind that boundary.

Where to find it

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

Which SOPs get a card

Benchmarks does not compare every SOP you own one by one. It groups your active SOPs (archived ones are left out) 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 run SOPs across many categories.

A SOP only counts toward a card if at least one of its steps carries a recognized step type. If none of your documented SOPs have any typed steps yet, there is nothing to show, and the tab reads:

Peer SOPs Document at least one SOP and peer comparisons unlock the moment your cohort has enough contributing operators. 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 is not boilerplate. It is the actual trade the tab runs 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," not the raw database tokens underneath). Below the heading, a line reads Your SOP: N steps, plus LEAN N if your SOP has been scored. LEAN score is a 0 to 100 read on how efficiently a SOP's steps are structured, drawn from the LEAN discipline of eliminating wasted motion and unnecessary steps. A SOP that has not been scored yet just shows a dash instead of a number.

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

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

Verinode always tries the most specific cohort first and only widens when it has to. A "National" label is not a downgrade you caused, it just means your state-and-size slice of operators running that exact SOP shape has not 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

Verinode only publishes a cohort comparison once enough operators have contributed a SOP in the same category and work type bucket to protect anyone's anonymity. This is checked at every scope, from State Size all the way out to National. Until that bar is cleared anywhere in the cascade, 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 will not show you a comparison 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 is nothing to configure to speed this up beyond documenting your own SOPs, which is exactly what grows the cohort for everyone else too.

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 has not 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 alone is a verdict. A high step count with a low LEAN score usually means bloat, steps that do not 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 does not have, shows up under the heading "Steps your peers run that you don't."

Each gap row lists:

• The step type, in plain language (for example "Moisture Mapping," not the raw database token underneath).
• 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 is not available for that step, the duration is simply left off.

If your SOP already covers every step your cohort runs at that adoption level, the card shows a plain confirmation instead:

Your SOP covers every step your cohort runs at ≥50% adoption.

That is the version of this tab you want to see, but it is also the quieter, less common outcome. Most SOPs have at least one gap the first time they are compared.

Capture as gap

Each gap row carries a Capture as gap button.

1. 1Clicking it sends 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 is nothing to copy back.
2. 2The button reads Capturing… while it saves, then Captured once it lands, and stays disabled after that so you cannot double-capture the same gap.
3. 3A new entry appears in Pending Confirmations (open it from the All Processes tab, under the Pending Confirmations pill), pre-filled with a note along the lines of "Add a Moisture Mapping step, [X]% of 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 wording, sequencing, and ownership are your call.

The evidence attached to that pending item records which cohort scope and adoption percentage the recommendation came 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.

No peer copy, ever

The promise behind this whole tab is structural, not a policy note bolted on afterward. Peer SOP contributions are anonymized before they ever reach the cohort your card reads from: descriptions and free text are stripped at the point of contribution, so what lands in the intelligence layer is step types, step counts, framework scores, and timing, never a peer's actual wording. That is also why "Capture as gap" cannot hand you a peer's phrasing when you click it. There is nothing to hand you. Verinode surfaces that a step exists and how common it is; you write your own version of it.

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 do not, is worth a look even if your overall LEAN score is strong. A high score with a real gap usually means your existing steps are tight but something is missing outright, not padded.

Not every gap is worth adopting. A step sitting at just over half adoption might be regional, seasonal, or specific to a job mix that does not 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. Verinode surfaces the pattern and the adoption rate; it never tells you what to write or whether to add it. That call is yours.

Best-practice example

Say your Water Mitigation · Residential card shows your SOP at 9 steps against a cohort median of 11, with your LEAN score reading "Below median." The gap list shows one step, Moisture Mapping, at high peer adoption with a short typical duration attached. That combination, fewer steps and a below-median LEAN score, plus a specific named gap, is worth acting on: the missing step is a plausible reason your SOP reads thinner than the cohort. Tap Capture as gap, then open Pending Confirmations and write the step the way your team would actually run it: what gets photographed, at what stage, and who owns it. Confirm it, and it becomes part of your real SOP, in your own words.

Related reading

• The All Processes tab: where your SOPs, Pending Confirmations, and Standards library sit across the section.
• By Standard: adopt an IICRC, LEAN, OSHA, EPA, or state template as a starting SOP before you have one to benchmark.
• Confirming patterns Verinode spots: what happens after a captured gap lands in Pending Confirmations.
• 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