Practical guide

How to Track Employee Certifications and Licenses: An Expiration Checklist

A certification belongs to a person, not a system. Use this checklist to put every required credential on one honest list with owners and reminders — practice guidance, not a ruling on which credentials a role legally requires.

October 14, 2026 · 7 minute read

Why certifications lapse

A certification belongs to a person, not a system. It is earned by one employee, expires on its own date, and is easy to forget until someone asks for proof.

The usual pattern: a first aid card, a forklift ticket, or a professional license expires quietly. Nobody notices until a client audit, a site visit, or a job that requires it. Then the renewal course is booked out for six weeks.

The common causes:

  • Certificates live in email attachments, shared drives, or the employee's own wallet
  • The expiration date is known only to the person who holds it
  • Renewal takes longer than anyone planned, because it needs a class, an exam, or agency processing
  • Nobody is named as responsible for the next action

This checklist is for ops, HR, and admin teams who want every required credential on one honest list with owners and reminders. It is practice guidance. Which credentials a role legally requires belongs with your compliance lead, the issuing body, or the relevant regulator.

Certifications vs business licenses

Two kinds of dates often get mixed together:

  • Employee certifications and professional licenses belong to a person. They follow that person if they change jobs.
  • Business licenses and permits belong to the company or a location.

Track them as separate records with clear labels. They have different owners and fail in different ways. For company-side licenses and permits, see the business license and permit renewal checklist. For the general habit of labeling what each date means, see how to track expiration and renewal dates without missing one.

Step 1: Map credentials to roles

Before you collect a single certificate, decide what each role actually needs.

  • List roles or job types that require a credential
  • For each role, list the required certifications or licenses by exact name
  • Note whether each one is required by law, by a client contract, or by internal policy
  • Note any site, equipment, or region scope (for example, a ticket valid only for one equipment type)

This gives you a list of what should exist, so you can spot gaps, not just expirations.

Step 2: What to record for each credential

Use one record per employee per credential. Do not squeeze several into one "certifications" field.

  • Employee: full name and team or location
  • Credential: exact name of the certification or license
  • Issuing body: provider, board, or agency
  • Certificate or license number
  • Issue date
  • Expiration date: if there is no printed expiry, record the issue date and the review interval from the issuer or your policy; do not guess
  • Renewal lead time: how long renewal realistically takes, from booking to new card in hand
  • Start-renewal date: expiration date minus lead time
  • Record owner: the named person responsible for the next action (often the employee's manager)
  • Proof link: a stable link to the current certificate
  • Status: current, renewal in progress, expired, or pending proof

Step 3: Set reminders from the start-renewal date

A reminder on the expiration date is not a renewal plan. Count back from how long renewal really takes.

  • Simple online renewals: start about 30 days out
  • Renewals that need a course, exam, or approval: start 60 to 90 days out
  • Hard-to-schedule or contract-critical credentials: add more runway

A practical ladder:

  • At the start-renewal date: remind the employee and the record owner to book the renewal
  • 30 days before expiry: confirm the renewal is booked or done
  • 7 days before expiry: escalate anything still open to the manager
  • After renewal: upload the new certificate, update the dates, and confirm the next cycle's reminders are set

For why each reminder needs a specific job, see the 90/60/30-day renewal reminder schedule.

Step 4: Name an owner for every record

Employees hold the credential, but someone else should own the record. Usually that is the employee's manager, with HR or ops keeping the list honest.

  • The employee books and completes the renewal
  • The manager owns the outcome and approves time or cost
  • HR or ops keeps the list accurate, chases blanks, and runs reviews

"HR" is not an owner. Put a named person on every record, with a backup. The same ownership logic applies to software; see who should own software renewals.

Step 5: Handle joiners, movers, and leavers

Most gaps appear when people change.

  • New hire: collect required credentials before the first shift that needs them; add records on day one
  • Role change: compare the new role's requirements against what the person holds
  • Leaver: close their records and reassign any owner duties before their last day
  • Manager change: move record ownership to the new manager

Step 6: Keep history and proof

  • Keep superseded certificates attached to the record instead of deleting them
  • Note who confirmed each renewal and when
  • Be able to answer "who is currently qualified for this task?" from the list alone

The same keep-the-history habit applies to vendor paperwork; see vendor COI tracking.

Weekly and quarterly rhythm

Weekly (10 to 15 minutes): Scan start-renewal dates in the next 90 days. Confirm each has an owner and a booking in progress. Chase expired and pending-proof records first.

Quarterly: Compare your role map against your current team. Look for missing credentials, records for people who have left, and certificates with no proof link.

Spreadsheet version

A spreadsheet can carry this for a small team. Use one row per employee per credential, a computed "days until start-renewal" column, and highlighting for anything inside 90 days. Keep one master copy with one owner.

When the sheet starts to drift (rows with no owner, reminders in one person's calendar, proof links that go nowhere) see how to move renewal tracking out of spreadsheets.

FAQ

Who should be reminded, the employee or the manager?

Both. The employee does the renewal, and the manager owns the outcome. Escalate to the manager if the renewal is not booked by your cutoff.

What if a certification has no expiration date?

Record the issue date and confirm whether the issuer, a regulator, or your policy requires a periodic refresher. Do not invent an expiry date.

Do we need an HR system or LMS to track certifications?

Not to start. A clear list with owners, labeled dates, and reminders that reach real people solves most surprises. Larger teams may want dedicated tooling; the record and ownership discipline is the same.

Should certifications live in the same tracker as business licenses?

They can, if one team runs the reminders. Keep them as separate, clearly labeled records, since one belongs to a person and the other to the business.