How to track staff licence and certificate expiry dates without sticky notes

Somewhere in your business there's a list of who holds what. Electrical licences, white cards, first aid certificates, forklift tickets, working with children checks, worker screening, driver's licences, insurance certificates from subcontractors. Each one has an expiry date. Each one expires on its own schedule.

The list might be a spreadsheet. It might be a whiteboard in the office, a folder of scanned PDFs, or a sticky note on the manager's monitor that says "forklift ticket, March?". Often it's all of those, and none of them agree.

It works until someone turns up to a site, a client or an audit with something that lapsed six weeks ago. Then it's a scramble: find the person, find the renewal, find proof, and hope nobody asks how long it was out of date.

A ten-minute exposure test

Answer these honestly. One point for each "yes".

1. The dates live in more than one place. A spreadsheet, an email folder, someone's head.
2. Nobody gets told before something expires. You find out by checking, or by being asked.
3. The checking depends on one person remembering to do it.
4. You can't produce a copy of the certificate within five minutes if a client or auditor asks.
5. Subcontractors aren't on the list, or are on a different one.
6. You've had a lapse in the past year that you caught late.
7. Rostering or job allocation doesn't look at the list. Someone could be booked for work they're not currently cleared for.

0 to 2: You're in reasonable shape. Keep the list in one place and put a recurring reminder in a calendar to review it.

3 to 4: The system is a person, not a process. It holds while they're here and paying attention.

5 or more: You're relying on luck. The question isn't whether something lapses, it's when, and who notices first.

What an expiry register actually does

A proper register isn't a big system. At its simplest it's one place that holds every person, every credential and every date, and does the remembering for you. It's one part of our compliance and records systems, and it can be built on its own.

One record per person. Each staff member or subcontractor has a profile listing what they hold, the number, the issue date, the expiry date and a copy of the certificate. No more hunting through inboxes.

Reminders before the date, not after. The person and their manager get an email or text at the points you choose: say 60 days, 30 days and a week out. If nothing changes, the reminder gets firmer and goes higher.

Staff upload their own renewals. They take a photo of the new card on their phone and upload it. The manager checks it and approves. The new expiry date replaces the old one, and the old certificate stays on file.

Requirements by role. You set what each role needs: an electrician needs a licence, a white card and first aid; an office role needs none of those. The register shows who is missing what, not just who is expiring.

A clear view of who's cleared today. A simple screen shows everyone as current, expiring soon or lapsed. If you use a job or booking tracker, it can check that list before someone is assigned to work that needs a particular ticket.

Evidence on request. When a client, head contractor or auditor asks for proof, you export a PDF of current credentials for the people involved. It takes minutes, not an afternoon.

A record of what changed. Who uploaded what, who approved it and when. If you're ever asked whether someone was cleared on a given date, you can answer from the record.

A real example

We built a credential and licence register with expiry alerts and evidence uploads as part of Accorda, the compliance platform we designed and built for Australian care providers. It sits alongside incident, complaint and risk registers, and its records feed the audit evidence packs the platform generates as branded PDFs. Before that, we built a focused compliance portal for an allied health provider covering staff records, policy sign-offs and incident reporting. That portal's design became the foundation of the larger platform.

The shape is the same in other industries. Trades businesses have licences, white cards and SWMS sign-offs. Transport has driver's licences and medicals. Cleaning and security have police checks. The register doesn't care what the credential is called. It cares that it has a date and a person attached.

What stays the same

Your rules stay yours. You decide which credentials matter for which roles, how far ahead to remind people and who signs off. The register enforces what you already expect, it doesn't invent new policy.

Your payroll and HR system stays where it is. The register can sit beside it, and staff details can be imported from it so nobody types names in twice.

The responsibility stays with the person. Staff still renew their own licences. The difference is they get told in time, and the manager can see who has and hasn't.

When it isn't worth it

• You have a handful of staff and a few credentials. Put the dates in a shared calendar with reminders and keep the certificates in one folder. That's enough.
• Your existing software already does it. Some HR, rostering and job-management platforms track expiries well. Check what you already pay for before building anything.
• Nobody has agreed what's required. If the business hasn't decided which roles need which tickets, start there. A register built on guesswork will flag the wrong things.
• The bigger problem is elsewhere. If incidents are reported on paper and policies can't be found, the expiry dates are one part of a larger records problem. Our piece on replacing the spreadsheet only one person understands has a similar test for the wider mess.

Where the data lives

Copies of licences and checks hold personal information, so they shouldn't sit in a shared inbox. We host this kind of system in an Australian data centre, encrypted, with daily backups and role-based access, so staff see their own records and managers see their team's. Auditors can be given time-limited read-only access. If you want more detail on hosting, our database setup and hosting page covers it.

How long it takes

Compliance and records systems typically take two to four weeks. A focused expiry register sits at the shorter end; one that also connects to rostering or job allocation takes longer. We'll tell you which yours is before we start. If cost is the next question, our pricing page has the ranges.

If your staff already fill in checks on their phones before starting work, our piece on digital pre-start checklists with photos shows how the two can share the same staff records.

What working with us looks like

We start with a 30-minute call. Bring your current list, whatever form it's in, and the roles and credentials that matter. You get a written scope and a fixed price. Then we build a working prototype of the core feature, free: your people, your credentials, real expiry dates and the reminders firing. If it doesn't do what we agreed, you walk away. You see it working before you pay.

Send us your current list and we'll show you what it looks like as a register that reminds people for you.