How do you track who is certified across a large team?

Use one view that holds three things together: who is certified at what level, when each certificate expires, and which approval rights depend on it. Feed it from the issuer, not from copies, and let rights follow the certificate automatically. Spreadsheets kept by each manager drift within weeks on a large team. A single source keeps the answer current.

Why large teams lose track

On a team of ten, a manager knows who is certified. On a team of 300 across shifts, sites and contractors, nobody does. People join, move teams, go on leave and leave. Certificates were earned at different times, so expiries are scattered. Some staff hold one level, some another. Contractors arrive with certificates from previous engagements.

The failure is predictable: someone approves agent actions after their certificate has lapsed, because the record of the lapse was in one place and the approval right in another. The fix is to bring them together.

What should the tracking view show?

The last column is easy to forget and most useful. A view that shows 40 certificates expiring next month is a warning. One that shows 35 of them already booked for renewal is a plan.

How do you keep it accurate?

1. Read status from the issuer. Certificates that can be checked at source by number remove the main cause of stale records. A public register of certified professionals helps when people arrive from elsewhere.
2. Link rights to status. When a certificate lapses, the approval rights that depend on it end. A business can adopt this depth by depth.
3. Alert ahead of expiry. Give people and managers enough notice to renew without a gap.
4. Reconcile against the work. Monthly, compare the people who actually approved agent actions with the people certified to. Any mismatch is a finding.
5. Include contractors. They are often where the gaps are.

The step-by-step version is in how to track certificates and renewals across a large team.

Should you track agents in the same view?

Yes, alongside, not mixed in. Agents hold certificates too: each agent is certified for a business on its own cases, and those certificates lapse after 90 days. A lapse, or a run that clears no depth, drops the agent to depth 1 the same day. The question of whether and how an AI agent can be certified is covered separately.

Holding both in one place lets a manager see the full picture: a team whose people are all current but whose agent has just dropped a depth will see a surge in held actions, and needs approvers ready. Watching for drift in a certified agent is part of the same rhythm.

An example from a contact centre

A contact centre with 280 staff across three sites serves four clients. It holds certificate records in one admin view, read from the issuer. Each Monday, team leads see who expires within six weeks and whether renewal is booked.

During a winter peak, 22 people are due to expire in the same fortnight because they certified together the previous winter. The view flags it early; renewals are spread over four weeks. On one client's queue, the view also shows that the refunds agent is due for recertification in the same period. The operations manager plans extra certified approvers for the days around it, in case the run fails and refunds start being held.

The guide to AI literacy and certification explains how tracking fits into a wider literacy programme.

Where the Academy fits

For teams on paid Pryme Intelligence plans, Pryme Intelligence Academy seats include certificates for the people on them, and an admin view shows progress, results, certificates and expiry dates. Certificates are issued through VerifyDoc.ai and can be checked at source, so the view reflects the issuer's record rather than a copy.