The Coverage tab: which service lines have an SOP

What the Coverage tab shows

Every service line you run carries three separate compliance questions: do you have a documented procedure for it, do you have enough certified people to deliver it, and does it satisfy the carrier programs you're enrolled in? Most operators can answer one of those three from memory. Almost nobody can answer all three, for every service line, at once.

The Coverage tab is where Verinode answers all three in one screen. It reads your operator profile's service mix, your adopted SOPs, your team's active certifications, and your enrolled carrier programs, and lays out where you're solid, where you're drifting, and where you're exposed. Verinode doesn't decide what to fix first, it surfaces the gaps and drills you straight to the place that closes each one. You decide what to work on.

Where to find it

Open Processes from the sidebar (Operations group) at iq.verinode.ai/processes. The page is a card slider with six tabs: Findings, Flow, All Processes, By Standard, Coverage, and Benchmarks. Coverage is the fifth tab.

The Coverage tab stacks two surfaces top to bottom:

1. Carrier program compliance: one card per enrolled program, each rolled up to a single ALIGNED / DRIFT / EXPOSED stance.
2. Coverage matrix: one row per service line you run, three columns (SOP coverage, Certified holders, Carrier programs aligned), each cell its own stance pill.

They read the same underlying data at two altitudes: the matrix is the granular, per-service-line detail; the program cards are the rollup that answers "am I good with Carrier X" without you having to scan every row yourself.

Carrier program compliance

What it is. For every carrier or TPA program you have an active membership in, Verinode checks three things against that program's requirements: whether you have an active SOP in every category the program requires, whether your team holds the certifications those SOPs imply, and whether your crews actually follow those SOPs in the field over the last 90 days. It folds all three into a single stance per program.

Header. Reads "N program(s) enrolled" with a note underneath: "One card per program, SOP coverage + cert coverage + recent job adherence rolled into a single stance."

Per-program card. Each card shows:

• Program name and a stance pill: ALIGNED, DRIFT, or EXPOSED.
• A gap count beside the pill (e.g. "3 gaps") when the program has any open gaps. Not shown when there are none.
• A headline sentence assembled from whatever applies: "N of M SOPs aligned", "N of M certs covered", and "X% adherence on N jobs" (the adherence clause only appears once you have at least eight closeout jobs on that program's SOP categories, before that there isn't enough volume to read a percentage with confidence).

Below the headline, three columns break the rollup apart:

• SOPs: shows aligned / total required categories. If any are undocumented, a line lists up to three by framework and category (e.g. "IICRC Water Mitigation"), with a "+N more" style ellipsis past three. A separate line lists any that are documented but below the program's target score. When every required category is aligned, it reads "All required SOPs at or above the program target." When the program has no SOP requirements at all, it reads "No SOP requirements declared for this program."
• Certs: shows aligned / total required certifications (the certs implied by the SOPs feeding this program). Gaps list the certification name and its current-holders-over-minimum-holders count (e.g. "IICRC WRT 1/2"), up to three with an ellipsis. When there are no implied certs at all it reads "No implied certs for this program's SOPs." When every one is covered it reads "Every implied credential meets the implied min-holders threshold."
• Recent jobs (90d): the field-adherence read. With fewer than eight qualifying closeouts it shows the raw count ("5 / 6") with a note that the read is directional, not yet verified, until you clear eight jobs. At eight or more it switches to a percentage and a plain-language line: crews running the documented SOPs on most jobs, or crews deviating on more than half of them (worded as "adoption without adherence", the case where you documented the procedure but the field isn't following it). With zero qualifying jobs it reads "No closeouts on this program's SOP categories yet."

Links on each card. "Open program detail" always appears and jumps to /clients?tab=programs&program=<name>. When the stance isn't ALIGNED, a second link, "Adopt missing SOPs", jumps to the By Standard tab (/processes?tab=by_standard) so you can close the SOP gap directly.

Empty state. With no active program memberships, the panel reads: "No carrier programs enrolled yet. Programs join via /clients → Programs. Once enrolled, the platform reads each program's required SOPs, implied certs, and recent adherence into a single posture per program here." The "/clients → Programs" text links to /clients?tab=programs.

Coverage matrix

What it is. One row per service line in your operator profile's service mix, three columns for the dimensions that determine whether you can deliver cleanly on that line: SOP coverage, Certified holders, and Carrier programs aligned. Each row also shows the internal process category the service line rolls up to (for example, a water-mitigation service line rolls up to the Water category, fire and smoke lines roll up to Fire, and so on) directly under the service-line name.

Each cell is a stance pill plus a short label and, where relevant, a one-line detail. Four stances appear in the matrix specifically:

• Healthy: the coverage criterion is fully met.
• Drift: partial coverage: an SOP exists but scores below the framework's target, a certification is held but by fewer people than the standard implies you need, or a program requirement is partly but not fully satisfied.
• Exposed: no coverage at all on a required item.
• N/A (shown as a dash): the dimension doesn't apply yet, for example no cert requirement has been identified, or no carrier programs are enrolled.

Click any cell to drill straight into the place that fixes it.

Column: SOP coverage

Checks whether you have an active, documented procedure for the category, and how it scores against the framework's target.

• No SOP (Exposed): "Adopt a starter SOP from the standards catalog." Links to the By Standard tab.
• Draft only (N) (Drift): you've started one or more SOPs but haven't activated any. Detail: "Activate the draft to start contributing to peer benchmarks + match jobs." Links to All Processes filtered to SOPs.
• Active but no score (Drift): an SOP is active but its lean score hasn't finished computing yet. Links to All Processes filtered to SOPs.
• Active · LEAN [score] / [target] (stance depends on the gap): once a framework target score exists for the category, your best active SOP's lean score (a structural completeness score for how thoroughly the procedure is written and staffed) is measured against it.

- At or above target: Healthy. - Within 75% 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 framework target available for the category): Healthy by default, showing the lean score if one exists.

When Verinode has enough closeout history on that SOP (again, at least eight jobs), the label picks up a suffix like "· 62% followed (8/13)", the share of recent jobs where the crew actually ran the documented steps. If that adherence rate drops below half on eight or more jobs, a would-be Healthy cell is downgraded to Drift and the detail explains: "Crews deviate on more than half the jobs in this category. Field rollout has more drift than the documentation captures." Below eight jobs, the detail notes the reading is directional, not yet verified.

Column: Certified holders

Checks whether your team holds the certifications the category implies, and whether you have enough people holding each one. Requirements come first from the standards your adopted SOPs are built on (a real, catalog-sourced minimum-holders count per certification); if you haven't adopted a benchmark SOP for that category yet, Verinode falls back to a baseline certification list tied to the service line itself. The cell's detail line always notes which source is behind the requirement.

• No requirement identified (N/A, dash): "No cert requirement found. Adopt an SOP from the standards catalog to see implied credentials." Links to By Standard.
• 0 / N certs (Exposed if any missing cert is required, Drift if only preferred ones are missing): lists the missing certification names. Links to Certifications.
• Some held, some missing (same Exposed/Drift split): "N of M certs held", lists what's missing plus "Schedule the training." Links to Certifications.
• All present, some under threshold (Drift): every required certification has at least one holder, but one or more haven't reached the minimum-holders count the standard implies (e.g. "IICRC WRT 1/2"). Detail: "Below the implied min-holders count: [list]. Add depth." Links to Certifications.
• Fully covered (Healthy): "N of M held with depth", every required credential meets its implied minimum-holders count.

Column: Carrier programs aligned

Checks whether your active SOPs in the category satisfy every enrolled carrier program that requires an SOP there.

• No programs enrolled (N/A, dash): "No carrier programs enrolled." No drill-in.
• No requirement for this category (N/A, dash): your enrolled programs don't require anything in this category. No drill-in.
• 0 / N aligned (Exposed): lists the programs with the gap. Links to /clients?tab=programs.
• Some aligned (Drift): "N of M programs aligned", plus a gap count and the affected program names.
• All aligned (Healthy): "Active SOPs meet every enrolled program's target for this category."

Unmapped service lines

Not every entry on your operator profile maps cleanly to one of Verinode's process categories yet. When that happens, the entry is left out of the matrix rows and listed instead at the bottom of the table: "Unmapped service lines (no platform coverage view yet): [list]." It's a flag that your profile has a service line the coverage view can't score yet, not an error.

Empty state

If your operator profile's service mix is empty, the whole matrix is replaced with a single message:

"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 linking to /onboarding.

1. 1Open Processes from the sidebar and select the Coverage tab.
2. 2Scan the carrier program cards first (they're already sorted EXPOSED, then DRIFT, then ALIGNED). Note which programs and which columns (SOPs, Certs, jobs) are carrying the gap.
3. 3Drop down to the coverage matrix for the same picture broken out by service line. A program gap in the "SOPs" column usually traces to a specific "No SOP" or "Draft only" row in the matrix.
4. 4Click the cell that's furthest from Healthy. It drills you to the exact place to fix it: By Standard to adopt a starter SOP, All Processes to activate a draft or check a lean score, Certifications to book training or add depth, or Clients → Programs to see the program's own requirement detail.
5. 5Recheck the tab after you activate an SOP, log a certification, or a job closes out. Every cell recomputes from your live data, there's nothing to manually mark done.

Related

• Standards, drafts, and adopting SOPs for enrolling and managing carrier programs
• Acting on decisions for how a coverage gap can turn into a Finding you can work
• The decision workspace for how Verinode frames a decision once you act on a gap
• How benchmarks work for how framework target scores and peer SOP comparisons are built
• Connecting your data for how job closeouts and certifications flow in and keep the matrix current