How to handle a reviewer whose AI agent certificate has lapsed

Pause their approval rights on the expiry date, route their held work to a colleague with a current certificate, and book the renewal straight away. The reviewer keeps reading and preparing cases. Nothing they approved while current is reopened. The aim is a gap of days, recorded plainly, with no approval made by someone the business no longer treats as certified.

What has actually lapsed, and who owns the response?

Two certificates are in play around any agent. The agent's certificate lapses after 90 days unless it is renewed through certification on the customer's own cases. The reviewer's certificate is about the person: evidence that they can judge the agent's decisions. Professional certificates for people typically run for 12 or 24 months. This playbook is about the person's certificate, and what a lapsed AI agent certificate means for a reviewer covers the distinction in more depth.

The team lead owns the response. They control the review rota and know which queues depend on whom. Compliance or risk owns the policy that ties approval rights to a current certificate, if the business has adopted that practice. The reviewer owns their renewal.

The steps

1. Agent, depth 1: flag the expiry ahead of time. A reporting agent reads certificate expiry dates and lists every reviewer due to lapse in the next 60 days, by queue.
2. Person: confirm the status at source. The team lead checks the certificate with its issuer by number or QR code. A downloaded file is not proof of anything, as why a PDF certificate proves nothing explains, and how an employer can check an AI agent certificate covers the check itself.
3. Person: pause approval rights on the expiry date. Remove the reviewer from the eligible approvers for each depth their certificate covered. Do it in the workspace, so an attempted approval is refused rather than caught later.
4. Agent, depth 2: re-route held work. Held actions waiting for the lapsed reviewer are reassigned to named cover. The agent drafts the handover note listing each item, its deciding bound and its age.
5. Person: cover approves. A colleague with a current certificate clears the queue. The lapsed reviewer can add notes and gather documents for them.
6. Person: renew. The reviewer completes the renewal requirement. Book it before the expiry date where possible.
7. Person: restore rights and record the gap. Once the renewed certificate is checked at source, restore approval rights and note the start and end of the gap.

How do you keep the queue moving?

Cover is the hard part. A lapse rarely causes harm by itself. A queue of held payments or customer refunds with no eligible approver does.

Plan cover by depth. Depth 2 drafts can usually go to a wider group, since a person sends them. Depth 3 exceptions and depth 4 actions, such as moving money, need a certified approver. If a capability has only one certified approver, the lapse turns into an outage. Two is a minimum for any depth 4 capability.

Tell the requesters. If a held refund will wait an extra day, the customer-facing team should know why before the customer asks.

Which controls matter, and what evidence do they leave?

• Automatic early warning. Evidence: the dated reminder list and the booking that followed.
• Rights enforced by the workspace, not by memory. Evidence: a refused approval attempt in the record, if one occurs, and the change to the approver list.
• Status checked at source. Evidence: the check result, dated, for both lapse and renewal.
• Named cover. Evidence: the handover note and the approvals by the covering reviewer in the record.
• A written procedure. Evidence: the procedure itself, versioned. The lapsed certificate procedure template is a ready starting point.

Where reviewers handle customer financial data, privacy duties continue through the gap, and a lapsed reviewer still reading cases must stay within their data access. In the US, GLBA and training staff who handle customer data with AI agents covers the training angle.

What should you measure?

Track the days each lapse lasted, the number of held items re-routed and their extra waiting time, and the number of approvals attempted by someone without a current certificate. The last should be zero once the workspace enforces it.

Over a year, also track how many lapses were avoidable. If most were, the reminder is too late or renewals are being booked too close to the date.

Where does it usually go wrong?

The first failure is noticing late. A lapse found during an audit means weeks of approvals made by someone the policy says should not have made them. Each one then needs review.

The second is quietly carrying on. A trusted senior reviewer whose certificate lapsed on Sunday approves on Monday because the queue is long. The decision may be right, but the record now shows a breach of the business's own rule.

The third is treating a lapse like a revocation. A lapse is administrative. A revocation follows evidence that someone should not approve. Mixing them up makes people hide expiry dates.

Where the Academy fits

A Certified Pryme Operator certificate is valid for 12 months, and renewal is an update module and a short quiz, so a lapsed reviewer can usually be back within days. The certificate is issued through VerifyDoc.ai, and a lapsed or revoked certificate shows as such on the same page anyone uses to check it. For teams, the admin view lists expiry dates in one place. The broader topic is in the guide to AI literacy and certification for people who work with agents.