How conformance is graded: met, near, missed

What conformance grading is

Every restoration franchise makes a promise to the customer about pace: how fast a job gets assigned, how fast an estimate is submitted, how fast a supplement gets a response. Process Standards is where HQ writes that promise down as a target number of days per stage. Conformance grading is the other half: it takes each office's actual stage-time median and checks it against that target, automatically, every night. This article covers the grading math only, the three verdicts and the math behind them, so read hq-standards first for how a standard gets set in the first place, and network-health for where the graded results surface across the network.

Verinode does not set the target and it does not decide whether an office is doing well. HQ sets the target days. Verinode reads the aggregate stage medians your offices are already producing, grades them against that target, and lays the result out so leadership can see it. Verinode never sees a single job, a single file, or a single franchisee's underlying business data to do this: the entire grading pipeline runs on the same consented, aggregated stage medians the rest of Network Health is built on.

Where to find it

Conformance grading has two homes:

• Process Standards, at hq.verinode.ai/standards/process (reached from the sidebar under Compliance, then the Process Standards tile). This is where a standard is set per transition, and where each row shows a quick read on how the network is conforming to it.
• Network, at hq.verinode.ai/network (the sidebar's Network entry, i.e. Network Health). Once at least one standard exists, a Standards Conformance tile leads the Network Flow row. Clicking it opens the Conformance tab on the Network Health card slider, where every standardized transition is broken out office by office.

Both surfaces read the same underlying grades. Process Standards is where you write the target and skim the result per transition; Network is where you drill into which offices are meeting it.

The grading math

For a given milestone transition (say, Assigned → Started in the Job lifecycle), HQ sets a target days number, the number of days the network commits to for that step. Every office that has enough history on that transition gets its own stage median, the office's own typical days for that step, recomputed nightly. Grading compares the two:

• Met. The office's median is at or under the target. medianDays <= targetDays.
• Near. The office's median is over the target, but not by more than 20%. targetDays < medianDays <= targetDays * 1.2. This is the tolerance band: a small overshoot that hasn't become a real problem yet.
• Missed. The office's median is more than 20% over the target. medianDays > targetDays * 1.2.

For example, if the standard for Assigned → Started is set at 2 days: an office running a 2-day or faster median grades Met. An office running anywhere up to 2.4 days grades Near. An office running past 2.4 days grades Missed. The 20% tolerance band is fixed across every transition and every process, it is not configurable per standard.

This is exactly the same math the Network Median row uses, too: the network's own median across all offices on that transition is graded against the same target, so you can see at a glance whether the network as a whole is meeting its own promise, not just individual offices.

Warming up: when there is no verdict

Grading an office's median only makes sense once there is enough history behind it. Any office with fewer than five in-order cases on a transition carries no median at all, and no verdict. Rather than force a grade off a thin sample, Verinode marks it Warming Up, an honest no-verdict, never a guessed one.

On the Network Health Conformance tab, a warming-up office shows "Warming Up · N of 5 [cases/jobs/supplements/etc.]" in place of a grade, using whichever noun fits the process (a job, a supplement, an applicant, an incident, a purchase, a lead, a review). Once the office clears five cases in order on that stage, its median populates and it grades on the next nightly rollup like everyone else.

Warming-up cells are never averaged into a percentage and never treated as a miss. They are simply left out of the count until there is enough to grade honestly.

Conformance %: the network number

Conformance % is the headline number in this whole system: the share of scored office checks that met the standard. "Scored" means Met, Near, or Missed combined, warming-up cells are excluded entirely since they carry no verdict.

The math: conformancePct = round((met / scored) * 100), where scored = met + near + missed. If nothing has cleared the five-case floor anywhere, scored is zero and conformancePct reads as null (shown as a dash), not zero, since zero would wrongly imply the network is failing rather than simply still warming up.

This percentage rolls up two ways depending on which surface you are on:

• On Process Standards, the hero panel's headline percentage is the network-wide conformance share across every office-cell on every transition that has a standard set.
• On the Standards Conformance tile on Network Health, the same network-wide percentage drives the tile's gauge and color.
• Per transition (each row in the Process Standards editor, and each card on the Network Health Conformance tab), the same formula runs scoped to just that transition's office cells, so you can see whether, say, the Job lifecycle's Assigned → Started step is a network-wide strong point even if another transition is dragging the overall number down.

Reading the Process Standards editor

Each row on hq.verinode.ai/standards/process is one milestone transition (for example, "Assigned → Started" under Job lifecycle, or "Submitted → Responded" under Supplement turnaround). Under each transition's name:

• Network Median [X]d · N Office(s) Reporting, or "No Network Median Yet" if no office has cleared the floor on that transition. This is the raw network-wide median, the starting point most HQ admins use before tightening a target.
• If a standard exists and has scored data: "[met] Met · [near] Near · [missed] Missed", with "· [n] Warming Up" appended when applicable. This is the per-transition breakout of the conformance math above.
• "From Network Median" appears when the current standard was adopted directly from the network's own median rather than typed in by hand.

On the right, admins see the target-days input, a Use median shortcut (only shown when a network median exists) that fills the input with that value, a Save button, and a Clear button (only shown once a standard is set) to remove the target entirely. Viewers without admin rights see a plain read-out instead: "Standard [X]d" or "No Standard".

Above the rows, a note frames the intent: standards keep the network's customer promise consistent, each target is the working pace the network commits to at that stage, measured on office stage medians from the nightly rollup, and the recommended approach is to start from the network's own medians and tighten from there.

Adopt network medians. When at least one transition has a live network median and no standard yet, admins see an Adopt network medians button in the page header. This bulk-writes the network's current median as the starting standard for every transition that doesn't have one, so you are never starting a network-wide standards program from a blank slate.

The hero panel at the top of Process Standards

The panel above the editor rows shows a status pill and a headline number:

• Not Set Yet (neutral) when no standards exist anywhere.
• Warming Up (neutral) when standards exist but nothing has scored yet.
• On Pace (green/expand tone) when conformance is 90% or higher.
• Watch (amber/maintain tone) when conformance is between 70% and 89%.
• Action Needed (red/analyse tone) when conformance is below 70%.

Below the pill, three secondary figures:

• Standards Set, the count of transitions with a target defined, out of the total number of registered transitions across every process.
• Checks Met, the count of office-checks that graded Met, out of however many have scored (or "Awaiting Data" if nothing has scored yet).
• Missed, the count of office-checks that graded Missed, with "Need Attention" underneath if that count is above zero, or "All Clear" if it is zero.

Reading the Conformance tab on Network Health

The Standards Conformance tile on the Network Health page shows the same network-wide percentage as a gauge, colored green at 90% or above, amber between 70% and 89%, and red (Ember) below 70%, with a trend line reading "[N] Near The Line" when there are Near cells but nothing worse, or "All Checks Met" when the network is clean. The tile is not shown at all until at least one standard exists anywhere in the group.

Clicking the tile opens the Conformance tab, one card per standardized transition, ordered the same way the Job lifecycle, Supplement turnaround, Recruiting pipeline, and other processes are ordered elsewhere on Network Health. Each card shows:

• The process label (e.g. "Job lifecycle") and the transition label (e.g. "Assigned → Started").
• "Standard [X]d", with "· From Network Median" appended if the target came from an adopted median rather than a manual entry.
• On the right, the network median in days, colored by its own verdict, with "Network Median" and, when graded, "· Met" / "· Near" / "· Missed" beneath it.
• A summary line: "[met] Met · [near] Near · [missed] Missed", plus "· [n] Warming Up" when relevant.
• Below that, one row per office with an aggregate on this transition: a colored dot (green for Met, amber for Near, red for Missed, neutral for warming up), the office's name, and either its verdict label with its median in days and its case count, or "Warming Up · N of 5 [cases]" when it hasn't cleared the floor.

Office rows are sorted slowest-first among scored cells, with warming-up offices pushed to the bottom, so the office needing attention on that transition is the first thing you see, not buried in an alphabetical list.

Empty states

• No standards anywhere. The Conformance tab reads: "No stage-time standards set yet. Define target days per stage under Standards → Process Standards; every office is then measured against the same bar, and the grades land here." The Standards Conformance tile does not render on Network Health at all until this changes.
• Standards set, no snapshot yet. If standards exist but the transitions list comes back empty (no aggregate snapshot has landed yet), the tab reads: "Standards are set. Office grades appear after the next nightly rollup of stage medians."
• No office data on a specific transition. Within a transition card, if no office has an aggregate row yet, it reads: "Office grades appear once an office clears five in-order [cases] on this stage." (the noun matches the process, e.g. "jobs" or "supplements").
• No network median for a transition. On the Process Standards editor, a row with no network-wide median yet shows "No Network Median Yet" in place of the median line.

Privacy boundary

Conformance grading never exposes which specific franchisees fed a network median, and it never surfaces a peer's underlying business data, only the office's own stage median, already anonymized to the group's entity model the same way office names are handled everywhere else on Network Health. The n-of-5 floor exists specifically so a single office's early, thin data never gets displayed as a real number: until there is enough history to trust, the office reads as warming up, not as a number that happens to be based on one or two cases.

HQ sets the bar. Verinode grades against it and shows the result. Leadership decides what to do about a Missed transition, whether that is a conversation with one office or a rethink of whether the target itself was realistic.

Related articles

• hq-standards: how to set a target-days standard per transition, and how to adopt network medians in bulk.
• network-health: the full Network Health page, including the Standards Conformance tile's place among the other network tiles.
• hq-compliance: the Compliance hub that Process Standards lives inside, alongside Forms & Audits and SOPs.
• hq-overview: how the HQ product fits together and where standards sit relative to benchmarks and programs.