"Certified" gets used to mean at least four different things, and the gap between them is where most operator allocation problems live. A person can hold a valid licence, have been trained on the machine class, and still be the wrong person to put on that particular excavator this morning — because they have never operated that model, or because their site authorisation lapsed last month and nobody noticed. Supervisors generally know this informally. The problem is that the knowledge lives with whoever does the allocating, and disappears the day they are not there. You can look at how your own records are structured in a free 30-minute session.
Know Who Can Operate What, Before You Hand Over the Key
Licence, class training, machine familiarity, and current authorisation tracked separately — because they expire separately and mean different things.
Four Things People Mean by "Certified"
The formal qualification required for the machine or vehicle category. Externally issued, externally verifiable, and the one most fleets already track.
Expires on a date. Necessary, and on its own not sufficient.
Having been trained to operate excavators, or cranes, or forklifts, as a category rather than a specific unit.
Often recorded at induction and then never revisited, even years later.
Controls, attachment behaviour, and quirks differ between models and between units of the same model. An experienced operator on an unfamiliar machine is a real and underrated risk.
Rarely recorded anywhere, which is why it is usually the missing layer.
Site-specific permission, medical validity where required, and any restriction currently applying to that person.
The layer most likely to have quietly lapsed while the other three remain valid.
The Check Has to Happen at Allocation
A competency record that is reviewed monthly, or at audit, answers the wrong question. The question that matters is asked dozens of times a day at a site office: this machine, this person, this shift — yes or no?
If answering it requires opening a file, calling someone, or trusting a supervisor's memory, the honest answer is that it is not being asked at all. Allocation happens under time pressure, and any check that adds friction at that moment gets skipped, regardless of policy.
Which means the record has to be available where allocation happens, on a phone, in seconds, and it has to answer with the machine in mind rather than listing everything a person holds.
Answer It in Seconds, at the Machine
Operator competency checked against the specific asset being assigned, with lapses flagged before the handover rather than after.
What an Operator Record Should Hold
Each qualification separately, with its own issue and expiry date rather than one combined status.
Machine classes the person is trained on, and the specific models they have actually operated.
Site authorisations, with the sites they apply to and when they were granted.
Any current restriction, without recording the underlying reason where that is personal information.
Refresher and reassessment dates, since training does not stay current indefinitely.
A history of what they have operated, which builds familiarity evidence without anyone maintaining it manually.
Frequently Asked Questions
What qualifications does our operation legally require?
It depends on the equipment, the setting, and whether the site falls under mining, factory, or road transport requirements. Confirm the applicable set with your statutory safety officer rather than a general list, since the obligation sits with the operator of the site. We can show how whatever set applies is tracked on a call with our team.
Is model-specific familiarity really necessary to track?
It matters most where control layouts or attachment behaviour differ meaningfully, which on mixed OEM fleets is often. Tracking what someone has operated costs nothing once allocation is recorded anyway.
How do we handle contractor and hired-in operators?
Same structure, with responsibility for verification recorded. Assuming the contractor has checked is a common gap that only becomes visible after an incident.
What about personal information in these records?
Record the operational fact — that a restriction applies, or that an authorisation is current — rather than underlying medical or personal detail, and limit who can see what through role-based access.
Where should we start?
By checking what has already expired. In most fleets that first pass finds several lapsed items that everyone assumed were current. Start with a free trial.
Four Layers, Tracked Separately, Checked at Handover
Hold licence, class training, machine familiarity, and current authorisation as separate records with their own dates, and make the answer available on a phone at the moment a machine is assigned rather than at the next audit.
