# What Is Dispatching?

Dispatching is the job of assigning booked work to a specific technician or crew, at a specific time, and getting them there with the information they need. Good dispatching matches each job to the right skills, keeps drive time low, leaves room for emergencies and keeps the customer updated, so more billable work fits into every day.

## Key takeaways

- Scheduling puts a job on the calendar; dispatching decides who goes, in what order, and sends them.
- The goal is more billable hours per tech per day, not just a full board. Drive time, callbacks and idle gaps are the enemies.
- Match on skill first, location second, availability third. Sending the wrong tech costs a second trip.
- Hold capacity for same-day and emergency calls, because those are usually your highest-margin jobs.
- Measure it: jobs per tech per day, drive time per job, first-time fix rate and on-time arrival.

## How does dispatching work in a trades business?

Dispatching turns a list of booked jobs into a plan for each truck. A call comes in, the job gets booked into a window, and the dispatcher (often the owner, a [customer service representative](https://www.brix.so/learn/customer-service-representative) or software) picks the tech, sets the order of stops, and sends the job details to the tech's phone. During the day the dispatcher moves jobs around when one runs long, a part is missing, or an emergency call lands.

In a two-truck shop, dispatching might be the owner texting addresses at 7 a.m. In a 20-truck shop it's a full-time seat with a dispatch board, live GPS and rules for who gets which calls. Either way the job is the same: put the right person at the right door with the right parts, and don't waste paid hours driving or waiting.

## What's the difference between scheduling and dispatching?

Scheduling is booking a job into a date and arrival window with the customer. Dispatching is deciding which technician does it, in what order, and releasing it to them. Scheduling is a promise to the customer; dispatching is how you keep it. Many small shops do both in one step, which is fine until the board gets crowded.

**Scheduling vs. dispatching**

|  | Scheduling | Dispatching |
| --- | --- | --- |
| Question it answers | When will we be there? | Who goes, in what order, with what? |
| Who it talks to | The customer | The technician or crew |
| When it happens | When the job is booked, often days ahead | The night before and all through the day |
| Typical output | Arrival window, e.g. 8–11 a.m. Tuesday | Tech's route, job notes, parts, customer history |
| What goes wrong | Overbooking, no buffer for emergencies | Wrong skill sent, zig-zag routes, idle gaps |

## How do you dispatch technicians efficiently?

Efficient dispatching means sending the closest qualified tech, grouping jobs by area, and keeping a buffer for emergencies. Set the next day's board the afternoon before, assign by skill then location, release jobs in route order, and re-plan only when something actually changes. Track jobs per tech per day to see if it's working.

1. **Qualify the job before it hits the board.** The call-taker should capture the problem, equipment age and brand, access notes, photos if possible and whether it's an emergency. A job booked as 'AC not working' with no detail is how a junior tech ends up on a compressor replacement. A good [work order](https://www.brix.so/learn/work-order) carries this information.
2. **Match on skill first.** Tag every tech with what they can do: installs, commercial, gas, panels, sewer camera, roof types. Tag every job type with what it needs. Sending the wrong skill set causes a second trip, which costs more than any amount of drive time you saved.
3. **Then group by geography.** Split your service area into zones and try to keep each tech in one or two zones a day. Book customers into zone-days where you can. See [route optimization](https://www.brix.so/learn/route-optimization) for how to plan the stops.
4. **Leave room for same-day work.** Don't book every tech to 100% the day before. Keep one tech or a few hours per tech open for emergency and same-day calls, which are often your highest tickets. Fill the gap with maintenance visits you can move.
5. **Load the truck to the job.** Check the next day's jobs against [truck stock](https://www.brix.so/learn/truck-stock) the afternoon before. If a job needs a part the truck doesn't carry, pick it up or reorder the stops, so the first visit is the last visit.
6. **Communicate in both directions.** Send the customer an on-my-way text with the tech's name. Have techs update job status (en route, on site, done) so the dispatcher sees the real board, not the planned one.
7. **Review the day.** Each evening, look at jobs completed per tech, drive time, late arrivals and jobs that needed a return trip. Fix the cause, not just the day.

> **Example: what 30 minutes of drive time is worth**
>
> Illustrative numbers. A plumbing company runs 4 techs, each paid for 9 hours a day. Their average job takes 1.5 hours on site, and the average drive between jobs is 40 minutes.
>
> Each job uses about 2.2 hours of the day (1.5 on site + 0.67 driving), so a tech fits about 4 jobs into 9 hours.
>
> Grouping jobs by zone cuts the average drive to 20 minutes. Each job now uses about 1.83 hours, so the same tech can fit closer to 5 jobs, if the demand is there.
>
> One extra job per tech per day × 4 techs × 250 working days = 1,000 more jobs a year. At a $400 average ticket that is $400,000 of capacity, without hiring anyone. You only capture it if the phone is answered and the jobs are booked.

## What metrics show if dispatching is working?

The best dispatching metrics measure how much of a tech's paid day turns into billed work. Track [technician utilization](https://www.brix.so/learn/technician-utilization), jobs per tech per day, drive time per job, first-time fix rate, on-time arrival and callbacks. One number on its own can mislead; a full board with long drives and repeat visits is not efficient.

**Technician utilization**

```
Utilization = Billable hours ÷ Paid hours × 100
```

Where:
- Billable hours = hours on site doing work you charge for
- Paid hours = every hour on the clock, including driving, shop time and waiting

> **Worked example**
>
> An HVAC tech is paid for 45 hours in a week and spends 29 of them on billable work.
>
> Utilization = 29 ÷ 45 × 100 = 64%. The other 16 hours went to driving, the supply house, paperwork and gaps between calls.
>
> Run your own numbers in the [technician utilization calculator](https://www.brix.so/tools/technician-utilization-calculator).

**Dispatch metrics to track**

| Metric | How to calculate it | What it tells you |
| --- | --- | --- |
| Jobs per tech per day | Completed jobs ÷ tech-days worked | Raw throughput; compare techs doing similar work |
| Drive time per job | Total drive minutes ÷ jobs | Whether routes and zones are tight |
| Utilization | Billable hours ÷ paid hours | How much paid time turns into billed time |
| [First-time fix rate](https://www.brix.so/learn/first-time-fix-rate) | Jobs fixed on first visit ÷ total jobs | Whether the right tech and parts were sent |
| On-time arrival | Arrivals inside the promised window ÷ total | Whether the board is realistic |
| [Callback rate](https://www.brix.so/learn/callback-rate) | Return visits for the same problem ÷ jobs | Quality, and whether skills were matched |

## How does dispatching differ by trade?

**Dispatching by trade**

| Trade | Typical dispatch pattern | Main dispatch challenge |
| --- | --- | --- |
| HVAC | Demand service + maintenance visits; installs as full-day crews | Heat waves and cold snaps flood the board; keep tune-ups movable so no-cool calls get slots |
| Plumbing | Short demand calls, drains, water heaters; 24/7 emergencies | Unknown job length (a clog can be 30 minutes or a sewer replacement); needs re-planning mid-day |
| Electrical | Service calls plus multi-day project work | Splitting licensed electricians between service calls and project sites |
| Roofing | Inspections and repairs dispatched; replacements run as crew projects | Weather. Storm days create inspection surges and rain cancels installs |
| Landscaping and lawn care | Fixed recurring routes by day of week | Rain delays push the whole week; route density matters more than skill matching |
| Cleaning | Recurring visits, fixed teams, tight windows | Team availability and keys or access codes for each home |
| Pest control | Recurring routes plus one-time treatments | Keeping routes dense while squeezing in urgent one-time calls |
| Garage door | Fast emergency dispatch (door stuck open or shut) | Carrying the right springs and openers to fix on the first visit |

## Who should do the dispatching?

In a shop under about three trucks, the owner usually dispatches, and that's fine if it takes minutes a day. Once the owner is re-planning the board from a ladder, it's time to hand it off: first to an office manager or CSR, then to a dedicated dispatcher as the truck count grows. Software with skill tags and a map makes the handoff easier because the rules live in the system instead of the owner's head. For the bigger picture, see [how to systemize a contracting business](https://www.brix.so/learn/how-to-systemize-a-contracting-business).

## Common dispatching mistakes

- **Booking every tech to 100%.** The first emergency of the day blows up every arrival window after it.
- **Dispatching by who's free, not who's qualified.** It feels fast and creates return trips.
- **Zig-zag routes.** Accepting any slot the customer wants, anywhere in the territory, without zone days.
- **Thin job notes.** Techs arrive without the model number, gate code or history, and call the office from the driveway.
- **No status updates.** The dispatcher plans against a board that stopped being true at 9:15 a.m.
- **Measuring only revenue per tech.** It hides drive time and callbacks. Look at [gross profit per hour](https://www.brix.so/learn/gross-profit-per-hour) as well.
- **Dispatch lives in one person's head.** When they're sick, the day falls apart.

BRIX books calls straight onto the schedule and assigns the right crew to each job based on skills, location and availability. The AI receptionist captures job details on the call, so the work order is ready before the tech rolls.

- [Scheduling and dispatch](https://www.brix.so/features/scheduling-dispatch): Assigns the right crew to the right job based on skills, location and availability.
- [AI receptionist](https://www.brix.so/features/ai-receptionist): Answers every call 24/7, qualifies the caller, books the job and texts back anyone it misses.
- [CRM](https://www.brix.so/features/crm): One record for every customer, lead, call, job, quote and invoice.

## Frequently asked questions

### What does a dispatcher do in a service company?

A dispatcher assigns booked jobs to technicians, sets the order of stops, sends job details to the field, and re-plans the day when jobs run long or emergencies come in. In smaller shops the dispatcher often also answers calls and books jobs.

### How many technicians can one dispatcher handle?

It depends on job length, how many calls change mid-day, and how much the dispatcher also handles phones and booking. A shop running long install jobs needs far less dispatching per tech than one running six short demand calls per tech per day. Watch for late arrivals and missed calls as the sign the seat is overloaded.

### Should I dispatch by skill or by location?

Skill first, then location. Sending a closer tech who can't finish the job causes a second trip, which costs more than the extra drive time of sending the right tech. Within the set of qualified techs, pick the one who is closest or whose route the job fits best.

### What is dispatch software?

Dispatch software shows booked jobs and technicians on one board and map, lets you assign and reorder jobs, and sends job details to techs' phones. Most tools also track job status and send customers on-my-way texts. It is usually part of a broader [field service management](https://www.brix.so/learn/field-service-management) system.

### How do I handle emergency calls without wrecking the schedule?

Hold capacity for them. Leave a few open hours per day, or one floating tech in busy season, and fill the board around them with movable work like maintenance visits. When an emergency comes in, slot it into the reserved time instead of bumping a booked customer.

### What is a good number of jobs per technician per day?

There's no universal number because job length varies so much by trade and job type. A tech doing quick service calls might complete five or six; a tech doing installs might complete one. Compare each tech against your own history for the same job mix, and watch utilization alongside it.

## Related

- [What Is Route Optimization?](https://www.brix.so/learn/route-optimization)
- [What Is a Work Order?](https://www.brix.so/learn/work-order)
- [What Is Field Service Management (FSM)?](https://www.brix.so/learn/field-service-management)
- [What Is Technician Utilization?](https://www.brix.so/learn/technician-utilization)
- [What Is First-Time Fix Rate?](https://www.brix.so/learn/first-time-fix-rate)
- [What Is Truck Stock?](https://www.brix.so/learn/truck-stock)
- [What Is a Customer Service Representative (CSR) in Home Services?](https://www.brix.so/learn/customer-service-representative)
- [Scheduling and Dispatch Software That Puts the Right Crew on Every Job](https://www.brix.so/features/scheduling-dispatch)
- [Technician Utilization Calculator](https://www.brix.so/tools/technician-utilization-calculator)
- [What Is Callback Rate?](https://www.brix.so/learn/callback-rate)

---
Written by BRIX Editorial Team. Last updated 2026-10-12.
Canonical: https://www.brix.so/learn/dispatching