Team Depth and single-point-of-failure warnings

What Team Depth shows

A credential on a wall plaque does not tell you what happens the day the person who holds it quits, gets sick, or takes another job. Team Depth is the tab where Verinode answers that question directly: for every certification your crew holds, how many active team members currently carry it, and does the answer to that come down to exactly one person. That second condition is a single point of failure, SPoF for short, and it is the whole reason this tab exists as its own view instead of being folded into the general certifications list.

Verinode does not cross-train anyone or book a renewal class for you. It reads the team certifications you have on file, counts how many active team members hold each one, and flags the ones sitting on a bench of one. You decide whether to schedule a second holder, accept the risk for now, or let a renewal lapse on a cert nobody is using.

Where to find it

Open Certifications from the sidebar at iq.verinode.ai/certifications. Across the top of the card slider that opens from the page is a row of tabs: Findings, All Certifications, Team Depth, Benchmarks. Team Depth carries a Deere Green accent, the platform's tone for the operational-capacity views.

You can land on it two ways:

• Click the Team Depth tab directly in that row.
• From the Certifications home screen, click the Training Compliance tile in the Explore row. It opens the same card slider and jumps straight to the Team Depth tab, since training compliance and bench depth are read from the same team-cert records.

Reading the matrix

The tab is a single table, one row per certification slug your team holds. Three columns:

• Cert. The certification slug that identifies the credential. This is the one place on the Certifications page where the slug prints in its stored form rather than the humanized name Verinode uses everywhere else on the page (see the callout below).
• Holders. How many active team members currently hold that certification. When the count is one or zero, the number is shown in Ember Red with (SPoF) appended beside it, short for single point of failure.
• Members. The names of the active team members who hold it, comma-separated. If a holder isn't on your active roster (a certification row still marked active or expiring for someone who has since gone inactive), that slot in the list shows a dash instead of dropping silently, so the count and the name list can look slightly out of step. That mismatch is itself a signal worth checking, since it usually means a departed team member's cert record needs cleanup.

Rows are sorted alphabetically by cert slug, not by risk. If you are scanning for exposure, read the Holders column top to bottom rather than assuming the riskiest row is first.

What counts as a holder

Only team certifications feed this matrix, the credentials held by people on your crew. Firm-level certifications (held by the business itself) and subcontractor certifications (held by the subs you hire) do not appear here; they carry different risk profiles and are covered in their own rows and tabs. See Team, firm, and subcontractor certifications for how the three tables split.

A team member counts as a current holder of a slug when their record on that cert reads Active, Expiring Soon, or has no status set at all. A cert that has already lapsed to Expired, or one still sitting as Pending, does not count toward the Holders number, even if the same person holds an in-date cert on a different credential. In practice this means a cert with a Holders count of zero usually means every record for that slug on your team has either expired or was never activated, not that nobody has ever taken the class.

The tab itself only renders once you have both team certifications on file and at least one active team member. A cert stack with no active roster (everyone marked inactive) will not populate the matrix even if the certification records themselves are still there, which is a deliberate choice: bench depth is only meaningful against the people currently available to work.

Why the SPoF flag matters more than the count

A Holders count of one is not automatically an emergency. Plenty of small operators run a lean crew where a handful of credentials will always sit with a single person, and Verinode is not telling you to over-hire. The flag is there so you know which credentials are load-bearing for a single relationship, so the decision to accept that risk is one you're making on purpose rather than one you discover the week that person is out.

Whether a thin row actually becomes a Take Action item elsewhere on the Certifications page depends on more than the raw headcount. Verinode only raises a dedicated single-point-of-failure finding when the cert is also gating one of your active service lines, meaning losing the holder would stop you from bidding or running that line of work, not just leave the credential itself unrenewed. A cert with one holder that isn't tied to an active service line will still show (SPoF) here in the matrix, since the matrix is a straight headcount, but it will not necessarily surface as a decision worth working in Take Action. That finding, when it does fire, carries no invented dollar figure: Verinode names the real consequence (which service line or carrier program stops) rather than attaching a made-up cost, and recommends scheduling a second team member into the next renewal class to build the backup bench.

The same logic runs on each credential's own detail page. Open any team certification from the All Certifications tab and its Team Depth section states the same fact in plain language: "Single point of failure, if this cert lapses, the qualification has no coverage on the active crew" when the holder count is one, or "Deep bench. Rotation won't break coverage" once three or more people hold it. That per-credential framing and this matrix are reading the same underlying holder count from two different altitudes, the matrix for a portfolio-wide scan, the detail page for the one credential you're already looking at.

What to do with a thin row

• One holder, gating an active service line. This is the row worth acting on first. Schedule a second team member into the next available renewal class or CEC session for that credential. See Take Action: certification decisions and activation for how that surfaces as a decision you can act on directly.
• One holder, no active service line depends on it. Lower priority. Worth a note if you're planning to expand into that service line later, but not something to interrupt other work for today.
• Zero holders on a slug you expect to have covered. Check whether every record for that slug has expired or gone unactivated; either renew the lapsed cert or confirm the credential no longer matters to your service mix.
• A count that doesn't match your headcount. If Holders reads higher than the names listed in Members, or a dash shows up where you expect a name, a team member who left the roster likely still has an active-status cert record. Clean up that record so the matrix reflects who is actually on the crew today.

Related reading

• Reading the certifications home screen
• Take Action: certification decisions and activation
• Team, firm, and subcontractor certifications
• How benchmarks work