Detail, Capacity: pieces, classes, purchase value, age vs peers

What the Capacity section shows

Capacity is the first of three sections inside a location's Equipment detail overlay, the scoped drill-in you reach by clicking any location tile in the Equipment page's per-location rows. Where the overlay's other two sections (Utilization & age mix, and Maintenance & calibration watch) describe how a location's fleet is deployed and serviced, Capacity answers a narrower question: how big is this location's equipment investment, and how does that size stack up against its peers.

Four metric tiles sit side by side: Pieces of equipment, Distinct equipment classes, Total purchase value, and Avg age. Each one shows the location's own number, the peer median at whatever scope you have selected, and a plain delta line reading whether that number is ahead of, behind, or on par with peers, colored to reflect whether that particular direction is good news or a gap.

Verinode does not decide what a "healthy" equipment capacity looks like for your network. It reads the location's own equipment records and its peers' records, computes the medians and percentiles, and lays them side by side. Leadership reads the comparison and decides what, if anything, warrants a conversation.

Where to find it

Open Assets from the HQ sidebar, then the Equipment pill (hq.verinode.ai/equipment). Click any location tile in the Maintenance & Calibration Risk, Refresh Cycle, or Equipment by Franchisee rows to open that location's detail overlay. Capacity is the first section inside the overlay, directly beneath the header and the scope switcher, above Utilization & age mix and Maintenance & calibration watch.

The four tiles

Pieces of equipment

The location's total count of registered equipment, active and otherwise, formatted as a plain integer (for example, "38"). More equipment on file reads as more capacity: a location running a larger inventory can generally take on more simultaneous jobs without waiting on a piece of gear to free up. The peer comparison and delta both treat a higher count as the favorable direction.

Distinct equipment classes

The count of different equipment classes the location has on file (dehumidifiers, air movers, truck mounts, contents-drying units, and so on), formatted the same way as a plain integer. This is a proxy for loss-type coverage rather than raw size: a location running four pieces across only two classes can service fewer job types than one running the same four pieces spread across four classes. A higher count is the favorable direction here as well.

Total purchase value

The sum of the location's recorded equipment purchase prices, rounded and abbreviated for readability: under $1,000 shows as a plain dollar figure, from $1,000 up shows as a rounded "$Xk" figure, and from $1,000,000 up shows as "$X.XM." When no purchase price has been recorded for any of the location's equipment, the tile reads ", " instead of a dollar figure.

Purchase value is treated as an investment-base signal, not a cost-control signal: a higher total reads as the favorable direction, on the reasoning that a bigger recorded capital base generally means bigger job-taking capacity, not that the location is overspending. Read a location sitting well above peers on this tile as carrying more capital invested in equipment, not as a red flag on its own.

Avg age

The location's average equipment age in years, formatted to one decimal place with a "y" suffix (for example, "3.4y"). When no equipment has an age on file, the tile reads ",." Unlike the other three Capacity tiles, a lower number here is the favorable direction: newer equipment on average means less near-term refresh pressure and, generally, fewer breakdowns mid-job.

How the peer comparison works

Under each tile's own value sits a Median line, for example "Median 32," "Median $180k," or "Median 2.6y." This is the median value across the location's peers at whichever scope you currently have selected (Group, Regional, or National). It appears only once the peer cohort at that scope is large enough to publish; otherwise the tile explains why not (see "When the peer line doesn't show a number," below).

Where a percentile can be computed, the median line adds a compact percentile marker, for example "Median 32 · p64." That figure means 64% of the location's peers at the selected scope have a lower value on this metric than this location does. It is not a ranking position or a percent-of-quota figure, it is strictly "share of peers below you" on that one metric.

Beneath the median line, a colored delta line states the comparison in plain terms: "+18% vs median," "-12% vs median," or "On par with peers" when the location's value sits close enough to the median that a percent figure would be noise rather than signal. The delta's color reflects whether that direction is favorable for that specific metric, not simply whether the number is higher or lower:

• Green when the location's value sits meaningfully ahead of median in the favorable direction (more pieces, more classes, more purchase value, or less average age than peers).
• Yellow when it sits meaningfully behind in the unfavorable direction, by a moderate margin.
• Red when it sits behind by a wide margin, the same red used for "needs a look" signals elsewhere in HQ.
• Neutral (no color, "On par with peers") when the location's value and the peer median are close enough that the gap isn't worth flagging either way.

Because the delta's color logic already flips for direction, you never have to remember that "more" is good for one tile and bad for another. Green always means "this location's Capacity posture on this metric compares favorably to peers"; red always means the opposite.

When the peer line doesn't show a number

Two different reasons can leave a Capacity tile without a median and delta:

• Cohort too small. If the active peer cohort at the current scope has too few members to publish a comparison without risking identifying a specific peer, the tile reads "Cohort too small" instead of a median. This is Verinode's anonymity floor at work, the same protection used across every peer benchmark on the platform: a comparison only publishes once enough peers sit behind it that no single peer's number can be reverse-engineered from the aggregate.
• Pending benchmark seed. At Regional or National scope, if the cross-network equipment benchmark for that metric hasn't seeded data yet, the tile reads "Pending benchmark seed" instead of a median. This is a data-maturity gap, not a privacy gate, and it currently applies to Regional and National scope on real (non-demo) networks for every Capacity metric, and to every scope other than Group for Total purchase value specifically.

Program targets

If your network has an active program that declares a network-wide target for one of these metrics, its tile carries an extra tag beneath the delta line: a green "✓ Meets target" or a red "✗ Below target", with the program's target value in parentheses and the program's name available on hover. This is a separate signal from the peer comparison above it: peer comparison tells you how this location stacks up against other locations, the target tag tells you whether it clears a bar your network's leadership set on purpose.

As of today, network programs can declare a target against Pieces of equipment, Distinct equipment classes, and Avg age. Total purchase value does not currently have a program type that can set a target against it, so its tile never carries a target tag, regardless of how the location compares to peers.

The scope switcher

Three pills above the Capacity section let you choose the peer pool every tile compares against:

• Group, the rest of your own network. This shows the peer count in parentheses once the cohort is large enough, for example "Group (14)." When your network doesn't yet have enough active peers for a within-network comparison, the pill disables with the explanation "Need 3+ active peers in the network for within-network comparisons."
• Regional, cross-network peers in the same state. Disables with "Need 3+ peers in the same state. Smaller state cohorts hidden by K-anonymity floor." when the state cohort isn't large enough, and additionally reads as pending on real networks until the cross-network equipment benchmark seeds (see the callout above).
• National, cross-network peers with no state filter. Disables with "Cohort too small for cross-network comparison." under the same conditions as Regional.

Switching scope re-renders every tile in Capacity (and in Utilization & age mix) against the newly selected peer pool in one action, you don't have to re-select scope per tile.

Below the four Capacity tiles, a scope-context footer states your current comparison in plain terms:

• Under Group scope with enough peers: "Within-network comparison · [confidence label] · n=[cohort size]." The confidence label (High confidence, Directional, or Low confidence) reflects how much weight to put on the comparison, wider peer pools earn a higher confidence label.
• Under Group scope without enough peers: "Peer cohort too small, need 3+ active franchisees in the network."
• Under Regional or National scope: "Regional industry benchmarks pending, equipment metrics will seed via Verinode's cross-network intelligence layer in a future update" (or the National equivalent).

This footer's cohort size reflects the Pieces of equipment peer pool specifically. Total purchase value's own peer pool can be smaller than that number if some peers haven't recorded a purchase price for their equipment, since a peer with no purchase value on file simply doesn't contribute to that one tile's median.

Privacy: what this section does and doesn't show you

Capacity is built entirely from the nightly network equipment rollup HQ is permitted to read, the same aggregate boundary that governs every HQ surface. It never opens a location's private equipment log, purchase invoices, or individual asset records, and the peers behind every median and percentile are never named or individually visible, only the pooled statistic is. Whether the location's own name appears at the top of the overlay, or an anonymized "Franchisee #XXXX" label instead, depends on your network's entity model, covered in Equipment: what HQ sees across the network.

How to use this section

1. 1Start at Group scope so you're reading the tightest, most-populated comparison your network can currently support.
2. 2Scan all four tiles for red deltas first, those are the largest unfavorable gaps against peers, and check whether a program target tag reinforces or contradicts the gap.
3. 3Read Total purchase value alongside Pieces of equipment and Distinct equipment classes together, rather than any one in isolation. A location with a high purchase value but a low class count may be carrying a concentrated, expensive inventory rather than a broad one, worth a different conversation than a straightforward "under-invested" read.
4. 4Check Avg age last. A location that looks strong on count and value but old on average age is a refresh-cycle candidate even though its Capacity tiles otherwise look healthy.
5. 5If Regional or National scope is what you actually want, note the footer's pending-benchmark message rather than reading a blank tile as "no equipment," it means the cross-network comparison hasn't seeded yet, not that the location has nothing on file.

Related articles

• Equipment: what HQ sees across the network: the full Equipment page, including the Maintenance & Calibration Risk, Refresh Cycle, and Equipment by Franchisee rows that open this overlay.
• Maintenance & Calibration Risk row: the row most likely to lead you into a location's overlay in the first place.
• The 'vs national' deltas on hero tiles: why real networks see no Regional or National comparison yet, and what changes once the benchmark seeds.
• What HQ sees: the network privacy boundary: the aggregate-only boundary this section, and every HQ surface, operates inside.
• HQ overview: how the sidebar sections fit together.