The cycle-time hero: how your network compares to the industry

What this panel is

The Operations home opens on a single number: your network's median cycle time, in days, measured against every operator on the platform who is not part of your network. Everything else on the page (the Capacity Pressure row, the Process Maturity row, Shared SOPs, and Bulk Buy) is a way of acting on the same underlying idea, how fast jobs move through your locations and how much room they have to take on more work. This article covers only the top band: the headline cycle-time figure, the percentile pill beside it, the industry-median line underneath, and the three secondary metrics to the right, process maturity, capacity utilization, and fleet items.

Verinode does not read a single location's raw jobs to build this number on the page. It reads your network's own pre-aggregated median, computed by the group's nightly aggregator from each location's own job data, then compares that one figure against an anonymized industry reference built the same way from operators outside your network. HQ's server never opens a franchisee's job file to draw this line; see What HQ sees: the network privacy boundary for the full trust model.

Where to find it

Open Operations from the HQ sidebar. It is the first item in the Operations group, alongside Assets, Vendors, and Materials, or go directly to hq.verinode.ai/operations. The page opens with a sticky, uppercase OPERATIONS title, and the hero sits at the very top, above Capacity Pressure. There is no tab to switch to and no separate hero page, it is always the first thing you see when Operations loads.

The headline: cycle-time group median

What it is. The large number is your network's median cycle time in days, the middle value across every location in your network currently reporting job data, so one unusually slow or unusually fast location cannot drag the figure the way an average would. The small-caps eyebrow above it reads "Cycle Time · Group Median (Days)."

How it renders. The number animates up from zero on load, the same count-up treatment used across every Verinode hero. Unlike the Margin & Cash hero, which shows a muted dash when there is no group figure yet, the cycle-time headline always renders as a number, it reads 0 until your network has a qualifying group median, rather than a blank placeholder. Read a headline of 0 alongside the sentence underneath it, described below, before assuming your network's actual cycle time is zero.

The line underneath. Once a group median exists, the sentence beneath the headline reads:

"Industry median 24d · 68% Process Maturity · 74% Capacity."

Reading it left to right: the industry median in days (the same anonymized comparison the pill uses, described next), then the two secondary percentages restated in one line, Process Maturity and Capacity utilization, so you don't have to look at the tiles on the right to get the gist. If the industry side of the comparison has not cleared Verinode's anonymity floor yet, that segment reads "Industry median, d" rather than a manufactured number, while your own network's process maturity and capacity figures keep rendering normally beside it.

Empty state. Until your network has a group median at all, the sentence reads, verbatim:

"Cycle time appears as members share job data."

No pill renders in this state either, only the headline (still 0) and this one sentence.

The percentile pill

Beside the headline, a small pill only appears once a group median exists, and shows one of two things depending on how much data is behind the comparison:

• "P[N] (lower is better)." Where your network's median cycle time sits within the industry's distribution of cycle times, expressed as a percentile, for example "P62 (lower is better)." Because a shorter cycle time is the better outcome, the parenthetical is there deliberately: a lower percentile number here is the good direction, the opposite convention from a metric like margin, where a higher percentile is better.
• "n=, [rest]." The fallback shown when the industry side of the comparison has not cleared Verinode's anonymity floor yet, for example "n=9/210." The first number is how many of your own locations have a qualifying cycle-time figure; the second is how many industry peers outside your network were found in the eligible comparison pool. Cycle time is an operational metric, so it sits behind Verinode's base anonymity floor rather than the higher bar reserved for financial figures like margin, a P&L number is more identifying than a days-to-complete figure. Below that floor there is no percentile, full stop, not a number built from too few contributors and flagged as uncertain. See Benchmark methodology for the qualitative explanation of how that floor works, and What HQ sees: the network privacy boundary for why the exact contributor count behind the floor is never surfaced as a threshold you could reverse-engineer.

Pill color tracks direction, not magnitude: green (the Expand tone) when your network's median cycle time is at or below the industry median, red (the Analyse tone) when it's slower. When either side of the comparison has no data at all, the pill and headline render in a neutral tone, there's nothing yet to color as ahead or behind.

The industry comparison

The industry-median figure quoted in the subtext line and used to color the pill is a single anonymized number: the median cycle time among operators entirely outside your network, restricted to the world your network belongs to. A real network is always compared against real peer data and a demo network against demo peer data, the two are never mixed, even behind the scenes. It is one number, nothing else about who is behind it, no roster, no list, no way to narrow it down. If the anonymity floor hasn't been cleared for cycle time specifically, this figure reads as a dash rather than a number built from too thin a sample, while your own network's median keeps rendering normally beside the gap.

The three secondary metrics

To the right of the headline (or beneath it on a narrow screen) sit three flat metric tiles, no boxes, just a label, a number, and a short sub-line flowing on the glass.

• Process maturity. Your network's overall process-maturity percentage, the sub-line reads "Above SOP coverage threshold." This is a network-wide read computed by the same nightly aggregator snapshot, distinct from (but related to) the per-location SOP-coverage percentage graded in the Process Maturity row further down the page. It renders in green (the Expand tone) at 70% or above, and in a neutral tone below that, there's no red state for a low process-maturity reading here.
• Capacity utilization. How full your network's active-job capacity is right now, the sub-line reads "Network active jobs vs cap." It renders in yellow (the Maintain tone) above 80%, a nudge that the network as a whole is running tight, and in a neutral tone at or below that. This is the same 80% line used to decide which of your locations appear in the Capacity Pressure row beneath the hero.
• Fleet items. A plain count of equipment registered across your network, the sub-line reads "Equipment registered." This tile always renders in a neutral tone regardless of the count, it's an inventory fact, not a graded metric. It's the same total the Bulk Buy row further down breaks out by equipment class.

Each of the three percentages formats with one decimal place below 10% (for example 7.4%) and as a whole number at 10% and above (for example 72%). Because all three secondary values fall back to 0 rather than a dash when your network's aggregator snapshot has no reading yet, a genuinely empty network shows "0% · 0% · 0" across the row rather than three blank placeholders. Read those zeros together with the headline and the "Cycle time appears as members share job data" sentence, not as a literal claim that your network's process maturity or capacity is actually nil.

How this connects to the rest of the page

The hero is the summary; the four rows below it are the workspace built from the same underlying data:

• Locations above 80% capacity utilization, the same threshold that turns the hero's Capacity utilization tile yellow, populate the Capacity Pressure row, sorted worst first and split into Stretched (above 80%) and Maxed Out (above 95%).
• Every active location's own SOP-coverage percentage populates the Process Maturity row, graded Mature, Partial, or Low, the per-location detail behind the hero's network-wide Process maturity tile.
• Shared SOPs is the network's library of standard operating procedures a location has shared for the rest of the network to adopt, unrelated to the percentage math above, it's a separate, opt-in knowledge-sharing surface.
• Bulk Buy breaks the hero's Fleet items count out by equipment class, flagging classes rented or owned by enough operators across the network to be worth a group purchasing conversation.

Clicking through to a location from Capacity Pressure or Process Maturity opens that location's own record. HQ still never opens that location's underlying job files from there, what you see is the same kind of pre-aggregated per-location figure the hero rolls up to a network level, just scoped to one location instead of the whole network.

1. 1Read the headline and the pill together. A green pill with a low percentile number means your network is genuinely faster than most of the industry it's being measured against, a red pill means the opposite, and lower is always the better direction for this particular metric.
2. 2If the pill reads "n=[X]/[Y]" instead of a percentile, treat the headline as a real internal fact about your network with no industry comparison attached yet, not a sign that something is broken.
3. 3Scan the three secondary tiles. A yellow Capacity utilization tile is your cue to scroll down to the Capacity Pressure row and see exactly which locations are driving it.
4. 4Treat a 0% / 0% / 0 secondary row on a network you know has active locations as a data-freshness signal, not a real reading, and check back once the nightly aggregator has had a chance to run.

Related articles

• Benchmark methodology
• What HQ sees: the network privacy boundary
• The network margin hero: median margin, percentile, and 12-month trend
• Per-office benchmarks: ranking your own locations
• The office leaderboard and composite ranking
• Network benchmarks: how the section works
• Network health