Keep one list, not one per team. Each row is a person and a credential: the certificate number, issue and expiry dates, the status as last checked at source, and the approval rights it supports. Refresh status from the issuer on a fixed cycle, send renewal reminders well before expiry, and remove rights the day a certificate lapses.
Why does a large team need a single list?
Small teams track certificates in someone's head. Large ones track them in spreadsheets kept by each manager, and the spreadsheets disagree. The result is predictable: an approver whose certificate lapsed months ago is still releasing payments, because their manager's sheet said "certified" and nobody asked the issuer.
One list solves three problems at once. It shows who can approve what today. It shows what will lapse and when. And it connects each credential to the rights it supports, so a lapse has a consequence. The guide to AI literacy and certification for people who work with agents covers why credentials for agent work should lapse at all; how to track who is certified across a large team gives the short answer.
Who owns the list?
One owner, usually in operations or the governance team, not learning and development alone. Learning and development knows who completed what; operations knows who approves what. The list joins them, so its owner must answer to both. Each business unit names a contact who confirms role changes and joiners and leavers.
What are the steps?
- Person (list owner): decide which credentials count. Only those that support an approval right or are required for a role. A list of every course ever taken is noise.
- Agent, depth 1: compiles the starting list. From the training admin view and the workspace's approver lists, matched by person.
- Person (list owner): checks every credential at source once. By certificate number or QR code on the issuer's page. Record the date and the result.
- Person (business unit contacts): confirm roles. Each person's role determines which credential they need.
- Agent, depth 1: re-checks status on a fixed cycle. Monthly suits most teams. Changes, such as a revoked certificate, are flagged to the owner the same day.
- Agent, depth 2: drafts renewal reminders. At set points before expiry, sent by the owner or the manager. A renewal reminder email template saves drafting from scratch.
- Person (administrator): removes approval rights on lapse. The list shows the right that depended on the credential, so nothing is missed.
- Person (list owner): reports monthly. Coverage by team, upcoming lapses, overdue renewals, exceptions.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Choose credentials | Nothing | n/a | Deciding what counts |
| Starting list | Joins training records to approver lists | 1 | Resolving mismatches |
| First check at source | Nothing | n/a | Verifying each credential |
| Status refresh | Re-checks and flags changes | 1 | Acting on a change |
| Reminders | Drafts reminders at set points | 2 | Sending and following up |
| Lapse | Flags the dependent rights | 1 | Removing them the same day |
What columns does the list need?
Keep it short enough to maintain:
- Person, team, role, manager
- Credential and certificate number
- Issue date and expiry date
- Status at source, and the date last checked
- Approval rights this credential supports, by capability and depth
- Renewal status: not due, reminder sent, booked, overdue
- Exception, if any, with owner and end date
The "rights supported" column is what turns a training record into a control. Without it, a lapse is an admin note. With it, a lapse removes a right. That link is set out in how to tie approval rights to certificates.
Which controls matter, and what evidence do they leave?
Status comes from the issuer. The evidence is the check date and result on every row. A certificate with a practical part, as explained in why AI agent certificates need a practical part, is worth checking because it says something about real work; a status copied from a PDF is not a check.
Joiners and leavers are reconciled. The evidence is a monthly reconciliation between the list and the HR system of record.
Lapses lead to removals. The evidence is a dated change to the approver list for each lapse.
What should be measured?
- Rows checked at source within the cycle.
- Approvals in the period made by people with a current credential.
- Renewals completed before expiry.
- Days from lapse to removal of rights.
- Open exceptions and their age.
Where does it go wrong?
Cohort expiry. A team trained in one month lapses in one month. Spread renewals across the year where you can.
Role changes are missed. Someone promoted to approve depth 4 still holds the credential for depth 2. The business unit contact must flag role changes, not just joiners.
The list becomes the source of truth. It is a copy. The issuer's page, or a public register of certificates, is the truth. Re-check rather than trust the list.
Where the Academy fits
For teams, the Academy's admin view shows each person's progress, results, certificates and expiry dates, which is the starting data for the list. Certificates are issued through VerifyDoc.ai and checked at source by number or QR code, with lapsed or revoked status shown on the same page. Certified Pryme Operator and Builder last 12 months and Architect 24, so renewal dates are predictable.
Questions people ask
How far ahead should renewal reminders start?
Far enough to complete renewal, including any update module and quiz, before expiry. Two reminders, one early and one close to the date, work for most teams.
Should contractors be on the same list?
Yes. If a contractor approves agent actions, their credential supports a right and belongs on the list. Mark them as contractors so reconciliation uses the contract record rather than HR.
What if the list and the issuer disagree?
The issuer wins. Update the list, then find out why it was wrong; the cause is usually a missed revocation or a mistyped number.