When One Crew Becomes Two: The Dispatch Problem
Managing one crew's schedule is a coordination task. Managing two or more crews simultaneously is a logistics operation. The moment you add a second technician or crew, you need a system that can handle overlapping schedules, last-minute changes, real-time status updates, and customer communication — all at once, often from the job site.
Most contractors who struggle with multi-crew dispatch are using tools designed for single operators: a shared calendar, a group text chain, or manual phone check-ins. These work until they don't — and when they fail, they fail expensively.
Territory and Route Assignment
Before you can dispatch efficiently, you need a territory strategy. Randomly distributing jobs across the map to any available tech wastes drive time for every crew. Instead:
- Assign geographic zones: Each technician or crew owns a geographic territory for recurring customers. Crew A covers the north side; Crew B covers the south. Customers in each territory are always assigned to the same crew unless there's a capacity issue.
- Route jobs by cluster: Within a territory, group same-day jobs in geographic clusters so each crew's drive time is minimized. A crew that works northeast zip codes in the morning and northwest zip codes in the afternoon wastes an hour of drive time they wouldn't spend if jobs were grouped.
- Use drive time as a scheduling variable: When booking, factor in how far the next job is from the previous one. A 20-minute gap between jobs on the same street is different from a 20-minute gap between jobs 15 miles apart.
Real-Time Status Updates: The Communication Layer That Prevents Chaos
With multiple crews in the field, the dispatcher (often you) needs to know job status in real time. Without it, you're flying blind — and customers calling to ask "where are you?" create a second job on top of running the first one.
The minimum viable status system for multi-crew dispatch:
- Technicians update job status on arrival, completion, and any unexpected delay
- Customer receives an automated "on the way" notification when the tech checks in
- Dispatcher sees all crew locations and job statuses on a single view without calling individual techs
Handling Mid-Day Changes Without Cascading Delays
When a job overruns or a customer cancels mid-day, the change affects every subsequent job on that crew's schedule. The protocol:
- Assess the impact immediately — how many jobs will be affected and by how much?
- Proactively communicate to affected customers: "We're running about 45 minutes behind — will that still work?" before the delay becomes a no-show from their perspective
- If a job must be rescheduled, reassign it to the other crew if they have capacity, or reschedule with an apology and a small gesture (priority scheduling next time, minor discount)
Dispatch Checklist — Start of Day
- ✓ All crews confirm today's schedule received
- ✓ First job for each crew is confirmed (customer texted)
- ✓ Tool and supply inventory verified for each vehicle
- ✓ Buffer slot identified on each crew's schedule
- ✓ Any pending reschedulings from yesterday addressed
Fieldbase provides a dispatch board that shows all crew schedules and job statuses in real time, lets you drag-and-drop jobs between crews, and sends automated status updates to customers — so multi-crew dispatch runs smoothly without a dedicated dispatcher.
Key Takeaways
- Assign geographic territories to each crew — don't randomly distribute jobs across the map
- Cluster jobs geographically within each territory to minimize drive time
- Real-time job status updates prevent customer complaints and dispatcher guesswork
- When a job overruns, proactively communicate to downstream customers before they call you
- A shared dispatch board with drag-and-drop is 10x more effective than group texts