
It is ten past seven on a Monday, and the service coordinator has three breakdowns before her first coffee. One came in by phone to the switchboard, one arrived as a WhatsApp voice note to a technician who is on leave, and one is an email from a customer who says they reported the fault on Friday afternoon. Nobody can find Friday’s call.
By nine, two technicians are on the road. One has the customer’s name but not the fleet number. The other is heading to the right site, but the wrong warehouse. In the office, someone is already asking whether last week’s completed jobs have been invoiced.
Every person in this story is working hard. The work itself just has no agreed route from the moment a customer needs help to the moment the record is closed.
A workflow is just the route the work takes
“Workflow” can sound like a word for consultants and flowcharts. In a service department it is something simpler: the path a job follows, and the hands it passes through, from call-in to close-out.
Every service operation already has one. The question is whether it was designed or whether it grew. A workflow that grew tends to live in people’s heads. It works well when the experienced coordinator is in the office and the regular technician knows the customer. It works less well on a public holiday, during peak season or the week a new branch opens.
A designed field service workflow does not need to be complicated. Most dealers and service providers can describe theirs in four steps. Job logged. Technician assigned. Work completed. Close and report. The detail that matters sits in the handovers between them.
Step one: the job has to exist before it can be managed
The first handover is from the customer to the business, and it is where many problems begin. A request that arrives by phone, email, message or a word in the corridor is not yet a job. It is a conversation, and conversations are easy to lose.
A useful job record captures the basics at the start: the customer, the site, the asset, the priority and what is actually wrong. “Forklift not working” is a start. “Fleet number 14, mast won’t lift, standing since 06:00, second shift affected” is a job someone can act on.
Logging every request in one place also gives the clock a fair starting point. Response times mean very little if half the requests only become official when somebody gets round to writing them down.
Step two: the right technician, with the right information
Assigning a job is more than choosing whoever is closest. It means matching the work to the skills, considering what is already scheduled and making sure the technician leaves with what they need: the asset history, the site contact, the access requirements and any open actions from the last visit.
A technician who arrives knowing the truck had the same fault three weeks ago is already halfway to a better repair. One who arrives with only an address is starting from scratch, and sometimes in the wrong building.
This is also where workload becomes visible, or doesn’t. When assignments live in a group chat, it is hard to see who is overloaded, who is waiting on parts and which planned services are quietly slipping to make room for breakdowns.
Step three: capture the work where it happens
The third handover is from the technician back to the business, and it is the one most often done twice: once on site and again later from memory. Labour, findings, readings, parts used, photographs and the customer’s signature all describe the same job. They are most accurate when they are recorded against that job while the machine is still in front of the technician.
Findings deserve particular care. The worn tyre, the leaking cylinder and the chain that will need attention next month are not just notes. They are the next quotation, the next service or the next breakdown, depending on what happens to them.
Step four: closed is not the same as finished with
A job is not really closed when the technician drives away. Close-out is where the record becomes useful to everyone else: the customer, who needs to know what was done; the office, which needs to invoice it; and the next technician, who will rely on the asset history it adds to.
It is also where outstanding actions either get an owner or quietly disappear. A good close-out asks two questions. Is the information complete? And is anything still open that someone needs to follow up?
Over time, closed jobs are what turn into management information: response times, first-time fix, job completion and how service commitments are actually being met.
Why scale exposes every weak handover
A loose workflow can survive in a small team because people compensate for it. They remember, they phone each other and they fix gaps as they appear.
Add technicians, customers or branches and that informal glue stops holding. Each branch develops its own habits. One logs jobs centrally, another lets technicians take calls directly. One closes jobs the same day, another batches them on Friday. Managers end up comparing branches that are not measuring the same thing.
Scaling a service operation is less about adding people and more about making sure every new person follows the same route. The steps can stay simple. They just need to be the same everywhere.
Where FMC fits in
FMC follows this same route. For dealers and service providers, it connects the job logged, the technician assigned, the work completed and the close and report in one traceable workflow, linked to the customer, the site and the asset.
FMC Service Management keeps breakdowns, planned services, inspections, repairs and follow-up work visible from the moment they are raised until the outcome is recorded, showing what is planned, in progress, delayed or completed. Technicians capture labour, findings, photographs, parts and signatures digitally, and completed job cards are distributed to the customer once the office closes the job. Across branches, the same processes create a common standard, so activity and outstanding work can be compared fairly.
The software supports the workflow. Deciding how jobs are prioritised, who owns each step and what good service looks like remains with the people running the operation.
Mapping your own workflow
A useful first exercise needs nothing more than a whiteboard and an honest hour with the people who do the work. Take one recent breakdown and trace it:
- Where did the request first arrive, and how long before it became a job?
- What did the technician know before they reached the site?
- Where were the findings, photographs and signature recorded, and when?
- When was the job closed, and what was still open at that point?
- Would another branch have handled the same breakdown the same way?
Wherever the answer is “it depends who was on duty”, there is a handover worth tightening.
A service operation scales when every job takes the same route, no matter who picks up the phone.

