How to Handle Schedule Changes When a Contractor Job Running Late

It's 1:15 and you're still ripping out the old vanity. The 2:00 estimate across town isn't happening, and the 3:30 punch-list job behind it is now in question too. This happens to every contractor who runs more than one job a day — tile takes longer than expected, a part isn't where the supplier said it would be, the customer wants to talk through three extra things before you leave. The job itself isn't the problem. How you handle the next three hours is what decides whether you lose a customer or just move a slot.

The mistake most contractors make is waiting too long to decide anything. You tell yourself you'll make up the time, you push through, and by 2:45 you're calling a customer to say you're running late with no real new time to offer. That call lands differently than one made at 1:15 with a plan attached. Speed and specificity are what customers actually judge you on — not whether you're ever late at all.

{"h2":"Decide early, not when you're already late"}

Set a decision point for yourself on every multi-job day: the moment you're 30-45 minutes behind where you expected to be, stop and look at the rest of the day instead of hoping it resolves itself. Waiting until the appointment time has already passed means you're making the call from a worse position — apologizing instead of informing.

A simple rule works well: if you're going to be more than 20 minutes late to the next stop, decide right then whether to push it, swap it, or call in help. Don't wait for the lateness to become obvious to the customer first. If you're running a daily schedule for a small crew, build in a 15-minute buffer between jobs specifically so small overruns don't cascade — but even with a buffer, know your trigger point for acting instead of absorbing it silently.

{"h2":"Call the customer yourself — don't text and don't wait"}

A text that says "running a bit behind, will update you" is better than nothing, but a phone call from you is what actually protects the relationship. Customers forgive lateness far more easily than they forgive feeling managed by an auto-message. If you've got someone answering your office line or an AI receptionist covering missed calls, that's for inbound traffic — the outbound call to warn a customer about a delay should come from you or whoever's running the job, because it carries weight a text doesn't.

Keep the call short and lead with the new information, not the apology:

{"ul":["State the delay plainly: \"I'm still at the Miller job, it ran longer than planned.\"","Give a real new time, not a vague window: \"I can be there by 3:15 instead of 2:00.\"","Ask if that still works for them, and if not, offer the next real alternative.","Keep the apology to one sentence. A long apology makes the delay feel bigger than it is."]},

This is the same instinct behind keeping customers updated during a project — people don't need constant reassurance, they need the one update that changes what they should plan around.

{"h2":"Offer a specific new slot, not an apology"}

"Sorry for the delay" doesn't give the customer anything to act on. "I can be there at 3:15, or if that doesn't work I have 9am tomorrow" gives them a decision to make instead of a feeling to process. Always have the next option ready before you dial — check your schedule for the rest of the day and tomorrow morning before you call, so you're not fumbling for an answer while they're on the line.

If the delay pushes the appointment out by more than two or three hours, offer the next-day slot upfront rather than making them ask for it. Most customers will take a firm tomorrow-morning appointment over an uncertain this-afternoon one.

{"h2":"Protect the next day by moving the smallest job"}

When a job runs long enough to threaten multiple appointments, don't just push everything back by the same amount — that spreads the damage across every customer instead of containing it. Instead, find the smallest or most flexible job on the day and move that one. A quick caulk touch-up or a small punch-list item is far easier to reschedule than a job the customer took time off work for.

This keeps your bigger commitments intact and limits the disruption to one relationship instead of three. It also means you're choosing who gets inconvenienced rather than letting the schedule choose for you. If you're scheduling without double-booking already, you likely have visibility into which jobs are time-sensitive and which aren't — use that information the moment you sense a delay, not after it's already caused a conflict.

{"h2":"Log the reason so you can fix the estimate next time"}

Every time a job runs long, write down why — in the job notes, not just in your head. "Old pipe had to be cut out, added 45 minutes" or "customer added two outlets mid-job" takes ten seconds to log and pays off the next time you estimate something similar. Without that note, you'll make the same scheduling mistake on the next five jobs that look like this one.

Patterns show up fast once you're logging them. If every cabinet install is running 30 minutes over your estimate, that's not bad luck five times in a row — that's a line item in your price book that needs adjusting. The fix isn't working faster, it's scheduling the job accurately the first time.

{"h2":"Where Trusso fits"}

Trusso's scheduling view makes the reshuffle easier because every job, crew assignment, and customer contact lives in one place — when a job runs long, you can see the rest of the day's jobs, call the affected customer, and drag the appointment to a new slot without flipping between a calendar app and a separate customer list. Job notes attach directly to the job record, so logging "ran long because of X" takes seconds and shows up automatically the next time you estimate a similar job. It won't make the late job finish faster, but it removes the friction that turns one late appointment into a chaotic afternoon. Plans run flat-rate at $29/mo for an owner plus 2 crew, $59/mo for up to 10, or $99/mo unlimited, with a 14-day free trial and no contract.