Architects

Client Update Presentation Builder

Build a structured client update presentation for a project milestone meeting, covering design progress, schedule status, budget tracking, open decisions, and next steps. This prompt helps architects communicate project status efficiently and professionally, keeping clients informed and engaged through the design and construction process.

This prompt builds a client milestone update presentation structure covering a one-page status dashboard (design phase completion, schedule green/yellow/red, budget green/yellow/red, open decision count), a design progress narrative, a schedule and budget update, an open items section formatted as specific decision requests with deadlines, a risk and issues section, and a preview of the next phase. Budget and schedule data must be verified from the contractor's actual reports before the presentation — the prompt explicitly cautions against presenting unverified status to clients. It is for licensed architects managing client relationships through complex multi-phase design or construction projects where regular structured communication reduces surprises.

Testedclaude-sonnet-4-6ValidatedMar 2026ScopeVerify all code references and calculations independently. T…TierProfessional
AI Role
You are a licensed architect experienced in project management, client communica…
Models
Claude
Confidence
Professional
Constraints
Verify all code references and calculations independently. This does not replace licensed professional review.
Budget reporting must be based on documented estimates and change orders — never present a budget status without confirming the underlying numbers with the project quantity surveyor or contractor.
Schedule information must reflect the actual construction schedule from the contractor — do not present an optimistic schedule status that does not reflect the contractor's current plan.
Tested Models
claude-sonnet-4-6
Uncertainty
Where project status data is incomplete or not yet available, flag those sections with [DATA REQUIRED] and note specifically what information must be gathered before the presentation can be completed.
Last updated
2026-05-28 — Published

The prompt

1,790 characters
client-presentation-builder.prompt
You are a licensed architect experienced in project management, client communication, and structured project reporting for complex building projects.

Build a client update presentation for the following:

Project information:
- Project name: [PROJECT_NAME]
- Presentation date: [DATE]
- Current project phase: [PHASE]
- Milestone being reported: [MILESTONE — e.g., end of schematic design, mid-construction update, 50% completion]

Project status data:
- Design progress: [DESCRIBE WHAT HAS BEEN COMPLETED IN THIS PHASE]
- Schedule status: [ON SCHEDULE / BEHIND / AHEAD — explain if not on schedule]
- Budget status: [WITHIN BUDGET / OVER / UNDER — describe status]
- Open decisions requiring client input: [LIST OPEN ITEMS]
- Issues or risks: [CURRENT ISSUES]

Key messages to convey:
[WHAT DO YOU WANT THE CLIENT TO TAKE AWAY FROM THIS MEETING]

Build a presentation structure covering:

## Project Status Summary
One-page visual dashboard: design phase completion %, schedule green/yellow/red, budget green/yellow/red, open decision count.

## Design Progress Update
What was completed this phase, what it means for the overall project, and how it advances toward the client's goals.

## Schedule Update
Current schedule status against baseline. If behind: cause, impact, and recovery plan.

## Budget Update
Current cost status. Known changes from initial budget. Contingency status.

## Open Items and Decisions Required
For each open item: what needs to be decided, by whom, by when, and the consequence of delay. Structured as a decision request, not just an information item.

## Risks and Issues
Any active issues and mitigation actions in progress.

## Next Phase: What to Expect
What will be accomplished in the next phase, what the client will see, and key upcoming milestones.
WAITLIST

Runner beta coming — join the waitlist.

In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.

How to use this prompt

1

1. Confirm all project status data with the project team before building the presentation — presenting unverified schedule or budget information in front of the client is a significant professional risk.

2

2. Structure open decisions as specific action requests with deadlines, not as information items — clients need to know that their decision is required to keep the project moving.

3

3. Send the presentation materials to the client 24-48 hours before the meeting to allow review, particularly for decision items.

Customization tips

Add 'The client is an experienced developer who wants data-dense reporting — include actual vs. budgeted hours, cost-to-complete forecasts, and schedule float analysis' for sophisticated clients.
For public sector clients, add 'Format the budget section to align with the public agency's budget tracking categories and reporting requirements.'
Append 'The client has a board approval requirement for changes over [threshold] — flag any open decisions that may require board action and allow sufficient lead time.'

Sample output

Mar 2026Professional
CLIENT PRESENTATION STRUCTURE — Revised Office Schematic Design MEETING: Design Presentation — Response to Open-Plan Rejection Feedback AUDIENCE: Corporate client leadership team (CEO, CFO, VP HR, Facilities Director) DURATION: 60 minutes PRESENTATION FLOW: PART 1 — ACKNOWLEDGE THE FEEDBACK (5 minutes) Open by naming the feedback directly: the original open-plan concept did not match how the organization works. Do not be defensive. Frame the revision as what good design process looks like: we designed something, tested it against your reality, and redesigned accordingly. This is the process working as intended. PART 2 — WHAT WE LEARNED (10 minutes) Before showing any design, share what you heard: - Your teams have different privacy needs by department (legal, finance, and HR consistently flagged the need for acoustic enclosure; creative and product teams expressed more openness to collaborative arrangements) - Your existing office, despite its dated design, has something the open plan lacked: a sense of place and territory that people find anchoring - The open plan was read as an erasure of team identity, not an enabler of collaboration PART 3 — THE REVISED DESIGN (30 minutes) Present the neighborhood model concept: a structured organizational strategy that responds to each department's specific privacy and collaboration needs while maintaining a coherent, identity-driven design language throughout the floor plate. Walk the audience through the design in the order they will experience it: - Arrival experience and reception - Collaborative heart of the floor (town hall, café, large meeting rooms) - Neighborhood zones (walk through one representative neighborhood in detail) - Focus and private zones - Leadership suite and boardroom For each zone, state: what behavior it supports, who uses it, and what design moves enable that behavior. PART 4 — WHAT STAYS THE SAME (5 minutes) Confirm what the client liked in the original design that is retained: material palette, the central atrium concept, the view orientation strategy, the sustainability commitments. PART 5 — QUESTIONS AND NEXT STEPS (10 minutes) Structure the Q&A around decisions that must be made to proceed: neighborhood assignments by department, headcount per zone, and timeline for design development. Note: Adapt timing and content to the specific project and audience. This is a structural framework, not a script.

Related prompts

design communicationProfessional

Design Concept Presentation Builder

Structure a compelling design concept presentation for a client meeting, design review board, or public presentation. This prompt helps architects organize their design narrative, key visuals, and talking points into a presentation structure that communicates the design intent clearly and builds client confidence in the direction.

Testedv2.3Reviewed
Claude · ChatGPTOpen prompt →
design communicationBasic

Design Review Feedback Organizer

Organize and analyze client or stakeholder feedback from a design review meeting into actionable categories. This prompt helps architects transform raw feedback — often a mix of specific requests, general impressions, and contradictory preferences — into a prioritized action list that drives the next design iteration.

Testedv2.3Reviewed
Claude · ChatGPTOpen prompt →
design communicationProfessional

Engineering Consultant Coordination Memo Writer

Draft a professional coordination memo to engineering consultants documenting design decisions, coordination requirements, or information requests. This prompt helps architects maintain clear written communication with structural, MEP, and civil engineering consultants — creating a documented coordination record that protects all parties and keeps the project on track.

Testedv2.3Reviewed
Claude · ChatGPTOpen prompt →

Frequently asked questions

Read the Architects AI Guide
Professional Disclaimer

This AI-generated content is for informational and educational purposes only. It does not replace the professional judgment of a licensed architect. Always verify code compliance, structural calculations, and design decisions with qualified professionals.