Technician beside an equipped service van outside a forklift workshop, illustrating a forklift planned maintenance schedule.

Monday morning briefing. Three machines are due for service this week. Two of them were due last week. One of those was due the week before that. Nobody argues with the list. The list just keeps sliding.

A reach truck that should have been serviced sits in the busy aisle because a breakdown call came in first. The planned job is still on the board. It has simply moved three days to the right, again. By Friday the board looks organised. The overdue column does not.

Planned work loses to the loudest call

Breakdowns arrive with urgency attached. A standing machine, a frustrated site and a technician already on the road are hard to ignore. Planned maintenance rarely shouts. It sits on a calendar, a spreadsheet or a reminder that felt optional the moment something louder appeared.

That trade-off is understandable in the moment. Over a month it becomes a pattern. Services slip behind callouts, then behind the next callouts, until “due soon” is a polite label for work that is already late.

The danger is not that teams prefer breakdowns. It is that planned work has no equal claim on attention unless someone can see it as clearly as the emergency.

A schedule that only one person trusts is not a schedule

Many fleets do have a maintenance plan. Hours are estimated. Dates are written down. A supplier is named. The problem is where that plan lives: in one coordinator’s spreadsheet, a supplier’s diary or a printed wall chart that was last updated when the floor was quieter.

When the plan lives in one place, only one person can defend it. If that person is on leave, chasing a quotation or covering a late shift, the planned jobs lose their advocate. Technicians do what the open tickets demand. Sites keep using the machines that still move. The schedule becomes a hope rather than a shared commitment.

A useful test is simple. If the coordinator disappeared for a week, would the next person know which services are due, which are overdue and which can safely wait?

Date due is not the same as work done

Marking a service as “due” is the easy half. Closing it on time is the half that protects uptime. Between those two points sit allocation, attendance, parts readiness and a clear record that the work was finished — not merely intended.

Without that trail, overdue services hide in polite language. “Booked for next week.” “Waiting on the supplier.” “We’ll catch it after peak.” Those phrases can be true. They can also stretch for months while the machine keeps accumulating hours it was never meant to run without attention.

A reliable forklift planned maintenance schedule treats the due date as the start of a visible job, not a note on a calendar. Once the service is raised, it needs an owner, a status and a next action that other authorised people can find.

Hours and dates both matter — if anyone can see them

Some fleets plan by calendar intervals. Others plan by operating hours. Most need both, because a quiet machine and a hard-working one do not age at the same pace. The method only helps if the next due point is visible before the machine is already overdue.

Operating information that sits in a separate hour book, a printout nobody opens or a notebook in a supervisor’s drawer does not feed the schedule. The schedule then drifts on dates alone, while the hardest-working units quietly outrun their service intervals.

Bringing asset identity, location and service history into one place does not invent the maintenance plan. It stops the plan from arguing with itself across three files.

Reactive and planned work need the same queue

The strongest schedules do not hide planned services in a different system from breakdowns. When both live in one operational view, planners can see the real load: which technicians are already committed, which sites are waiting and which planned jobs are about to tip into overdue.

That view also makes trade-offs honest. If a breakdown must take priority, the delayed service stays visible as delayed — not deleted from memory because it lost the morning’s scramble. The team can reallocate, move the date with intent or flag the risk to the customer. What they cannot do, once the work is visible, is pretend the slip never happened.

Customers notice the difference. A supplier who can show planned work progressing alongside reactive callouts looks organised. A supplier who only appears when something has already failed looks reactive, even when the planned work was sincerely intended.

Where FMC supports planned maintenance visibility

FMC does not replace the judgement of when a machine should be serviced. What it does is keep planned and reactive work in the same clearer operational picture.

FMC Service Management gives authorised teams a way to organise planned maintenance, breakdowns, repairs and follow-up work. Service scheduling supports recurring services and required maintenance around operational dates, priorities and commitments. Planned services can be set around due dates, operating requirements and agreed service commitments, while job progress stays visible across planned, allocated, in progress, delayed, awaiting action and completed. Stronger service planning means keeping planned maintenance and reactive work organised around clear operational priorities — so a planned job is less likely to disappear behind the next loud call.

FMC Dashboards & Reporting helps teams monitor planned maintenance, completed services, outstanding work and recorded service activity, and to recognise overdue activity sooner rather than at the next awkward review. FMC Asset Management gives every machine a clearer digital identity and central record, so the schedule sits against known assets, locations and lifecycle history instead of a half-remembered list.

Software can make the due work visible. People still decide what to prioritise on the day.

A practical check before next week’s board meeting

Before the next planning conversation, it is worth asking a few plain questions:

  • Which services are due in the next seven days, and which are already overdue?
  • Can more than one authorised person see that list without opening someone’s personal spreadsheet?
  • When a breakdown takes priority, does the delayed service stay visible as delayed?
  • Are the hardest-working machines on intervals that match how they are actually used, not only a calendar date?
  • After a service is completed, is the outcome recorded where the next planner will look?

If most answers still depend on one inbox or one wall chart, the board will keep looking tidy while the overdue column grows.

A maintenance plan only works when planned work is as visible as the breakdown that tries to push it aside.