Tell a client about a delay before they ask, using four parts: what happened, the new date, what you're doing about it, and what it means for anything downstream. Delivered early and specifically, a delay update builds trust; delivered late or vaguely, it reads as an excuse. Miscommunication and poor project data account for 48% of all rework on U.S. construction jobsites, and a large share of that traces back to updates that didn't go out when they should have.
Every job hits a delay eventually — a failed inspection, a sub who no-shows, a backordered vanity. The delay itself rarely costs you the client. What costs you the client is how long it takes them to hear about it, and from whom. If they find out because they called you first, you've already lost ground you don't get back.
Why builders put off the call
It's an uncomfortable conversation, and there's a temptation to wait until you have better news — the new date confirmed, the sub rescheduled, something more solid to say. That instinct is backwards. The gap between when you know and when they know is the part that erodes trust, not the delay itself. A client who hears about a two-day slip the same day it happens stays calm. A client who has to call and ask why nobody's shown up in three days starts assuming the worst.
The cost of staying quiet
This isn't just a feelings problem. Miscommunication and poor project data account for 48% of all rework on U.S. construction jobsites, according to "Construction Disconnected," a report from FMI Corporation and PlanGrid that surveyed nearly 600 construction leaders (source: Construction Executive, reporting on the FMI/PlanGrid study). A late or vague update isn't just an awkward phone call — it's the same failure mode that produces redone work: information that should have moved and didn't.
The four-part update
A delay update that actually lands has four parts, in this order:
- What happened. One or two plain sentences — the inspection didn't pass, the tile shipment is delayed, the plumber had a family emergency. No jargon, no over-explaining.
- The new date. A specific one. "We're now looking at finishing the week of the 14th" beats "soon" or "hopefully next week" every time — vague timelines are what generate the anxious follow-up calls.
- What you're doing about it. Rescheduling the inspection, sourcing the tile from a second supplier, shifting the next trade to keep other parts of the job moving. This is the line that turns a delay into evidence you're still running the job.
- What it means downstream. If the delay pushes their move-in date or another milestone they're planning around, say so now. Finding out about a downstream impact a week later, separately, reads as if it was withheld.
An example
"Quick update on the bathroom: the rough-in inspection got pushed to Thursday because the inspector's office is backed up this week, not because of anything we did wrong. That moves tile start to Monday and pushes final completion to the 22nd instead of the 18th. I've already got the tile setter rebooked for Monday so we don't lose more time than the four days. I'll confirm Thursday once the inspection's done."
That message takes under a minute to write and answers every question a client would otherwise call to ask.
Make it a habit, not a crisis response
The builders who handle delays well aren't the ones with fewer delays — every real-world job has them. They're the ones who've made the update automatic: something that goes out the same day, every time, regardless of how small the slip is. That's easier to keep up when the update is drafted from wherever your schedule already lives instead of written from scratch each time. Lilli's free schedule builder is set up to draft that update from your plan when a date moves, so the habit doesn't depend on remembering to do it on the day something goes wrong.
Questions, answered.
How do you tell a client their remodel is delayed?
Call or message them before they'd have reason to ask, and cover four things: what happened, the new date, what you're doing about it, and whether it affects anything else on their timeline. Specific beats reassuring — a real date lands better than "soon."
Should you call or text a client about a delay?
Call for anything that moves the completion date or costs money; text or email is fine for minor, same-week slips that don't change the overall schedule. The bigger the delay, the more it deserves a live conversation instead of a message they read alone.
How far in advance should you tell a client about a delay?
As soon as you know, not as soon as they ask. If an inspection fails or a sub cancels, that's the day to send the update — not the day of the appointment they were expecting, and not after they've already texted asking where things stand.
What's the biggest mistake builders make when delivering bad news to clients?
Going quiet. Silence reads as either incompetence or something being hidden, even when the actual cause was a permit office or a supplier. A short, honest update sent early does more for trust than a perfect explanation sent late.
How do you keep a delay from turning into a bigger problem with the client?
Pair the bad news with the plan. A delay alone sounds like the job is out of control; a delay plus "here's the new date and here's what I'm doing to hold the rest of the schedule" sounds like a job that's still being run.