Client Communications and Design Narratives with AI
Architects and engineers do not just produce drawings — they produce confidence. Every meeting minute, every design narrative, every email to an anxious client is part of how the work gets approved, funded, and built. AI is, frankly, excellent at this part of the job. A well-prompted ChatGPT produces a design narrative in ten minutes that used to take a senior architect two hours. The catch is that the best AI writing still needs the human voice and judgment — otherwise all projects start sounding the same.
What You'll Learn
- How to draft design narratives that actually move clients
- Using AI for meeting minutes, agendas, and project status reports
- How to handle difficult client conversations with AI-drafted responses
- Techniques for keeping your firm's voice in AI output
The Design Narrative
A design narrative is the story of a project in prose. It appears in award submissions, marketing materials, board presentations, and owner reports. A good narrative explains the moves without jargon and connects them to the client's priorities. Prompt template:
Write a 400-word design narrative for a {project type} at {location}. Program: {brief summary}. Key design moves: {3-5 major moves, e.g., double-height atrium, cross-laminated timber frame, central shared staircase}. Audience: the owner's board. Emphasize how the design responds to the client's stated priority of {priority}. Use active voice. Avoid architectural jargon (no "activation," no "programmatic engagement"). End with one sentence on schedule and budget confidence.
The output is a solid first draft. The architect then injects the one or two personal phrases that make it sound like the firm.
Meeting Minutes
Meeting minutes are high-drag, low-value work that AI handles perfectly.
Draft formal meeting minutes from these notes. Structure: Attendees, Summary, Decisions Made, Action Items (with owner and due date), Next Meeting Date. Group items by discipline. Use past tense. Flag any item where a decision was NOT reached so we can follow up. Here are my notes: {paste rough notes or transcript}
If you record meetings (with consent) and run the audio through a transcription service, AI can produce a complete set of minutes in two minutes. Always review for accuracy before sending — transcripts mishear technical terms.
Project Status Reports
Owners want weekly status reports. AI converts your raw project log into a polished update.
Draft a weekly project status report for the owner. Format: (1) Executive Summary (2-3 sentences), (2) Schedule Status (on track / at risk / behind), (3) Key Decisions This Week, (4) Pending Decisions Needed From Owner, (5) Issues and Risks, (6) Photo Highlights. Tone: professional, confident, direct. Do not sugar-coat schedule issues. Here is the raw project log: {paste}
Owners read more of these when they are structured the same way every week. Pick a template and stick with it.
Difficult Client Conversations
Sometimes the email you need to send is the hardest. AI is a good partner for drafting hard-but-professional messages.
The budget overrun email:
Draft an email to the client explaining that the DD estimate has come in 12% over the target budget. Causes: {scope additions during SD, material escalation, seismic upgrade requirement}. Options: (a) reduce scope (list areas), (b) increase budget, (c) phase the project. Tone: professional, responsible, not defensive. Do not apologize excessively. Present the recommendation clearly.
The delay notice:
Draft an email informing the owner that the permit review has been extended by 6 weeks due to a new zoning overlay discovered in plan check. Explain: (a) what happened, (b) what we're doing about it, (c) impact to schedule and budget, (d) what we need from the owner. Firm but collaborative tone. Avoid passive voice.
The scope dispute:
A client is claiming a feature they want is "in the base contract" when it is not. Draft a polite but firm email that: (1) references the specific contract exhibit that defines the base scope, (2) acknowledges the feature would be valuable, (3) offers a path forward via an Additional Services Request. Do not concede. Do not be adversarial.
Proposals and RFP Responses
AI drafts proposals faster than a marketing team can brief a writer.
Draft the Project Approach section of an RFP response for a {project type} competition. Key themes to emphasize: {sustainability, equity, phasing, operational excellence}. Include: (1) understanding of the owner's priorities, (2) our approach to each of the 5 phases (programming, SD, DD, CD, CA), (3) schedule strategy, (4) communication protocol, (5) team structure. 1,200 words. Avoid boilerplate language and generic claims.
Always have the principal-in-charge read it before submission — AI sometimes drifts into claims you cannot fully back up.
Presentations and Pitch Decks
AI drafts presentation narratives quickly but cannot design the slides themselves. Useful prompts:
I have a 12-slide concept presentation to the owner. Write speaker notes (120-150 words per slide) for: {paste slide titles}. Keep the notes connected so the story flows. Flag any slide where I need to insert a specific dollar figure, schedule date, or technical detail.
Keeping Your Firm's Voice
The biggest risk of AI-written communications is that every firm starts sounding the same. Techniques to preserve voice:
- Build a style guide. Write 6 sentences describing your firm's tone ("confident but humble," "technical when needed," "never pompous," etc.) and paste this at the start of every communication prompt.
- Provide samples. Upload 3-5 past narratives or emails and ask the AI to match that voice.
- Edit the first and last paragraphs. AI defaults are strongest in the middle; the opening and closing are where voice lives.
- Remove AI tells. Words like "delve," "tapestry," "navigate the landscape," "holistic," and phrases like "it is important to note that" signal AI. Cut them.
- Read aloud. If it sounds like a corporate press release, rewrite the weakest sentence.
Internal Communications
Not everything is external. AI also helps with:
- Team standups: summarize a week of Slack into 5 bullets
- Fee proposal memos to the principal: calculate hours, risk factors, dependencies
- Project kick-off briefs for junior staff: scope, consultants, deliverables, schedule
- End-of-project debrief memos: lessons learned, what worked, what to do differently
The Confidentiality Rule
Never paste client names, addresses, or contract terms into a public (free-tier) AI. Use your firm's enterprise seat for anything project-specific.
A Client Communication Stack
A practical setup:
- Enterprise AI (ChatGPT Team or Claude for Enterprise) — for all project correspondence
- Firm Claude Project with style guide, sample narratives, and standard templates
- Grammarly or similar for light polish after AI generation
- Principal review for any communication with contractual or financial implications
Key Takeaways
- AI is excellent at design narratives, meeting minutes, status reports, and difficult emails
- Give AI your firm's voice via style guide, samples, and example paragraphs
- Always have the principal-in-charge review anything with contractual or financial implications
- Remove common AI tells: delve, tapestry, navigate, holistic, "it is important to note"
- Use enterprise AI for anything project-specific; never paste confidential info into free-tier AI