Setting and clearing a stage standard

What this page is

The Process Standards editor is where HQ writes down the pace it expects every office to hit at each stage of a process, in days. A standard is nothing more than a target-days number attached to one milestone transition, for example "Assigned to Estimate submitted" in the job lifecycle, or "Submitted to Responded" in supplement turnaround. Once a target exists, every office's own stage median is graded against it every night, and that grading surfaces elsewhere as Standards Conformance. This article covers the editor itself: the row layout, how to type or adopt a target, how to clear one, and who is allowed to touch it. For how the Met, Near, Missed, and Warming up verdicts actually work, see Standards conformance.

Verinode does not choose the number for you. The editor's own framing, printed at the top of the page, says it plainly: 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.

Where to find it

Open Compliance in the HQ sidebar, then click the Process Standards tile in the Standards & Audits row near the top of the page. That opens this editor at hq.verinode.ai/standards/process. (The page also has a page title of "Process Standards" in your browser tab.)

The hero: your standards at a glance

At the top of the page, above the row list, sits a summary panel under the eyebrow "Operational Standards · Conformance." What it shows depends on where your network is:

• No standards set yet. The headline reads the count of standards (zero) with a "Not Set Yet" pill, and the description underneath reads: "Target days per stage, committed to by the network. Set a standard per transition (or adopt the network's own medians) and every office is measured against the same bar."
• Standards exist, but nothing has scored yet. The pill reads "Warming Up."
• Standards exist and have scored office checks. The headline becomes the network-wide conformance percentage, the share of scored office checks (across every standardized transition) that came back Met. The pill reads "On Pace" (90% or higher), "Watch" (70% to 89%), or "Action Needed" (under 70%). The description underneath reads: "Share of scored office checks meeting the network's stage-time standards. Grades ride on office stage medians; offices under the five-case floor read as warming up, never as a verdict."

Below the headline, three secondary figures:

• Standards Set, the number of transitions with a target defined, with "Of N Transitions" underneath, N being every registered transition across every process your network tracks.
• Checks Met, the count of office checks that came back Met, with "Of N Scored" underneath once anything has scored, or "Awaiting Data" if nothing has yet.
• Missed, the count of office checks that came back Missed, with "Need Attention" underneath if that count is above zero, or "All Clear" if it is zero.

Adopt network medians (admins only)

If your network already has live stage medians on transitions that have no standard set yet, an Adopt network medians button appears next to the page title, visible only to admins. Clicking it bulk-adopts the network's own current median as the target for every such transition in a single action, and tags each one "From Network Median" rather than manually typed. This is the fastest way to get a full baseline in place: start from what the network is already doing, then tighten individual transitions from there. While the action runs the button reads "Adopting…". If it fails, an inline message explains why (for example, if no nightly rollup has produced medians yet: "No stage medians yet. Network medians appear after the nightly rollup runs."). The button disappears once every transition with a live median already has a standard.

The row list

Below the hero, every registered milestone transition across every process your network tracks is listed as one flat row, grouped under a small-caps section heading per process (for example JOB LIFECYCLE, SUPPLEMENT TURNAROUND, RECRUITING PIPELINE, INCIDENT FOLLOW-THROUGH), in the same process order used across Network Flow. There is no pagination or search: every registered transition on the network shows, whether or not it currently has a standard.

Each row shows the same three lines regardless of your role, then a control area on the right that differs for admins and viewers.

Line 1: the transition name, for example "Assigned → Estimate submitted."

Line 2: the network median, one of:

• "Network Median Xd · N Office(s) Reporting", where X is the network's own current median for that transition and N is how many offices have reported enough cases to count toward it (the singular reads "1 Office Reporting," never "1 Offices").
• "No Network Median Yet", when no office has cleared the sample floor on this transition yet.

Line 3 (only when a standard is already scoring): the conformance rollup, in the form "X Met · Y Near · Z Missed," with "· W Warming Up" appended when at least one office is still below the sample floor on that transition. This line is omitted entirely until at least one office check on that transition has scored.

An extra line when the current standard came from the bulk-adopt action: "From Network Median," so you can tell a hand-typed target apart from one that was adopted wholesale.

Day figures throughout the row list are formatted the same way: a value of 10 or more rounds to a whole number ("12d"), and anything under 10 keeps one decimal place ("4.5d," "0.5d").

Setting a standard (admin view)

If you are an HQ admin, each row's right side has a live input, not just a display:

1. 1If the row shows a network median, an optional Use median shortcut sits to the left of the input. Clicking it fills the input with the network's current median for that transition, so you can start from where the network already runs and adjust from there rather than typing a number from scratch.
2. 2Type a target directly into the number field if you'd rather set your own pace. The field accepts increments of half a day (0.5, 1, 1.5, and so on) and shows a ", " placeholder when empty. It is labeled "days" beside it.
3. 3Click Save. The button is disabled until you've entered a valid, positive number that actually differs from what's currently saved for that row, so there is nothing to accidentally resave. While the save is in flight the button reads "Saving…".
4. 4To remove a standard entirely, click Clear, which only appears on rows that currently have one saved. Clearing empties the input and the row reverts to no standard.

Saving or clearing a standard immediately refreshes this page along with the Compliance page and the Network page, so the Process Standards tile and the Standards Conformance scoreboard both reflect the change without a manual reload.

The 0 to 365 day guardrail

Every target you save is checked against a hard range before it's written: it must be greater than 0 and no more than 365 days. A target outside that range is rejected with the message "Target must be between 0 and 365 days", shown inline in red under the row. The upper bound exists because the longest registered transition in the product, Billed to Paid, runs in weeks, not years. A three-digit typo (for example, keying in "3650" instead of "36.50") is almost certainly a mistake, not a real target, and the guardrail catches it before it can silently poison a conformance grade for every office on that transition. The value you type is also rounded to two decimal places on save, so a target like "5.005" simply saves as "5."

Read-only view (non-admin viewers)

If you are not an HQ admin, the row list looks identical, but there is no input, no Use median shortcut, and no Save or Clear control. In place of the control area, each row simply shows its current state as text: "Standard Xd" when a target is set, or "No Standard" when it isn't. Only HQ admins can set, adjust, or adopt in bulk, or clear a standard; the underlying server actions enforce this independently of what the page displays, so a non-admin cannot force a save even by calling the same action directly.

Reading the numbers as an admin, in practice

A sensible way to build out standards on a network that has none yet: click Adopt network medians first to establish a baseline across every transition that already has live data, then come back to individual rows and tighten the ones you want the network to actually improve on, typing a lower target and saving. For a transition with no network median yet (too few offices have cleared the sample floor), you can still type a target by hand; it will simply have nothing to grade against until an office's own stage median clears that floor.

Because every grade downstream of this editor rides on office stage medians and never on individual jobs, changing a standard here changes future grading immediately (after the next nightly rollup) but never rewrites history: past Met, Near, or Missed verdicts already recorded elsewhere are not recalculated retroactively against a new target.

Empty states

• A transition with no network median and no standard shows "No Network Median Yet" on line 2, no line 3, and an empty input (admin view) or "No Standard" (viewer view).
• A brand-new network with zero standards anywhere still shows the full row list, since rows are driven by the registered transitions in the product, not by what's been set. Only the hero (0 standards, "Not Set Yet" pill) and the missing "Adopt network medians" button (until a network median exists somewhere) signal that nothing has been configured yet.

The privacy boundary

Every number on this page, network medians, conformance rollups, and office counts, is an aggregate computed from office stage medians in the nightly rollup. Nothing here reads a single franchisee's job list, invoice, dollar figure, or customer detail. Setting or clearing a standard changes only the target HQ compares those medians against; it never edits, deletes, or has any effect on a franchisee's own operational data. Franchisees keep ownership of the underlying jobs, supplements, and incidents that produce their medians.

Data sources

Related help

• Standards conformance: grading offices against your bar for the full Met, Near, Missed, and Warming up grading system this editor's targets feed, and the read-only scoreboard on the Network page.
• Standards & Audits entry: Process Standards, Forms, SOPs for the navigation tile on Compliance that leads here, and its two sibling surfaces.
• Compliance: brand health across your network for the full page this editor is reached from.
• Network overview: signals, interventions, and the network home for where Standards Conformance also appears, as a tile and a Conformance tab, on the Network page.