Where technician overtime actually comes from

Most technician overtime is not caused by too much work. It is caused by small errors in drive time and job duration that pile up through the day and all land on the last job. To reduce technician overtime, fix how the day is planned and re-planned, not how hard people work.

Ask an owner where overtime comes from and you will hear about busy season, a tech who works slowly, or an emergency that came in at 3:00. Those happen. But pull a month of time cards and look at which days ran over. You will usually find something duller. The days that ran over were not the days with the most jobs. They were the days where every job ran a little long, or every drive took a little longer than the board assumed.

The late-day cascade

A schedule is a chain. Each job's start depends on the previous job's finish plus the drive. When one job runs 10 minutes long, the next starts 10 minutes late. Nothing absorbs the delay unless there is slack between jobs, and most boards have very little, because slack looks like waste.

So the delay travels down the chain. By the last job, the tech is carrying the sum of every overrun of the day.

End-of-day overrun = Sum of (Duration error + Drive error) for every job − Slack on the day

Nobody on that board did anything wrong. Six minutes over is a normal job. Five minutes over on a drive is one stoplight and a slow gate. But 3.3 hours a week, on a tech who was already scheduled for 40, is 3.3 hours of overtime.

Under federal law, that time costs more. As of October 2026, the U.S. Department of Labor says covered nonexempt employees must receive overtime pay for hours worked over 40 in a workweek at not less than time and one-half their regular rate. States can add their own overtime rules, so check your state's labor department.

The overtime cost definition breaks down the full loaded cost. The technician overtime cost calculator will put a yearly number on it for your crew.

Why drive error is the bigger half

Duration errors at least average out a little. Some jobs run long, some finish early. Drive errors tend to run one way, because a board that hides or guesses the drive almost always guesses low:

• The drive is hidden in the job block. A two-hour block that is really 30 minutes of drive and 90 of work has no room for a slow drive.
• The estimate is from the shop. A drive measured from the shop says nothing about the drive from the job before.
• The estimate ignores the hour. The same 12 miles at 4:30 p.m. is not the 12 miles at 9:00 a.m. Afternoon drives run long exactly when the day has no slack left.

That last one is why overtime clusters at the end of the day. The afternoon drives are often the longest and the least accurately planned, and they come after the morning's overruns have already used up the slack. Windshield time covers why drive time stays invisible on most reports.

Four fixes, in order of how much they help

1. Plan the day with the drive on it

Put the drive between jobs on the board as its own block, measured from the previous job, at the hour it will happen. A day that looks like six jobs might honestly be five once the drives are real. Booking five is not losing a job. It is not paying overtime to do the sixth late. The guide to planning a dispatch day around drive time walks through the sizing.

2. Re-plan at halftime, not at 4:30

The cascade is only a problem if nobody sees it coming. If a tech knows at 11:00 that the current job needs another 30 minutes, the office has five hours to move the 3:30 job to someone with room. If the office finds out at 4:30, the only option left is overtime.

CrewLink's tech app does this with a mid-job check-in. About halfway through a job it asks whether the tech is on track or needs +15, +30 or +60 minutes. An extension re-flows the rest of that tech's day right away: later jobs that no longer fit go to a teammate who can make the same time, or move to the nearest open time, and the affected customers are texted.

3. Protect the last slot

The last job of the day absorbs everything. Do not put your longest, least predictable, or farthest-away job there. A short, close, predictable job in the last slot gives the day somewhere to land. If something has to be far, put it in the morning when drives are shorter and nothing has gone wrong yet.

4. Put slack where the cascade starts

A few minutes of slack in the middle of the day does more than the same minutes at the end, because it stops the delay before it reaches the afternoon drives. Slack after the jobs with the widest duration range does the most of all.

How to tell if your overtime is a scheduling problem

Pull four weeks of time cards and the matching boards. For each day that ran over, ask:

1. Did the tech have more jobs than usual? If yes, it may be demand.
2. Did one job run very long? If yes, it may be estimating.
3. Did every job and drive run a little over? That is the cascade.

If most overtime days are the third kind, more techs will not fix it. Each new tech will get the same board.

Common questions

How do you reduce technician overtime?

Start with the schedule. Put real drive times on the board, measured from the previous job and at the hour of the drive. Check in mid-job so the office can move late-day work while there is still time, and keep the last slot short and close.

Is technician overtime always a bad sign?

No. Peak-season overtime can be cheaper than hiring someone you cannot keep busy in the slow months. The problem is overtime that comes from planning errors, because you pay time and a half for work that was not extra.

Why do technicians always run late at the end of the day?

Because delays add up. Each job that runs long and each drive that takes longer than planned pushes everything after it, and the last job of the day carries the total.

How do I calculate what overtime costs my company?

Multiply overtime hours by 1.5 times the regular rate, then add the burden that scales with pay, such as payroll taxes. The overtime cost calculator does this across a crew for a year.