What Should You Do When a Job Takes Longer Than Estimated?

When a job takes longer than estimated, decide immediately whether the overrun is your miss or a genuine scope change, then tell the customer before the day the job was due to finish — not after. If it's your estimating error, absorb it and move on. If it's a documented scope change, that's the only time you bill more, and only with a signed change order backing it up.

Every contractor underestimates a job eventually. A wall turns out to be plaster over lath instead of drywall. The crew hits a cast-iron pipe nobody could see. A customer adds "one more thing" on day two that turns into a day and a half. None of that is unusual. What's unusual — and what actually damages a business — is handling the overrun badly: going silent, surprising the customer with extra charges at the end, or eating costs you had every right to bill for because you never documented the reason the job ran long.

Step One: Figure Out Why It's Running Long

Before you say anything to the customer, answer this question honestly: is the extra time because you misjudged the job, or because something changed after you quoted it?

• Your miss — you underestimated labor hours, didn't account for prep work, or missed a detail during the walkthrough. This is on you. The customer shouldn't pay more because your math was off.
• Scope change — the customer added work, changed a selection, or a condition appeared that genuinely couldn't have been seen at the time you estimated (hidden rot, undersized electrical, a sub who no-showed through no fault of yours in some cases). This can justify more time and, with documentation, more money.
• Something in between — a condition you should have caught with a better walkthrough. If you regularly get surprised by the same category of hidden cost, that's a sign your site visit checklist needs work, not that the customer owes you for it.

Be honest with yourself here. It's tempting to reclassify your own estimating miss as a "surprise" so you can bill for it. Customers can usually tell the difference, and a contractor who blames every overrun on hidden conditions loses credibility fast.

Tell the Customer Before the Deadline, Not After

The single biggest mistake contractors make with a running-long job is staying quiet until the original completion date arrives and then explaining why it didn't happen. By then the customer has already rearranged their week around a finish date you knew — or should have known — you weren't going to hit.

As soon as you know the job will run past the estimate, call or text. Don't wait for the customer to ask. The message is simple: what's taking longer, why, how much more time you need, and whether it affects the price. If the delay also pushes other appointments on your schedule, loop that into the same conversation rather than letting each affected customer find out separately — see how to handle schedule changes when a job is running late for the scheduling side of this.

What to Say

Keep the script short and specific. Vague updates ("running a little behind, should be done soon") create more anxiety than clear ones.

• State the fact: "We found [specific issue] once we opened up the wall."
• State the impact: "That adds about [X] hours / 1 extra day to finish properly."
• State the cost, if any: "This is a scope change outside the original estimate, so I'll send you a change order for [$X] before we continue" or "This one's on us — no change to your price, just timing."
• Give a new target: "We're now looking at Thursday instead of Wednesday."

That last point matters as much as the first three. A customer can tolerate a delay. What they can't tolerate is an open-ended one with no new date attached.

Only Bill More for Documented Scope Changes

If the overrun qualifies as a real scope change, don't just add it to the final invoice and hope the customer doesn't push back. Write it up before the extra work continues: what changed, why, the added cost, and get sign-off — a text reply saying "approved" is better than nothing, a signature or online approval is better still. For the full process on pricing and documenting this correctly, see change orders 101.

Skipping this step is how a legitimate overrun turns into a disputed invoice. A customer who sees an unexplained higher number at the end — with no heads-up and no paperwork — has every right to push back, and in most cases they'll win that argument, because you have nothing in writing to support the charge.

If It's Your Miss, Absorb It and Move On

If the job ran long because you underestimated it, don't pad the invoice to recover the loss quietly. Eat it, finish the job well, and use it as information. One overrun on one job is a rounding error. The same type of overrun on every kitchen remodel you bid is a pricing problem, and padding invoices to cover for it will eventually get you caught and cost you the customer relationship entirely.

Fix the Pattern, Not Just the Job

After the job is closed out, spend ten minutes figuring out why the estimate was wrong, specifically. Was it a line item you consistently underprice? A category of hidden condition you keep getting surprised by? A task you never time correctly? Feed that back into your numbers rather than just making a mental note. If you're estimating the same type of job repeatedly and it keeps running long for reasons you *could* have anticipated, your estimate contingency is probably set too low for that job type.

This is also where having your estimates and actuals in one place pays off. Trusso keeps every estimate tied to your own price book, so when a job type consistently runs over, you can see it across jobs instead of relying on memory — and when a scope change does happen mid-job, you can generate and send the change order from the same app you're already using for scheduling and invoicing, so there's a clean paper trail instead of a text thread nobody can find later.