---

name: architecture-client-presentation description: "Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options, or when a client keeps changing their mind after sign-off. Produces the presentation structure, the brief-to-design traceability, the options with honest trade-offs, the cost and programme position, and the decision record that makes sign-off stick."

Architecture Client Presentation

Clients who reopen decisions usually never made one. They were shown a rendering, said they liked it, and nobody wrote down what had been settled. This structures the meeting so each design move is visibly traceable to the brief they agreed, options carry their real trade-offs, and the session ends with named decisions recorded — which is the only thing that makes a sign-off hold.

What This Skill Produces

• The presentation structure — the order that produces decisions rather than reactions
• Brief-to-design traceability — each major move shown answering something the client asked for
• Options with honest trade-offs — what each costs, gains, and gives up, including the one you do not recommend
• The cost and programme position — where the scheme sits against budget and dates, stated plainly
• The decision request — the specific decisions needed at this meeting, and what is blocked without them
• The decision record — what was agreed, what was rejected, and what remains open, issued afterwards

Required Inputs

Ask for these if not provided:

• The stage and the brief — where the project is, and the agreed brief the design answers
• The design — the scheme and the major moves, with the reasoning behind each
• The options — what genuine alternatives exist, and their cost and programme consequences
• The commercial position — current cost estimate against budget, and the programme status
• The audience — who is in the room, who actually decides, and what each of them cares about

Framework: Brief, Moves, Options, Decision

1. Restate the brief first. In their words, from the signed version. Every design decision that follows is then measured against something already agreed rather than against taste.
2. Present moves, not views. 'We pushed the mass north to keep the garden in afternoon sun' is a decision the client can engage with. A rendering invites a reaction about the colour of the brick.
3. Show the trade-off, always. Every option gives something up. A client who is only shown upside will feel misled when the downside arrives, and will reopen the decision.
4. Put cost and programme in the room. Not at the end, not in a covering email. Cost surprises are what destroy trust in a design team.
5. Ask for named decisions. 'We need agreement on the roof form today; the structural package is blocked without it.' Vague approval is not a decision.
6. Record and issue the same day. Decided, rejected, still open, and what each open item is waiting for. This document is what prevents the reopening.
7. Protect the non-negotiables. Where a client request conflicts with statutory or structural reality, say so in the room, once, clearly.

Output Format

Design presentation: [project] · [stage] · [date]

1. The brief we are answering — [restated from the agreed brief, in the client's words] · Changes since sign-off: [any, with who requested them]

2. The design moves | Move | Answers this in the brief | Consequence | |---|---|---| | [the move] | [brief requirement] | [what it gains and costs] |

3. Options | Option | Gains | Gives up | Cost delta | Programme delta | |---|---|---|---|---| | A (recommended) | | | | | | B | | | | | Recommendation: [which and why, in one sentence]

4. Where we are commercially — estimate [amount] vs budget [amount] → [position] · programme [status against key dates]

5. Decisions needed today | Decision | Options | Blocked without it | Decide by | |---|---|---|---|

6. Constraints that are not negotiable — [statutory, structural, or site facts, stated once and plainly]

---

Decision record — issued [date]

• Agreed: [what, by whom]
• Rejected: [what, and the reason given]
• Open: [what, waiting on what, by when]

Quality Checks

• [ ] The agreed brief is restated before any design is shown
• [ ] Every major move is traced to something in the brief
• [ ] Every option states what it gives up, not only what it gains
• [ ] Cost and programme are presented in the meeting, not sent afterwards
• [ ] Specific decisions are requested, with what they block
• [ ] A decision record is issued the same day
• [ ] Non-negotiable constraints are stated clearly rather than softened

Anti-Patterns

• Leading with renderings. Produces reactions to materials instead of decisions about arrangement.
• Options without downsides. The client picks on preference and reopens it when the cost lands.
• Holding cost back. The single fastest way to lose a client's trust in the whole team.
• Accepting 'looks great' as approval. It is not a decision and will not survive contact with the next meeting.
• No written record. Guarantees the decision is relitigated.
• Softening a statutory constraint to keep the mood good. It returns later, larger, and now it is your fault.
• Presenting to the room instead of the decision-maker. Consensus without the decider is a rehearsal.

Example Trigger Phrases

• "Help me structure a design presentation for the client"
• "The client keeps changing their mind after sign-off — what am I doing wrong?"
• "How do I present three concept options?"
• "Prepare a design review meeting agenda"
• "How do I tell a client their request is not possible?"