Standards Conformance on the Network home

What this tile is

The Standards Conformance tile is the first tile in the Network Flow row on your Network home page, but only once your network has at least one stage-time standard defined. It answers one question at a glance: across everything HQ has set a pace target for, what share of your offices are actually keeping it?

Verinode does not set that pace and does not audit a single job to produce the answer. It reads the stage medians your offices are already producing (the exact same aggregate numbers behind the rest of Network Flow), checks each one against the target days HQ defined, and rolls the result into one percentage and a set of office-level grades underneath. HQ never touches a franchisee's job list, dollar figures, or customer detail to get there, only the median each office is already reporting and how it lines up against a bar leadership set on purpose. Franchisees keep their operational data; HQ sees the aggregate and the grade.

Where to find it

Open Network from the HQ sidebar (hq.verinode.ai/network). The page runs three rows: a hero panel at the top, Take Action below it, then Best Practices To Propagate, then the Network Flow row. The Standards Conformance tile leads that Network Flow row, sitting to the left of the individual stage-transition tiles (Job lifecycle, Supplement turnaround, Recruiting pipeline, Incident follow-through, and any other registered process).

The tile is conditional: if your network has not defined a single stage-time standard yet, it is not rendered at all, the row simply starts with the first Network Flow tile. The moment HQ sets one target days figure anywhere, the tile appears at the front of the row on the next page load.

Clicking the tile opens the Network card slider on its Conformance tab, the ninth tab across the top (Signals, Interventions, Top, Watchlist, Risers & Fallers, Network Flow, Conformance, Activity, Location Directory). You can also swipe to the Conformance tab directly from any other tab in the slider.

Setting the standards themselves happens on a different page entirely: Process Standards, reached from Compliance in the sidebar (hq.verinode.ai/standards/process). That page is the editor where HQ types in a target days figure per transition. This article covers only the read side, the tile and its drill-in, both of which are read-only.

Reading the tile

Once at least one standard exists, the tile shows:

• Label: "Standards Conformance."
• The headline value, a percentage (for example "84%"), or a dash if no office has scored a check yet.
• A ring gauge behind the percentage, colored green (accent) at 90% or above, amber between 70% and 89%, and Ember Red below 70%. The gauge tone also sets the tile's overall accent color.
• A subtitle line underneath: once at least one check has scored, it reads "X Of Y Checks Met" ("X" is the count of office-checks graded Met, "Y" is the total number scored across every standardized transition). Before anything has scored, it instead reads "N Standard(s) · Warming Up" ("Standard" singular if you have exactly one target set, "Standards" plural otherwise).
• A delta line below that: "N Missed" (flagged in the bad tone) if any office-checks graded Missed anywhere in the network; otherwise "N Near The Line" (neutral tone) if any graded Near but none Missed; otherwise "All Checks Met" (good tone) once every scored check across the network clears the bar.

A "check" here means one office's stage median on one standardized transition. If your network has standards on three transitions and five offices reporting on all three, that is up to fifteen possible checks (fewer if some offices are still warming up on a given transition).

What "Met," "Near," and "Missed" mean

Every check is graded by comparing one office's own stage median against the target days HQ set for that transition:

• Met. The office's median is at or under the target.
• Near. The office's median is over the target, but not by more than 20%. This is a tolerance band: a small overshoot that has not yet become a real problem.
• Missed. The office's median is more than 20% over the target.
• Warming up. The office has not yet logged enough in-order cases on that transition for its median to be trustworthy (the same five-case floor used everywhere stage medians appear on Network Flow). A warming-up office carries no verdict at all rather than a guessed one.

The 20% tolerance band is fixed across every transition and every process, it is not something HQ configures per standard.

The Conformance tab, transition by transition

Inside the slider, the Conformance tab lists one card per standardized transition, in the same process order as the rest of Network Flow (Job lifecycle first, then Supplement turnaround, Recruiting pipeline, Incident follow-through, and any other process your network has registered). Each card shows:

• The process label (for example "Job lifecycle") in small caps above the transition name.
• The transition name (for example "Assigned → Started").
• The standard, formatted as days, for example "Standard 5d." If HQ adopted the network's own median as the target rather than typing a figure in by hand, " · From Network Median" is appended.
• The network median on the right, in the verdict's accent color, with "Network Median" underneath. If the network-wide median has scored, the verdict label is appended, for example "Network Median · Met." This is the whole network's own pooled median on that transition, graded against the same standard as every individual office.
• A rollup line underneath: "X Met · Y Near · Z Missed," with " · W Warming Up" appended when any offices on that transition are still under the sample floor.

Below the rollup line, every office reporting on that transition is listed, sorted slowest first so the offices needing attention surface at the top, with warming-up offices always pushed to the bottom of the list regardless of their reporting order. Each office row shows:

• A small colored dot: green for Met, yellow (amber) for Near, Ember Red for Missed, or a neutral border color for warming up.
• The office name (see the naming section below).
• If scored, three figures side by side: the verdict label (Met, Near, or Missed), the office's own median in days, and how many cases sit behind it, for example "12 jobs" (the case noun matches the process: jobs, supplements, applicants, incidents).
• If warming up: "Warming Up · N of 5 [cases]" in place of a grade, spelling out exactly how close the office is to a real verdict rather than hiding the gap.

How to use it

1. 1Glance at the tile's percentage and gauge color first. Green and 90%+ means the network is broadly keeping its own promise; amber or red means it is worth a closer look before your next leadership meeting.
2. 2Read the delta line under the percentage. "N Missed" tells you there is at least one office genuinely out of tolerance somewhere in the network right now, not just drifting.
3. 3Click the tile to open the Conformance tab. Scan each transition's rollup line for the ones with the most Missed offices, that is where a standard is being broken most often, not just at the network-median level.
4. 4Read the sorted office list under a transition that stands out. Because it sorts slowest first, the office most out of tolerance on that specific stage is always at the top, without you needing to hunt for it.

Office naming and the privacy boundary

Office names on the Conformance tab follow the same rule as the rest of Network Flow and every other per-location surface on HQ. If your network is set up as independent, separately owned franchisees, each office appears under a stable anonymized label rather than its real name, the same label consistently, so a pattern is trackable over time 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, the Conformance tab, and the tile that leads to it, only ever carries a stage median and the verdict it produces. No job list, adjuster name, dollar figure, or customer detail crosses this boundary in either direction. A Missed verdict is a starting point for a conversation with that office's leadership, using whatever context you already have, not evidence in itself.

Empty states

• No standards defined anywhere. The Standards Conformance tile does not render on the Network home at all, the Network Flow row starts directly with the first stage-transition tile. Inside the slider, the Conformance tab (still reachable by swipe) 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."
• Standards are set, but the nightly rollup has not 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 cleared the sample floor yet. That transition's card reads: "Office grades appear once an office clears five in-order [cases] on this stage," with the case noun matching the process.

None of these are errors. They mean HQ has defined a standard leadership wants to hold offices to, but the underlying data has not caught up yet, or in the first case, that no standard exists to grade against.

Related

• Network Flow: how work moves through the network, the row this tile leads, and the stage-median tiles that follow it.
• How conformance is graded: met, near, missed, the full grading math, the warming-up floor, and how the conformance percentage rolls up, in more depth than this article covers.
• Process standards and conformance, how HQ sets, adjusts, and clears a stage-time standard on the Process Standards editor.
• Network Health: your network's overview, the home page this tile lives on, and the rest of its rows.