
It is Monday morning and the regional operations meeting starts in twenty minutes. Three site managers have sent their fleet reports. One arrives as a PDF, one as a spreadsheet with six tabs and one as a WhatsApp photo of a whiteboard.
The main distribution centre reports 14 hours of forklift downtime for the month. The second warehouse reports three days. The newest branch reports “two breakdowns, both sorted”. Somebody asks which site has the bigger problem, and the room goes quiet while everyone tries to work out whether hours, days and “sorted” can be compared.
They can’t. And by the time someone has rebuilt the numbers, the meeting has moved on to the next item.
More sites, more versions of the truth
A single-site fleet is hard enough to keep on top of. Add a second site and something subtle happens. Each site develops its own way of doing things, and each way makes perfect sense locally.
One site logs a breakdown when the operator reports it. Another logs it when the service provider is called. One counts downtime until the technician leaves. Another counts it until the machine is back on shift. One keeps service records in a ring binder because the workshop has no reliable signal. Another relies on the supplier’s monthly report.
None of this is carelessness. It is what happens when good people solve problems with the tools in front of them. The result, though, is that head office receives several accurate reports that cannot be added together.
The comparison problem
Multi-site fleet management is mostly a comparison problem. Managers want to know which site is running well, which is struggling and where money or attention would make the biggest difference.
That only works if the sites are measured the same way. A site with high recorded downtime may simply be the most honest one. A site with suspiciously clean figures may be under-recording. A site with high costs may have the oldest machines, the hardest shifts or the most expensive supplier, and each of those calls for a different response.
Without shared definitions, comparisons tend to reward the site that reports neatly rather than the site that runs well. That is unfair to the people doing the work and unhelpful to the people making decisions.
Agree the definitions before you compare the numbers
The first fix costs nothing and needs no software. Agree what the common terms mean across every site:
- When does a breakdown start: when it is reported, logged or acknowledged?
- When does it end: when the technician leaves, or when the machine is back in use?
- What counts as a service, an inspection and a repair?
- Which costs belong to the machine: parts, labour, call-outs, hire replacements?
- Which machines are included: owned, leased, rented and hire units?
Write the answers down, share them with every site manager and service provider, and treat them as the rules of the game. It sounds bureaucratic. It saves hours of argument later.
One record per machine, wherever the machine is
The second fix is making sure each machine has one record that follows it. Forklifts move between sites more often than head office realises. A reach truck is lent to the busier branch for peak season. A battery is swapped into a truck at another facility. A hire unit arrives at one site and is quietly transferred to another.
If each site keeps its own list, every move creates a gap. The history stays behind at the old site, and the new site starts from scratch. Months later, nobody can say whether a machine’s repeat faults started before or after it moved.
When the record belongs to the machine rather than the site, the history travels with it. Allocation changes, but the service history, documents and costs stay in one place.
Let the sites run their day, and let head office see the pattern
Site managers and head office need different things. A site manager wants to know what is standing today, what is booked for tomorrow and who is attending to it. A regional or national manager wants to see trends: which sites have recurring failures, where costs are climbing and whether suppliers are meeting their commitments across the board.
Both views should come from the same recorded information. If the site manager keeps one system for the day and head office receives a monthly summary built from another, the two will drift apart. The best multi-site arrangements let each site work in its own detail while the consolidated view builds itself from that same work.
Where FMC supports multi-site fleet management
FMC is built for fleet customers who need one connected view of their materials handling fleet across every site, covering assets, service activity, suppliers, compliance and costs. FMC Asset Management gives every machine a central record, including its allocation across branches and sites, so the history stays with the machine when it moves.
FMC Dashboards & Reporting lets authorised users review information for an individual location or consolidate it for a broader view, and compare recorded information across branches and facilities. Breakdowns, downtime, service activity, compliance and costs can be reviewed by site or across the operation, without rebuilding the same report from several spreadsheets.
Software keeps the information consistent. Managers still decide what the comparison means and what to do about it.
Where to start this week
Before the next regional review, try a simple test:
- Ask each site how it defines downtime. Do the answers match?
- Pick one machine that has moved between sites. Can you see its full history?
- Check whether hire units and borrowed machines appear in any site’s figures.
- Ask each site for last month’s fleet costs. How long did it take, and what was included?
- Compare one measure across all sites and ask whether the difference is real or just recorded differently.
If the answers vary by site, the first job is not to improve the worst performer. It is to make sure everyone is keeping score the same way.
Comparing sites is only fair when every site is measured by the same ruler.

