Coverage: service lines, SOPs, certs and program posture

What the Coverage tab shows

Every service line you run carries three separate readiness questions: do you have a written procedure for it, does your team hold the certifications it implies, and does your documented process actually satisfy the carrier programs you're enrolled in. Those three questions usually live in three different places, a binder, a training tracker, a program handbook, and nobody checks them against each other until an audit or a program review forces the issue.

The Coverage tab is where Verinode reads your operator profile, your SOP library, your team's certifications, and your enrolled carrier programs together and lines them up. It does not file your certifications or enroll you in a program. It reads what's on file and shows you, service line by service line and program by program, where you stand: Healthy, Drift, or Exposed. You decide what to close and in what order.

The tab has two panels, stacked top to bottom: the carrier program compliance panel at the top rolls up your standing per enrolled program, and the coverage matrix below it breaks the same underlying data out by service line instead. They're two views of the same readiness data, one organized around your carrier relationships, one organized around the work you do.

Where to find it

Open Processes from the sidebar, or go to /processes directly. Processes is a Premier membership feature, see the Processes section for what Contributor and Executive memberships see instead.

Inside Processes, click almost any tile to open the full-screen card slider, then select the Coverage tab (accented green), fifth of six tabs across the top: Findings, Flow, All Processes, By Standard, Coverage, Benchmarks.

Panel one: carrier program compliance

What it is. One card per carrier program you're actively enrolled in (TPA and carrier network programs join through Clients → Programs, not here). Each card rolls up three data layers, your SOP coverage against the program's published requirements, your team's certification coverage against what those SOPs imply, and how closely your crews actually followed the documented steps on recent jobs, into a single stance.

Empty state. If you have 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 straight to the Carrier Programs tab. See Carrier Programs: eligibility, required certs, and vendor approvals for how enrollment itself works.

Header. Once you have at least one program, the panel header reads "N programs enrolled" (or "1 program enrolled"), with a note underneath: "One card per program · SOP coverage + cert coverage + recent job adherence rolled into a single stance."

Reading a program card

Each card leads with the program name and a stance pill:

• Aligned (green), every required SOP meets the program's target score, every required certification is held at the implied depth, and (where you have enough job history) your crews are actually following the documented steps.
• Drift (yellow), nothing is missing outright, but something is under target: an SOP scoring below the program's threshold, or crews deviating from a documented SOP on more than half of the last 90 days' relevant jobs.
• Exposed (red), a required SOP is completely undocumented, or a required certification (not just a preferred one) has zero holders.

Beside the pill, a gap count reads "N gaps" when the program has one or more open issues across SOPs, certs, or adherence. Under that, a one-line headline summarizes the whole card, for example "3 of 5 SOPs aligned · 2 of 3 certs covered · 71% adherence on 22 jobs." A program with no SOP requirements at all reads "No SOP requirements" in that first clause instead.

Below the headline, three columns:

SOPs. The count reads "X / Y", how many of the program's required SOP categories you have documented at or above the program's target score, out of the total required. Underneath:

• If any required category is completely undocumented, it lists them: "N undocumented: WRT Water, LEAD Reconstruction" (framework in caps, category humanized), truncated with "…" past three.
• If any documented SOP is below the program's target score, it lists those separately: "N below target: …".
• If every required SOP is aligned, it reads "All required SOPs at or above the program target."
• If the program has no SOP requirements published, it reads "No SOP requirements declared for this program."

Certs. The count reads "X / Y", certifications implied by the program's required SOPs that you hold at the required depth (enough active holders, not just one person on staff), out of the total implied. Underneath:

• Any gap lists the certification name and your current count against the required count, for example "WRT 1/2," truncated past three with "…".
• If the program's SOPs don't imply any certifications, it reads "No implied certs for this program's SOPs."
• If every implied credential is covered, it reads "Every implied credential meets the implied min-holders threshold."

Recent jobs (90d). This is the adherence check, whether the documented SOP is actually what happened on the job, not just what's on file. The count shows a percentage once you have enough sample, or a raw "followed / total" while the sample is still thin:

• With no closeouts in the program's relevant categories yet, it shows a dash and reads "No closeouts on this program's SOP categories yet."
• With fewer than eight qualifying jobs, it shows "followed / total" and reads "X of Y jobs followed, directional read, not yet verified (need at least 8 jobs)." Below eight jobs the read is too thin to trust as a trend.
• At eight or more jobs with adherence below half, it reads "Field crews deviating on more than half the program-relevant jobs. Adoption-without-adherence." This is the case where the SOP exists and looks fine on paper, but the field isn't running it.
• At eight or more jobs with adherence at or above half, it reads "Field crews running the documented SOPs on most jobs."

Footer links. Every card links to "Open program detail →" (your standing on that program under Clients → Programs). Any card that isn't Aligned also shows "Adopt missing SOPs," which opens the By Standard tab so you can scaffold the missing procedure straight from the standards catalog.

Panel two: the coverage matrix

What it is. Where the compliance panel is organized by carrier program, the matrix is organized by service line, the work you actually do, day to day. It's the same underlying SOP, cert, and program data, read from the other direction: instead of "how do I stand with Liberty Preferred," it answers "is my water mitigation service line covered end to end."

Empty state. If your operator profile has no service lines on file yet, the whole tab shows this instead of a 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. Add your service mix and the matrix populates.

The table. Once you have service lines on file, you get a header line: "Service line × coverage dimension. Each cell tells you where the operator stands on SOPs, certifications, and carrier-program alignment. Click a cell to drill in." Below it, one row per service line, four columns:

• Service line. The humanized service-line name (for example "Water Mitigation"), with "Category:" underneath naming the underlying SOP category it rolls up to (water, fire, mold, biohazard, asbestos, lead, reconstruction, contents, or storm).
• SOP coverage.
• Certified holders.
• Carrier programs aligned.

Each of the three coverage columns is a cell with a stance pill (Healthy, Drift, Exposed, or a blank dash for N/A), a short label, and, on most cells, a line of detail underneath. Click any cell to drill straight to the place that fixes it.

SOP coverage cell

• No SOP on file for this category reads Exposed, "No SOP," with a link to adopt a starter SOP from the standards catalog.
• Only a draft exists, nothing active reads Drift, "Draft only (N)," prompting you to activate it so it starts contributing to peer benchmarks and job matching.
• Active, but the LEAN score hasn't computed yet reads Drift, "Active but no score."
• Active, with a score, measured against a framework target (where Verinode has a published target for that category):

- At or above target: Healthy, "Active · LEAN 82 / 75" (your score over the target). - Between 75% and 100% of target: Drift, same label format, "Active but below the framework target, refine steps to close the gap." - Below 75% of target: Exposed, same label format, "Active SOP scoring well below target, the documentation isn't doing the work it should."

• No published framework target for the category: reads Healthy with "Active · LEAN 82" (or just "Active" if no score).

Wherever adherence data exists for the SOP, the cell appends it: "· 71% followed (16/22)." If your job sample for that SOP is under eight, the detail line adds a caveat that the adherence read is still directional. If it's eight or more jobs and adherence is below half, the cell downgrades from Healthy to Drift even if the LEAN score itself clears the target, because a well-scored SOP the field isn't running isn't actually covering you.

Certified holders cell

This checks whether your team holds the credentials your SOP implies, and holds them in enough depth (more than one person, where the requirement calls for it). Two sources feed the requirement list: if you've adopted a benchmark-sourced SOP for the category, Verinode uses that standard's actual implied-certification list (tagged "implied by adopted standard"); otherwise it falls back to a general service-line baseline (tagged "service-line baseline").

• No cert requirement found at all reads N/A, a dash, prompting you to adopt an SOP from the standards catalog to surface implied credentials.
• None of the required certs are held reads Exposed if any of them are required (not just preferred), otherwise Drift. Label: "0 / N certs (source)," with the missing certifications named.
• Some held, some missing reads Exposed or Drift by the same required-versus-preferred rule. Label: "X / N certs held (source)," with the missing ones named and a prompt to schedule the training.
• All required certs held, but below the minimum holder count (for example the standard calls for two WRT holders and you have one) reads Drift: "N / N present, M under threshold (source)," naming which certs need more depth.
• Every required cert held at full depth reads Healthy: "X / N held with depth (source)."

Carrier programs aligned cell

This is the matrix's view of the same program-alignment math the compliance panel above computes, but scoped to this one service line instead of rolled up per program.

• No carrier programs enrolled reads N/A, a dash, "No carrier programs enrolled."
• Enrolled, but none of your programs require an SOP in this category reads N/A, "Enrolled programs don't have SOP requirements in this category."
• Programs require it and none are met reads Exposed: "0 / N programs aligned," naming which programs need it.
• Some met, some not reads Drift: "X / N programs aligned," with a gap count and the programs affected.
• Every enrolled program's requirement is met for this category reads Healthy: "X / N programs aligned."

Unmapped service lines. If an entry in your service mix doesn't roll up to a recognized SOP category, it doesn't get a row. Instead it's listed below the table: "Unmapped service lines (no platform coverage view yet): [names]." This is a vocabulary gap, not a data problem, the platform doesn't yet have a coverage view built for that exact service-line label.

1. 1Open Processes from the sidebar and select the Coverage tab in the card slider.
2. 2Scan the carrier program compliance panel first. Any card that isn't Aligned is the priority list, sort mentally by whether it's Exposed (a required SOP or cert is completely missing) or Drift (something's below target).
3. 3Use the Adopt missing SOPs link on an Exposed or Drift card to jump straight to the By Standard tab and scaffold the missing procedure.
4. 4Scroll to the coverage matrix and check the Certified holders column for any service line still reading Exposed or Drift after the SOP is fixed, missing certs need scheduling, not just documentation.
5. 5Recheck the Carrier programs aligned column last. Once the SOP and cert cells clear, this column usually clears with them, since it's testing the same underlying documentation and credential state against each program's specific bar.

Best-practice example

Say your coverage matrix shows Water Mitigation as Drift on SOP coverage: "Active · LEAN 68 / 75," meaning your documented procedure exists but scores below the framework's target. The Certified holders cell for the same row reads Exposed: "0 / 2 certs (implied by adopted standard)," missing WRT entirely. Up in the compliance panel, your enrolled program card for that carrier shows the same story from its own angle: "1 of 3 SOPs aligned," with Water Mitigation in the "below target" list, and the Certs column flags the same WRT gap.

Read together, this is one underlying problem showing up three ways, not three separate issues. Fix the SOP first (refine the steps against the framework's target, since it's the thing your own LEAN score is already grading you on), get the WRT-certified holders scheduled, and both the matrix row and the program card clear together.

Related reading

• The Processes section
• How your work flows: the Flow tab and process mining
• Confirming an observed process pattern
• Take Action and process decisions
• Carrier Programs: eligibility, required certs, and vendor approvals
• Clients and carriers
• How Verinode's benchmarks work