Dispatching Without Drama in a Small Service Department

Monday morning, 7:20 a.m. The advisors are already stacking repair orders, one technician is looking for a comeback from Friday, another is asking who got the waiter brake job, and somebody in the back is saying, again, “Just give me anything.” That is how a lot of small service departments dispatch work — not by plan, but by noise.

The trouble is, noise is not a system. In a small shop, it may feel like everybody can just “work it out.” Sometimes they do. But when dispatching depends on memory, personalities, or who hollers first, the same problems keep showing up: your best tech gets buried, your newer tech sits too long, waiters back up, and advisors start making promises the shop cannot keep.

Good dispatching does not have to be fancy. You do not need a giant board, a full-time dispatcher, or a management seminar with laminated acronyms. You need a simple way to get the right job to the right technician at the right time — and a routine everybody follows.

Why dispatching turns into a daily argument

In a small service department, dispatching usually breaks down for one of three reasons.

First, nobody has clearly decided who actually owns dispatch. Is it the service manager? The shop foreman? The lead advisor? If the answer changes by the hour, the process is already in trouble.

Second, jobs are assigned without a real sorting method. Everything arrives as “another RO.” But not every RO is the same. A waiter oil change, a diesel diagnosis, a warranty electrical concern, and a used-car recon ticket should not all be thrown in one pile.

Third, the department confuses fairness with randomness. Fair dispatch does not mean every tech gets the next ticket in rotation no matter what it is. Fair dispatch means work is assigned according to skill, availability, efficiency, promised time, and shop priorities. That is not favoritism. That is management.

When those three points are not settled, people start dispatching around the system. Advisors hand-pick techs. Technicians cherry-pick work. Promised times drift. Then everybody says the same thing: “We’re too busy.” Most times, they are not just busy. They are disorganized.

A simple dispatch system that works in a small shop

Here is the plain version.

Start by sorting every incoming job into a few simple buckets:

• Quick maintenance / waiters
• General repair
• Heavy line / advanced mechanical
• Electrical / drivability / diagnosis
• Internal / used car / recon
• Comebacks and carryovers

Then match each technician to the type of work he or she should normally receive. Not every technician needs one narrow lane, but everybody should have a known range. Your A-level diagnostic technician should not spend the morning buried in basic maintenance if there is electrical work stacked up. Your entry-level tech should not be handed a difficult intermittent concern just because his stall is empty.

Next, establish priorities for the day. In most small departments, the order should look something like this:

1. Waiters and same-day promises
2. Carryovers and confirmed comebacks
3. Customer-pay scheduled work
4. Internal work and recon
5. Fill-in maintenance and menu work

That priority list alone cuts out half the arguing.

Finally, dispatch from one point. One person owns the board, the queue, or the pile — whatever tool you use. That does not mean nobody else can speak up. It means one person makes the assignment. If three people are dispatching, nobody is dispatching.

Process → Procedure → Reference

This is where small departments get relief. Decide how the work should be done, write the steps down, and keep the records that prove the system is being followed.

Process

Your process is the rule for how work flows from write-up to technician assignment.

For dispatching, a sound process is simple:

• One person owns dispatch for each shift
• Every RO is categorized before assignment
• Jobs are assigned by skill, availability, priority, and promised time
• Waiters, comebacks, and carryovers are identified up front
• Advisors do not promise completion times without checking shop capacity
• Exceptions are documented, not handled by hallway conversation

That is the management decision. It sets the ground rules.

Procedure

Now write the steps so the shop can repeat them.

A practical dispatch procedure might look like this:

1. Advisor completes write-up and marks the RO type, promised time, transportation status, and any special flags.
2. Dispatch owner reviews new ROs every set interval — for example, every 15 to 30 minutes, or immediately for waiters and tows.
3. RO is placed in the correct work category.
4. Dispatch owner checks technician availability, current hours assigned, skill fit, and stall status.
5. Job is assigned based on priority first, then best technician fit.
6. Technician acknowledges receipt of the job.
7. If the assignment changes, the reason is noted.
8. At mid-day and again later in the afternoon, dispatch owner reviews carryovers, parts delays, and stalled jobs.

That is enough structure to create order without turning a small shop into a paperwork parade.

Reference

Reference is the proof. If you do not keep a few simple records, dispatching drifts right back into opinion.

Useful references include:

• Daily dispatch log or board snapshot
• RO category and priority markers
• Technician skill matrix
• Promised-time tracking sheet
• Carryover list
• Comeback tracking log
• Exceptions log for reassigned or delayed work

These do not have to be fancy. A whiteboard, printed form, or DMS note can do the job if it is used consistently.

What the service manager should watch every day

If you want dispatching without drama, watch the choke points.

Look for techs with too many assigned hours and others with too few. Watch how long waiters sit before touch time. Review how many jobs were reassigned after initial dispatch. Check whether diagnosis is getting trapped behind easy gravy work. And pay attention to carryovers. Carryovers tell the truth about your day better than the morning production meeting ever will.

Also, be honest about advisor behavior. A clean dispatch process falls apart fast when advisors start side-dealing jobs directly to favorite technicians. That may feel helpful in the moment, but it wrecks the system for everybody else.

A small service department does not need perfect balance every hour. It needs visible control. Your people should know who assigns work, how jobs are prioritized, and what to do when the plan changes.

Start small and tighten it up

Do not try to fix dispatching by rebuilding the whole department next Tuesday.

Start with three things: assign one dispatch owner, create four or five job categories, and post a daily priority order. Run that for two weeks. Then add a technician skill matrix. Then start logging carryovers and reassigned jobs. Small steps, done consistently, beat a big rollout nobody follows.

Dispatching will never be completely quiet. This is still the car business. Somebody will still want to know why another tech got “the good one.” But when the department has a real system, the answer is no longer personal. It is procedural.

And that is when the drama starts to leave the room.

Process → Procedure → Reference — Centennial Business Systems | Centennial Dealership Operating System