Coverage: which service lines still have no SOP

What this view shows

Every service line you run, water mitigation, fire and smoke, mold, reconstruction, and the rest, needs three things behind it to hold up under a real claim: a written standard operating procedure (SOP), the right certified people on staff to carry it out, and alignment with whatever carrier programs you belong to. The Coverage view is where Verinode reads your operator profile, your written SOPs, your team's certifications, and your enrolled carrier programs, and lays all three side by side, one row per service line, so you can see in one look which lines are solid and which ones are running exposed.

Verinode does not write the SOP for you or decide which line to fix first. It reads what is already in your profile, your standards library, and your team records, and shows you where the documentation, the credentials, or the program alignment has a gap. You decide what to close and when.

Where to find it

Open Excellence from the sidebar. It takes you to /processes, the same section that holds your SOPs, standards, and process mining, Coverage is one tab inside it.

Three places surface the coverage picture:

• The hero band at the top of the Excellence page, "SOPs written," shows your total SOP count and, beside it, a pill reading "N% Service Lines Documented." A second stat under that reads Lines Without An SOP, the count of service lines on your profile with no SOP behind them at all.
• The Explore row, a tile labeled Lines Without An SOP with a small gauge on it. Click it to jump straight into the Coverage tab.
• The Coverage tab itself, opened from either of the above, or from the tab strip inside the Excellence card slider (Findings, Flow, All Processes, By Standard, Coverage, Benchmarks). This is the full matrix.

The hero band and the "Lines Without An SOP" tile

What the hero shows. The headline number is how many SOPs you have written, across every service line. Beside it, a colored pill reads your documented-coverage percentage: the share of your service lines that have at least one SOP, healthy green at 90% or above, amber ("maintain" tone) at 60 to 89%, and red ("analyse" tone) below 60%. If you have not written any SOPs yet, the line under the headline reads "Upload your SOPs to get started." Once you have at least one, it reads either "N of your service lines have no SOP yet" or, when every line is covered, "Every service line has an SOP."

A second stat sits beside "To Confirm" (patterns your team's field notes have surfaced, waiting on your review): Lines Without An SOP, showing the raw count of uncovered lines, with "Write One To Close It" underneath when the count is above zero, or "All Covered" when it's zero.

What the Explore tile shows. The Lines Without An SOP tile repeats that same count as its headline value, but adds a gauge, a small ring reading your documented-coverage percentage against two bands: green above 90%, amber between 60 and 90%, red below 60%. The tile's accent color follows suit, green when the gap is fully closed, red ("ember") when lines are still uncovered. Clicking the tile opens the Coverage tab.

The Coverage matrix

Open the Coverage tab and, above the matrix, you'll see a Carrier program compliance panel, a separate rollup of how your SOP, cert, and adherence posture lines up against each carrier program you're enrolled in (see Clients and carriers for how programs are set up under Clients). Below that sits the matrix itself, one row per service line from your operator profile, three columns:

| Column | What it tells you | |---|---| | Service line | The service line's name (title-cased, e.g. "Water Mitigation," "Fire & Smoke"), with the SOP category it rolls up to underneath ("Category: water"). | | SOP coverage | Whether you have a written, active SOP for this line, and how it's scoring against the framework's target. | | Certified holders | Whether the credentials this line implies are held on your team, and in the right depth. | | Carrier programs aligned | Whether your active SOPs for this line meet what your enrolled carrier programs require. |

Each cell carries a stance pill: Healthy (green), Drift (amber), Exposed (red), or a dash for N/A when the dimension doesn't apply yet. Most cells are clickable, they drop you straight into the SOP, the standards catalog, or the certifications page behind the number.

SOP coverage column

• No SOP. Stance Exposed. Reads "No SOP," with "Adopt a starter SOP from the standards catalog." Clicking takes you to the By Standard tab so you can pull in a starter framework.
• Draft only. Stance Drift. Reads "Draft only (N)." A draft exists but nothing has been activated yet, so it isn't feeding peer benchmarks or matching jobs. Clicking opens All Processes filtered to SOPs so you can finish and activate it.
• Active, score still computing. Stance Drift. Reads "Active but no score." Rare, and resolves itself once the LEAN score finishes computing.
• Active, scored against a target. Once an SOP is active and has a LEAN score, Verinode compares it to the target score for that category (drawn from the process research library, scoped to global and federal standards). The cell reads "Active · LEAN {score} / {target}":

- At or above target: Healthy. - Between 75% and 100% of target: Drift, "Active but below the framework target, refine steps to close the gap." - Below 75% of target: Exposed, "Active SOP scoring well below target, the documentation isn't doing the work it should."

• Active, no target available for the category. The cell reads "Active · LEAN {score}" (or just "Active" if no score yet) and defaults to Healthy.

The adherence suffix. When Verinode has enough closed jobs in that category to read how often your crews actually followed the SOP, the cell adds "· NN% followed (F/T)" after the LEAN score, and the detail line explains the read's confidence: below eight jobs it's marked directional and not yet verified; at or above eight jobs, if crews deviated on more than half the work, the stance drops to Drift even if the LEAN score itself cleared the target, because a well-written SOP nobody follows in the field isn't actually coverage.

Certified holders column

This column checks whether your team holds the credentials this service line implies, and whether you hold enough of them. The requirement list comes from two places: preferably, the certifications your own adopted standard implies (tagged "implied by adopted standard"); when you haven't adopted a benchmark standard for the category yet, a baseline service-line-to-certification mapping fills in instead (tagged "service-line baseline").

• No requirement found. Stance N/A (dash). "Adopt an SOP from the standards catalog to see implied credentials."
• All required certs missing. Stance Exposed if any missing cert is marked required (or Drift if all missing ones are only "preferred"). Reads "0 / N certs," lists which credentials are missing.
• Some held, some missing. Same required/preferred logic for the stance. Reads "M / N certs held," lists what's missing, "Schedule the training."
• All present but thin. When every required credential has at least one holder but hasn't reached the depth the standard implies (more than one person should hold it, for resilience), stance is Drift: "N / N present, M under threshold," with the shortfall spelled out per credential, "Add depth."
• Fully covered. Stance Healthy: "M / N held with depth," every required credential at or above the minimum head count the standard implies.

Cells here link to your Certifications page.

Carrier programs aligned column

This column only applies once you're enrolled in at least one carrier program (via Clients → Programs). If you have no active enrollments, the cell reads N/A, "No carrier programs enrolled." If your enrolled programs simply don't have any SOP requirement in this category, it also reads N/A, "Enrolled programs don't have SOP requirements in this category."

Where a requirement does exist, Verinode checks whether you have an active SOP in the matching framework, and whether its LEAN score clears the program's minimum target:

• All undocumented. Stance Exposed: "0 / N programs aligned," names the programs requiring it.
• Some documented, some not, or below the program's target. Stance Drift: "M / N programs aligned," a count of the gaps and which programs they belong to.
• Fully aligned. Stance Healthy: "N / N programs aligned," every active SOP for this category clears every enrolled program's target.

Cells here link to Clients → Programs.

Unmapped service lines

Your profile's service-mix entries have to roll up to a category the platform recognizes (water, fire, mold, biohazard, asbestos, lead, reconstruction, contents, storm) before they can get a row in the matrix. If any entries don't map, they're listed underneath the table: "Unmapped service lines (no platform coverage view yet): …" It's a heads-up, not an error, it just means that particular line doesn't have a coverage view built for it yet.

Empty state

If your operator profile has no service lines on it at all, the whole tab collapses to a single explanation instead of an empty table:

"Verinode builds your coverage view from the service lines on your operator profile. Once you tell us what work you do, this matrix shows where you're HEALTHY, where you're drifting, and where you're exposed across SOPs, certifications, and carrier programs."

with an Open onboarding → button underneath. Fill in your service mix there (or through IQ chat) and the matrix populates on your next visit.

The process gap panel: uncovered lines inside a decision

Coverage gaps don't only show up in the matrix. When a decision Verinode surfaces touches a service line with weak or missing documentation, a process gap on this decision panel (tagged Process Coach) appears inside that decision's workspace, between the related research and the plan steps. See The decision workspace for how these panels sit inside a decision generally.

Each gap gets its own card, naming the service line in plain language (e.g. "water mitigation," "fire & smoke restoration") and one of two states:

• No documented SOP for {line}. If Verinode has a matching benchmark standard to suggest, the card adds "Verinode recommends {standard} as the starter" and offers an Adopt {standard} as draft SOP button, one click scaffolds the draft without leaving the decision.
• Existing SOP: {title}. The SOP exists but the gap detector flagged something about it relative to this decision.

Where relevant, the card also lists how many of your enrolled carrier programs require alignment with that framework, and which implied credentials come with it (with the required minimum head count and whether each is "required" or merely "preferred").

Every card carries Mark not relevant (dismisses the card and records that you reviewed it) and an Open in /processes → link that jumps to the existing SOP or the By Standard tab. After adopting, the card confirms: "Draft SOP created, open /processes to refine the steps."

How to use it

1. 1Check the Lines Without An SOP tile in the Explore row (or the hero's documented-coverage pill). A red or amber reading means at least one service line is running with no written process behind it.
2. 2Open the Coverage tab and scan the SOP coverage column top to bottom. Any row marked Exposed is a line with either no SOP or one scoring well below the target, start there.
3. 3For rows that are Healthy on SOP coverage, check Certified holders. A green SOP with an exposed cert column means the documentation is fine but you don't have the credentialed people to execute it.
4. 4Check Carrier programs aligned for any line you run under an enrolled program. A gap here can affect whether that program still considers you compliant, not just whether you're internally documented.
5. 5When a decision surfaces a gap directly, use the inline Adopt … as draft SOP button in the process gap panel rather than navigating back to Coverage, it's the same action with one click.

Best-practice example

Say your documented-coverage pill reads 67% (amber), and the Coverage tab shows Reconstruction as Exposed on SOP coverage: "No SOP." Below it, Certified Holders for Reconstruction reads Drift, two of three implied credentials held but under the depth the standard calls for. Rather than treating these as two separate problems, adopt the starter SOP from By Standard first, since the adopted standard is what feeds the correct certification requirements into the Certified Holders column in the first place. Once that SOP is active and scoring against its target, come back to the cert column with the real requirement list in hand, and schedule training for the credential still short of depth.

Data sources