An operator working on an expired certificate still looks competent on paper. On why validity tracking is not just about reminders.
A forklift operator's licence expired on 14 March. The system still reads "training completed". The operator keeps working, the shift plan counts them as competent, and the monthly report shows 88% proficiency.
Nothing in this picture raises an alarm. That is precisely the problem.
Because in most systems competency is recorded as a one-off event: training delivered, box ticked, done. But competency is a state, and states decay.
Once the record says "training completed", the information about how long ago that was is lost. Even if you keep the date in a separate column, nobody looks at that column — because looking would require someone to open the file every morning and check dates.
The usual answer is to send an email before expiry. Necessary, but not sufficient, because a reminder delivers information, not behaviour change.
The email arrives, the person is busy, the email is buried. Two weeks later the certificate expires and the system still counts that person as competent.
For validity tracking to work, three things must be in place together:
A single reminder always arrives at the wrong time. Too early and it is forgotten; too late and there is no time left to organise training.
A three-stage chain works well in practice:
Different competencies need different lead times. For externally provided training with limited places, even 90 days can be tight; for internal training, 30 is plenty.
If an expired score does not drop by itself, the matrix looks better than reality. This is the most dangerous failure a competency system can produce: it creates false confidence.
If your proficiency rate reads 88% and that number counts expired certificates as competent, it is not a measurement but an illusion. Used to make decisions, it causes harm.
When a score expires it must automatically become invalid, the person must become unassignable to that work, and the gap must land in the training plan.
The person alone is not enough. In practice three parties need to know:
If the warning goes only to the person and that person takes leave, the chain breaks.
To know whether validity tracking is actually working:
The third is the most overlooked and the most revealing. If certificates keep expiring and are renewed weeks later, the problem is not reminders but capacity.
Validity tracking is not a reminder feature; it is the mechanism that keeps the matrix truthful. Without automatic invalidation, a competency matrix gradually stops reflecting reality — and it does so without telling anyone.
In Skill Monitoring, every competency carries a renewal period, expired scores invalidate automatically, and the T-90 / T-30 / T-7 chain reaches the relevant people through in-app notifications, email and mobile push.