Field Service Scheduling: How to Schedule Crews Across Job Sites
The short answer: Schedule field crews by starting from your real capacity, clustering jobs by geography to cut drive time, matching the right crew and skills to each job, and getting the schedule onto the devices your techs carry. The goal is high billable utilization without overbooking, most field businesses aim to keep crews genuinely productive 70% to 85% of the day after travel and admin. CRMb schedules shifts and recurring work across client job sites, shows your crew capacity before you overbook, and syncs to Google or Apple Calendar so the field always has today's plan.
A field business lives or dies on its schedule. Book too little and crews sit idle on your payroll. Book too much and jobs run late, customers get bumped, and your team burns out. Route poorly and half the day disappears into windshield time you cannot bill. This guide is the practical version: how to build a schedule that keeps crews busy on the right work in the right order.
What makes field service scheduling hard
Scheduling an office team is easy: everyone is in one place for a fixed block. Field scheduling is harder because of three moving parts.
Geography. Your jobs are spread across a service area, and the time between them is real cost that bills to no one. A schedule that ignores drive time silently throws away hours.
Variable job length. A service call might take 45 minutes or half a day, and you often do not know until the tech is on site. Overrun on the first job and every job behind it slips.
People and skills. Not every tech can do every job. A schedule has to put the right skills, and the right number of hands, on each job, while keeping everyone busy.
Handle these three, capacity, geography, and matching, and the rest of scheduling is administration.
Start with capacity, not the calendar
The most common scheduling mistake is booking jobs onto a calendar until it "looks full," with no idea whether the crew can actually do them. Start the other way around: calculate how many productive hours you truly have, then book within that.
Gross hours are not bookable hours. A crew does not bill travel, restocking, paperwork, or breaks. Subtract those first:
| Resource | Gross hours/day | Less travel and admin (~20%) | Bookable hours |
|---|---|---|---|
| Crew A (2 techs) | 16 | 3.2 | 12.8 |
| Crew B (2 techs) | 16 | 3.2 | 12.8 |
| Total | 32 | 6.4 | 25.6 |
So this two-crew shop has about 25.6 truly bookable hours a day, not 32. Book to 32 and you are guaranteeing overruns and unhappy customers. Knowing the real number is what lets you say yes to the right amount of work and no to the rest. CRMb's capacity view shows this at a glance, so you book against real availability instead of a calendar that only looks full. For the planning side in depth, see capacity planning for field crews.
Cluster jobs by geography
Drive time is the quietest margin-killer in field service. Every hour a crew spends between sites is an hour you pay for and cannot bill. The fix is route density: schedule jobs that are near each other on the same crew on the same day.
Instead of sending Crew A across town at 8 a.m. and back again at 2 p.m., group the west-side jobs on Tuesday and the east-side jobs on Wednesday. The same eight hours of work fits in less clock time when the stops are close together, which means more billable jobs per day from the same crew. In a business with recurring routes, cleaning and maintenance especially, tight clustering is the single biggest lever on profit. Because CRMb ties every scheduled shift to a client's job site, you can see where the day's work actually is and build routes that keep crews working instead of driving.
Match the right crew to the job
A schedule is not just when, it is who. Two things have to line up:
- Skills. Put the tech who can do the work on the job. Sending someone who cannot complete it guarantees a second visit, which is the most expensive outcome in field service.
- Headcount. Some jobs need two hands, some need four. A schedule that assigns one tech to a two-person install is a job that will not finish on time.
CRMb supports multiple assignees on a shift, so a job that needs a three-person crew is scheduled as exactly that, and everyone assigned sees it. Matching skills and headcount up front is how you keep the first-visit completion rate high, which customers feel as reliability and you feel as margin.
Use recurring shifts and open shifts
Two scheduling patterns save enormous time once your volume grows.
Recurring shifts are for work that repeats: the Tuesday-morning office clean, the monthly maintenance visit, the standing route. Set it once and it lands on the calendar every cycle, instead of being rebuilt by hand each week. Recurring scheduling is where a maintenance business gets its time back. See how to schedule a cleaning crew for a recurring-route walkthrough.
Open shifts are jobs posted without a specific person assigned yet, that available crew members can pick up. They are useful for filling gaps, covering a callout, or handling overflow without the office manually assigning every hour. Together, recurring and open shifts turn a schedule from something you rebuild constantly into something that mostly maintains itself.
Get the schedule into the crew's hands
A perfect schedule the crew cannot see is useless. The plan has to reach the devices your techs actually carry, and update when it changes. A tech working off yesterday's printed sheet will drive to a job that got moved.
CRMb keeps the schedule live across Mac, iPad, and the web, and syncs shifts to Google Calendar or Apple Calendar, so a job lands in the calendar your crew already checks. When the office moves a job, the field sees the change, not a stale copy. Removing the gap between "scheduled" and "the tech knows" is what stops the missed and doubled visits that erode customer trust.
Close the loop: scheduled versus actual
Scheduling is not finished when the crew is booked. The schedule is a plan, and the value comes from comparing it to what actually happened. If you scheduled a job for three hours and the crew punched five, that is information: your estimate was off, the job was harder than expected, or the route cost more than planned.
When your crew punches in against each job through Punch, those real hours flow back into CRMb next to what you scheduled, and the reports view shows where the day's plan met reality. Over a few weeks, that gap becomes better estimates: you learn that a certain job type always runs long, that a route needs more drive-time buffer, that one crew is faster than another. A schedule you measure against is a schedule that gets more accurate every week.
Frequently Asked Questions
How do I schedule field service crews efficiently?
Start from your real bookable capacity, gross crew hours minus travel and admin, then cluster jobs by geography to cut drive time, and match each job to a crew with the right skills and headcount. Get the finished schedule onto the devices your techs carry so changes reach them instantly. Then compare scheduled hours to actual punched hours to sharpen future plans.
What is the biggest cause of wasted time in field scheduling?
Drive time between jobs. Every hour a crew spends traveling is paid but unbillable, and a schedule that ignores geography can lose a large share of the day to windshield time. Clustering nearby jobs on the same crew and day, route density, is the most effective fix and often the biggest single lever on field-service profit.
How many hours a day can I actually book a crew?
Fewer than the clock suggests. After travel, restocking, breaks, and paperwork, most field crews are genuinely billable roughly 70% to 85% of a shift, so an eight-hour day yields closer to six billable hours. Booking to the full gross hours guarantees overruns. Calculate bookable hours first and schedule within them.
What is the difference between scheduling and dispatching?
Scheduling is planning ahead, deciding which crews do which jobs on which days. Dispatching is the real-time act of sending a specific tech to a specific job, often adjusting on the day as jobs run long or emergencies come in. Good scheduling reduces the chaos dispatching has to absorb, because a well-planned day needs fewer last-minute scrambles.
Do I need scheduling software, or is a spreadsheet enough?
A spreadsheet can work for a single crew, but once you are coordinating multiple crews across job sites, it breaks down, changes do not reach the field, recurring work is rebuilt by hand, and capacity is invisible. Scheduling software that ties shifts to client job sites, handles recurring and open shifts, and syncs to the crew's calendar removes that manual burden and keeps the field current.
Getting started
Rebuild next week's schedule from capacity: calculate your real bookable hours per crew, cluster the jobs by area, assign the right skills, and set your recurring work to repeat on its own. Then make sure every tech has the schedule on their device before the week starts.
CRMb schedules crews across client job sites with recurring and open shifts, shows your capacity before you overbook, and syncs to Google and Apple Calendar so the field always has the plan, while real punched hours flow back to show scheduled versus actual. It runs on Mac, iPad, and the web. Start free and get your crews on one schedule.