Team benchmarks: cert currency, tenure, and utilization vs peers

What Team Benchmarks shows

Every operator has a gut feeling about their crew: certifications are probably fine, people probably stay a while, the schedule is probably full enough. Team Benchmarks replaces the gut feeling with three numbers read against your peers: how current your team's certifications are, how long people typically stay, and how full your capacity is running. Verinode reads this from the roster, certifications, and job history you already have in the platform, lines it up against restoration operators at your size and against published industry research, and shows you where you stand. Verinode does not tell you who to hire, fire, or retrain: it surfaces the comparison and the gaps behind it, you decide what to do with it.

This is the same peer-benchmarking pattern used everywhere else on the platform, see how benchmarks work and reading a benchmark for the general mechanics: peer medians (P50), a stronger tier (P75), and a research fallback when the peer group hasn't formed yet.

Where to find it

Open Team from the sidebar, at /team. Team benchmarks show up in two places:

• The Benchmarks tile, in the Explore row on the Team home page. It shows your cert currency percentage with a small marker chart and, once your contributions have unlocked a peer comparison, a peer-delta line ("+8 vs Peer" or "-4 vs Industry" depending on whether a peer median or the research figure is the reference).
• The Benchmarks tab, one of six tabs across the top of the Team card slider: Findings, Team, Depth Chart, Performance, Capacity, Benchmarks. Clicking the Benchmarks tile opens straight to this tab. The Benchmarks tab is where all three metrics live together with their full peer and research comparison.

A Wages tile sits next to Benchmarks in the same Explore row. It compares your median hourly wage in the supervisor (or, if you have no supervisors on file, entry-level) bracket against the published market wage bands for your role and clicking it opens the same Benchmarks view. Wage-band comparison is its own topic and isn't detailed further here.

The three metrics

Each metric appears as its own row on the Benchmarks tab. Every row has the same shape: the metric name and your own number in the top corner, then three columns underneath: Peer P50, Peer P75, and Research.

Cert currency

What it is. The share of certifications on file across your team that are currently active, out of every certification anyone has ever held (active, expiring soon, or expired). A certification counts as current if it isn't expired as of today.

What you see. Formatted as a whole-number percentage, for example "82%". If you have no certifications logged for anyone on the team, this and the "You" figure both read as a dash.

Tenure (median months)

What it is. The median tenure, in months, across active team members who have a hire date on file. Median, not average, so one very long-tenured or very new hire doesn't skew the number.

What you see. A number with one decimal place and an "mo" suffix, for example "14.3mo". If no active member has a hire date recorded, this reads as a dash, both for you and (until enough peers report it) for the peer columns.

Capacity utilization

What it is. How full your team's schedule is running, relative to headcount, benchmarked against peer operators and industry research.

What you see. Formatted as a whole-number percentage, same as cert currency. As shipped today, the "You" figure for this specific metric reads as a dash on the Benchmarks tab: the peer and research columns are populated, but your own capacity number isn't wired into this view yet. Your own utilization picture (weather-driven demand, seasonal peaks and troughs, and the hire/fire signal) lives on the Capacity tab next to Benchmarks, described in a separate article.

Reading the three columns

• Peer P50. The median value among peer operators in your cohort, that is, the typical operator at your size and profile. When the peer comparison is unlocked, a small line under this column shows the cohort backing the number, so you know it's a real peer group, not a single outlier account.
• Peer P75. A stronger tier than the median, roughly what the better-performing quarter of your peer cohort is doing. Useful once you've cleared the median and want the next bar to aim for.
• Research. The published industry figure for this metric, with its source named underneath (for example, an industry survey or association benchmark report). This column shows regardless of whether your peer cohort has formed, because it draws on external research rather than contributed operator data.

A line underneath the three cards makes the rule explicit: you get a peer comparison once enough operators at your size are contributing team data; until then, or for any metric where the peer group hasn't formed, you see the research benchmark instead.

The data dividend: unlocking the peer columns

Peer comparison on Team Benchmarks isn't switched on by a plan or a toggle, it's earned by contribution. Team benchmarks need enough restoration operators at your size contributing their own roster data before a peer median means anything, both statistically and for privacy: Verinode will never show you a number that could be reverse-engineered to a single other operator, and it never sells your team data, or anyone else's, to carriers.

Before the peer group has formed, the top of the Benchmarks tab shows a callout titled "Data dividend", with this copy: "Your contributions unlock the peer picture. Team cohorts need more operators contributing roster data at your size before peer medians land. Until then you see the research benchmarks; peer bars appear when the cohort is large enough. Verinode never sells raw operator data to carriers." While this callout is showing, the Peer P50 and Peer P75 columns for every metric read as dashes, only the Research column has a value.

Once the cohort is large enough, the callout disappears, the Peer P50 and Peer P75 columns fill in with real numbers, and the cohort count appears under the Peer P50 figure so you can see the comparison is grounded in a genuine peer group. Every operator who keeps their roster, certifications, and hire dates current in Verinode is what grows that cohort for everyone, including themselves.

Empty states

• No certifications logged for anyone. Cert currency and its "You" figure both read as a dash. Peer and research columns for cert currency still populate normally, since those don't depend on your own data.
• No active member has a hire date. Tenure (median months) reads as a dash for "You." Log hire dates on the Team tab's member list to populate it.
• Cohort not yet formed for any of the three metrics. The Data dividend callout shows at the top of the tab, and every Peer P50 / Peer P75 cell reads as a dash while the Research column still shows a value with its source.
• No wage data on file (the neighboring Wages tile, not a Benchmarks-tab row). The tile itself shows a dash and reads "Add wage data to compare to market wage brackets."

Best-practice example

Say your Team home page shows the Benchmarks tile reading "68%" with a small red-toned marker (below the 90% target line) and a peer-delta line reading "-12 vs Peer." Click through to the Benchmarks tab. The Cert currency row confirms: You 68%, Peer P50 80%, Peer P75 91%, Research 84% (SOTI). You're behind both peers and the published research, not just a soft target. The Tenure row shows You 9.2mo against a Peer P50 of 15mo, a second data point suggesting your bench turns over faster than peers at your size, which is worth cross-checking against the Performance tab and the Depth Chart's bench-thin flags before you decide anything. Because both numbers point the same direction, the fix isn't "renew some certifications," it's a broader look at onboarding and retention. Verinode surfaced the gap and the comparison; what you do about it, retraining push, comp review, hiring plan, is yours to call.

Related reading

• How benchmarks work
• Reading a benchmark
• Benchmarks overview
• The decision workspace

Data sources