“The technician was there.”
“The quote was sent.”
“We’re waiting for feedback.”

Each of these statements may be true. None, on its own, tells a customer when their forklift will be back in operation.

In fleet and service management, activity is easy to report. Establishing who owns the next step, what is holding it up and when it should be completed takes more discipline. Without that clarity, a breakdown can move between departments while the machine remains exactly where it was.

Accountability starts with making those responsibilities explicit. Every unresolved issue needs an owner, an agreed next action and a way to establish whether that action happened.

Every handover needs someone to accept responsibility

A breakdown can involve an operator, a site manager, a service administrator, a technician, a parts department and someone authorised to approve expenditure. Each person may complete their own task correctly, yet the overall repair can still stall between them.

Consider a typical scenario: a technician diagnoses a fault and requests a replacement part. The parts department provides pricing. A quotation is prepared and emailed to the customer. Two days later, the machine is still standing because the quotation went to someone who cannot approve it.

The diagnostic work was done. The price was obtained. The email was sent. But who was responsible for confirming that the quotation reached the decision-maker and following up on the approval?

A reliable handover identifies the person taking the next action and makes sure they have the information and authority to proceed. Copying several people into an email does not establish who has accepted that responsibility.

“Waiting” needs an explanation and a next action

“Awaiting parts” can describe a genuine supply constraint. It can also hide an order that has not yet been placed. “Awaiting customer approval” might mean a quotation is under review, or that nobody has confirmed its receipt.

Useful status reporting makes the difference visible. It should explain what is outstanding, who is responsible for progressing it, when the last action took place and when the next update is due.

Where a delivery date is uncertain, that uncertainty should be recorded honestly. The responsible person can still commit to checking availability or updating the customer at an agreed time. Accountability includes managing a dependency even when the final outcome is outside that person’s control.

A status should give the next person enough information to act. Otherwise, every review meeting starts with reconstructing the same story.

Evidence makes accountability fairer

Service performance discussions become difficult when the only available evidence is someone’s recollection of a phone call. A customer remembers reporting the breakdown in the morning. The service team remembers receiving the instruction later. The technician recalls recommending further repairs during an earlier visit, but the recommendation cannot be found.

A consistent service record provides a firmer basis for the discussion. Job details, recorded times, findings, photographs, work descriptions and customer acknowledgements help establish what happened and what was communicated.

That record also protects people who have fulfilled their responsibilities. A technician should not carry responsibility for a delay caused by an outstanding approval. A supplier’s performance should be assessed with visibility of access restrictions, changes in scope and other relevant dependencies.

Evidence needs context and review. An incomplete record or an incorrect timestamp should be investigated before conclusions are drawn. Fair accountability depends on the quality of the information as well as its availability.

A completed job needs a clearly recorded outcome

A job marked “completed” should have a defined meaning. Was the fault resolved? Was the work tested? Were findings explained to the customer? Does any further action remain outstanding?

A technician may complete the assigned repair and identify a separate issue that needs a quotation. Closing the original job can be appropriate, provided the additional requirement is recorded and someone takes responsibility for progressing it.

The problem arises when closing the job also makes the unresolved issue disappear from attention. A signed job card records an acknowledgement; it does not, by itself, establish that every recommendation has been actioned.

Businesses need clear completion standards and a dependable way to carry outstanding work forward. Otherwise, an apparently healthy list of closed jobs can coexist with customers still waiting for answers.

Management must own the conditions for delivery

Accountability applies across the operation, including leadership. Technicians need clear instructions, realistic schedules, suitable support and access to the information required to perform their work. Administrators need defined responsibilities and a route for escalating issues they cannot resolve.

Managers, in turn, need to make decisions when work is blocked. Repeatedly asking for an update on an unresolved problem adds little if the team is waiting for management to approve the next step.

When the same delays recur, the review should examine workload, capacity, training, approval processes and supplier dependencies. Holding someone responsible for delivery also requires giving them a workable route to deliver.

A useful management question is: “What decision or support is needed from me to move this forward?”

Performance measures should explain the service experience

The number of jobs closed is useful, but it cannot describe service performance on its own. A team can close many jobs while repeat faults, unresolved recommendations or long periods of downtime continue to frustrate customers.

A balanced review considers the time taken to respond, the time taken to restore equipment, the reasons for delays, the quality of records and whether follow-up actions were completed. Measures should have clear definitions, particularly where contractual response or resolution commitments are involved.

Elapsed downtime and the time attributable to a particular party answer different questions. Customers need to understand how long equipment was unavailable. Managers also need to understand which parts of that period they could influence.

Used carefully, these distinctions help teams identify where intervention will make a practical difference.

Where FMC supports accountability

FMC brings asset information, service activity and supporting records into a connected operational platform. Digital job cards, technician-captured information, photographs and signatures help create a clearer record of the work performed. Completed job cards can be automatically emailed to customers and relevant internal recipients, supporting the handover of information.

Service history, downtime reporting and SLA monitoring give managers information they can use to review performance, question recurring delays and follow up on unresolved issues. A shared operational record makes it easier to establish the facts without relying entirely on separate messages and individual recollections.

The organisation still needs to define responsibilities, agree working standards and act on what the information reveals. Software supports those decisions; managers and teams remain responsible for making them.

Make accountability part of the daily workflow

A practical starting point is to review every machine standing and every unresolved service issue against a few questions: who owns the next action, what must happen, when is it due, and what will demonstrate completion? If progress is blocked, there should be a clear route to someone who can make the necessary decision.

These questions belong in the daily workflow, while there is still time to intervene. Waiting until a customer escalates a complaint makes the conversation harder and leaves the underlying delay untouched.

A machine cannot return to work on an explanation alone. Someone has to own the next action—and see it through.