The Tech Who Runs Behind Every Day: Decision Tree

Why this matters

Every shop has a tech who is always running late, every day, no matter the schedule. It is rarely that they are slow with their hands. It is almost always a process problem: where time leaks out of the day in places nobody is watching. This is a fault tree for finding the leak. Work it from the most common and easiest-to-check cause toward the harder ones, the same way you would diagnose a piece of equipment.

Start here: is the schedule itself realistic?

Before blaming the tech, rule out a schedule that nobody could hit.

• If the jobs are booked back to back with no travel time or buffer between them, the tech is not behind, the schedule is fiction. Fix the booking to include realistic drive and setup time. A tech cannot beat a calendar that assumes teleportation.
• If the schedule has reasonable time and the tech still runs behind, move to the next branch. The leak is in how the day is run.

Branch one: is the day starting late or unprepared?

The most common real cause is a morning that begins with a scramble instead of a plan.

• If the tech leaves the shop without reading the schedule, staging the truck, or knowing the first job, the whole day starts behind and never catches up. Fix the morning routine and the night stage. A prepared departure is the single biggest lever here.
• If the mornings are clean but the day still slips, keep going.

Branch two: is drive time eating the day?

A tech who looks slow is often just driving too much.

• If the route zigzags across town because jobs were booked first-come instead of by area, the drive time alone can sink the day. Fix the routing: cluster by area, anchor the time-locked jobs.
• If the tech keeps returning to the shop or supply house for forgotten parts, that is the two-trip problem bleeding the schedule. Fix it with staging and truck stock.
• If the driving is tight and there are no surprise return trips, the leak is at the jobs themselves.

Branch three: is each job running long?

If the route is clean but every job overruns, the time is leaking on site.

• If the tech diagnoses by trial and error, swapping parts and re-checking, the diagnosis is eating the clock. Tighten it: confirm the symptom, measure toward root cause, do not throw parts at it.
• If the tech does the work fine but lingers, the issue may be unclear scope or scattered focus. Batching similar jobs and setting a clear plan per job both help.
• If the jobs are genuinely bigger than booked, that is an estimating problem at the desk, not a speed problem in the field. Fix how those jobs are scoped and timed when booked.

Branch four: is paperwork stealing time from the next job?

Sometimes the tech is on time at the work but loses the gap doing paperwork the wrong way.

• If the tech stops to do lengthy write-ups or billing in a way that bleeds into the next appointment, restructure it. Capture quickly at the truck between jobs, not in long blocks that push everything back.
• If the paperwork is being saved for the evening and the days still run late, the leak is elsewhere; recheck the branches above.

Branch five: is the tech absorbing chaos from outside?

Some "behind" is not the tech's process at all.

• If the tech is constantly handed last-minute add-ons, emergency squeeze-ins, or changes mid-day, the schedule is being disrupted faster than anyone could keep up. Fix the dispatch discipline: protect the route, slot urgent work deliberately, do not pile onto whoever answers.
• If the tech keeps getting the hardest or least-defined jobs while others get clean ones, the load is uneven. Balance it.

When it is genuinely the tech

If you have worked every branch above and the schedule is fair, the mornings are prepared, the route is tight, the diagnosis is sound, the paperwork is captured at the truck, and the day is not being disrupted, then it may be a pace or skill gap that coaching can close. But check the process first. Far more "slow techs" are actually fast people stuck in a leaky process than the other way around. Fix the process and most of the problem disappears.

How to actually find the leak

Do not guess. For a few days, note where the time actually goes: departure, driving, each job's length, paperwork, disruptions. The pattern shows up fast and points at the branch to fix. One leak usually dominates. Plug the biggest one first and the days stop running long.

References

• See related: The Morning Routine That Saves an Hour.
• See related: Minimizing Drive Time Without Software.
• See related: The Two-Trip Problem and How to Kill It.
• Trade-standard time-management and dispatch practice.