How to track staff certificate expiry dates without the weekly spreadsheet check

Every clinic has a spreadsheet like this. A row for each person. A column for each document. Some cells red. A few that should be.

It works until the person who checks it goes on leave.

Registrations, insurance, first aid, working with children checks, police checks, NDIS worker screening. Each has its own expiry date and its own renewal cycle. Somebody has to notice when each one is close, chase the right person, and check the new one came in.

At a multi-disciplinary clinic we worked with, that somebody checked by hand every week. At an NDIS provider with ten practitioners, document checks were manual too, and the reminder system meant to help kept failing.

Here are your three options, and what we learned building two of them.

Option 1: the spreadsheet

Free, and everyone understands it.

But a spreadsheet can't read a certificate, notice a date or send a reminder. Every one of those is a person's job. And when a renewed certificate lands in a shared folder and nobody updates the row, the spreadsheet is wrong and nobody knows.

Option 2: compliance or HR software

A real step up, especially if your rostering tool already has it. Staff upload documents. The software sends reminders.

Two catches. Someone usually still reads each document and types in the date. And the rules are the software's, not yours. If you withhold payment when a document is overdue, or treat contractors differently from employees, it may not bend.

Option 3: an agent that reads the documents

This is where AI earns its keep.

Certificates don't follow one format. One says "valid until". Another says "expires". A third gives an issue date and leaves you to count twelve months. A person can read any of them. So can AI.

At the clinic, AI reads each uploaded certificate, finds the expiry date and posts any problem to Slack, in its own channel. The weekly check is gone. The team only hears about the certificates that need action.

Whoever builds yours, three choices make an agent like this dependable:

• If it's unsure, it asks. An unreadable scan or an odd date should be flagged, not guessed.
• Alerts go where people already look. For the clinic, that's Slack. A dashboard nobody opens fails the same way the spreadsheet did.
• One register is the truth. The agent checks against a single list of who should hold what, so a missing document shows up as missing. At the NDIS provider, that list is the capacity register.

The part everyone gets wrong: reminders

Finding the date is half the job. Getting someone to renew is the other half. It's where most systems quietly break.

When we audited the NDIS provider's reminder workflow, we found three faults:

• Drafts landed in an account nobody could see.
• The duplicate check was switched off, so practitioners were chased twice.
• Some drafts were lost unsent.

So some people got two reminders, others got none, and nobody could tell which.

One message per person. Everything they owe. Sent on a schedule. Never twice.

That's the standard we build to.

What replaced the old setup is a compliance system that checks every practitioner's documents against the capacity register, using rules agreed with the owner. Overdue items are flagged. Reminders and payment-withheld notices send based on payment status. Every fortnight, a summary lists who's overdue and on what.

Nobody checks documents by hand any more. The manager deals only with what's overdue. (Case study.)

We've also designed an agent to replace the old reminder workflow: 220 documents across 10 practitioners, one clear email each. That agent is designed, not yet built.

Start with the register

Every option above needs one thing first: a register you trust. You can build one this week.

1. One row per person, per document. Person, role, employee or contractor, document, issue date, expiry date, where the file lives, status.
2. List what each role must hold. A physio, a support worker and a receptionist need different things. Write it down once.
3. Keep every file in one place, named the same way: Surname - Document - Expiry YYYY-MM-DD.
4. Decide your rules. How many weeks' notice? Who's told when something lapses? What happens to rostering or pay in the meantime?
5. Give one person ownership until it's automated.

Step 4 is the one most businesses have never agreed. It's also the part an agent needs most.

Where to start

Still checking certificates by hand every week? Write down your step 4 rules tonight. They're the hard part of any system, and only you can write them.

Then, if you'd like help turning them into something that runs itself, start with an audit. See how the clinic's version works in the case study, or read how we decide what to automate first in the admin audit.