A certificate should say what someone can do today

A certificate is only useful if it answers one question: can this person be trusted with this work now? Most answer a different one: did they pass something once? For people who approve AI agents' work, the gap matters, because agents, depth and product all change. A good certificate states scope, carries an expiry and shows live status at source.

What is wrong with certificates that only record the past?

The traditional certificate is a record of an event. On a certain date, a person sat an assessment and passed. The paper says so, and it says so forever.

That is fine for some things. A degree records that you completed a programme of study, and nobody expects it to say whether you remember organic chemistry. But when a certificate is used as a gate to doing work, such as approving payments or signing off claims an agent prepared, an event in the past is the wrong evidence. The employer does not need to know that someone was competent once. They need to know whether that person is competent on the system as it runs this morning.

Agents make this gap wider than usual. An agent's own certificate lapses after 90 days. Its depth on a capability can drop the same day a run fails. The workspace gains features, verdicts change shape, new sources are connected. A reviewer who learned the system at launch and never revisited it is approving work in a system they partly do not know.

What should a certificate say instead?

Three things, each of them about the present.

What the person is certified to do. Not "completed AI training" but a defined role: for example, a reviewer who may approve held items in a live workspace, or a builder who may design and certify agents. The scope should be narrow enough that an employer can map it to approval rights.

When it stops counting. An expiry date printed on the certificate and enforced at source. After that date, the certificate says lapsed. Renewal is a defined, proportionate step, which the guide on how to renew an AI agent certificate sets out.

Whether it is still valid, checked live. A certificate that can be revoked must be checked where it was issued, not trusted from a copy. Checking a certificate at source means looking it up with the issuer, by number or QR code, and seeing its current status on the same page.

Some certificates add a fourth: the product version the person was assessed on. That helps an employer see at a glance whether the holder learned on a version that predates significant changes.

How does this change the way businesses use certificates?

It turns a certificate from a file in a personnel record into an input to a control. A business can choose to make the right to approve held actions depend on a current certificate, capability by capability. When a credit controller's certificate lapses, their right to approve account stops pauses until they renew. That practice is explored in whether credit controllers need a certificate to approve agent actions, and the same logic applies to any role that approves an agent's work.

It also gives managers a clear procedure when standing lapses. The person does not stop working. They stop approving at the level that requires certification, and held items route to a colleague. The practical steps are in how to handle a reviewer whose certificate has lapsed, and a lapsed certificate procedure template gives you a starting point to adapt.

What is the trade-off?

Present-tense certificates are less comfortable. People lose standing they used to keep indefinitely. Managers have to track expiry dates and schedule renewals. A reviewer who is excellent at the job but forgot to renew will find their approvals paused, which feels bureaucratic.

There is also a risk of renewal becoming a box-ticking exercise in its own right: a quiz clicked through to restore access. If renewal is too light, the expiry date proves little.

Both costs are real, and both are manageable. Renewal should be proportionate to what changes: an update module covering what is new, and a short check that it landed. That is far lighter than the original assessment. Expiry tracking is a list, and a workspace that shows certificate status alongside approval rights makes it a list nobody has to maintain by hand.

Against those costs, set what you avoid. An employer relying on lifetime certificates cannot tell which of its approvers learned the current system. When something goes wrong, it cannot show that the person who approved the action was competent on the day. A present-tense certificate answers that question before anyone asks.

What should you do differently?

If you hire, assign or audit people who approve agents' work:

1. Stop accepting certificates without an expiry as evidence for approval rights. They may be useful background; they are not current evidence.
2. Check at source, on the day it matters. When you grant approval rights, and again when you audit, look the certificate up with the issuer.
3. Map certificates to rights. Write down which certificate allows which approvals, so a lapse has a defined effect.
4. Plan renewals like any other operational date. Put them in the same calendar as the agent's own recertifications.
5. Keep the evidence. A screenshot of a status check on the day of an approval is weaker than a record that ties each approval to the approver's certificate at that moment, but both beat nothing.

The guide to AI literacy and certification for people who work with agents covers how certificates and literacy fit together.

Where the Academy fits

Pryme Intelligence Academy's professional certificates are written in the present tense. Certified Pryme Operator and Certified Pryme Builder are valid for 12 months, Certified Pryme Architect for 24. Each is issued through VerifyDoc.ai and can be checked at source by number or QR code, where a lapsed or revoked certificate shows as such. The free Foundations badge is stamped with the product version.