Daily Updates for Multi-Day Jobs

Day three of a five-day roof replacement. The homeowner has watched strangers tear apart her house for 72 hours and nobody has told her a single thing — not what's done, not what's next, not whether they're on schedule. She's not angry about the work. She's anxious about the silence. By day five she'll leave a 3-star review that says "work was fine, communication was terrible" — the most common complaint in contracting, and the most preventable. This is the communication layer of the calendar and dispatch pillar: the daily update that turns a stressful project into a 5-star story.

Why multi-day jobs need their own communication system

Single-day jobs are simple: you arrive, you work, you leave, the customer sees the result. Multi-day jobs are different — the customer lives inside your work zone for days, sees the mess without seeing the progress, and fills the information vacuum with worry. Every day without an update, the customer's mental story drifts: are they behind? did something go wrong? will this take two weeks? The daily update exists to replace that story with yours. It takes the tech or office three minutes, and it's the difference between a customer who endured your project and a customer who'd hire you again.

The end-of-day text: the four-part anatomy

Send it when the crew wraps for the day — 4:30 to 5:30pm, before the customer starts wondering. Four parts, same order every day:

• 1. What got done today. Concrete and visible: "tear-off complete on the south slope, underlayment down." Not "made good progress" — progress is invisible, completed milestones are not.
• 2. What's happening tomorrow. "Tomorrow: north slope tear-off, then we start shingles." This is the anxiety killer — the customer goes to sleep knowing the plan.
• 3. Anything they need to know. Driveway blocked until 9am, water off for an hour, keep the dog inside, crew arriving at 7:30. The logistical details that prevent tomorrow's friction.
• 4. The schedule status in one line. "Still on track for Friday finish" or the honest alternative (below). Never skip this line — it's the one they're actually reading for.

Who sends it (and the 3-minute rule)

The update must come from a human who was on the job — the lead tech, the project manager, or the owner. Not a generic office blast, and not an automated template with no name on it. Customers can smell automation, and a "daily update" that reads like a robot defeats the purpose. The practical setup:

• Lead tech sends it from the company texting number at wrap-up. Give them the four-part template on a laminated card; it takes three minutes once it's habit.
• Office sends it if the tech calls in the four bullet points at 4:30. Better for shops where techs won't reliably text — the office becomes the consistency layer.
• Photos attached, always. One photo of today's progress does more than the words. A picture of the dried-in roof, the roughed-in plumbing, the set concrete — visual proof that the day produced something.

Make it a non-optional line on the job-close checklist: no update sent, the day isn't closed. The first two weeks you'll remind people. After that it's muscle memory.

Delivering bad news: delays and change orders

The daily update is also the vehicle for the two conversations contractors dread most. The rule for both: the update carries the news the day you know it, never the day it becomes undeniable.

Delays. When the schedule slips, part 4 of the update changes — and nothing else does. State the new date, give the one-line reason, and keep the rest of the update normal. Normalcy around the bad news signals that the project is under control, just slower.

Change orders. Never bury a change order in a text and never surprise the customer with it on the invoice. The update announces the discovery ("we found rotted decking under the shingles on the north slope"), states that you'll have pricing tomorrow, and — critically — says no work proceeds on it without their approval. The change order itself gets a separate conversation and a signature. The update's job is just to make sure the discovery isn't a surprise.

The mid-project check-in (day 3 of 5, or the halfway mark)

Once per project, at roughly the halfway point, add a fifth element to the update: a direct satisfaction question. "Quick check — how are we doing so far? Anything bugging you about the project?" This is the early-warning system for the complaint that would otherwise surface as a review. Customers with a small grievance will tell you by text at the halfway mark; the same grievance unaddressed becomes the 3-star review at the end. Ask while you can still fix it.

The final-day update (the review setup)

The last daily update is different: it's the handoff to the review ask. Same four parts, plus the walkthrough invitation and the forward look:

The gratitude is genuine and the walkthrough invitation shows confidence. The review ask comes separately after the walkthrough (covered in the review engine posts) — the final update's job is to end the project on a high note so the ask lands on warm ground. Note the compliance point: the review ask goes to every completed job equally. Never use the daily updates to pre-screen who gets asked — filtering unhappy customers before the review ask (review gating) violates Google's policy.

Installing it this week

Write the four-part template on one page — that's your setup guide (standard operating procedure). Add "send daily update" to the job-close checklist. Brief the lead techs: three minutes, 4:30pm, photo attached, and the bad-news rule (same day you know it). Start it on the next multi-day job that kicks off. Within two projects, customers will start mentioning the updates unprompted — "I loved the daily texts" shows up in reviews with remarkable consistency, because almost nobody in contracting does this.

Related guides in this series

Daily updates are the long-project layer of the Full & Calm Calendar pillar — confirmations get the job started right, arrival windows keep the day predictable, and daily updates carry multi-day projects across the finish line with the customer informed at every step. Together they eliminate "poor communication" as a review category for your business.

The done-for-you version

This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step setup guide, every script, the worksheets, and click-by-click setup instructions for all 8 systems. The daily update template, the delay and change-order scripts, and the final-day handoff are pre-written and ready to hand to your lead techs.

Stats sourced as labeled: no statistics used in this post.

Keep building your systems

Related guides from the Leveraged Owner blog: