Field notes

The weekly client update.

August 9, 2026 · 6 min read

Ask designers what clients complain about and it is almost never the design. It is silence. The weekly update is the cheapest fix in the business — if writing it doesn't eat your Friday.

Somewhere between the trade showroom, the drapery workroom, and the fourth revision of a millwork drawing, a week disappears. You know exactly what happened on every project. Your client knows none of it. And a client who hears nothing for two weeks doesn’t assume things are going smoothly — they assume nothing is happening, and the Sunday-night “just checking in!” email arrives right on schedule.

The studios that never get that email share one habit: a short, predictable, weekly update — same day, same shape, every project, whether or not anything dramatic happened. Here is the version of that habit we see working, and how to make it cheap enough to keep.

What the update is for

Not documentation — reassurance. The client is spending real money on something they can’t see yet. The update’s job is to make the invisible work visible: decisions made, items ordered, trades scheduled, problems caught. Three short sections cover it:

  • What happened.Three to six bullets, plain language. “Confirmed COM yardage with the workroom” beats a paragraph about drapery logistics.
  • What’s next. One or two lines. What the studio does next week, and any date the client should hold.
  • What we need from you.The most important section, and the one most updates bury. If an approval is blocking an order, say so here, every week, until it isn’t.

Leave out: hour-by-hour narration, vendor drama the client can’t act on, and anything that reads as an apology for the pace of custom furniture. Reassurance, not confession.

Why studios stop doing it

Nobody disputes that updates are good. Studios stop because of how the email gets made: scroll the texts, scroll the email thread, open the project folder, try to remember what the electrician said Tuesday — times five projects, on a Friday afternoon. Forty-five minutes per update is why the habit dies by week six.

The fix is unglamorous: keep one running log per project, in one place, as the week happens. A two-line entry when the tile order confirms. A photo and a sentence after the site visit. By Friday the update writes itself — you are curating a list that already exists, not reconstructing a week from memory.

The twenty-minute Friday

One studio we work with runs five active projects and sends every update before Friday lunch. The routine:

  1. Skim the week’s activity per project — their communication log, completed tasks, and client approvals live in Studiohaus, so the week is already one scrollable list.
  2. Pick the three-to-six bullets a client actually cares about. Skip the rest.
  3. Drop them into the studio’s update template — same greeting, same three sections, studio branding — tweak the voice, send.

The newest version of this routine hands step two to an assistant: with Studiohaus’s read-only AI connection, the studio’s own AI (Claude, in their case) pulls each project’s week of activity and drafts the update in the studio’s template. The designer edits tone and hits send. The AI never touches the project — it can only read — and the designer stays the author. Twenty minutes became eight.

Make it a system, not a resolution

  • Same day, every week. Predictability is most of the value. A boring update on schedule beats a brilliant one that arrives whenever.
  • One log per project, kept as you go. Whatever tool you use, the log is the system; the email is just its summary.
  • Template the shape once.Clients learn where to look for “what we need from you.” That alone shortens approval cycles.
  • Send it even on quiet weeks.“Lead times are long; everything is on order and on track” is a complete, valuable update.

The studios that do this stop fielding check-in calls, get approvals back faster, and — the part nobody predicts — get referred more. A client who always knew what was happening tells the next client exactly that.