Crew Scheduling for Service Businesses
Why this matters
A service business's gross profit is generated almost entirely by billable technician hours. A 5-technician shop with average labor recovery of 30 hours/week per technician produces three quarters of the revenue of one with 40 hours/week per technician - same headcount, same trucks, same overhead, and a far wider gap in gross profit than in revenue, because the wages and the trucks cost the same either way. The single biggest lever on that recovery rate is scheduling. Routes that crisscross the service area, gaps between calls, mismatched skill assignments, and chaotic same-day changes all destroy productivity. Disciplined scheduling, by contrast, fills the day with the right work in the right order. This reference covers the principles that distinguish a well-run dispatch operation from a chaotic one.
The components of billable hour recovery
Where the day actually goes for a typical residential service technician:
| Time category | Percentage of clock-in to clock-out | Notes |
|---|---|---|
| Productive on-customer-site time | 50-65% | What gets billed |
| Travel between calls | 15-25% | Some unavoidable; most reducible |
| Material pickup / shop runs | 5-10% | Should be near-zero with truck stock |
| Diagnosis on calls that don't book | 5-10% | Cost of leads |
| Administrative (paperwork, calls, etc.) | 5-10% | Should compress with mobile tools |
| Breaks and personal time | 5-10% | Legitimate; should be planned |
A shop that increases on-site time from 55% to 70% increases gross revenue per technician proportionally - without hiring, training, or selling more.
Two scheduling models
Static daily schedule
The technician's day is built before they arrive in the morning. Stops are sequenced, materials are loaded, customers have been confirmed.
- Pros: Predictable for the technician; allows pre-trip preparation; customers know their window.
- Cons: Doesn't flex well when same-day demand spikes; emergencies disrupt the day.
Best for: trades with mostly scheduled (non-emergency) work - lawn care, cleaning, maintenance, contracted work.
Dispatch-as-you-go
A dispatcher assigns the next call as the technician finishes the current one. Real-time optimization.
- Pros: Maximum responsiveness to incoming demand; can geographically optimize as the day unfolds.
- Cons: Requires skilled dispatcher; technician can't pre-stage; uncertain workday end.
Best for: trades with high emergency demand - plumbing, HVAC in peak, electrical, locksmith.
Hybrid
Most well-run shops use a hybrid. A morning schedule is built with 70-80% of the day's capacity; the remainder is reserved for same-day emergencies dispatched as they come in.
Geographic optimization
The single biggest scheduling win is routing. A technician who drives 15 minutes between each of 8 stops loses 2 hours per day. The same 8 stops sequenced by geography can drop to 5 minutes between each - gaining 1 hour 20 minutes.
Manual optimization techniques:
- Map view of the day's jobs.
- Sequence stops in a logical path (zone-by-zone).
- Cluster appointments in the same area on the same day.
- Avoid criss-crossing the service area.
Routing software automates this:
- The Manuall scheduling system, FleetSharp, Route4Me, OptimoRoute, Onfleet.
- Algorithms like the Traveling Salesman Problem solver applied to the day's stops.
- Real-time traffic integration adjusts the route based on current conditions.
For shops with more than 5 technicians, route-optimization software pays back in weeks through recovered hours.
Skill matching
Not every technician can do every job. A 10-year master plumber on a leaky faucet is overpriced labor; a 1-year apprentice on a complex repipe is a quality risk and a re-do.
Matching elements:
- Trade skill level. Senior, mid, apprentice tracked in the CRM.
- Specific certifications. Backflow tester, gas fitter, etc.
- Equipment familiarity. Brand-specific training (Generac, Trane, etc.).
- Customer history. Some technicians have rapport with specific accounts.
- Language capabilities. Spanish-speaking customers benefit from a Spanish-speaking technician.
A scheduling system that captures these dimensions and assigns by best-match instead of next-available produces higher quality and better customer experience.
Time-of-day patterns
Service demand isn't even across the day. Typical residential patterns:
- 7-9 AM: high demand (overnight problems discovered at wake-up)
- 9 AM-12 PM: moderate steady demand
- 12-2 PM: lower demand (lunch hour)
- 2-5 PM: peak afternoon demand
- 5-8 PM: residential customers home for service
- 8 PM+: after-hours emergency only
A schedule that loads heavy in the morning and light in the afternoon wastes the afternoon. Better: book the morning, leave the afternoon for emergency capacity, and book again into the evening for working customers.
Capacity planning by day-of-week
Most trades have weekly patterns:
- Monday: highest demand (weekend-discovered problems)
- Tuesday-Thursday: steady
- Friday: customers want it fixed before the weekend
- Saturday: high residential demand if you're open
- Sunday: emergency only for most trades
Staffing should mirror the pattern. Five technicians on Monday and three on Tuesday may serve customers better than five every day.
Emergency / same-day capacity
A shop that says "next available is Thursday" loses emergency revenue to competitors. A shop that says "we can have someone there in 2 hours" wins those same calls at a premium.
Reserving capacity for same-day:
- 20-40% of daily hours unreserved at start of day, depending on trade and season.
- Filled with same-day calls in priority order (emergency > urgent > routine).
- Predictable per-technician availability so dispatcher can promise windows.
Refusing to reserve same-day capacity is a strategic choice that limits the trade ceiling. Most growing shops dedicate capacity even at the cost of some pre-booking efficiency.
The pre-call and en-route call
Two communication moments that disproportionately affect customer satisfaction:
- Pre-call (the day before or morning-of). Confirms appointment, reminds of access requirements, captures last-minute changes.
- En-route call/text (15-30 minutes before arrival). Customer knows the technician is on the way; reduces uncertainty.
Skipping either generates "where are they?" calls to dispatch that consume staff time and erode satisfaction. Both can be automated through customer notification systems.
When the schedule breaks
It will. A call goes long, a tech calls out, a part is wrong, a customer is not home. The difference between shops is not whether the day falls apart, it is how fast the dispatcher decides and how fast the customer hears about it.
Decide in this order:
- Protect the promises you cannot move. Contracted commercial windows, permit inspections, jobs with a crane or a rental on the clock, and customers who already took a day off work. These do not get bumped for a bigger ticket.
- Protect safety and habitability. No heat in a freeze, no water, sewage backing up, gas odor, no power. These jump everything.
- Then optimize the rest. Reroute by geography, not by call order.
Call the customer before they call you. The moment the dispatcher knows a window will slip, the customer gets contacted with a new window and a reason. A customer told at ten in the morning that the afternoon slipped to tomorrow is mildly annoyed. The same customer discovering it at five is a review problem.
Move the job, not just the time. If the tech running late has three stops left and another tech is closer to two of them, reassign. Waiting for the original tech to catch up costs more billable hours than the reassignment costs in context switching.
Know when to stop selling the day. There is a point in the afternoon past which adding one more call guarantees overtime, a rushed job, or a no-show on somebody else. Set that cutoff explicitly and let the dispatcher enforce it. A same-day call booked at that hour should be tomorrow's first stop instead.
Never send a tech to a job they cannot finish just to make the appointment look kept. A trip that ends in "I have to come back with the part" burns two windows and one customer's patience.
Debrief the break. At end of day, note why each schedule failure happened: bad duration estimate on a job type, missing truck stock, a customer who always runs long, a tech who consistently underestimates. Those notes are what fix next quarter's schedule. A break with no cause recorded will simply happen again.
Track the reschedule rate the way you track callbacks. If a meaningful share of the week's appointments move, the problem is not the day, it is the durations you plan with or the capacity you hold back.
References
- US Department of Labor, Bureau of Labor Statistics - productivity standards for service industries.
- Christofides, N. "Worst-case analysis of a new heuristic for the travelling salesman problem." 1976 (TSP-routing foundational paper).
- Service Council and ServicePower industry benchmark reports.
- OSHA 1910.243 - guarding of portable powered tools (when scheduling around equipment limitations).
- DOT Hours of Service regulations, 49 CFR Part 395 (if any vehicles cross the CMV threshold).
- Manuall internal: Route Optimization, Seasonal Business Planning, Inbound Call Script.