Verinode
Open Verinode

Standards conformance: grading offices against your bar

Every restoration network has a pace it wants every office to hit: how many days a job should sit before the estimate goes out, how fast a supplement gets a response, how quickly a safety incident…

9 min read·Updated July 14, 2026
On this page

What Standards Conformance shows

Every restoration network has a pace it wants every office to hit: how many days a job should sit before the estimate goes out, how fast a supplement gets a response, how quickly a safety incident gets closed. Standards Conformance is where you write that pace down once, as a target-days standard per stage, and then see every office graded against it, automatically, on the same bar.

Verinode does not set the bar for you and it does not audit a single job to produce the grade. It reads the stage medians your offices are already producing (the same per-office numbers behind Network Flow) and checks each one against the standard you defined. The result is a Met / Near / Missed / Warming up verdict per office per stage, so you can see who is keeping the network's promise and who needs a conversation, without touching a single franchisee's underlying job file.

This is standards support, not surveillance. HQ never sees the individual jobs behind a stage median, only the median itself and how it compares to the target you set.

Where to find it

Standards Conformance lives on the Network page, at hq.verinode.ai/network (sidebar: Network). It shows up in two places on that page:

  • The Standards Conformance tile, leading the Network Flow row on the Network home. It only appears once your network has at least one stage-time standard defined; until then, the row starts directly with the Network Flow tiles.
  • The Conformance tab, one of nine tabs in the Network card slider (Signals, Interventions, Top, Watchlist, Risers & Fallers, Network Flow, Conformance, Activity, Location Directory). Clicking the Standards Conformance tile opens the slider directly on this tab; you can also swipe to it from any other tab.

Setting the standards themselves happens on a separate page: Process Standards, reached from Compliance in the sidebar. Open Compliance, find the Standards & Audits row, and click the Process Standards tile. That page (hq.verinode.ai/standards/process) is the editor; the Network page and its Conformance tab are the read-only scoreboard.

How grading works

A standard is a target number of days for one milestone transition, for example "Assigned → Estimate submitted" in the job lifecycle, or "Submitted → Responded" in supplement turnaround. HQ sets the target once per transition. Every night, the aggregate refresh recomputes each office's own median days for that same transition from its own jobs, and that median is what gets graded, never an individual job.

The grade compares an office's stage median to the target:

  • Met: the office's median is at or under the target. The bar is being kept.
  • Near: the median is over the target but still within a tolerance band around it (up to 20% over). The office is a little slow but not yet a real problem.
  • Missed: the median is more than 20% over the target. This is where a follow-up is worth having.
  • Warming up: the office hasn't logged enough of that stage's cases yet for its median to be trustworthy. Standards Conformance never assigns a fake verdict to a thin sample; it says so instead, exactly as it does everywhere else stage medians are used. In the office list, a warming-up office reads "Warming Up · 2 of 5 cases" (the case noun changes per process, for example "jobs," "supplements," "incidents").

Every verdict rides on the office's own stage median, the same aggregate surface used across the Network page. No job-level detail, adjuster name, dollar figure, or customer information ever enters this grading. If an office is under the sample floor for a transition, it simply doesn't get scored on it yet, on any surface.

Note

"Missed" is not automatically a conversation starter on its own. A single bad snapshot can happen for any office. Verinode's cross-network signal detector separately watches for offices that miss the same standard on two consecutive nightly snapshots before it raises anything to your Signals feed, so a one-off dip in the Conformance grid doesn't turn into unnecessary noise. See Signals and interventions for how that escalation works.

The Standards Conformance tile

When at least one standard is defined, the tile shows:

  • A percentage, the share of scored office checks, across every standardized transition, that came back Met. This is your headline conformance rate.
  • A ring gauge behind the number, colored green above 90%, amber between 70% and 90%, and Ember Red below 70%.
  • A subtitle reading "X Of Y Checks Met" once you have scored checks, or "N Standard(s) · Warming Up" while every office is still below the sample floor on every transition.
  • A delta line underneath: "N Missed" (flagged) if any checks missed, otherwise "N Near The Line" (neutral) if any are in the tolerance band, otherwise "All Checks Met" once every scored check clears the bar.

Clicking the tile opens the Conformance tab on the card slider.

The Conformance tab

Inside the slider, the Conformance tab lists one row per standardized transition, grouped in the same order as Network Flow (job lifecycle first, then supplement turnaround, recruiting pipeline, and so on through every process your network has registered milestones for). Each transition row shows:

  • The process label (e.g. "Job lifecycle") in small caps above the transition name.
  • The transition name (e.g. "Assigned → Estimate submitted").
  • The standard, formatted as days (e.g. "Standard 5d"), with " · From Network Median" appended if HQ adopted the network's own median as the target rather than typing one in by hand.
  • The network median on the right, in the same accent color as its verdict, with "Network Median" underneath and the verdict label appended (e.g. "Network Median · Met"). This is the whole network's own median on that transition, graded against the same standard as every office.
  • A rollup line: "X Met · Y Near · Z Missed", with "· W Warming Up" appended when any offices are still below the sample floor.

Below that, every office reporting on this transition gets its own line, sorted slowest first so the offices needing attention surface at the top, with warming-up offices always at the bottom of the list regardless of anything else. Each office line shows:

  • A colored dot (green for Met, yellow for Near, Ember Red for Missed, neutral border color for warming up).
  • The office name.
  • If scored: the verdict label (Met, Near, or Missed), the office's own median in days, and the case count behind it (e.g. "12 jobs").
  • If warming up: "Warming Up · N of 5 [cases]" instead, spelling out exactly how close the office is to a real verdict.

Setting standards on Process Standards

  1. 1Open Compliance in the sidebar, then click the Process Standards tile under Standards & Audits.
  2. 2The page opens with a hero panel reading your network's current conformance percentage (or the count of standards you've set, if none have scored yet), a Standards Set count ("of N transitions" registered across every process), a Checks Met count, and a Missed count.
  3. 3Below the hero, every registered milestone transition is listed, grouped by process (Job lifecycle, Supplement turnaround, Recruiting pipeline, Incident follow-through, and any other processes your network tracks). Each row shows the transition name and, if the network already has a median for it, "Network Median Xd · N Office(s) Reporting."
  4. 4To set a standard, type a target number of days into the input next to a transition (in 0.5-day increments) and click Save. To start from what the network is already doing, click Use median first, which fills the input with the network's current median for that transition, then adjust and save.
  5. 5To remove a standard, click Clear next to a row that already has one.

If your network already has live medians on transitions with no standard set yet, an Adopt network medians button appears at the top of the page (admins only). Clicking it bulk-adopts the network's own current median as the standard for every such transition in one action, tagging each as "From Network Median" rather than manually typed. This is the fastest way to get a full standards baseline in place: start from what the network already does, then tighten individual transitions from there as you see fit.

Only HQ admins can set, adjust, or clear standards. Non-admin viewers see the same rows read-only, with each transition showing either "Standard Xd" or "No Standard."

The Process Standards page carries its own framing at the top: 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.

Reading it in practice

A useful way to work the grid: open the Conformance tab, scan the rollup line on each transition for the ones with the most Missed offices, and look at the sorted office list underneath, since the worst-performing office on that transition is always listed first. A transition where most offices are Near, clustered just over the tolerance line, usually means the standard itself may be a touch aggressive for where the network currently operates; a transition where a handful of offices are badly Missed while the rest are comfortably Met is a coaching opportunity for those specific offices, not a standard problem.

Because grading rides entirely on stage medians and never on individual jobs, a Missed verdict is a starting point for a conversation with that office's leadership, not evidence in itself. Use it alongside whatever context you already have, including anything visible in Network Flow's own office breakdown.

Office naming and the privacy boundary

Office names on the Conformance grid follow the same naming rule as the rest of the Network page: if your network is set up as independent, separately owned franchisees, each office appears as a stable anonymized label rather than a name, so that grading and coaching conversations still work without exposing one franchisee's standing to another. If your network is configured as commonly owned, multi-location operations, office names show in full. Either way, HQ only ever sees the stage median and the resulting verdict, never the underlying job list, dollar figures, or customer detail that produced it. Franchisees keep ownership of their operational data; Standards Conformance exists to give HQ a shared, honest bar, not a window into any single office's business.

Empty states

  • No standards defined at all. 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 appear on the Network home at all until at least one standard exists.
  • Standards are set, but the nightly rollup hasn't produced a snapshot yet. The Conformance tab reads: "Standards are set. Office grades appear after the next nightly rollup of stage medians."
  • A specific transition has a standard but no office has reported enough cases yet. That transition's row reads: "Office grades appear once an office clears five in-order [cases] on this stage" (the case noun matches the process, e.g. "jobs," "supplements," "incidents").

Related reading

Was this helpful?