The Licence That Expired in a Drawer
A practising licence renews annually, sits in a folder, and lapses without a single thing in the working day changing. Everyone keeps working. The exposure is retrospective, and it is discovered by an inspector or an insurer rather than by you.
A clinical officer's registration expired in March. She has worked every shift since, competently, and nothing at all has drawn attention to it — not the rota, not the payroll run, not a patient, not a colleague. The certificate is in a folder in an office she has no reason to open.
It surfaces in September, when an insurer asks for current registrations as part of a renewal, or when an inspector asks to see the file. And the question that follows is not about March. It is about every single shift between March and September, and whether the facility was covered for any of them.
This is a distinctive kind of risk because it accrues silently and is discovered retrospectively. There is no bad day. There is one bad afternoon, six months later, about a period you cannot go back and change.
Why this particular failure is so persistent
Every facility knows licences expire. Almost every facility has a system for it. The systems fail in the same four ways, and none of them is about not caring.
- The reminder lives with the person who is leaving. A spreadsheet maintained by one administrator is a dependency on that administrator. When they move on, the file survives and the habit of opening it does not.
- The calendar entry was set for the wrong date. A reminder on the expiry date is useless, because a renewal that takes six weeks needed to start six weeks earlier. The reminder arrives to tell you it is already too late.
- Nobody owns the second half. Somebody notices the expiry, tells the member of staff, and the loop closes there. Whether the renewal actually arrived is a separate question that nobody is assigned.
- The document is filed but not dated. A scanned certificate in a folder is a record of a licence, not a record of when it stops being one. The expiry lives in a person's head or on the paper itself.
There is no bad day. There is one bad afternoon six months later, about a period you cannot go back and change.
What the document vault does
Documents attach to an employee or to an employment contract, and each one can carry an expiry date. That date is the whole mechanism — a document without one is stored and never watched, which is worth knowing before you assume filing something has protected you.
A job runs every day and looks for active documents attached to staff whose expiry falls within the next thirty days, ordered so the nearest is first, and emails a reminder to the administrators and the organization contact.
| Property | Behaviour |
|---|---|
| Runs | Daily, on a schedule |
| Looks ahead | Thirty days |
| Watches | Active documents attached to employees and contracts |
| Ignores | Archived documents, and anything with no expiry date set |
| Notifies | Administrators and the organization contact |
| Reports at most | Fifty documents in one run |
Three of those rows are limits worth planning around rather than discovering, so they are worth taking one at a time.
Thirty days, and why that may not be enough for you
The window is thirty days and it is the same for every document. For a great many things that is generous — an identity document, a contract, an internal certification.
For clinical registrations it is frequently not. A professional council renewal with a payment, a verification step and a printing queue can take two or three months in practice, and a reminder arriving thirty days out is a reminder that you are already behind.
The workaround is straightforward and worth adopting deliberately rather than by accident: record the expiry date you need to act on rather than the one printed on the certificate. If a licence expires on the thirty-first of December and renewal reliably takes ten weeks, record it as expiring in mid-October and note the real date on the document itself. The reminder then arrives when it is useful rather than when it is accurate.
Record the act-by date, not the printed date
This is a small habit with a disproportionate effect. The system tells you thirty days before whatever date you enter, so entering the date by which the renewal must start gives you a warning you can act on. Write the true expiry into the document title or notes so the real figure is never lost — you want both dates, used for different purposes.
It notifies, and it does not stop anything
Nothing in the system prevents a person with an expired document from being rostered, from clocking in, or from being paid. Attendance does not read the expiry, shift scheduling does not read it, and payroll does not read it. The reminder is an email to an administrator, and the entire control is whatever that administrator does next.
It is worth being unambiguous about this because it is exactly the sort of capability that gets assumed. A system that emails somebody about a lapsing licence is a reminder system, not a compliance gate, and the difference matters enormously when the question is asked in September.
What that means practically is that the process around the reminder is the control. Somebody has to receive it, act on it, and confirm the renewal arrived — and that third step is the one that is almost never assigned.
What AWRA OpsHub does today
- Documents attach to an employee or an employment contract and carry an optional expiry date.
- A scheduled job runs daily and reports active documents expiring within thirty days, nearest first.
- The reminder goes to administrators and the organization contact, with the document, who it belongs to, when it expires and how many days remain.
- Archived documents are excluded, so superseded copies do not generate noise once a renewal is filed.
More we can add to your workspace
- The thirty-day window is fixed. It is not configurable per document type, so a registration needing three months of lead time gets the same notice as an identity document. Record the date you need to act on rather than the printed one.
- Supplier and facility documents watched for expiry. They are stored today — the supplier prequalification pipeline files them — and the expiry job looks at documents attached to employees and contracts.
- A block on an expired document, so it prevents rostering, clocking in or payment. Attendance, scheduling and payroll read no expiry date today.
- A single run reports at most fifty documents. For a large clinical workforce with many registrations renewing together, that cap can be reached, so treat the email as a prompt to open the list rather than as the complete list.
- A notification to the person holding the document. Reminders go to administrators today, so telling the member of staff is a step somebody performs.
Where we point you to a specialist
- We will not judge whether a document satisfies your regulator. The system holds a file and a date; whether a particular certificate meets a particular council's requirement is a professional judgement, and a vendor making it on a marketing page is offering you a false assurance.
- We will not silently archive a lapsed document. An expired certificate stays visible with its date, because a record that quietly disappears when it becomes inconvenient is worse than no record.
A configurable lead time per document type, expiry watching extended to supplier and facility documents, notification to the document holder, and a hard block on rostering someone whose registration has lapsed, are all scope rather than ceilings. The vault, the scheduled job, the notification routing and the permission model all exist and work — each is a written specification and a price.
Supplier documents are the ones most facilities will feel second. Licences, tax compliance certificates and insurance for the organizations you buy from are stored perfectly well and sit outside the sweep, so those need a rhythm you run rather than a reminder you receive.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsA register that actually works
The software half takes an afternoon. What makes the difference between a register that holds and one that decays is a handful of decisions about who does what.
-
List what expires, once, properly
Professional registrations, indemnity cover, contracts, work permits, internal certifications, and anything with a renewal cycle. Do this as a workshop rather than as a task, because the items nobody thinks of are the ones that lapse.
-
Decide the act-by lead time for each type
How long does this renewal actually take, at its slowest, in your experience rather than the council's published figure? That number, subtracted from the true expiry, is the date you record.
-
Name an owner per document type, not per document
Registrations to the clinical lead, contracts to HR, insurance to finance. Per-document ownership does not survive staff turnover; per-type ownership does, because the role outlives the person.
-
Assign the confirmation step explicitly
Somebody has to check that the renewal arrived and the new document was filed with a new date. This is the step that is almost always missing, and it is where the loop closes or does not.
-
Put supplier documents on a calendar rhythm
Since they are not watched, they need a standing quarterly review with a name against it. Store them in the same place so at least the record is in one system.
-
Audit the register twice a year
Not the expiries — the register itself. Which staff have no documents recorded at all? Which documents have no expiry date and are therefore invisible? Those two questions find more exposure than any reminder does.
That last step is the one worth protecting when time is short. A reminder system only watches what it has been told about, so the largest risk in any document register is not the certificate expiring next month — it is the one that was never entered, which will never generate a reminder and will never be missed until somebody asks.
The rostering side of this is in who was on Sunday night, the supplier equivalent in the certificate expired and the work carried on, and the custody discipline for controlled items in controlled medicines.
Our take
Record the date you need to act on rather than the date printed on the certificate — the reminder arrives thirty days before whatever you enter, and for a clinical registration thirty days is often already late. Then be clear that this is a reminder and not a gate: nothing prevents an expired licence holder from being rostered or paid, so the process around the email is the entire control. And twice a year, audit the register rather than the expiries. The document that was never entered is the one that will not be missed until an inspector asks.
See the document register
Documents attached to staff and contracts with expiry dates, a daily job reporting what lapses within thirty days, archived copies excluded, and reminders to your administrators.
Explore HR documentsFrequently asked questions
Will the system tell us before a practising licence expires?
Yes, provided the document is attached to the employee with an expiry date recorded. A job runs daily and reports active documents expiring within thirty days, nearest first, by email to your administrators and organization contact. The critical word is "recorded" — a document stored without an expiry date is never watched, so filing a certificate is not the same as protecting yourself with it.
Thirty days is not enough for a council renewal. What do we do?
Record the date you need to act on rather than the date printed on the certificate. The window is fixed at thirty days for every document type, so if a renewal reliably takes ten weeks, enter an expiry ten weeks before the real one and write the true date into the document title or notes. The reminder then arrives when it is useful instead of when it is accurate, and you keep both figures.
Does an expired licence stop someone being rostered or paid?
No. Nothing is blocked — attendance, shift scheduling and payroll do not read the expiry date at all. This is a reminder system rather than a compliance gate, and the distinction matters a great deal when the question is asked retrospectively. The control is entirely the process around the email: somebody receives it, acts on it, and confirms the renewal actually arrived. That third step is the one most facilities never assign to anyone.
Are supplier licences and insurance certificates watched too?
No. They can be stored — the supplier prequalification pipeline files documents in the same vault — but the expiry job looks only at documents attached to employees and employment contracts. Supplier tax compliance certificates, licences and insurance therefore need a rhythm you run rather than a reminder you receive. Put a standing quarterly review against a named person, and keep the documents in the same place so at least the record is unified.
Who receives the reminder?
Your administrators and the organization contact — not the member of staff whose document it is. Telling them is a step a person performs. That is worth designing around rather than working around: a reminder that reaches an administrator who is on leave reaches nobody, so make sure more than one person is on the operational contact list, and treat the email as a prompt to open the register rather than as the register itself.
What is the biggest risk in a document register?
Not the certificate expiring next month — that one generates a reminder. It is the document that was never entered, or entered with no expiry date, because neither will ever produce a warning and neither will be missed until an inspector or an insurer asks. Audit the register itself twice a year rather than only the expiries: which staff have no documents recorded, and which documents have no date. Those two questions surface more exposure than any reminder ever will.
