Scheduling is the daily mechanism of a field service franchise. Every working day, each job has to be assigned to an operative, placed in a sensible order and communicated to the person who will do it. In a lot of franchise networks this still happens on a whiteboard, in a spreadsheet, or through a chain of phone calls and text messages the evening before.
Those methods are not wrong. They work well enough for one or two operatives, which is why most franchisees start with them. The trouble is that they stop working gradually rather than suddenly, so nobody notices the point at which the schedule became the bottleneck.
Where the time actually goes
It helps to separate the cost of manual scheduling into three parts, because they behave differently.
The evening rebuild. Somebody, usually the franchisee, sits down each evening and assembles tomorrow. Which jobs, which operative, what order. For a franchise running three operatives and fifteen to twenty jobs a day, this is commonly thirty to forty-five minutes. That is a fixed cost: it is paid every working day whether the day is busy or quiet, and it is paid by the most expensive person in the business.
The mid-day change. A customer cancels at 8:30am. A job overruns. An operative is off sick. Each of these means re-planning part of a day that has already started, and doing it by phone while the operatives are driving. The cost here is not the planning time so much as the knock-on: the job that gets moved to a day that was already full, the operative who drives to an area for one job that no longer exists. The route planning consequences of a reshuffled day are usually worse than the original plan.
The forgotten job. This is the expensive one. A booking taken by phone, written on a notepad, never transferred to the sheet. The customer waits in, nobody arrives, and the franchise has lost not just one job but, quite often, the customer. It is hard to put a number on this because the franchise rarely finds out how many times it happened. When a franchise does go through its own complaint records, missed appointments are usually near the top, and the cause is rarely that the operative forgot. The job never reached them.
What a scheduling tool has to do
The feature lists for scheduling software tend to be long. For a network of vans, most of the value comes from a short list of things done properly.
One calendar that everyone looks at. The franchisee, the operatives and head office all see the same jobs, in day, week and month views. Changes made by one person are what the next person sees. This sounds obvious, and it is the single thing a whiteboard cannot do.
Jobs with a time, and jobs without one. A boiler service is booked for 10am. A window cleaning round is booked for Tuesday, in whatever order suits the round. A scheduling tool that forces every job into a clock slot creates fiction: the operative is given times that nobody intends to keep. The better approach is to let a job be timed or flexible (morning, afternoon, any time), and to let flexible jobs be dragged into an order around the timed ones. Jobs360 works this way: flexible jobs sit in their own lane on the calendar, and the operative or manager arranges the day by hand.
No double booking. When a job is created or dragged to a new slot, the tool should check the operative’s other work for that day and refuse an overlap, naming the clash. It is a small thing that prevents a whole category of mid-day phone calls.
The operative’s day on their phone. Customer name, phone number, address with directions, the work to be done, any notes. Laid out for one person and one day. A printable version for those who prefer paper, because some do, and insisting otherwise slows adoption.
Completion recorded where the work happens. When the operative marks the job done, with photos and a signature where the service requires them, the office knows immediately. That completion is also the starting point for the invoice, which is where real-time job data starts paying for itself.
What it does not have to do
It is worth being clear about automatic route optimisation, because it is often presented as the point of scheduling software.
Computing the shortest route through a day’s jobs is a real and useful capability, and for networks with long rounds it can be worth a lot. But it is a separate problem from scheduling, and most franchises get most of the available gain without it. An operative who can see the whole day on one screen, with addresses, and can drag the flexible jobs into a geographic order in a minute, will produce a route close to what an algorithm would. The large losses described in the route planning article come from booking-order scheduling, where nobody considered geography at all, not from imperfect hand ordering.
So the sensible sequence is: get everyone on one calendar first, make flexible ordering easy, and treat automatic routing as a later refinement if the numbers justify it. Jobs360 does the first two and not, at present, the third.
Before and after
A fair comparison for a three-operative franchise looks something like this.
Before: thirty to forty-five minutes each evening building tomorrow. A cancellation means phone calls to two operatives and a rewritten sheet. The operative’s information is a printout, correct as of last night. Head office finds out what happened at month end.
After: the franchisee books jobs as they come in, and tomorrow is mostly built by the time the evening arrives. A cancellation is a drag on the calendar, and the operative’s phone reflects it. The operative’s information is current. Head office can see today’s jobs across the network without asking anyone.
The time saved is real but modest, perhaps three to four hours a week for the franchisee. The larger effects are the ones that are harder to count: the jobs that are no longer forgotten, and the evenings the franchisee gets back.
What it means for head office
For the franchisor, scheduling is less about any one franchise’s day than about what becomes visible when every franchise runs on the same calendar.
Head office can see scheduled and completed jobs across the network, the cancellation rate by franchise, and which operatives are carrying the work. It can push a job to any franchise when an enquiry lands in the wrong territory. It can print a schedule for any operative over any period, which turns out to matter for audits and disputes. None of this requires a report to be compiled; it is simply the by-product of the jobs having been booked in one system.
That network view is the reason scheduling belongs in the franchisor’s software decision rather than being left to each franchisee to solve separately. Thirty franchisees choosing thirty different tools produce thirty different pictures, and head office sees none of them.
Jobs360 gives franchisees a shared calendar, timed and flexible jobs, and an operative app that shows each person their day. See all features or get in touch to see it in action.
