What an Extra Day on Every Job Is Actually Costing You

A job runs one day over schedule. The customer is understanding. Nobody files a complaint. You move on to the next job.

That response - treating the overrun as a rounding error - is exactly what makes it expensive. The true cost of a one-day overrun rarely shows up on the job that caused it. It shows up on the job that was waiting for it to finish, in the rescheduling that follows, and in the monthly margin review that produces a number nobody can quite explain.

The Cost Is Never Just the Extra Day

When a job runs long, the day you lose is the least expensive part of the problem.

A one-day overrun on Monday's job pushes Tuesday's scheduled start back by a day. If a sub-contractor was booked for that start date, you are now paying for a rescheduling conversation at minimum - and a wasted day's labour at worst. If materials were organized for delivery to coincide with that start, those plans shift too. The customer waiting for the next job gets a revised timeline nobody planned to give them.

This is the cascade that makes a single day's overrun disproportionately expensive. The direct cost of running one day long might be a few hundred pounds in additional labour. The second-order costs - the rescheduling, the call, the revisit, the wasted journey - often run two or three times higher than the direct figure.

For businesses running multiple jobs concurrently, this compounds fast. Every overrun compresses the buffer between jobs until there is no buffer left. At that point, delays stop being recoverable. Every problem in the diary becomes an emergency.

You Usually Find Out When It Is Too Late to Do Anything

Research published by the Royal Institution of Chartered Surveyors found that 64% of small UK building firms only discover cost or time overruns after the job is finished. This is not a statistic about catastrophic failures. It describes normal businesses running normal jobs - without the visibility to catch problems while there is still time to act.

When an overrun surfaces at the end of a job, the decisions are already made. You cannot reassign the labour that has already been spent. You cannot renegotiate the sub-contractor invoice that has already been raised. You cannot recover the margin that has left the business. What remains is a final account that does not add up, and no clear path to prevent the same outcome on the next job.

The structural cause is straightforward: most small businesses review job profitability once, at the end. That turns a project review into a post-mortem. A post-mortem can explain what went wrong, but it cannot change the outcome.

The Margin Math Most Owners Do Not Run

The financial impact of time overruns is typically larger than it looks because the extra cost comes directly off margin, not off revenue.

On a job scoped to take ten days, carrying a 35% gross margin, a 10% time overrun adds roughly one day's additional labour and overhead to the total cost. That increase hits the margin, not the quoted price. Analysis of the cost overrun formula - where overrun cost is subtracted from profit rather than from revenue - shows that a 10% cost overrun on a 35% margin job wipes close to a fifth of that job's total profit. (These figures are illustrative; the impact depends on your own cost structure and margin level, and this calculation should be applied to your actual numbers.)

The practical implication is uncomfortable: a business that quotes accurately, wins jobs at the right price, and delivers technically competent work can still end the month with disappointing margin, simply because delivery took marginally longer than planned across a handful of jobs.

This pattern rarely appears as one clear problem in the accounts. It shows up as margin that is consistently lower than expected, without a single obvious cause.

What Useful Visibility Looks Like in Practice

The fix is not more effort at the end of a job. It is a different check at the midpoint.

For any job running across more than two or three days, there are two questions worth answering halfway through: is the job on track against the original time estimate, and if not, what is the cause? A scope change that expanded the work without a corresponding price adjustment is a different problem from a job that was underestimated at the quoting stage. Both affect the final result, but the action each requires is different.

Job costing connects time tracked to margin earned - not just at the final account stage, but during delivery, where the information can still influence the outcome. A business that reviews this consistently does not eliminate overruns. It catches them early enough to respond. Knowing a job is running a day long on day three is recoverable. Finding out on day eight is not.

Zigaflow's jobs feature gives businesses a live view of where each job stands against the original scope, without waiting for a manual end-of-month review. That visibility is what moves the discovery of a problem from "after the job" to "while there is still time."

For a broader look at the patterns your completed jobs can reveal, see What Your Finished Jobs Are Still Trying to Tell You. And if scope creep is driving your overruns rather than poor time estimation, that is a separate problem worth diagnosing on its own terms.

Sources

• The Hidden Cost Killing Your ProfitHBXL · accessed 2026-08-27
• Construction Overruns: Why Projects Go Over Budget?Livecosts · accessed 2026-08-27
• Cost Overrun: Causes, Calculation & How to Prevent ItProductive · accessed 2026-08-27

Related pages