Guides
Homeowners call when nobody told them what happened this week. How to send a regular update by hand, and how we'd automate it.
It's Wednesday afternoon and you're on a ladder when your cell rings. The homeowner drove past the lot on the way to work, saw nobody there, and wants to know if the job stalled. It didn't. The framing inspection got pushed to Thursday and you told the framer to hold. You told your super, you told the framer, you moved it on the schedule. Nobody told the people paying for the house.
So you climb down and explain it. That evening their spouse texts the same question, because the first call didn't get passed along. Friday your office manager gets a call asking whether the cabinets came in, and has to text you to find out, and you answer from the truck at a red light.
The same thing happens on good weeks. Framing passed, the windows are in, the slab is poured. You know because you were there and your camera roll is full of it. Monday the lender asks for a progress note on the same house, and you write it again from scratch in different words.
None of this is new information. The update already exists, spread across your head, your camera roll and three text threads. What's missing is the one message that puts it in front of the homeowner before they start to wonder. A homeowner who hears about a delay from you on the day it happens stays calm. One who finds out by driving past starts wondering what else nobody told them, and every call after that starts from suspicion.
Pick one day and time for updates. Friday afternoon suits most builders: the week is done and the homeowner has the weekend to read it. Set a recurring calendar reminder for that slot on every active job. A fixed day tells the homeowner when news is coming, so they wait for it instead of calling on Wednesday.
Make one update template. Create an email template, or a saved note on your phone, with four short headings: what got done this week, what's planned next week, anything that moved and why, and any decision you need from them with the date you need it. The same headings every week mean you fill in blanks instead of writing from scratch, and the homeowner learns where to look.
Make a photo folder per job. Set up a shared folder for each job. When you take a photo on site, drop it there before you leave instead of leaving it in your camera roll. On Friday you pick from the folder instead of scrolling past three other houses.
Keep a running note per job. One note on your phone or one simple spreadsheet per job, one line each time something happens: "Rough plumbing inspection passed." "Cabinets pushed, supplier delay." On Friday most of the update is copied from those lines, not pulled from memory.
Send delays the day they happen. Don't save a slipped date for Friday. When something moves, send two or three lines that day: what changed, why, and the new date if you know it. A homeowner takes a delay better when they hear it from you than when they notice an empty lot.
Write it once and send it to everyone who needs it. Put both homeowners on every update and copy your office. Save the sent copy in the job folder. When the lender or the office asks for a status, you forward what you already wrote instead of retyping it, and you have a record of what the homeowner was told and when.
Set the rhythm at kickoff. Tell every new client: you'll hear from me every Friday with photos, and the same day if anything changes. Once they know when news comes, they have less reason to call in between.
This works on the weeks it gets done. The trouble is the weeks it doesn't. Friday afternoon is also when the drywall crew needs paying, a sub calls about Monday, and a new lead wants a walk-through. The reminder pops up and you swipe it away for later. Later turns into Sunday night, and by then you're writing four updates from memory with photos scattered across your phone.
The running note only holds what someone remembered to type. Same-day delay messages depend on you thinking of the homeowner at the moment something goes wrong, which is the moment you're busiest fixing it. If your office manager sends the updates, they have to chase you for what happened, which is the same retyping you set out to stop. With several jobs running, the update for the quiet job is the one that slips, and that's the homeowner who calls.
The whole system depends on one person remembering, every week, on every job. That's the part that fails.
Milestone photos and status notes go out to the homeowner on a schedule you set, pulled from what already happened on the job that day. The photos your crew takes on site and the notes and schedule changes you already record become the update, so nobody has to remember to write it.
It's built inside the accounts you already own: your email and calendar, your phone number, QuickBooks Online, and JobTread if you use it. There's nothing new for you or the homeowner to log into, and the homeowner hears from you, not from a new system.
You decide what needs your eyes. A routine update can go out on its schedule, while a delay, a change order or anything touching money comes to you to review and approve before the homeowner sees it. Your job records stay in accounts you own, and the AI step that drafts each update runs on your own AI subscription.
You stop fielding a worried call asking what's going on, because nobody told them. This time someone did.
If you want to see how this would fit your jobs, book a free discovery call. You leave with a written plan for your client updates, whether you build it yourself from this guide or have us build it.
Written by Oak City Intelligence's AI writer and reviewed before publication.