
“When was truck 7 last load tested?”
“It should be on the certificate.”
“Which certificate?”
It is a Tuesday morning, an auditor is in reception and the operations manager is opening a folder labelled “Compliance 2025”, a shared drive called “Certs NEW” and an email thread that ends with “see attached, I think”. The truck itself is fine. It was tested. Somebody signed for it. The trouble is that nobody can prove it before the coffee goes cold.
Most sites do not miss inspections because they do not care. They miss them because the date lived in one place, the reminder in another and the evidence somewhere else entirely. Good forklift inspection records close that gap long before anyone asks for them.
“Due soon” is the most dangerous status on the floor
An inspection that is overdue at least gets attention. One that is “due soon” is easy to postpone. There is always a busier week, a machine that cannot be spared or a technician who is booked elsewhere.
The date slips by a few days, then a few more. Nobody decides to let it lapse. It simply drifts, one reasonable delay at a time, until a routine task has become a finding.
The fix is not more urgency. It is earlier visibility. When upcoming inspections and load tests are planned around real operating dates, with enough warning to book the work, “due soon” becomes a scheduling decision rather than a surprise.
An inspection belongs to the machine, not the paperwork
Certificates tend to be filed by date, by supplier or by whoever happened to receive the email. Machines, however, are what auditors, insurers and safety officers actually ask about.
When the record sits against the asset, the question “Is this forklift in order?” has one place to start. The fleet number leads to the last inspection, the last load test, the outcome and the next due date. When records are filed by supplier instead, the same question becomes a small research project.
This matters most when machines move. A forklift transferred to another site should take its compliance history with it, not leave it in the old site’s filing cabinet.
Done is not the same as recorded
A technician completes the inspection, notes a worn chain and moves on to the next callout. The work happened. But if the result, the finding and the follow-up only exist in a notebook, the site cannot show what was found or what was done about it.
A useful inspection record answers four plain questions: what was checked, what was found, who did it and what happens next. Anything less leaves the next person guessing, and guessing is not a compliance strategy.
Findings need an owner and a finish line
The inspection that identifies a defect is only half the story. The repair that follows is the other half, and it is the half that most often goes missing.
“Noted on report” is not a status. Each finding should become an action with someone responsible for it and a way to see whether it has been closed. Otherwise the same worn chain appears on the next three inspection reports, each time described a little more urgently.
One version of the truth for everyone involved
Inspections usually involve more than one party. A service provider does the work, a site manager arranges access, a safety officer needs the evidence and a procurement team wants to know whether the contract was honoured.
When each of them holds a different copy of the story, disagreements are inevitable. One shared record of completed work, outcomes and supporting documents turns the conversation from “Did you do it?” into “What do we do next?”, which is a far more productive meeting.
Expiry dates do not care about your calendar
Load-test certificates, inspection intervals, service agreements and warranties all have dates attached. Few of them land conveniently.
The sites that stay ahead treat these dates as operational information, not admin. They review what is coming up over the next month or two, book the work while there is still choice about when to do it and keep an eye on anything that has slipped past its date.
Where FMC supports inspection records
FMC brings planned inspections and load tests into the same operational view as the rest of the service work. Through FMC Service Management, authorised teams can plan required inspections and load tests, see which jobs are planned, in progress, awaiting action or completed and retain accessible records of the work once it is done. Repairs and corrective actions identified during earlier service events can be managed through to completion, so a finding does not quietly disappear.
For customers, the FMC Customer Portal makes relevant inspection, load-test and compliance documentation easier for authorised users to retrieve, across one site or several. Renewals, SLAs and expiry dates sit within FMC Contract Management.
Software supports these decisions; managers, technicians and safety teams remain responsible for making them and for doing the work properly.
Where to start this week
You do not need a new system to improve tomorrow’s audit. Start with a few honest questions:
- Can we show the last inspection and load test for any forklift within five minutes?
- Which inspections fall due in the next 60 days, and are they booked?
- Do our findings have owners, or only descriptions?
- If a machine moved sites this year, did its records move with it?
- Does our service provider’s record match ours?
If any answer starts with “It should be…”, that is the place to begin.
A forklift is only as compliant as the record that proves it.

