On this page
Scheduling and dispatching run on written rules
Field service scheduling and dispatching work when they run on written rules instead of one person's memory. Mine are seven: route every job by where the crew starts, plan two weeks ahead, ask the crew before the customer, put every promise on the calendar the same hour, keep one system of record, hold a labor-hour floor on every job, and write down the hard cases. A coordinator then runs a 20-minute routine each morning.
I run operations for a residential and light-commercial cleaning company. When I started, tomorrow's calendar was built today, by the owner. On these rules it is built two weeks ahead, on routes, and a coordinator runs it.
Two different jobs
Scheduling decides which job happens on which day, with which crew, in which order, days or weeks ahead. Dispatching is the same-day work: getting the crew out with what they need, and handling the sick call, the late finish and the customer who wants to move. Most small field-service companies blend the two, so the owner does both every evening. Separate them and the dispatch part shrinks to minutes, because the schedule already answered most of the questions.
Signs your scheduling is the problem
- Rule 02
Tomorrow's calendar is built today, or this morning.
- Rule 01
Crews cross the service area more than once a day.
- Rule 03
Customers hear a date before anyone has checked that a crew can do it.
- Rule 04
A promise made on the phone is not on the calendar an hour later.
- Rule 05
Invoices are typed after the job, and some visits are never billed or are billed twice.
- Rule 06
Nobody can say what a given job earned against the hours it took.
Two or more of those and the fix is in the rules below, not in a new app.
The 7 rules
- Route by home base. Assign every job by where the cleaner or technician starts the day, in geographic clusters. A crew stays inside one cluster for the day. The rule I hold: never send a crew across the service area for a single job.
- Plan two weeks ahead. Move the working calendar from day-of to two weeks out. A reschedule then changes one slot instead of rebuilding a day, and the coordinator fills gaps by cluster before they become empty hours.
- Ask the crew first. The crew agrees to a slot before the customer is offered it. The customer only ever hears a firm date, so nothing confirmed gets moved later.
- Promises on the calendar the same hour. If it was said to a customer by phone, text or email, it is on the schedule before the next call. A promise that lives in a message thread is a missed visit waiting to happen.
- One system of record. Scheduling, GPS clock-in, customer messages and invoicing sit in one field-service tool. Every invoice is created from the job, never typed separately. Typed invoices leave visits that look unbilled, and the next automatic billing run charges them again.
- A labor-hour floor on every job. Each job has to earn a minimum for every hour of labor it uses. The arithmetic is in the next section.
- Written rules for the hard cases. Who covers a sick call, how a first visit is staffed, when a job needs two people, how many jobs a crew takes in a day. Written once, so the coordinator never has to ask the owner.
The labor-hour floor, with the arithmetic
The schedule decides payroll, so the schedule has to know what each job earns. The calculation is one line:
Earned per labor hour = price ÷ (hours on site × people on the job)
Illustrative numbers, not a client's prices: a $180 clean done by two people in 2.5 hours uses 5 labor hours and earns $36 per labor hour. If one experienced person can do the same home in 4 hours, it earns $45. Same customer, same price, a different crew size.
Set your floor from what a labor hour costs you loaded (pay, payroll tax, drive time, supplies) plus the margin you need. Then read every recurring job against it on clocked hours, not booked hours. A job under the floor gets one of three fixes, decided on the numbers:
- Crew size. Small homes often earn more with one person than with a pair.
- Cadence. A weekly visit that runs short of the floor can earn it every two weeks, because there is more to clean each time.
- Price. Last, and only after the first two. The owner decides it, with the number in front of him.
The 20-minute daily dispatch routine
This is the routine I write for a coordinator. It assumes the two-week board exists and the rules above are written down.
Why Every change that reaches the crew late costs a visit, a customer or a wasted drive.
Starts when The working day opens, before the first crew leaves.
- Read every door: missed calls, texts, the inbox, the booking form. Anything that changes today, tomorrow or this week goes on a list. (5 minutes)
- Check today's crews are out and clocked in at the first job. A crew not clocked in by [15 minutes] after start gets a call.
- Check tomorrow: every job has a crew, an address, access notes, the right checklist attached and a confirmation sent.
- Sick call or no-show: cover from the same cluster first. If nobody nearby is free, move the job whose customer has said they are flexible, and give that customer a firm new date this morning.
- Requests to move a visit: look at the whole week before agreeing, then offer two slots the crew has already accepted.
- Look at the day two weeks out. Fill open time by cluster: waiting quotes first, then customers who asked for an earlier date.
- Send the owner one message: decisions needed, in one list. Nothing else goes to the owner during the day.
Done when Tomorrow is fully staffed and confirmed, and nothing waits in any inbox.
Owner [name]
Step 7 is the one that frees the owner. Every routine call has a written rule, so the only things left for him are the ones that need an owner: price, hiring, an exception the rules did not foresee.
Worked example: rebalancing an overloaded route day
To show a system without client data I use Quillmoor Operations, a fictional operator from my demo workspace. One of its fictional clients, Briarhollow Pest & Lawn, runs 412 recurring accounts on pest and lawn routes with four technicians. The lead technician agreed that a route day holds 30 stops comfortably; above 33, callbacks rise.
| Pest route day | Before | Target | After the move |
|---|---|---|---|
| Thursday | 38 stops | 32 or fewer | 32 |
| Tuesday | 22 stops | 30 or fewer | 28 |
| Both days | 60 stops | No new truck | 60, six moved |
The obvious fix was another truck. The arithmetic said otherwise: 60 stops over two days is 30 a day, exactly what a route holds. The problem was where the stops sat, not how many there were. The plan:
- Pull both stop lists with addresses and service type.
- Get drive time per route from the office manager.
- Mark the Thursday stops that sit closer to Tuesday's area.
- Move the two commercial accounts first, after checking the service windows in their agreements. That takes Thursday from 38 to 36 before a single homeowner is asked.
- Ask homeowners, five a day, with a short script. Ask, never tell. Anyone who says no stays on Thursday.
- Keep the new technician off any changed route for his first three weeks.
- Go live once every moved customer has agreed in writing. Review after two full weeks with no missed stop.
The askHi [first name], it is [office manager] at [company]. We are rebalancing our routes so every visit gets the time it needs. Could we move your service from Thursday to Tuesday, starting [date]? Same service, same price. If Thursday matters to you, reply and it stays.
The same method works for a cleaning company's crews or an HVAC team's maintenance visits: count the work per day, find the comfortable ceiling with the people who do it, and move work by geography before you add a crew.
Move the six stops yourself.
The same fictional route board. Slide the stops from Thursday to Tuesday in the order the plan moves them, and watch Thursday come back under the line where callbacks rise.
Thursday 32, Tuesday 28. Same 60 stops, no new truck.
The system counts and keeps the log. The homeowners are asked by a person, and nobody moves without saying yes in writing.
Software records a schedule. The rules decide whether it makes money.
- 46%
Crew payroll as a share of revenue, from over 80% in one quarter, through scheduling by route, a labor-hour floor on every job and profitability reporting job by job.
- 90%
Drop in the owner's daily involvement.
- 2weeks
How far ahead the calendar is built, where it used to be built on the day.
Which software?
I am not tied to one product. Most field-service platforms can do everything on this page, and many companies already pay for one and use a fraction of it. The first step is usually to switch on what you have: GPS clock-in, invoices from the job, automatic confirmations, recurring visits placed by the tool.
The procedures that keep the schedule honest
Three of the procedures in my pack exist for the schedule: booking and confirmation (on the calendar the same hour, staffed, confirmed in writing), schedule change (look at the whole week before moving one job) and the daily inbox and phone sweep. Each is written out with steps, an owner and a done-when line, ready to fill in for your business.
The AI-Ready Procedure Pack: twelve procedures from first inquiry to paid invoice, the rollout order and an AI prompt that fills every bracket for your business. An eight-page PDF plus an editable text copy. One payment, 30-day refund.
Questions
What is the difference between scheduling and dispatching?
Scheduling decides which job happens on which day, with which crew, in which order, usually days or weeks ahead. Dispatching is the same-day work: getting the crew out with everything they need, and handling the sick call, the late finish and the customer who moves their visit. Good scheduling makes dispatching short. If dispatching takes hours every day, the schedule is the problem.
How far ahead should a field service company schedule?
I plan two weeks ahead. Far enough that a reschedule changes one slot instead of rebuilding a day, and near enough that crews and customers still know their plans. Recurring work is placed further out by the field-service tool; the two-week board is what a person checks and staffs.
Do I need route optimization software?
Usually not first. Most field-service platforms already map jobs and suggest an order. The bigger gain comes from the rule behind the route: assign every job by where the crew starts and keep each crew inside one cluster for the day. Software orders the stops; it does not decide that a crew should never cross the service area for one job.
What is a labor-hour floor and how do I set mine?
It is the minimum a job has to earn for every hour of labor it uses: the price divided by the clocked hours times the number of people on the job. Set yours from what a labor hour costs you loaded (pay, payroll tax, drive time, supplies) plus the margin you need. A job under the floor gets a different cadence, crew size or price, decided on the numbers.
How should we handle a sick call?
With a rule written before it happens. Cover from the same cluster first. If nobody nearby is free, move the job whose customer has said they are flexible, and give that customer a firm new date the same morning. Never send a crew across the service area for a single job, and never let the customer find out at the door.
Who should own dispatch?
One named coordinator, not the owner. The owner sets the rules and sees one short message a day with anything that needs a decision. The coordinator runs the daily routine and the two-week board, and has written permission to make every routine call without asking.
Who this is for
US cleaning, landscaping, pest control, HVAC, restoration and other field-service companies with crews on the road and an owner or manager still acting as dispatcher.
If yours is a cleaning or home-services company, there is more in fractional COO for cleaning and home-services companies.
How it starts
With a 45-minute Operations Leak Audit. Have your scheduling tool open. We walk through last week job by job, and you leave with a one-page leak map and the one build I would do first.
Scheduling is one system of several
I build AI systems and automations for growing businesses in any industry, and I work beside founders as their fractional COO. In field service the schedule decides payroll. The same rule-first approach runs a private lender's servicing calendar.
See what I build and how I work, or how it runs at a private lender.
