Field notes › Compliance
Why 60 days is the right runway for cert renewals
Every compliance system has to pick a number: how far ahead of a certificate's expiry do you start making noise about it? Pick too short a window and renewals become emergencies. Pick too long and the warnings become wallpaper. Mustr surfaces expiring certs up to 60 days out, and that number was not plucked from the air. It falls out of how rostered crews, especially remote ones, actually live and work.
The renewal that arrives mid-swing
Think about what renewing a certificate involves for a FIFO worker. They cannot do most renewals from site. The course runs in a regional centre or a capital city, on dates the training provider sets, and the worker is only home for the off part of their swing. So a renewal is not one task. It is: notice the expiry, find a course that runs during an off-swing, get a seat on it before it fills, attend, and then get the new certificate back into the hands of whoever tracks it. Each of those steps has a wait built in, and the waits stack.
Why 30 days is a trap
A 30-day warning sounds reasonable until you lay it against a swing pattern. A worker on a two-and-one roster might be on site for most of that window. If the notice lands at the start of a swing, they have perhaps one block of days at home before expiry, and if the course they need is not running that week, or is full, the cert lapses. Now you have a compliant worker turned non-compliant by scheduling, a roster with a hole in it, and a client asking why. The warning technically worked. It just arrived after the last realistic chance to act on it had nearly passed.
Why longer windows turn into noise
The tempting fix is to warn earlier, and the logic seems sound: more runway, more safety. But warnings compete for attention, and a cert expiring far in the horizon is, honestly, not urgent. When a list mixes things that need action this fortnight with things that will not matter for months, people learn to skim it, and skimming is how the genuinely urgent item gets missed. An expiry window is only useful if everything in it deserves attention now. Stretch it too far and you have rebuilt the problem you were solving, just with more email.
What 60 days actually buys
Sixty days covers roughly two full swing cycles for most common patterns. That means at least two windows at home in which to book and sit a course, so a full training calendar or a missed first attempt does not turn into a lapse. It leaves room for the admin tail, the certificate that takes a while to be issued and uploaded. And it is short enough that everything on the expiring list is a this-month problem, so the list stays worth reading. Two chances to fix it, no room to ignore it. That is the balance.
Make the reminder do the work
A window is only half the mechanism. The other half is what happens when a cert enters it. In Mustr, expiring certs surface automatically and a reminder email to the worker is one click. The worker uploads the renewed certificate through the worker portal from their phone, and the record updates. And because every booking is checked server-side against competencies before it is confirmed, a cert that does lapse despite the runway cannot quietly carry a worker onto site. The booking is blocked. The compliance page covers both halves.
If your renewals keep turning into last-minute scrambles, see it on your own roster.