Compliance posture: standards adherence at a glance

What it is

Every carrier program you join publishes a set of expectations: which SOPs it wants documented, at what quality bar, and which certifications those procedures imply your team should hold. Those expectations usually live in a program handbook somewhere, separate from your own SOP library and your team's certification records. Nobody checks the three against each other until an audit or a program review forces the question.

Verinode reads all three together. It reads the program's published requirements, your documented SOPs and their lean scores, your team's active certifications, and (once you have enough job history) whether the field is actually running what's written down. It rolls that into one posture per program: Aligned, Drift, or Exposed. Verinode does not enroll you in a program, write your SOPs, or file your certifications. It reads what's on file and shows you where you stand. You decide what to close and in what order.

This article covers two panels that work together on the same underlying data: the compliance posture panel, one card per enrolled carrier program, and the adherence panel, the per-SOP execution check that sits inside a SOP's own detail card.

Where to find it

Open Excellence from the sidebar. It takes you to /processes, Excellence and Processes are the same feature. Processes is a Premier membership feature, see the Processes section for what Contributor and Executive memberships see instead.

Inside Processes, click a tile to open the full-screen card slider and select the Coverage tab, one of six tabs across the top (Findings, Flow, All Processes, By Standard, Coverage, Benchmarks). The compliance posture panel sits at the top of that tab, above the service-line coverage matrix. For the matrix and its full service-line breakdown, see Coverage: service lines, SOPs, certs and program posture.

The adherence panel lives one level down: open any SOP's own detail card (click a tile in My SOPs), and it appears under the heading Adherence (90 days), below the SOP's status section and above any credentials the SOP implies.

The compliance posture panel

Empty state

If you have no active carrier program memberships, the panel reads, verbatim:

"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."

That "/clients → Programs" text is a link 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 active membership, 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." Cards are ordered Exposed first, then Drift, then Aligned, alphabetically within each stance, so the programs needing attention surface at the top.

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 depth the program implies, and, where you have enough job history to judge it, your crews are running 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 a merely preferred one) has zero holders.

Beside the pill, a gap count reads "N gaps" (or "1 gap") whenever the program has one or more open issues across SOPs, certs, or adherence. Below that sits a one-line headline that 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 published SOP requirements at all reads "No SOP requirements" in that first clause instead, and the cert clause and adherence clause each drop out of the headline when there is nothing to report for them.

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:

• Any completely undocumented category is listed: "N undocumented: WRT Water, LEAD Reconstruction" (the framework in capitals, the category name humanized), truncated with "…" past three.
• Any documented SOP scoring below the program's target is listed separately: "N below target: …", same format.
• 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", how many certifications implied by the program's required SOPs 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 and your current count against the required count, for example "IICRC 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 field-adherence check for the program as a whole, whether the documented SOP is actually what happens on the job, not just what's on file. It aggregates adherence across every one of your SOPs whose category matches something the program requires:

• With no qualifying closeouts yet, the number reads as a dash and the note underneath reads "No closeouts on this program's SOP categories yet."
• With fewer than eight qualifying jobs in the 90-day window, the number shows the raw count ("followed / total") and the note reads that this is a directional read, not yet verified, because the sample is still too thin to trust as a trend.
• At eight or more qualifying jobs with adherence below half, the number switches to a percentage and the note reads "Field crews deviating on more than half the program-relevant jobs. Adoption-without-adherence." That phrase names the specific failure mode: the SOP exists and looks fine on paper, but the field isn't running it.
• At eight or more qualifying jobs with adherence at or above half, the note reads "Field crews running the documented SOPs on most jobs."

Footer links

Every card links to Open program detail →, which opens your standing on that program under Clients → Programs. Any card that isn't Aligned also shows Adopt missing SOPs, which jumps straight to the By Standard tab so you can scaffold the missing procedure from the standards catalog instead of starting from a blank page.

The adherence panel

Where the compliance posture panel rolls adherence up across every SOP that touches a program, the adherence panel is the single-SOP version: it lives inside one SOP's own detail card and only counts jobs in that SOP's own category that closed out and linked back to it. A mitigation SOP's adherence number has nothing to do with your fire or reconstruction SOPs.

Verinode reads the job executions that flow in through your closeout process, checks each one against the SOP's documented steps, and counts what it finds. A job with no recorded deviation counts as followed. A job with one or more recorded deviations counts as not followed. Verinode does not watch or grade your crews personally, it reads execution data and turns it into a number, a trend, and a plain-language read. You decide what to do with it: retrain a step, simplify the SOP, or leave it alone because the SOP is fine and the field just needs a refresher.

The headline count

At the top of the panel, a large number reads followed/total, for example 18/24. Beside it, a percentage repeats the same ratio (18/24 renders as 75%), colored to read at a glance:

• Green, 80% or higher: most jobs are running the SOP as written.
• Amber, 50% to 79%: adherence is mixed.
• Red, under 50%: more than half the jobs in the window deviated from the documented steps.

The cohort confidence label

Beside the headline count, a pill names how much weight to put on the number: Early signal, Indicative, Observed, or Verified. This is the platform's labels-over-gating ladder, rather than hiding the ratio until enough jobs have closed out, Verinode always shows the number and tells you in plain language how much confidence to place in it. The label strengthens on its own as more jobs close out and link to this SOP, there is nothing to configure or unlock.

The 13-week sparkline

Below the headline, a small chart plots adherence week by week across the same 90-day window, one dot per week. Height encodes that week's ratio, color follows the same green/amber/red bands as the headline percentage, and a thin stem connects each dot to the baseline so the trend's shape reads at a glance. A week with zero qualifying closeouts renders as a small, faint dot sitting on the baseline, distinct from a week that scored low: a faint dot means no signal that week, not that adherence collapsed. Hover any dot for the exact date, followed/total count, and percentage.

The variance line

When the panel has enough data, a line beneath the sparkline reports whether closeout jobs ran on plan, over plan, or under plan, on actual versus estimated minutes. This measures something different from adherence: adherence asks whether the crew ran the documented steps, variance asks whether the job took as long as the SOP's steps predicted, averaged across every closeout job in the window with both an estimate and an actual figure recorded. Within about 5% either way counts as on plan. This line only appears once at least one qualifying job carries both figures, there is no separate empty-state message for it, it is simply omitted until then.

The closing guidance line

The panel ends with one sentence that changes with the headline ratio, framed as Verinode's read, not an instruction:

• Under 50%: crews are deviating from the documented SOP on more than half the jobs in the window, walk a few jobs end to end before second-guessing the SOP, since adoption-without-adherence is more common than the SOP itself being wrong.
• 50% to 79%: adherence is on the way up but not consistent yet, and the deviation captures on the Jobs tab point to which specific steps the crew skips most.
• 80% and above: field crews are running the SOP step for step, and the sparkline's dips are where to look next, not the average.

Empty state

Before any job has closed out and linked to this SOP, the panel shows no zero count and no empty chart. It reads, verbatim:

"No execution data yet. When jobs in this category close out and link to this SOP, adherence + drift signal land here."

If the SOP has no category recorded, an uncommon case for a hand-built SOP that hasn't had one assigned, the second sentence instead reads:

"When jobs close out and link to this SOP, the adherence rate lands here."

Either way, nothing needs configuring. Once jobs in the category start closing out and linking to this SOP, the panel switches to the live count on its own.

How the two panels relate

The compliance posture panel is the program-level rollup: it answers "how do I stand with this carrier program." The adherence panel is the single-SOP drill-down: it answers "is this one procedure actually being followed in the field." When a program card's Recent jobs (90d) column reads low, open the individual SOPs behind that category and check their own adherence panels, the sparkline and the closing guidance line will usually point to whether the whole program is deviating or just one procedure inside it.

1. 1Open Excellence from the sidebar and select the Coverage tab in the card slider.
2. 2Scan the compliance posture panel first. Any card that isn't Aligned is the priority list, Exposed cards (something is completely missing) generally come before Drift cards (something is below target).
3. 3Use Adopt missing SOPs on a Drift or Exposed card to jump to the By Standard tab and scaffold the missing procedure.
4. 4For a program flagged on the Recent jobs (90d) column, open the relevant SOPs under My SOPs and check each one's own Adherence panel to see which specific procedure is driving the low read.
5. 5Read the closing guidance line on that SOP's panel before acting: a low ratio is an adoption question first (is the field running this SOP at all), a quality question second (is the SOP itself wrong).

Best-practice example

Say your compliance posture panel shows a program card in Drift: "3 of 5 SOPs aligned · 2 of 3 certs covered · 42% adherence on 19 jobs." The Recent jobs column is the flag, adherence is below half but the sample (19 jobs) is over the eight-job floor, so it's a real signal, not noise. Opening the Water Mitigation SOP behind that category shows its own Adherence panel at 8/19, an Indicative cohort label, and a sparkline that dips hard in the last three weeks after holding steady above 70% before that. The closing guidance line reads the under-50% framing: check adoption before rewriting the SOP. A quick look at the Jobs tab's deviation captures shows the same step skipped on nearly every recent job, one to walk with the crew, not a reason to rewrite the procedure.

Related reading

• Coverage: service lines, SOPs, certs and program posture
• Adherence: how often your jobs actually follow the SOP
• Processes overview
• Carrier Programs: eligibility, required certs, and vendor approvals
• Clients and carriers
• How Verinode's benchmarks work
• Connecting your data