The call came in at 07:12. A reach truck was down on aisle four, pallets stacked behind it and a picking wave waiting. The service desk logged it at 07:18. A technician arrived at 08:40, diagnosed a hydraulic fault and left a quotation with the site supervisor.
By lunchtime the dashboard looked respectable: response within SLA. The truck, however, was still standing. Parts had not been ordered. Approval had not been chased. Nobody had told the warehouse when they might expect the machine back.
That is the gap between response time and downtime. One measures how quickly someone arrives. The other measures how long the customer actually goes without the asset. Customers feel the second number. Many reports still celebrate the first.
Response time answers the phone. Downtime answers the floor
Response time is useful. It tells you whether the callout was acknowledged and whether a technician got to site within the agreed window. It is also easy to game, or at least to misunderstand.
A team can respond promptly, leave a quotation and still leave the machine idle for three days. On paper the SLA was met. On the floor the customer lost a shift of capacity. Forklift downtime tracking starts from that customer view: from the moment the asset stops working until it is genuinely available again.
The two measures are not rivals. They answer different questions. Response time checks attendance. Downtime checks restoration. Mixing them up makes service look healthier than the operation feels.
Define the clock before you argue about the numbers
Downtime conversations go wrong when people use the same word for different clocks. Did downtime start when the operator reported the fault, when the helpdesk logged it or when the technician arrived? Did it end when the repair was finished, when the customer signed or when the machine returned to productive work?
Without agreed definitions, every review meeting becomes a debate about the stopwatch rather than the delay. Pick plain meanings and stick to them. Elapsed downtime is the customer’s experience. Time attributable to a particular party is a management tool. Both matter. They are not interchangeable.
Write the definitions down somewhere people can find them. Then use them consistently in reports, SLA reviews and supplier discussions.
A status that hides the wait is not a status
“Awaiting parts”, “awaiting approval” and “awaiting feedback” can all be true. They can also conceal work that has not started. Useful forklift downtime tracking makes the wait visible: what is outstanding, who owns the next step, when the last action happened and when the next update is due.
If a quotation is sitting with someone who cannot approve it, the status should say so. If a part has been priced but not ordered, that is different from a part that is already on a supplier’s backorder. Honest status reporting shortens downtime because people stop reconstructing the same story every morning.
Measure restoration, not only attendance
A strong service review looks past “how quickly did we get there?” and asks “how long was the machine unavailable, and why?” Breakdown frequency, affected equipment, recorded downtime and recurring issues tell a clearer story than attendance alone.
Patterns appear once those records sit against the asset. The same truck may keep failing after a “completed” repair. One site may absorb longer waits because approvals take longer. One supplier may respond quickly and still leave equipment standing while paperwork moves around.
Those patterns are where management can intervene. Celebrating a green response metric while the same machines keep standing is how teams get surprised by customer complaints.
Separate what you can influence from what you cannot
Some downtime belongs to the service provider: late attendance, incomplete diagnosis, slow ordering. Some belongs to the customer: delayed approval, restricted access, machines that cannot be released during peak hours. Some sits with suppliers further up the chain.
Good reporting does not pretend every hour is equal. It attributes delay carefully enough that the next conversation is fair. A technician should not carry a three-day approval wait. A customer should not be told the SLA was fine when their truck was idle for a week.
Elapsed downtime still matters most to the person paying for the fleet. Attribution helps everyone decide where to change the process.
SLAs only help if they describe the experience that was sold
Many agreements define response or attendance windows. Fewer define what “back in service” means, how downtime is calculated or how exclusions work when access is refused. When the contract is vague, both sides fill the gaps with memory.
Clearer contracts record response, attendance, performance and reporting commitments against the agreement, alongside exclusions and supporting documents. Then the operational record can be checked against what was actually sold. That is how an SLA review becomes evidence rather than theatre.
Where FMC supports downtime visibility
FMC brings breakdowns, job progress and recorded downtime into one operational view. Through FMC Service Management, authorised teams can capture urgent callouts, assign responsibility and keep visibility until the issue is resolved, with job status showing what is planned, in progress, delayed, awaiting action or completed.
FMC Dashboards & Reporting helps teams examine breakdown frequency, affected equipment, recorded downtime and recurring operational issues, alongside service history and wider fleet performance. SLA commitments, warranties and related terms sit within FMC Contract Management, so operational numbers can be read against what was agreed.
Software supports these decisions; managers and teams remain responsible for defining the clocks, acting on exceptions and restoring machines to work.
Where to start this week
You do not need a perfect dashboard to improve tomorrow’s review. Ask a few practical questions about every standing machine:
- When did downtime start, by our agreed definition?
- What is the next action, and who owns it?
- Is this wait parts, approval, access or something else?
- How long has the customer been without the asset, not only how quickly we attended?
- Does our SLA language match the experience we are measuring?
If the answers live in three inboxes and a WhatsApp group, that is the first gap to close.
Customers do not feel your response time. They feel the hours the forklift stayed down.
