There is a particular kind of exhaustion that shows up in owner posts across Reddit, Quora and the trade Facebook groups: "I am on the tools all day AND every job flows through my phone. My crew cannot find an address without calling me. I am a human router." It reads like a staffing problem, and the usual reply is "hire a dispatcher". But at three to eight staff, the maths rarely supports a full salary, and the real problem is architectural: all job information lives in one head, so all questions route to one phone. You do not need a dispatcher yet. You need the information to stop living in you.
Count your interruptions for one week
Before changing anything, log a week of calls and texts in three buckets: "where or what is my next job", "status updates from the field", and "genuine decisions". Small-business bodies like the SBA keep flagging owner overload as a growth ceiling, and owners who do this consistently find 70 to 80 percent of interruptions are the first two buckets, which are purely informational. Only the third bucket needs you. That number is your business case, and it will be embarrassing.
Give every job a single home
The root cause is that the answer to "where am I going" lives in your memory, your texts and a diary on the ute seat. Move every job into one system with the address, contact, gate code, notes and materials attached, and give the crew the mobile app. The question "where next" is now answered by a glance at a phone, not a call to yours. This single change typically kills half the interruptions in the first week.
Let status flow up without being asked
The other half of your calls are you asking the field what is happening. Live job status inverts that: en route, on site, blocked, done, visible on the dispatch board without a single call. The emergency callout stops being a ring-around; you can see who wraps up next and drag the job onto them. Crews prefer it too, because a status tap beats narrating their day on the phone.
Push decisions to the edge with simple rules
A chunk of "genuine decisions" are actually policies you have not written down. If the part costs under X, buy it. If the extra work is under an hour, do it and note a variation. If the customer is not home, photo the door, wait fifteen minutes, next job. Write ten rules like that, put them where the crew works, and a third of your decision calls vanish. What remains is the judgement work that actually deserves an owner.
The stepping stones to a real dispatcher
With information centralised, the dispatcher role shrinks from a salary to a part-time seat: many businesses give scheduling to an office partner or a senior tech for the first hour of each day. When call volume genuinely outgrows that, hire, and note the interview advantage: you are handing over a working board with history, not a phone number and chaos. The role starts productive on day one, and your hiring decision is grounded in the interruption log you kept, not burnout.
Frequently asked questions
When can a trade business afford a dispatcher?
Run the interruption log first: when informational calls are gone and genuine scheduling decisions still consume more than an hour or two of an owner's day across eight-plus field staff, a part-time scheduling seat usually pays. Many businesses discover after centralising job information that the full-time role they budgeted is actually two hours a morning.
What is the fastest way to cut where-do-I-go calls?
Put every job, with address, contact, gate codes and notes, into a system the crew opens on their phones, and stop answering the question by text from day one. The calls collapse within a week because the answer is now faster to look up than to ask.
How do standing rules reduce decision calls?
Most field decisions repeat: small purchases, minor variations, no-access, running late. Writing the ten most common as explicit rules, with money limits, moves them from the owner's phone to the tech's judgement, safely bounded. What still reaches you is the genuinely unusual, which is the part of the job an owner should keep.
The bottom line
The pattern across every topic on this blog repeats here: the businesses that win are not working harder, they are keeping better records and letting systems carry the routine. Start with one change this week, measure it for a month, and let the results argue for the next one. And if you want the whole loop, scheduling, field app, safety and invoicing in one place, start a free SKEDS trial and test it on a real week of your own jobs.
Key takeaways
- Log a week of interruptions; most are informational, not decisions
- Move every job into one system the crew can see on their phones
- Live status replaces the daily ring-around
- Write ten standing rules so field decisions stop routing to you
- Hire a dispatcher when the log says so, and hand over a working board
Stop running the job from a spreadsheet
Schedule your crew, run jobs from the van, and invoice the moment they are done. Free for one user, forever.
Start free trial

