Write down how the day gets built
An experienced dispatcher makes dozens of judgement calls a day and cannot explain most of them. That knowledge is a risk while it is undocumented, and it is why a second dispatcher never works out.
Record the actual rules:
- How long each job type really takes, including travel and paperwork
- Which technicians can do which work
- Which customers require a specific person
- What warrants moving an existing appointment
- How emergencies are absorbed
- How much slack each day should hold
Most of this exists only as habit. Writing it down is what allows anyone else to do the job.
Get durations from data, not memory
Schedules break because job times are estimates and estimates are optimistic. Record real start and finish times for a month and compute the actual average and the spread by job type.
The spread matters as much as the average. A job averaging two hours that sometimes takes five needs a different slot from one that is reliably two hours.
Structure the day around geography
Sugar Land, Missouri City, Stafford and the surrounding areas are close together, but the wider metro is not. A schedule that sends a technician from one side to the other and back loses most of an afternoon.
The structure that scales:
- Assign each technician a zone for the day
- Book new work into the zone that already has a technician near it
- Hold a small amount of flexible work to fill gaps in each zone
- Set realistic travel allowances that reflect time of day
Separate the roles hiding inside dispatch
As a business grows, dispatch quietly absorbs several jobs: taking new enquiries, scheduling, routing, customer updates, technician support, parts ordering, and following up quotes.
That is not one role. The natural split:
- Intake — answering enquiries and booking routine work
- Dispatch — building and adjusting the day
- Support — customer updates and technician assistance
Splitting these lets you add capacity where it is actually short instead of hiring another generalist.
Instrument it
Without numbers you are managing by how busy people feel. Track weekly:
- Jobs completed per technician per day
- Wrench time percentage
- Reschedules, and the reason for each
- Second visits caused by wrong parts or wrong skills
- Time from enquiry to appointment
Watch the trend rather than the week. A slow decline in wrench time is the earliest sign that the structure has outgrown itself.
Plan for the seasons you already know about
Demand in this market is predictable — cooling in summer, heating in the occasional cold snap, storm-driven work after heavy weather. Plan capacity, overtime arrangements and subcontractor relationships before the season rather than during it.
A business that arranges overflow help in April is in a much better position than one calling around in July.
Choose tools last
Software helps once the process exists and makes a bad process faster if it does not. Get the rules written and the durations measured first; then a scheduling system encodes something that already works.
Frequently asked questions
Why does hiring a second dispatcher rarely work?
Because the decisions are undocumented. An experienced dispatcher makes dozens of judgement calls a day and cannot explain most of them, so nobody else can take the work on.
Where should job durations come from?
Recorded start and finish times over a month, not memory. Compute the average and the spread by job type — a job averaging two hours that sometimes takes five needs a different slot from a reliable two-hour job.
How should the day be structured?
By geography. Assign each technician a zone, book new work into the zone that already has someone nearby, hold flexible work to fill gaps, and use travel allowances that reflect time of day.
What roles are hiding inside dispatch?
Intake, dispatch and support — answering enquiries, building the day, and customer updates plus technician assistance. Splitting them lets you add capacity where it is actually short.
When should I buy scheduling software?
After the rules are written and durations measured. Software encodes a process; it makes a bad one faster rather than better.