Most small crews schedule off a whiteboard, a group text, and the owner’s memory. It works until the day a tech is sick, a job runs two hours long, and a customer calls to move their window — all before 9 a.m. Then you are re-typing addresses into three places and hoping the guy in the truck got the last text. How to schedule field service jobs is not a fleet problem for a crew of three to ten. It is a handful of concrete decisions, and once you make them the same way every time, the day stops fighting you.
Scheduling for a small crew, not a fleet
The software built for 200 trucks solves a 200-truck problem: which of forty techs across a metro takes the next call to minimize drive time. You do not have that problem. You have three to ten people, you know who is good at what, and you know your service area cold. What you need is a shared, current answer to two questions: who is doing what today, and where does the next job go.
How far out to book, and how to leave slack
Book firm dates about two to three weeks out and no further. Past that, the world changes — weather, cancellations, a job that runs long — and a calendar packed solid a month ahead is one you spend the month un-packing. Hold a rough week for anything beyond the firm window, then confirm the exact day as it gets close.
The mistake that burns small crews is booking to 100%. If every hour is spoken for, the first job that runs long pushes the second, the second pushes the third, and you are calling customers at 4 p.m. to bump them. Leave slack on purpose.
- Hold roughly 15–20% of the day open. For an 8-hour day that is a 60–90 minute cushion — the buffer that absorbs the job that ran long instead of dominoing onto the next customer.
- Block travel time as its own thing. A 2-hour job across town is not a 2-hour block. Put the drive on the calendar so the day reads honestly.
- Keep one recurring “catch-up” slot a week. The warranty return, the punch-list item, the thing you keep pushing — give it a home instead of jamming it into a real job’s window.
Assigning by skill and location
For a small crew, two things decide who takes a job, and they are both in your head already: who can do the work, and who is closest to it. Route optimization software exists to compute the second one across a big fleet. You can do it by looking at a map, because you have three techs, not forty.
The move that saves the most windshield time is grouping by geography. Two jobs on the same side of town go to the same tech on the same day. That one habit does more for a small crew’s drive time than any optimization engine, and it costs nothing but a glance at where the pins sit.
Filter by skill first
A panel upgrade goes to the licensed electrician, not whoever is free. Match the job to the person who can actually do it before you think about anything else.
Then group by location
Among the people who can do it, pick the one whose day is already headed that direction. Same side of town, same tech, same day.
Then check the load
If two jobs both fit the closest tech, but they’re already full, hand one to the next-closest. Balance the day so nobody is idle and nobody is buried.
Handling same-day changes and cancellations
Same-day chaos is where a whiteboard fails hardest. A change is only safe when it updates in one place and everyone sees it — the office, the tech in the truck, and the calendar on the wall are the same calendar, not three copies you keep in sync by text.
When a customer cancels, backfill the hole instead of losing the day. Keep a short standby list — the customer who said “any time this week,” the estimate that’s close by — so an open slot becomes a phone call, not a dead two hours. When a job runs long, reschedule the next one rather than making that customer wait past their window, and let the change reach the tech and the customer without you re-keying the address.
One change, one place
The rule that makes same-day work sane: a reschedule happens on the job, and everything else reads from it. Move a visit and the tech’s phone and the office view both show the new time. You never text “new ETA” to five people and hope it lands.
What a tech should see on their phone (and what they shouldn’t)
A tech in the driveway needs a short, exact answer, not a dashboard. Give them the day’s stops in order, and for each one: the address with a tap-to-navigate link, the customer’s name and phone, the scope of work from the signed quote, and any notes or photos. That is the job. Nothing else belongs on that screen.
A field tech never sees your margins
Permissions are per person, not a plan upsell. A tech sees the job, the address, and the schedule — but not the margin, the finances, or the settings. The crew runs the work off their phone; the office runs the numbers. You decide what each seat sees.
Why you probably don’t need route optimization yet
Live GPS tracking and route optimization are real features that solve real problems — for fleets. On a crew of three to ten, they add cost and a surveillance feel your crew will notice, and they optimize a variable you already control by grouping jobs geographically. You do not need an algorithm to tell you the two jobs on Oak Street should go together.
The honest signal you’ve outgrown grouping-by-hand: enough trucks and same-day density that nobody can see the best assignment at a glance. Most small crews never hit that. Until you do, spend the effort on slack in the day and one shared schedule.
One record: the schedule sits on the same job as the quote
Here is where scheduling stops being a separate chore. In Mortar, the schedule is not its own app — it is a field on the job. The signed quote becomes the scheduled visit, so the address, the scope, and the customer are already there. Nobody re-types the job into a calendar. The visit is dispatched to a tech, who sees it on their phone the moment it’s scheduled, and when the work is done, the invoice generates from that same signed quote.
That is the whole point of keeping it on one record: how to keep track of jobs stops being a question you re-answer in three tools. Scheduling and dispatch — the ability to assign visits, dispatch to a tech, and sync your calendar — is included on Mortar’s Core plan ($99/month, 5 seats) and up, alongside recurring service billing. Walk the full workflow end to end in how to run a service business without living in five apps.
How far in advance should a small crew schedule jobs?
Book firm dates two to three weeks out, and hold rough weeks — not exact days — for anything beyond that. Confirm the exact day as it gets close. A calendar booked solid a month ahead spends the month un-booking itself when weather, cancellations, and long jobs move things.
How do I dispatch jobs to a small crew without a dispatch board?
Assign by skill first (the job goes to whoever can actually do it), then by location (group jobs on the same side of town with the same tech on the same day), then balance the load. For three to ten people you can do this at a glance — the enterprise dispatch board solves a forty-truck problem you don’t have.
Do I need GPS and route optimization for a small crew?
Usually not. Route optimization earns its cost across a large fleet with high same-day density. On a small crew you already know who is good at what and where your area is, and grouping jobs by geography by hand captures most of the drive-time savings without the cost or the surveillance feel.
What should a field tech see on their phone?
The day’s stops in order, and per stop: the address with a navigate link, the customer’s name and phone, the scope from the signed quote, and any notes or photos. Not the margin, the finances, or the settings — those stay with the office. In Mortar, per-person permissions enforce that split.
Building Mortar — the all-in-one CRM for service businesses. One shared record, one number behind every job.