The counterbalance truck in the dispatch bay stopped at 07:40 on a Thursday. By 08:00 the breakdown had been logged. By 11:30 the warehouse manager was on the phone to the service provider, asking why nobody had arrived yet.
“Our agreement says four hours,” the service coordinator explained. “Four hours to attend, during business hours. We’re still inside that.”
The warehouse manager had always understood it as four hours to have the truck working again. Both companies had signed the same forklift service level agreement. Neither person had read that clause since the day it was signed.
Most contracts are read twice
A service agreement usually gets serious attention on two occasions: when it is negotiated and when something goes wrong. In between, it lives in a folder, an email attachment or a shared drive that takes a small archaeological dig to find.
Meanwhile the operation runs on what people believe the contract says. The site team remembers “four-hour response”. Procurement remembers the rate. The service provider remembers the exclusions. Each version is partly right, and that is precisely the problem.
An agreement that nobody can quote accurately is hard to manage. It is, however, very easy to argue about.
Response, attendance and repair are three different promises
The most common misunderstanding sits in a single word. “Response” can mean a call returned, a job acknowledged, a technician on site or a machine back at work. Those are very different moments, and the gap between them can be most of a working day.
A useful agreement says which clock it means, when that clock starts and whether it pauses after hours, over weekends or while parts are on order. If those definitions are vague, the reporting will be vague too, and both parties will be able to show they were right.
It is worth reading the response clause aloud in a meeting with the people who actually live with breakdowns. If the room disagrees on what it means, the contract is not doing its job yet.
Inclusions and exclusions decide the invoice
The next surprise usually arrives with the invoice. Tyres, forks, batteries, attachments, operator damage, consumables and callouts outside agreed hours are typical places where a maintenance agreement and a site’s expectations quietly part ways.
None of this means the contract is unfair. It usually means the exclusions were agreed by people who are not the ones signing job cards. When the workshop or the site manager cannot see what is covered, every disputed line becomes a phone call, and every phone call becomes a delay.
Knowing what is excluded before a job is approved is far cheaper than discovering it afterwards.
Which machines are actually covered?
Equipment schedules age faster than the agreements attached to them. Machines are added, moved to another site, replaced or returned. A truck that arrived three months after the contract started may never have made it onto the schedule. Another may still be listed, and billed, long after it left.
The schedule is the bridge between the contract and the floor. If the fleet number, site and coverage on paper do not match the machine in the aisle, the service level being measured is not the one being delivered.
Dates are obligations too
Commencement and expiry dates get attention. Review dates, notice periods, warranty end dates and rate adjustment dates often do not. A contract that renews automatically because nobody noticed the notice window has not really been renewed. It has simply carried on.
Each date is a decision point: renegotiate, extend, retender or accept the terms as they stand. Those decisions are easier when the date arrives with three months’ warning rather than three days’.
Measure the promise, not the paperwork
Once the terms are clear, the question becomes whether they are being met. That needs service records that match the contract’s own definitions: when the breakdown was logged, when the technician attended, when the machine returned to work and which agreement the asset falls under.
Without that link, supplier reviews tend to rely on recollection. The site remembers the bad week in winter. The provider remembers the hundreds of jobs closed on time. Both are partly true, and neither helps anyone decide what to improve.
Consistent records make the conversation fairer. They show where the provider delivered, where the site delayed access or approvals and where the agreement itself needs a clearer definition.
Where FMC supports contract visibility
FMC Contract Management keeps the essential agreement information in one accessible record. Reference numbers, responsible parties and supporting documents sit alongside the equipment, sites and customers covered, together with the agreed rates, service responsibilities, inclusions and exclusions. Response, attendance, performance and reporting commitments can be recorded against the appropriate agreement, while commencement, expiry, review and renewal dates stay visible before important deadlines are overlooked.
Service activity recorded in FMC can then support supplier and SLA reviews with consistent operational records rather than memory. For fleet customers working with several providers, that means tracking SLAs and contract compliance from one connected view.
Software keeps the terms visible. Managers and suppliers remain responsible for agreeing them clearly and honouring them.
Where to start this week
Take your largest service agreement and test it against a recent breakdown:
- What exactly does the response commitment measure, and when does the clock start and stop?
- Which items on the last three invoices were excluded from the agreement, and did the site know that beforehand?
- Does the equipment schedule match the machines currently working on each site?
- When is the next review, notice or renewal date, and who owns that decision?
- Could you show the provider, from records rather than memory, how last quarter’s service compared with what was agreed?
If the answers take a week to assemble, the contract is not yet a working document.
A service agreement only works when the people living with it know what it promises.
