If you're reading this, you already know the problem.
You issued a few hundred — or a few thousand — certificates with expiry dates. Now those dates are approaching, passing, or already past. You're trying to figure out who's expired, who's renewed, who's about to lapse, and who quietly slipped through the cracks two quarters ago.
This guide is for L&D managers, compliance teams, certifying bodies, and HR teams running recurring certification programs. We'll cover when to set expiry dates, which renewal models fit which programs, the operational pain of paper and PDF renewals, and how digital certificates fix the workflow end-to-end.
Not every certificate needs to expire. Setting an expiry date adds operational overhead — tracking, notifying, renewing, archiving. Before you add one, decide whether the underlying credential genuinely degrades over time.
Set an expiry date when:
Don't set an expiry date when:
A useful test: if you can't articulate what the recipient must do to renew, you don't have a renewal program — you have a deletion policy. Either design the renewal flow first or leave the credential permanent.
Most recurring certification programs fall into one of three patterns. Pick the one that matches how the underlying competency actually changes — not the one that's easiest to administer.
Every certificate is valid for a fixed length of time — typically one, two, or three years — measured from the issue date. On the anniversary, the recipient renews or the credential lapses.
Best for: safety training, compliance certifications, role-based credentials with predictable refresh cycles.
Pros: simple to explain, easy to automate, predictable revenue if you charge for renewals.
Cons: everyone renews on a different date, so support load is constant rather than batched.
The certificate stays valid as long as the recipient logs the required activity — continuing education credits, CPD points, training hours — within a rolling window. There's no single renewal date; the credential is "live" while the activity log is current.
Best for: professional bodies, medical and legal certifications, membership credentials with engagement requirements.
Pros: rewards ongoing engagement; aligns with how professionals actually maintain expertise.
Cons: more complex to track. You need a system that ties activity records to the credential.
The credential is valid until a specific condition changes — a product version update, a regulatory revision, an audit cycle, or an employment status change. When the trigger fires, all affected credentials require renewal.
Best for: product certifications, regulated workforces, partner programs, internal compliance.
Pros: credentials always reflect current reality.
Cons: triggers are unpredictable, so you need batch renewal capacity ready to deploy on short notice.
If your renewal process still runs on paper, PDFs, and a spreadsheet, you already know where it breaks. The pattern is consistent across every program we've seen.
You don't know who's expired. Spreadsheets don't notify you. By the time someone notices an expiry, it's usually because a recipient or an auditor flagged it.
Recipients don't know either. No automatic reminder goes out. People discover their certification has lapsed when they need to use it — which is exactly when it's most expensive to be unrenewed.
Renewal is a re-issuance from scratch. A new PDF gets generated, emailed, downloaded, stored. The old version still exists somewhere — on someone's desktop, in a forwarded email, attached to a job application from 2023. Nothing connects the new credential to the old one.
Verifying current status takes a phone call. A third party with a PDF can't tell whether it's been renewed, revoked, or replaced. They have to contact the issuer. The issuer has to look it up. Multiply by every verification request.
Forged renewals are easy. A PDF with an updated date is indistinguishable from a real one. There's no way to confirm a renewal happened other than checking the issuer's records — which the issuer often can't find.
Reporting is manual. "How many of our certified technicians are currently in good standing?" becomes a spreadsheet exercise. Compliance teams spend more time assembling the answer than acting on it.
A properly designed digital certificate platform turns each of those pain points into a routine operation.
Live status, not stale files. A digital certificate is a verifiable link — not a file. Anyone checking it sees the current status: valid, expired, revoked, renewed. The credential reflects reality the moment you update it.
Automated reminders. Expiry dates are stored as data, not as a line in a PDF. Reminders go out on schedule — to recipients, to managers, to compliance. Nobody has to remember to send them.
Renewals as updates, not replacements. When a recipient renews, the certificate updates. The verification link stays the same. Anyone who already has the link sees the new status. Recipients don't need to circulate a new file or update their LinkedIn — the existing share already reflects the renewal.
Permanent issuance record. With TRUE, original issuance is blockchain-locked — the fact that you issued the credential on a given date is permanent and cannot be edited. Expiry, renewal, and revocation operate on top of that permanent record. You get the integrity of an immutable ledger and the flexibility of a live status.
Instant verification, no phone calls. A third party scans the QR code or follows the link. They see whether it's valid right now. Your team doesn't field the verification request at all.
Analytics built in. TRUE's dashboard shows you who's overdue, who's renewed, and who's lapsed — without exporting anything to a spreadsheet.
A renewal workflow has six moving parts. If you're building one from scratch — or rebuilding one that drifted out of control — work through them in order.
1. Eligibility. What does a recipient have to do to qualify for renewal? Complete a course, log CPD hours, pass an assessment, attend a refresher, pay a fee? Write this down before you build anything.
2. Notification cadence. When does the first reminder go out — 90 days before expiry? 60? 30? 7? On the day? After? Most working programs use at least three touchpoints before expiry and one after.
3. Renewal action. What does the recipient actually click, sign, pay, or upload? The fewer steps, the higher the renewal rate.
4. Issuance trigger. Once eligibility is confirmed, the new (or updated) credential should issue automatically. Manual re-issuance is where renewal programs die.
5. Lapse handling. What happens if someone misses the window? Grace period? Reinstatement fee? Full re-certification? Decide in advance — don't decide per recipient.
6. Reporting. Who needs to see renewal status, and how often? Compliance, leadership, the recipients themselves, external auditors. Build the report once, point everyone at it.
For most programs, the workflow connects to an existing system — an LMS, a CRM, an HR platform, a member database. TRUE provides a REST API for exactly this: when your system confirms a renewal, it calls the API and the credential updates without a human in the loop.
These show up in almost every program that has been running for more than a year.
Setting expiry dates without a renewal plan. If you don't know how renewal will work, don't set an expiry. You're scheduling a problem for future-you.
One reminder, sent too late. A single 14-day notice is not a renewal program. People miss emails. Plan multiple touchpoints across at least 60–90 days.
Treating renewal as a new issuance. Replacing the old certificate with a new file orphans every share, link, and reference the recipient already distributed. Update in place wherever possible.
Hiding the expiry date. Recipients should be able to see their own expiry status at any time, not only when a reminder lands in their inbox.
No clear lapse policy. Inconsistent handling of lapsed certificates undermines the program. Either a credential expires or it doesn't — pick a rule, write it down, apply it the same way every time.
Confusing expiry with revocation. They're different operations with different meanings. The next section is the most important one in this guide.
This trips up almost everyone designing their first program. Expiry and revocation feel similar — both make a credential not-valid — but they mean very different things to anyone verifying.
Expiry is a scheduled, neutral event. The credential was valid for its term, the term ended, and the recipient now needs to renew. There's no implied judgment about the recipient. Anyone verifying sees: "expired — renewal required."
Revocation is an action you take to invalidate a credential before its expiry — typically because the underlying basis for issuing it no longer holds. Misconduct. Failed audit. Withdrawn accreditation. Mistaken issuance. Employment ended for a credential tied to a role. Revocation carries weight; it tells anyone verifying that the credential is no longer recognized by the issuer.
Use expiry when: the credential reached the end of its scheduled validity period.
Use revocation when: something happened that means the credential should no longer be honored, regardless of whether the expiry date has passed.
TRUE supports both as first-class operations. Expiry dates are set at issuance and trigger automatically. Revocation is an explicit action you take from the dashboard or the API. Either way, the original issuance record on the blockchain remains permanent — you're updating the credential's current status, not pretending the original event didn't happen.
That distinction matters for audit trails, disputes, and trust. A credential's history should be honest: issued, renewed, revoked, expired. Not edited, not deleted, not silently replaced.
TRUE was built for documents that need to live for years and stay verifiable the whole time. Recurring certification programs are exactly that.
Issuance is permanent. Every document is blockchain-locked at issuance — the original event is immutable.
Status is live. Expiry dates, renewals, and revocations update in real time. The verification link always reflects the current state.
Analytics show the whole program. The dashboard tracks who's active, overdue, renewed, and lapsed across your entire issuer base — no spreadsheet exports.
API-driven automation. Five REST endpoints connect TRUE to your LMS, HR system, CRM, or member database. Renewal flows run without manual re-issuance.
Issuer-branded. Documents live on your own domain, so renewal notifications, reminders, and verifications all reinforce your brand — not ours.
Issuers running recurring programs on TRUE include Active Sweden in wellness, SSF in security, and Skanska in L&D — each with their own renewal cadence, audience, and workflow.
For more on the lifecycle from issuance through renewal to retirement, see our guide to credential lifecycle management. If you're earlier in the process and still scoping the program itself, how to build a certification program walks through the design decisions that come before this one. And if you're a regulator or industry body, our overview for certifying bodies covers the institutional view.
If your renewal process is held together by reminders in a calendar and a spreadsheet that one person maintains, it will fail at scale. The question isn't whether — it's when, and how visibly.
A digital certificate platform turns expiry and renewal from an ongoing operational drag into a process that runs itself.
Book a FREE Demo to see how TRUE handles expiry, renewal, and revocation for recurring certification programs.
Or contact us if you'd rather start with a conversation about your specific program.
Save time, increase traffic and insights and build trust, by upgrading to blockchain secured diplomas and course certificates, which are loved by recipients and always verifiably authentic.
Book a demoNot sure where to start? Let us help!
Trusted by leading organisations worldwide
