Setup Considerations: certification expiry

What this achieves

A certification template decides how long a credential stays valid and who is warned as it runs out. Every certificate you issue with a validity period becomes a renewal somebody has to manage, so the policy is worth setting before the first one is awarded.

Decision 1: whether it expires at all

Option	Description
Never expires	Issued once and held permanently. No renewal work.
Valid for a set number of months	Expires, and generates renewal work for every holder.

Set an expiry only where the credential genuinely goes stale — a regulatory qualification, a safety certification, a vendor accreditation with its own renewal cycle. An internal induction certificate that expires creates work with no purpose.

Example: HC Corp UK Ltd sets no expiry on an internal induction certificate, and a validity period on a safety certification its warehouse staff must hold currently.

Decision 2: how long the validity period is

The validity period is measured in months from issue, so holders expire on staggered dates rather than together. That is usually what you want — a single expiry date for everyone means a cliff.

Match the period to whatever external body or internal policy actually governs the credential. Choosing a round number because it looks tidy means renewals fall out of step with the thing they are renewing.

Decision 3: expiry alerts

Alerts fire at intervals you configure — a set number of days before expiry, and on the day of expiry itself.

Expiry raises an alert. It does not revoke anything, block anyone, or remove access. A lapsed certificate remains on the record marked as expired, and acting on it is a human decision.

That matters for planning: if holding a current certification is a condition of doing a job, the enforcement is your process, not the system’s.

Example: an HC Corp UK Ltd warehouse employee whose safety certification expires is not stopped from working by Humavera. Somebody has to see the alert and act.

Set the earliest alert far enough ahead that renewal is actually possible — if a course takes six weeks to arrange, a two-week warning is a warning about something you cannot now prevent.

Decision 4: what issuance grants

A template can grant skills or competencies when it is issued, the same way a course grants them on completion. Where a credential is the proof of a capability, granting the skill keeps the skill profile and the certificate consistent.

Decision 5: auto-issue, and the trap in it

A course can nominate a certification template so completing the course issues the certificate automatically. The template must be active for that to happen — an inactive template silently issues nothing.

If you find learners completing a course without receiving their certificate, check the template’s status first.

Decision 6: retiring a template

Archiving a template stops auto-issuance immediately while leaving existing holders valid. That is the safe way to withdraw a credential: nobody loses what they earned, and no new ones are created.

What is expensive to change later

Decision	Cost of changing later
Adding expiry to a template already issued	High. It creates a renewal obligation across every existing holder.
Changing the validity period	Medium. Existing certificates keep the terms they were issued under.
Alert thresholds	Low, and worth revisiting once you see how long renewals really take.
Archiving a template	Low. Holders keep their certificates.

What happens next

Create the template with its validity and alerts, then either award certificates directly or nominate the template on a course so completion issues them. Once holders exist, the expiry view is where the renewal work lives.