Performance: peer-relative dimensions, not a single score

What Performance is, and what it deliberately is not

Verinode does not reduce a team member to a single performance score. There is no letter grade, no 0-100 rating, no ranked list of who is "best." Instead, Performance reads a member against the dimensions that actually ship restoration work, drying time, callback rate, documentation completeness, whatever your detectors watch, and shows you where that member lands versus the peer distribution on each one. A person can be strong on one dimension and developing on another. The signal is the dimension, not a summary number.

This shows up in three places, all reading the same underlying attribution data at different altitudes:

• The Performance tile in the Explore row on the Team page.
• The Performance tab in the Team card slider, which shows per-role distribution bars once enough jobs have been attributed.
• The Performance section inside a member's own detail card, which lists that individual's latest dimension values once jobs have been attributed to them.

Where to find it

Open Team from the sidebar, at /team. The page opens on a hero panel and three rows: Decisions, Explore, and Your Team.

The Explore row is a horizontal strip of tiles: Members, Depth Chart, Performance, Capacity, Benchmarks. Click the Performance tile to open the Team card slider already scoped to its Performance tab. The slider's own tab bar (Findings, Team, Depth Chart, Performance, Capacity, Benchmarks) lets you jump there directly too.

To see one person's dimensions, open any member from the Team tab or the Explore row's member tiles. Their detail card's Performance section sits near the top, above Role And Tenure.

The Performance tile (Explore row)

What it shows. The tile's headline number is your current single-point-of-failure count: the number of active members who are the sole qualified holder of a required certification for at least one service line. If nobody on your team is a sole cert-holder, the tile reads "no single-point-of-failure today." If one or more members are, it reads "member(s) you haven't built depth behind," phrased as something you have not done yet, not as a flaw in the person.

The dot preview. Below the number, a row of dots represents your active member count, with the flagged single-point-of-failure members picked out in a different tone. The whole team is visible at a glance, and the exposure is a small, specific slice of it, not the whole workforce.

What clicking it does. It opens the Team card slider on the Performance tab, described next.

The Performance tab (per-role distribution bars)

Open this from the Explore row's Performance tile, or from the Performance tab in the card slider directly.

The framing line. At the top: "Peer-relative dimensions, where you land versus peer operators at your size, not a single performance score. Dimension distributions populate once you've attributed enough jobs to surface a signal." This is the same rule stated at the tile and the member level: dimensions, never a score.

What the tab shows once it is populated. Per-role distribution bars: one bar per role, per dimension, showing where your team's attributed jobs fall across the peer distribution for that dimension. This is a role-level view, aggregated across everyone in the role, distinct from the member-level dimension list you see inside an individual's detail card.

The threshold to populate. The tab needs every active role to reach a sufficient number of job attributions within the measurement window before it renders bars. Until every active role clears that bar, the tab shows a placeholder panel: "Per-role distribution bars. Performance signals appear as job attributions flow in. Once every active role has enough attributions in the window, this tab renders the peer distribution for each dimension your detectors watch."

Empty state, no team members at all. If there are no member records on the team yet (nobody hired or entered), the entire tab reads: "Performance signals appear as job attributions flow in."

Performance inside a member's detail card

Open a member and look at the Performance section, the first section on their card.

Populated state. Once attribution data exists for that member, you see up to three of their most recent dimension readings (the most current period per metric key, deduplicated so an older reading for the same dimension does not also show). Each row has:

• The dimension name, written out in title case (for example, a metric key like callback_rate reads as "Callback Rate").
• Sample size and period, in small type under the name: "sample N · period ending [date]." The sample size is the count of job attributions the reading is built from; the period-ending date is the end of the measurement window that reading covers.
• The value itself, right-aligned, shown to two decimal places where the metric calls for it.

Above the rows, a short line repeats the framing: "Peer-relative dimensions: where you land versus the cohort on the work that matters. No single score; the dimensions speak for themselves."

Empty state. Before any jobs have been attributed to this member, the section reads: "Performance signals appear here as jobs get attributed to this member. You'll see peer-relative dimension chips, not a single score, the signal is where they stand versus the peer distribution on the dimensions that actually ship restoration work."

Note that the member-level Performance section shows this individual's own dimension values (with sample size and period), while the Performance tab one level up shows the aggregated per-role peer distribution. They answer different questions: "where does this person's latest reading sit" versus "where does the whole role sit against peers."

How Performance connects to posture

Every team record, a member, a cert-gated service-line slot, or a custom role slot, carries a posture pill in its header: Thriving, Steady, Developing, At Risk, or Watching. Performance dimensions are one of several inputs into that pill (alongside certification status, tenure, and depth-chart coverage), but the pill itself is never shown as a numeric score either. It is a label plus a plain-language reason, for example a member new enough that there is not yet enough attribution data reads Watching, with the reason "the first 90 days are for standard-work orientation, performance signals mean more after that." A member trending below peers on a dimension long enough to matter reads At Risk with a specific, coachable next step, never a blanket "underperforming" label pointed at the person.

Why Verinode does this

A single score invites the wrong conversation: it turns a coaching opportunity into a ranking, and it hides which specific part of the job needs attention. Peer-relative dimensions keep the conversation concrete: this person, this dimension, this cohort, this action. It also means the signal only ever appears once there is enough attributed job history behind it, so you are never coaching someone off a guess.

The peer distributions themselves come from the same cohort mechanism used across Verinode: your data contributes anonymized signal into the pool, and once the pool at your size is large enough, you see where you land against it. Verinode never sells that operator data to carriers; it exists only to sharpen the peer picture every contributing operator sees. See How benchmarks work for the mechanics of that exchange.

Related reading

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