You get more jobs out of the same engineers by taking the waiting and the rework out of their day. That means a route that gets redone when the day changes, the job history and access details on their phone before they arrive, the next job sent without ringing the office, and paperwork finished at the job so it becomes an invoice the same day. Hiring comes after that.
When things get busy, the first answer we hear from field service owners is "we need another engineer." And I get it, because the diary is full and customers are waiting. But a new engineer is a van, a phone, tools, training and a few months before they know your customers.
Where the day actually goes
So picture a normal day for one of your engineers. The schedule was built last night, and the first job is across town because that's where it landed on the spreadsheet. Then a customer cancels at nine, the office rings round to fill the gap, and the engineer drives past two jobs to get to a third.
Then they get to site and the access code isn't on the job. They ring the office, the office rings the customer, and that's twenty minutes in the van. Then they open the unit and it needs a part that isn't on the van, and nobody told them this site had the same fault last time. So that's a return visit booked.
And then they finish and wait for someone to tell them what's next. In the evening they fill in job sheets at the kitchen table. The customer's signature didn't get taken, so someone chases it next week. And the job sheet sits in a tray for days before anyone turns it into an invoice.
And the engineer did nothing wrong in any of that. All of it comes from how the day was set up around them.
A table you can run your own day against
Go through this with your operations team and be honest about which rows you recognise.
| Where the time goes | What usually causes it | What fixes it |
|---|---|---|
| Driving between jobs | The route is set the night before and not redone when a job moves or cancels | Scheduling and dispatch re-plans the day when something changes and keeps nearby jobs together |
| Going back a second time | The engineer didn't have the site history, the right part or the access details | The field app shows history, notes, parts and access info before they arrive |
| Waiting in the van for the next job | The next job only comes when someone in the office is free to ring | The next job goes straight to their phone, and the office can see who's free |
| Calls about where the engineer is | The customer has no idea when anyone is turning up | Customer updates send on the way and running late messages |
| Paperwork in the evening | Forms are on paper or typed up later | Job sheet, photos and signature done on the phone at the job |
| Chasing sign-off | Signature or client reference not taken on site | Signature captured at the job, and the back office chases anything still missing |
| Finished but not invoiced | The job sheet waits until someone types it up | The completed job sheet becomes a draft invoice for a person to check and send |
| Nobody seeing any of this | The numbers only come together at month end | Insights shows jobs per engineer, return visits and unbilled work today |
You don't need every row. Pick the two that hurt the most.
A worked example with made-up numbers
This is an example, not a client, and the numbers are round so the sum is easy to follow.
Say you've got 20 engineers and each one does four jobs a day. That's 80 jobs a day, or 400 a week. Say each engineer loses about an hour a day to extra driving, waiting on the office and going back to jobs that should have been done first time.
Now say you win back half of that hour. Across 20 engineers that's ten hours a day. If a job takes about an hour and a half with travel, that's six or seven extra jobs a day, so somewhere around 30 a week.
One engineer in this example does 20 jobs a week. So getting back half an hour each is roughly the same as one and a half extra engineers, without the vans or the training. Rough numbers, but you get the point. Put your own in and see where it lands.
Where to start
The first thing we'd do is find out where the time really goes. Two weeks of your own job data, plus asking the engineers, usually tells you more than any report. Engineers know exactly which jobs they go back to and why.
Then you fix the biggest leak first and leave the rest alone for now. We wrote more about picking that first thing in what to automate first in a service business. And then you try it with one team or one area before the whole business moves over. If you're worried about changing systems mid-year, this piece on switching without breaking things goes through how we do it.
We've done this kind of build before. Rota is an app we built for domestic cleaning companies. It plans recurring visits, gives each cleaner their day with access instructions and a checklist per home, takes photos and notes as evidence, lets them report a problem from the visit and works offline when there's no signal. It also records the money due for each finished visit and shows the owner what needs attention today. Cleaning and engineering are different trades, but the day has the same shape.
What stays with a person
Some decisions should never be handed to a system. The AI doesn't price jobs, so quotes stay with your estimators or your engineers. Safety calls stay with the engineer on site, because they're the one looking at it.
Complaints stay with a person too. A customer who's annoyed wants to talk to someone who can fix it. And anything that goes to a customer or moves money gets signed off by someone on your team first. We wrote about where we draw that line in decisions to keep human in AI workflows.
When it isn't worth fixing with software
If you've got a handful of engineers and one person runs the diary in their head and it works, leave it. You won't get enough back to make a new system worth the change.
If your work is mostly long projects, where an engineer is on one site for weeks, most of this doesn't apply. There's no daily route to fix and no next job to wait for.
And if your engineers are sat waiting because there isn't enough work coming in, that's a sales problem. More capacity won't help until the diary is full. Fix the pipeline first, then come back to this.
If you want a second pair of eyes
If the table looked familiar, book a 30-minute call. We'll look at how your jobs move from the first call to the invoice and show you what we'd hand over to AI first. If it turns out you don't need us, we'll tell you that too.
