Client system · Field-service scheduling
It groups the work by where it is, and has the day ready before you start. You keep the call on what gets booked.
An Australian field-service business
Pump and plumbing service
One van, no dispatcher
Location-aware scheduling
Inside the system
The job console
Where the day gets decided, and who decides it.
Four screens: take a job in, review the run, re-order the day, see what is booked.
Built on tools the business already had
A short account of how the week used to be planned, and what the agent does with it now.
The owner on the diary, the maps tab, and what he still decides himself.
This is a one-van business. The owner is the person on the tools, the person answering the phone, and the person working out where to be tomorrow.
Every dot is a suburb the scheduler can already place on a map. The dashed circle is how far apart two jobs are allowed to sit on the same day. The gap between those two things is the whole problem.
It runs at five in the morning, Monday to Friday, so there is a day to look at rather than a day to build.
Warranty claims sync in from the builder form. The booking page writes straight in. Incoming email is read every fifteen minutes and anything that looks like a new job is added for you to check.
Each new suburb is placed on the map and remembered, so the planner is working from real locations rather than text in a cell.
Before it opens a new day, it looks for one you are already working near that job. It keeps a day inside a 50 km spread, budgets the job by type, and leaves half an hour between visits.
A second pass re-times each day nearest first, using real road distances rather than straight lines. The finished run lands on your approvals screen as a suggestion, and you are the one who books it.
The booking page reads the live calendar. Days that are already committed simply are not offered, and on the day below only one hour is left open. So what a customer is promised and what the van can do cannot drift apart.
Live capture of the customer-facing booking page.
The customer gets a text, not a phone call. The same text is how they change the time. That is what stops one reschedule turning into three voicemails from the side of the road.
“This here has freed me up.”
Live capture of the second step of the booking page.
Once you approve the run, the customer gets the time by text and the job goes in the calendar.
Every booked job gets a reminder text the afternoon before, with a number to call if it has to move.
A working system is never finished all at once. This is where it stands.
Jobs coming in from the form, the booking page and email
Locating jobs and building the run
Putting each day in road order
Confirmation, reminder and reschedule texts
Invoice and payment sync to the accounts
Quoting and pricing
No one timed this owner’s evenings before the build, so there is no saving to claim. What we can show is the numbers the system runs on, and what one recovered slot is worth in service capacity.
Measured
The job list left his head Three ways in, one list, every job with a status and an ID. The day can be looked at without rebuilding it from memory.
Planning moved off the evening The run is built at five in the morning. He reviews a day now instead of writing one.
Nearby work gets grouped A new job gets pulled onto a day the van is already in that area, instead of opening a fresh trip across the region.
Customers hear back without a phone call A confirmation text on booking, a reminder the day before, and a link to move the time. None of it interrupts the job in front of him.
This suits businesses whose day is decided by where the work is.
Trades and field-service operators planning their own runs.
One-van and small-fleet businesses with no dispatcher.
Anyone whose jobs arrive through several channels at once.
Owners doing the scheduling after hours.
Teams who want the day prepared, not decided for them.
We can map how jobs reach you, build the planning around your calendar and your addresses, and leave the approval with you. Built on your tools, owned by you.
Jobs arrived in three different places. Warranty claims came off a builder form. Others came by email or phone. So the real job list only ever lived in his head and on paper.
Planning happened after the last job. Open the diary. Look up each address. Guess the drive. Write out the day. Get the order wrong and you cross the region twice for nothing, and that is a morning you do not get paid for.
The service area runs about 184 km east to west and 270 km north to south. One working day reaches a small circle inside that.
Two jobs in the same area on different days means driving the same run twice. Grouping them is the difference between a full day and a wasted morning.
Across the completed job list, 40 of the 42 days with more than one job sat inside one or two suburbs. Grouping was already how a day paid for itself.
Visit length comes from the type of work, so a short callout and a full-day job are never budgeted the same.
Tuesday to Friday, in hourly slots from 7am to 3pm. The same window the planner builds runs to.
The gaps in the day picker are days already full. Nobody has to check a diary to find that out.
On the day shown, seven of the eight slots are already gone. One hour is offered because one hour is what is left.
The confirmation carries a reschedule link. It belongs to one job and it expires, so an old text cannot move a new booking.
When a customer picks a new day, the job returns to your queue and gets planned against location again.
Anything urgent. No water or a gas job goes to the phone, not a form
Deciding a day has gone wrong and needs re-planning
The first reply on a new warranty claim, drafted for you to send
Telling the warranty partner when a job is logged
A maintenance handover document for the customer
Scheduling for more than one van
A status page the customer can check
Modelled, not measured
What the arithmetic is built from
A warranty visit is budgeted at one hour, plus a half-hour buffer.
The planner fills an eight-hour day and will not put two jobs more than 50 km apart on the same day.
The completed job list mixes short callouts and longer visits; each type has its own length in the scheduler.
Pulling a nearby job onto a day the van is already in that area saves the second trip. That is about an hour and a half of the day returned.
An hour and a half is one more warranty visit the same day could hold, without a longer day or more driving.
One extra visit a week is one extra visit the same van, the same day and the same driving already cover. Multiply that by the weeks in a year to size what grouping is worth to a business that owns its own pricing.
This is arithmetic on the system’s own settings, not a result. No hours saved and no revenue gained are being claimed here.
The decision stayed with him The agent prepares the day; the owner still chooses what gets booked. Leaving that call where it was is what makes the system something he uses rather than argues with.
2026-08-21
Read the case study