Where Time Leaks on a Typical Job
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
When a job runs long, it rarely blows up in one dramatic way. It leaks — thirty minutes here, an hour there, across a handful of predictable spots that don't feel like much in the moment but add up to a job that's well over its quote by the end. The good news about predictable leaks is that they're predictable. Job time doesn't vanish randomly; it leaks in the same recurring places, and once you know where to look, you can see the overruns coming and quote for them.
WHERE THE HOURS GO (typical job)
setup / getting started ........ longer than you think
waiting (parts, decisions, access) ... dead time
interruptions / task-switching ....... hidden drag
surprises / hidden problems .......... the big one
rework / callbacks ................... paid once, done twice
cleanup / wrap-up / admin ............ always underestimated
──────────────────────────────────────────────────────────
None feels big alone. Together, they blow the quote.Owner symptoms
Jobs run over but you can't point to one big cause.
The overrun is lots of small delays, not one disaster.
The same time-sinks recur job after job.
Why this happens
Time leaks are easy to miss because each one is small and feels like a normal part of the day. You don't count the extra setup, the twenty minutes waiting on a decision, the interruption that broke your flow, the surprise that ate an hour. Individually they're forgettable; collectively they're the reason the job ran two hours over. Because you never tallied them, they don't make it into your next quote, so the same leaks drain the same hours on the next job.
Common mistakes
Looking for one big cause when it's many small leaks.
Not counting the "small" delays, so they never enter your estimates.
Treating waiting and interruptions as free when they cost real hours.
How experienced operators think about it
They know their leaks by name. Rather than treat overruns as mysterious, they've noticed the recurring spots where their jobs bleed time — setup, waiting, surprises, rework — and they plan and quote with those in mind. Their instinct after a long job is to ask where exactly did the time go? so the answer sharpens the next estimate. Predictable leaks, to them, are just costs to account for, not surprises to absorb.
Practical actions
Audit one long job — where exactly did the hours go?
Name your recurring leaks — the spots that drain time on most jobs.
Quote for the leaks you know will happen, especially waiting and surprises.
Attack the biggest leak — reduce it where you can (better prep, fewer interruptions).
Questions every owner should ask
On my last over-budget job, where exactly did the time go?
What time leaks show up on most of my jobs?
Which leak is biggest — and could I reduce it?
Frequently asked questions
Where does job time usually leak?
In a handful of predictable spots: setup, waiting on parts or decisions, interruptions, hidden surprises, rework, and wrap-up. Each feels small in the moment, but together they're what push a job past its quote.
How do I stop the leaks?
First see them — audit a long job to find where the hours went. Then reduce the biggest ones where you can, and quote realistically for the ones you can't eliminate.
Related articles
Jobs Take Longer Than I Quoted — the pillar.
Scope Creep: The Quiet Margin Killer — a major leak of its own.
Building in Buffers Without Padding Every Quote — quoting for leaks.
Try a free Weekly Focus assessment
If your jobs leak time in ways you can't quite pin down, finding the leaks is the first step. Throne of Profit's free Weekly Focus assessment is a no-cost way to start.