Most client relationships don't go wrong because of bad design. They go wrong because the client feels out of the loop.
They don't know what's happening week to week. They don't know what decisions they're supposed to be making. They don't know what "design development" means in practical terms. And then, at the presentation, something surprises them. And that surprise turns into a change request, a scope conversation, or a breakdown in trust.
The fix isn't more meetings. It's a more intentional communication protocol. One that tells clients what they need to know, when they need to know it, without overwhelming them with information they can't act on.
This is what it looks like, phase by phase.
Project Kickoff
What to send: A welcome package and project charter.
The welcome package sets expectations for the whole engagement. It should include:
- Project summary (scope, schedule, fee structure — a brief recap)
- Contact list (who's on the design team, who the client's primary contact is)
- Communication protocol (how the team communicates, how decisions get documented, how often clients will receive updates)
- Schedule overview (key milestones and what they mean)
- What's needed from the client (program input, access for site visits, decision turnaround times)
The last item is important and often skipped. Clients don't always know that their decision speed is on the critical path. A one-page overview of what you'll need and when helps set that expectation early.
During Schematic Design
Weekly: A brief progress note. Two to four sentences, no attachments. "this week we finalized the site plan options and completed preliminary massing studies. We're on track for the sd presentation on [date]." that's it. Not a status report. A human-readable signal that work is happening.
At each design review: A presentation package that includes the design options being reviewed, the questions the team needs the client to answer, and the decisions that need to be made before the team can move forward. Framing it as "here are the questions we need you to answer" rather than "here's what we've designed" changes the client's role from passive audience to active decision-maker.
At SD completion:. A formal SD submittal with a cover memo summarizing what was decided and what the approved direction is. Get a written sign-off. This document is your record of what the client approved.
During Design Development
Biweekly. A brief written update, slightly more detailed than the SD weekly notes. Include: what's been completed, what's in progress, any open items that require client input, and whether the project is on schedule. One page or less.
At coordination milestones:. If a major coordination decision has been made, structural system confirmed, mechanical approach established — a brief note explaining the decision and its implications for the client (cost, schedule, aesthetic) keeps them informed without requiring a formal meeting.
At DD completion. A full DD submittal including all discipline drawings, specifications in outline form, and an updated cost estimate. The cover memo should explicitly describe what has changed since SD and what decisions the client approved during DD. Again, get written sign-off.
During Construction Documents
Monthly: A project status update with a schedule comparison (original vs. Current). Note what's complete, what's in progress, and any items that require client action.
At permit submission: A brief note confirming submission, estimated review timeline, and what happens next.
At 100% CDs:. A transmittal of the complete CD set with a cover memo noting any significant changes from DD and confirming that the set is ready for bid or construction.
A Few Principles That Apply Across All Phases
Consistency matters more than volume. A brief weekly update sent reliably for six months builds more trust than an elaborate report sent occasionally. Set a cadence and keep it.
Make decisions explicit. Every time a client needs to decide something, say so clearly. "We need your confirmation on the exterior material by [date] in order to stay on schedule." Don't assume they know it's a decision or that it affects the timeline.
Don't wait for bad news to get worse. If the project is running behind or over budget, tell the client before they figure it out. Early disclosure, with a plan, is recoverable. Surprises at the end of a phase are not.
Write for someone who isn't an architect. Clients range from sophisticated developers who've built dozens of projects to homeowners buying their first major renovation. Write at the level of your actual client, not the level you'd write for a colleague.
The Payoff
A disciplined client communication protocol doesn't just prevent problems. It actively builds trust. Clients who feel informed are more likely to approve decisions quickly, less likely to second-guess directions they've already approved, and less likely to generate the kind of mid-phase pivots that blow up schedules and fees.
The investment — maybe thirty minutes a week for a structured update: returns multiples in reduced scope creep, faster approvals, and client relationships that generate repeat work.