Adopt network medians: start from where you run today

What this action does

Adopt network medians is a single bulk button on the Process Standards editor. Click it once and Verinode fills in a starting standard, for every milestone transition that doesn't have one yet, using the network's own current pace on that transition as the target. Nothing is invented and nothing is borrowed from outside your network: the number it writes down is the same stage median your own offices are already producing, pulled straight from the nightly aggregate rollup.

This is the doctrine behind the whole Process Standards page: don't ask a network to hit a number nobody has validated. Start every standard from where the network actually runs today, then tighten individual transitions from there as you see fit. The button exists so getting a full baseline in place is one click instead of typing in a dozen numbers by hand.

Every standard this action creates is tagged source: network_median in the database, as opposed to source: manual for a target an admin typed in themselves (or copied over by hand). That tag is what drives the "From Network Median" caption you'll see under a row afterward, and it's the detail this article is grounded in.

Where to find it

Open Compliance in the HQ sidebar, then click the Process Standards tile under Standards & Audits. That opens the Process Standards editor at hq.verinode.ai/standards/process.

The button sits in the page header, next to the Process Standards title, and only for HQ admins. If it's visible, its label reads Adopt network medians, styled as a solid copper button. While the action is running it reads Adopting…, and it disables itself for the duration so a second click can't fire mid-save.

When the button appears

The button is admin-only, and even for an admin it only shows up when there's actually something to adopt. Verinode checks every row on the editor and shows the button if at least one registered transition satisfies both of these at once:

• It has a live network median (the whole network, pooled, has produced enough cases on that transition for a trustworthy figure), and
• It doesn't have a standard set yet, whether manual or previously adopted.

If every transition with a live median already has a standard, or if no transition has a live median yet, the button doesn't render at all. There's no disabled, grayed-out version of it to signal "nothing to do here"; it's simply absent. Non-admin viewers never see it, regardless of what's adoptable, since only admins can write standards.

Because the check re-runs on every page load, the button reappears on its own whenever a new transition's median clears the sample floor for the first time, even if you've already adopted everything else once. You don't need to check back manually; if it's showing, there's something new worth a look.

What happens when you click it

1. 1Verinode confirms you're a group admin. Anyone else attempting the action (only reachable by tampering with the request, since the button itself is hidden from non-admins) gets "Only group admins can set standards."
2. 2It looks up the network's most recent aggregate snapshot date. If your network has never produced one, the action fails outright with "No stage medians yet. Network medians appear after the nightly rollup runs." In practice you won't hit this from the button itself, since the button only shows once a median exists somewhere, but it's the safety check behind the scenes.
3. 3It pulls every network-level row (the whole-network stage median, not any one office's) from that latest snapshot, alongside every standard your network has already set.
4. 4For each network-level row, it adopts the median as a new standard only if all of the following hold: the median is a real, positive number; the transition is one of the network's registered milestone transitions (the same fixed lifecycle stages used everywhere else on the page, not an arbitrary pair); and no standard already exists for that exact transition. Anything that already has a standard, manual or adopted, is left untouched.
5. 5Each qualifying median is rounded to two decimal places and written as a new standard row with source: network_median.
6. 6If anything qualified, the new standards are inserted, the Process Standards page, the Compliance page, and the Network page are refreshed so their conformance numbers reflect the new baseline immediately, and the page reloads. If nothing qualified (the button was showing based on data that changed a moment earlier), the action still reports success, it just adopts zero rows.

The action doesn't show a "3 standards adopted" confirmation banner. Success is quiet: the page simply refreshes, the rows that were missing a standard now show one, and (because the button's own visibility check re-runs) the button disappears once nothing is left to adopt. If something goes wrong, for example a network admin permission issue, the error message appears in small red text right next to the button, and the button becomes clickable again.

Reading the result on each row

Once a transition has an adopted standard, its row in the editor picks up a small caption underneath the transition name and its network-median line: "From Network Median." This is the only place the network_median tag surfaces as plain text on the page, and it's how you tell an adopted standard apart from one an admin typed in by hand.

For comparison, viewers who aren't admins see the same rows read-only. A row with an adopted standard shows "Standard Xd" exactly like a manually-set one, no different formatting, since from a non-admin's perspective the number is what matters, not how it got there.

How the numbers are formatted

Days on every row round the same way throughout the page: a value of 10 or more rounds to the nearest whole day (for example, "12d"); a value under 10 keeps one decimal place (for example, "4.5d"). The medianMeta line above a row's standard reads "Network Median Xd · N Office(s) Reporting", where the office count is how many offices cleared the sample floor on that specific transition, not your network's total office count. A transition where the pooled network hasn't produced enough cases yet reads "No Network Median Yet" instead, and rows in that state are never eligible for bulk adoption, only for a manually typed target.

Empty states

• The button never appears. Either no transition anywhere has a live network median yet (wait for the nightly rollup to build up a pooled figure across offices), or every transition that does have one already carries a standard. Neither is an error; the page simply has nothing left for the bulk action to do.
• You click it and the network has literally no aggregate snapshot on file. You'll see "No stage medians yet. Network medians appear after the nightly rollup runs." This is a defensive check more than a state you'll actually encounter from the button, since the button is hidden until a median exists.
• You click it and it adopts zero rows. This happens only if the set of qualifying transitions emptied out between the page loading and you clicking (for example, another admin adopted or manually set the same transitions moments earlier). The action still reports success; the page simply shows no new rows after refresh.

Related reading

• Standards & Audits entry: Process Standards, Forms, SOPs for how the Process Standards tile fits into the Compliance page, and its "Not set" / count / percentage states.
• Standards conformance: grading offices against your bar for the full Met / Near / Missed / Warming up grading system that adopted (and manually set) standards feed into, on both the editor and the Network page's Conformance tab.
• Network overview: signals, interventions, and the network home for where the network-wide conformance percentage and Standards Conformance tile live day to day.
• Programs and compliance for the rest of what sits under Compliance alongside Process Standards.
• HQ overview for how standards and conformance fit into the rest of the HQ platform.

Data sources