·9 min read·Prompt Guides
ChatGPT Prompts for Architects (Copy-Paste Ready)
Architects spend a disproportionate amount of their working hours on writing that has nothing to do with design — client briefs, planning letters, contractor instructions, tender documents, and business development. These 30 ChatGPT prompts for architects handle the writing so you can spend more time on the work that drew you to the profession.
Architecture is a profession that demands both exceptional design thinking and exceptional written communication. Every project generates an enormous volume of written output — discovery questionnaires, concept narratives, planning applications, site instructions, contractor briefs, and client presentations — and the quality of that writing shapes client confidence, planning outcomes, and contractor performance just as much as the drawings do.
ChatGPT won't design your buildings. But it can draft the planning cover letter while you're reviewing drawings, write the client brief summary that aligns expectations before scheme design begins, and generate a tender invitation in minutes rather than hours. These 30 prompts are organized around the six writing categories that consume the most architectural time.
Every prompt uses [BRACKETS] for the variables you fill in. Copy, customize, paste into ChatGPT, and review before use.
Section 1: Client Briefs & Design Concepts (Prompts 1–5)
A great project begins with a great brief. These prompts cover the full brief-development process — from discovery questionnaire through concept summary and design rationale — so you capture what you need and align client expectations before design work begins.
1. Initial Client Brief Questionnaire
Build a thorough client brief questionnaire that surfaces everything you need before design work begins.
✦ Client Briefs & Design Concepts
Create a client brief questionnaire for an architectural project. Project type: [E.G. "new residential build," "commercial office fit-out," "residential extension and renovation"]. The questionnaire should cover: (1) How the client intends to use the space — daily routines, functional priorities, and must-have spaces, (2) Aesthetic direction — styles they admire, examples they love, things they want to avoid, (3) Budget range and contingency expectations, (4) Programme constraints — when they need to occupy or open, key milestone dates, (5) Site considerations — what they know, love, or want to work with on the site, (6) Sustainability and performance priorities, (7) Decision-making process — who is involved, who has final approval, (8) Their greatest concern about the process, and (9) What success looks like to them at handover. Format as a clean numbered questionnaire grouped by category. Under 40 questions. Tone: thoughtful and professional — this questionnaire should make the client feel they are in the hands of a practice that genuinely wants to understand their vision.2. Design Concept Summary Email
Distill your design concept into a compelling email that aligns client expectations before drawings are shared.
✦ Client Briefs & Design Concepts
Write a design concept summary email to send to a client before or alongside the first concept presentation. Client name: [NAME]. Project: [DESCRIPTION — e.g. "three-storey residential new build on a narrow urban site"]. Core design concept: [DESCRIBE IN YOUR OWN WORDS — e.g. "a vertically layered house that captures light from above, creating bright, airy living spaces despite a constrained footprint"]. Key design moves: [LIST 3–4 — e.g. "a central lightwell that draws daylight through all three floors," "a rooftop terrace off the main bedroom," "a ground-floor living pavilion that opens fully to the garden"]. Guiding inspiration or references: [IF ANY]. How this concept responds to the brief: [BRIEF — how it addresses the client's stated goals]. Write an email that: introduces the concept narrative before drawings are seen, explains the thinking clearly in plain language, makes a specific link between the design moves and the client's stated priorities, and invites questions before the presentation meeting. Under 250 words. Tone: confident and evocative — this email sets the stage for the presentation; it should excite the client about what they're about to see.3. Concept Design Revision Email
Respond to design feedback professionally and confirm the revised direction before investing further design time.
✦ Client Briefs & Design Concepts
Write an email to an architectural client confirming your understanding of their concept feedback and proposed revision approach. Client name: [NAME]. Project: [DESCRIPTION]. Feedback received: [DESCRIBE — e.g. "they want the living space to feel more open to the garden," "they are concerned the master bedroom doesn't have enough storage," "they've asked whether the street elevation could feel less industrial"]. Your proposed revision: [DESCRIBE THE RESPONSE — e.g. "I'll explore a fully glazed rear wall with bifold doors to blur the boundary with the garden," "I'll introduce a fitted wardrobe run along the north wall of the master bedroom"]. Any clarifying questions before you proceed: [LIST IF ANY]. Write an email that: acknowledges the feedback specifically and positively, confirms your interpretation of what the client wants and how you'll address it in the revision, asks any remaining questions before work restarts, and sets a clear timeline for the revised concept. Under 200 words. Tone: collaborative and professional — revisions are part of the design process; this email should make the client feel heard and confident the next round will land.Section 1 (continued): Client Briefs & Design Concepts
4. Programme of Spaces Summary
Confirm the agreed programme of spaces in writing before scheme design begins — protects everyone and sets clear expectations.
✦ Client Briefs & Design Concepts
Write a programme of spaces summary email to send to an architectural client before scheme design begins. Client name: [NAME]. Project: [DESCRIPTION]. Agreed spaces and areas: [LIST — e.g. "Ground floor: open-plan kitchen/dining/living (approx. 65m²), utility/boot room (8m²), WC (3m²)," "First floor: master bedroom with en suite (28m²), two further bedrooms (12m² each), family bathroom (8m²)"]. Spaces that were discussed but are not in the current programme: [LIST — e.g. "home office — deferred to a possible future phase," "additional garage space — not within current budget"]. Gross internal floor area target: [APPROX. m² / ft²]. Budget confirmed: [$AMOUNT]. Write a summary email that: lists the agreed programme clearly by floor or zone, notes what was considered but deferred, confirms the target area and budget, and invites the client to flag anything that doesn't sound right before design work begins. Under 250 words. Tone: organized and professional — a clear programme confirmation protects the project and the client relationship.5. Design Rationale for a Key Architectural Move
Explain a significant architectural decision in language that builds client confidence and reduces hesitation at approval.
✦ Client Briefs & Design Concepts
Write a design rationale explanation for a key architectural move that a client has questioned or that needs clear justification. Architectural move: [DESCRIBE — e.g. "the rooflight running the full length of the kitchen," "the decision to use a mono-pitch roof rather than a traditional pitched roof," "positioning the house at 45° to the road to maximize garden orientation"]. Client concern or context: [E.G. "the client is concerned the rooflight will cause overheating in summer," "they've asked why we didn't use a more conventional roof form"]. Write a rationale that: acknowledges their question or concern genuinely, explains the design reasoning clearly and specifically — functional and architectural, addresses their concern directly with any relevant technical or practical context, and connects the decision back to their brief and what they said they wanted. Under 200 words. Tone: confident and educational — a great architect explains their moves with conviction while making the client feel their concern has been properly considered. Avoid being defensive; this should feel like a trusted professional helping the client see what you see.Section 2: Project Proposals & Scoping (Prompts 6–10)
Converting a prospective client into a signed appointment requires a proposal that demonstrates understanding, sets clear expectations, and communicates your value confidently. These prompts cover the full proposal and scoping workflow — from the initial services proposal through budget conversations and scope additions.
6. Architectural Services Proposal
Write a clear, compelling proposal that converts a prospective client and sets the right expectations from day one.
✦ Project Proposals & Scoping
Write an architectural services proposal for a prospective client. Client name: [NAME]. Project: [DESCRIPTION — e.g. "new three-bedroom family home on a client-owned suburban plot"]. Services to be provided: [LIST BY RIBA STAGE OR EQUIVALENT — e.g. "Stage 1: Preparation and Brief, Stage 2: Concept Design, Stage 3: Developed Design, Stage 4: Technical Design, Stage 5: Construction, Stage 6: Handover"]. Fee structure: [DESCRIBE — e.g. "fixed fee of $[AMOUNT] for Stages 1–3; Stage 4 at $[RATE]/hour; Stage 5 coordination at $[RATE]/hour"]. What is excluded from the fee: [LIST — e.g. "structural engineering, planning application fees, building control fees, specialist consultants"]. Estimated programme: [KEY MILESTONES AND DATES]. Structure: (1) Opening — what we heard about their vision, (2) Our approach and what makes us right for this project, (3) Scope of services by stage, (4) What's included vs. excluded, (5) Fee summary, (6) The process — how we work together, (7) Next steps. Under 600 words. Tone: professional and consultative — this proposal should make the client feel understood and confident they are engaging the right practice.7. Project Scope Clarification Email
Get the specific information needed to scope accurately — without making the client feel interrogated.
✦ Project Proposals & Scoping
Write an email to a prospective architectural client asking the clarifying questions needed to prepare an accurate proposal. Client name: [NAME]. Project they've described: [BRIEF DESCRIPTION]. What you need to clarify before you can scope accurately: [LIST — e.g. "whether they own the site or it is under offer," "whether they have planning permission or whether pre-application advice has been sought," "whether they have an existing structural or topographical survey," "their confirmed construction budget excluding fees"]. Write an email that: thanks them for getting in touch and briefly references their project, frames the questions as genuinely necessary to give them the best proposal (not a bureaucratic intake process), asks each question clearly and simply, groups logically if there are multiple, and closes with a note that their answers will let you prepare a thorough proposal quickly. Under 175 words. Tone: warm and professional — clarifying questions should feel like an engaged architect doing their homework.8. Fee Proposal for Additional Services
Propose additional services professionally when a project grows beyond the original scope.
✦ Project Proposals & Scoping
Write a fee proposal email for additional architectural services on an existing project. Client name: [NAME]. Original project: [DESCRIPTION]. Services originally agreed: [BRIEF SUMMARY — stages and fee]. What has changed or expanded: [DESCRIBE — e.g. "the client has asked us to add a garden studio to the scope," "a significant design change has been requested that requires substantial re-work of the Stage 4 package"]. Additional services now required: [LIST SPECIFICALLY]. Proposed additional fee: [$AMOUNT — and basis, e.g. fixed or hourly]. Impact on programme: [IF ANY]. Write an email that: references the original agreement and notes clearly what has changed, describes the additional services and why the additional fee is warranted, states the proposed fee simply and directly, notes any programme impact, and invites their agreement to proceed. Under 200 words. Tone: direct and professional — scope additions are a normal part of architectural practice; communicate them clearly from a position of confidence.9. Pre-Application Meeting Request to Planning Authority
Request a pre-application meeting with a planning authority in a way that gets taken seriously and schedules quickly.
✦ Project Proposals & Scoping
Write a pre-application meeting request letter or email to a local planning authority. Project: [DESCRIPTION — e.g. "proposed new-build residential dwelling on [SITE ADDRESS]"]. Key aspects requiring pre-application discussion: [LIST — e.g. "design approach and massing in a conservation area context," "proposed access strategy," "parking provision," "impact on neighboring amenity"]. What you have prepared: [E.G. "a site location plan, indicative site plan, and design concept drawings will be attached / shared in advance of the meeting"]. Applicant: [NAME / COMPANY]. Agent / architect: [YOUR PRACTICE NAME]. Write a meeting request that: introduces the project clearly and concisely, identifies the specific planning questions you want to discuss, demonstrates that you have done your homework (site context, policy position), and requests a pre-application meeting or written advice. Under 200 words. Tone: professional and respectful — pre-application engagement sets the tone for the whole planning relationship; this letter should read as coming from a well-prepared and experienced practice.10. Client Budget Reality Check Email
Navigate a mismatch between a client's ambitions and their budget with honesty and professional care.
✦ Project Proposals & Scoping
Write an email to an architectural client where there is a clear mismatch between their design ambitions and their stated construction budget. Client name: [NAME]. Project: [DESCRIPTION]. The mismatch: [DESCRIBE — e.g. "they want a 280m² house with high-specification finishes for a construction budget of $420,000 — a realistic budget for that specification would be $620,000–680,000, or the programme needs to be significantly reduced"]. Write an email that: opens warmly and acknowledges their vision clearly, presents the honest reality of the budget gap without embarrassing them, offers 2–3 concrete options for how to proceed (e.g. "reduce the programme to [AREA], phase the project, or revisit the specification level"), and invites a conversation to decide the path forward. Under 250 words. Tone: direct and empathetic — this is one of the most important conversations in an architect-client relationship; it should feel like honest advice from a trusted professional, not bad news from a distance.Section 3: Zoning & Code Research (Prompts 11–15)
Planning and building regulations research generates a high volume of written output — policy summaries, pre-application requests, planning applications, and objection responses. These prompts help you communicate complex regulatory information clearly to clients and authorities alike.
11. Zoning Research Summary
Summarize zoning and planning policy research in plain language so clients understand what their site can accommodate.
✦ Zoning & Code Research
Write a zoning and planning policy summary for an architectural client. Site address: [ADDRESS]. Project type: [E.G. "new residential dwelling," "residential extension," "change of use from commercial to residential"]. What you have researched: [LIST — e.g. "local development plan policies," "site-specific designations (conservation area, flood zone, etc.)," "permitted development rights," "any relevant planning history on the site"]. Key findings: [DESCRIBE — e.g. "the site falls within a designated conservation area — any new development must preserve or enhance the character; the local plan supports residential development here subject to design quality and neighbour amenity impacts"]. Implications for the project: [LIST SPECIFIC — what is likely to be acceptable, what will need justification, what is unlikely to be permitted]. Write a summary email that: presents the research findings clearly in plain language (no planning jargon without explanation), gives the client a realistic picture of what their site can accommodate, notes what design approach is most likely to succeed with the planning authority, and explains what happens next. Under 300 words. Tone: clear and authoritative — clients need to understand their planning position before committing to a design direction.12. Planning Policy Research Summary for a Conservation Area
Brief a client on conservation area policies in a way that shapes design ambitions early and avoids wasted effort.
✦ Zoning & Code Research
Write a conservation area planning policy briefing for an architectural client. Site: [ADDRESS OR AREA]. Conservation area designation: [NAME OF CONSERVATION AREA]. Key conservation area policies and their implications: [DESCRIBE — e.g. "all materials and fenestration must be sympathetic to the character of the area; contemporary design is acceptable but must demonstrate a clear design rationale; demolition of existing structures within the conservation area requires conservation area consent"]. Specific design implications for the proposed project: [DESCRIBE — how the policies shape the design response, what approaches tend to be well-received by the planning authority, what is likely to need a design and access statement]. What additional specialist input may be needed: [E.G. "a heritage statement prepared by a conservation architect or heritage consultant is strongly recommended for any significant extension or new build in this area"]. Write a briefing note of under 250 words in plain language. Tone: clear and educational — the client should finish reading this and understand exactly how the conservation area designation shapes what is possible, without feeling restricted or overwhelmed.13. Planning Application Cover Letter
Write a persuasive planning application cover letter that frames your proposal positively before the officer reads a single drawing.
✦ Zoning & Code Research
Write a planning application cover letter for submission to a local planning authority. Project: [DESCRIPTION — e.g. "proposed erection of a two-storey side and single-storey rear extension at [ADDRESS]"]. Applicant: [NAME]. Planning authority: [NAME]. Key planning policies the application responds to: [LIST — e.g. "Local Plan Policy H1: residential extensions — the proposal is consistent with the policy criteria for scale, mass, and design"]. Design approach and how it responds to the local context: [DESCRIBE — e.g. "the proposed materials match the host dwelling and surrounding streetscape; the side extension is set back from the front elevation to preserve the building line; the rear extension is single-storey to protect the amenity of adjacent properties"]. Any sensitive issues to address proactively: [E.G. "impact on the amenity of [NUMBER], the immediately adjacent property — the proposal is designed to avoid any significant overlooking or loss of light"]. Write a cover letter that: introduces the proposal clearly, demonstrates policy compliance specifically, addresses any sensitivities proactively, and presents the application in the most favourable light. Under 300 words. Tone: professional and confident — a well-written cover letter sets a positive tone with the planning officer from the start.14. Building Code Compliance Summary for a Client
Explain building code requirements to a client in plain language so they understand why certain design decisions are non-negotiable.
✦ Zoning & Code Research
Write a building regulations / code compliance summary email to an architectural client explaining key requirements that affect their project. Client name: [NAME]. Project: [DESCRIPTION]. Relevant building code requirements: [LIST THE RELEVANT REGULATIONS AND THEIR IMPLICATIONS — e.g. "Part L (Energy Efficiency): the fabric and services specification must meet current SAP targets — this drives the wall insulation thickness and window specification; Part B (Fire Safety): means of escape from the upper floor require a protected staircase — this affects the internal layout"]. How these requirements affect the design: [DESCRIBE SPECIFICALLY — e.g. "the wall build-up thickness we've used in the drawings is driven by the Part L requirement, not aesthetic preference; we cannot reduce it without triggering a non-compliant energy calculation"]. Any areas where the client will need to make decisions: [LIST — e.g. "specification choices for windows, heating system type, insulation"]. Write a summary that: explains the relevant requirements in plain language, makes clear which design decisions are driven by code (non-negotiable) vs. design preference (flexible), and flags where the client's input is needed. Under 250 words. Tone: clear and educational — clients make better decisions when they understand why certain things are fixed.15. Response to a Planning Objection
Draft a professional, factual response to a third-party planning objection that protects the application.
✦ Zoning & Code Research
Write a professional response to a third-party objection submitted during the public consultation period for a planning application. Our project: [DESCRIPTION]. Objection raised by: [NEIGHBOUR / LOCAL RESIDENT / OTHER — describe their relationship to the site]. Nature of the objection: [DESCRIBE — e.g. "the objector claims the proposed extension will cause significant loss of light to their property and overlooking of their rear garden"]. Facts and design evidence that counter the objection: [LIST — e.g. "a daylight and sunlight assessment has been prepared — it confirms no material loss of light to the adjacent property," "the proposed first-floor window on the flank elevation uses obscured glazing to prevent overlooking," "the extension footprint does not extend beyond the existing garden fence line"]. Write a response that: acknowledges the objection respectfully, responds to each point raised factually and with reference to the relevant evidence, notes where the design has already addressed or mitigated the concern, and confirms that the proposal is compliant with relevant planning policies. Under 300 words. Tone: professional, measured, and factual — this document is part of the planning record; it should be factual, non-confrontational, and persuasive.Section 4: Construction Documentation (Prompts 16–20)
The construction phase generates a constant stream of formal written communication — tender invitations, site instructions, RFI responses, and defect notices. These prompts help you issue clear, professionally structured documentation that keeps projects on programme and creates a proper contractual record.
16. Contractor Pre-Qualification Questionnaire
Screen contractors effectively before inviting them to tender so you only engage firms with the right experience and capacity.
✦ Construction Documentation
Write a contractor pre-qualification questionnaire for an architectural project going to tender. Project: [DESCRIPTION — e.g. "construction of a new 280m² residential dwelling"]. Estimated construction value: [$AMOUNT]. Key pre-qualification criteria to assess: [LIST — e.g. experience on similar residential projects, current workload and capacity, financial standing, insurance and accreditations, health and safety record, key subcontractor relationships, examples of completed work in the same specification range]. Format: a clear questionnaire with numbered questions grouped by category. Include: (1) Company overview and key personnel, (2) Relevant project experience (3 examples minimum, with values, client contacts for reference, and completion date), (3) Current workload — what projects are they currently running and what would this project's position be in their programme, (4) Insurance and accreditations, (5) Health and safety approach, (6) How they manage design queries and site issues, (7) Key subcontractors they would propose. Under 35 questions. Tone: professional and direct — this questionnaire is a real selection tool; it should surface the information needed to make a genuinely informed decision.17. Tender Invitation Letter
Invite contractors to tender with a clear, professional letter that sets the right expectations from the start.
✦ Construction Documentation
Write a tender invitation letter to send to a selected list of contractors for an architectural project. Project: [DESCRIPTION — e.g. "construction of a new-build family home at [ADDRESS]"]. Client: [NAME]. Architect: [YOUR PRACTICE]. Tender documents enclosed or provided: [LIST — e.g. "architectural drawings (listed)," "structural engineers' drawings and specifications," "employers requirements," "bill of quantities / schedule of works," "form of contract"]. Tender return date: [DATE AND TIME]. Tender return address / method: [ADDRESS / EMAIL]. Anticipated construction programme: [START DATE → COMPLETION DATE — if known]. Form of contract proposed: [E.G. "JCT Minor Works / NEC4 / AIA A101 — as applicable"]. Site visit: [DATE AND ARRANGEMENTS — if applicable]. Write a letter that: invites the contractor to submit a lump sum tender for the described works, lists all tender documents, states the tender return date and method clearly, notes the anticipated programme, and sets expectations around the tender process and selection. Under 200 words. Tone: professional and organized — this letter establishes the professional standard of the procurement process.18. Site Instruction to a Contractor
Issue a clear site instruction that leaves no room for misinterpretation and creates a proper record.
✦ Construction Documentation
Write a formal site instruction to a contractor on an architectural project. Project: [NAME / ADDRESS]. Contractor: [NAME]. Instruction number: [NUMBER — e.g. SI-012]. Date: [DATE]. Issued by: [ARCHITECT'S NAME AND PRACTICE]. Nature of the instruction: [DESCRIBE — choose from: design change, clarification of specification, instruction to open up or test work, instruction to rectify a defect, provisional sum instruction, or other]. Specific instruction: [DESCRIBE IN PRECISE TECHNICAL LANGUAGE — e.g. "The wall ties specified in Section 2.3.4 of the specification are to be replaced with Type 4 double-triangle wall ties at 600mm horizontal and 450mm vertical centres, fixed with stainless steel fixings throughout. This replaces the original specification of standard butterfly wall ties. No additional cost is anticipated for this change — please confirm." OR "The contractor is instructed to remove the installed first-floor bathroom floor tiles and allow inspection of the waterproofing membrane beneath. Works should not proceed until the architect has inspected and issued written approval."]. Contract clause under which the instruction is issued: [IF RELEVANT]. Any cost or programme implications: [NOTE IF ANY]. Tone: clear, precise, and professional — site instructions form part of the contract record and must be unambiguous.19. Defects Notification Letter at Practical Completion
Issue a defects schedule at practical completion that is clear, specific, and legally sound.
✦ Construction Documentation
Write a defects notification letter to issue to a contractor at or shortly after practical completion. Project: [DESCRIPTION — e.g. "new residential dwelling at [ADDRESS]"]. Contractor: [NAME]. Date of practical completion: [DATE]. Defects liability period: [E.G. "12 months from the date of practical completion"]. Defects identified: [LIST — be specific: location, nature of defect, what the contractor needs to do to rectify. E.g. "1. External terrace — paving has an inadequate fall toward the drainage channel; water is ponding adjacent to the threshold — contractor to re-lay or regrade paving to achieve minimum 1:80 fall. 2. Master bedroom — paint finish on north wall is uneven — contractor to apply a further full coat in the specified finish." Continue for all items]. Deadline for making good: [DATE — or note it is to be agreed]. Retention release: [NOTE WHERE RELEVANT — e.g. "Half of the retention sum is released on practical completion. The remaining retention will be released at the end of the defects liability period, subject to satisfactory making good of defects"]. Write a letter that: confirms practical completion has been certified, lists all defects precisely and specifically, sets expectations for making good, and notes the retention position. Tone: professional and factual — this document is part of the contract record.20. Architect's Instruction Response to a Contractor's RFI
Respond to a contractor's Request for Information clearly and in a way that keeps the project moving.
✦ Construction Documentation
Write an architect's response to a contractor's Request for Information (RFI) on a construction project. Project: [DESCRIPTION]. Contractor: [NAME]. RFI number: [NUMBER]. RFI subject: [DESCRIBE WHAT THE CONTRACTOR IS ASKING — e.g. "clarification required on the lintel specification above the new window opening in the east elevation — the structural engineer's drawing (ref SE-004) shows a steel lintel but the architectural specification refers to a pre-cast concrete lintel; contractor is requesting confirmation of which is correct"]. Architect's response: [DESCRIBE YOUR ANSWER — be specific and technically precise — e.g. "The structural engineer's drawing takes precedence on structural elements. The pre-cast concrete lintel reference in the specification is an error and will be updated in the next drawing issue. The contractor should proceed with the steel lintel as shown on drawing SE-004. A revised specification clause will follow with the next drawing issue."]. Reference drawings or documents: [LIST IF RELEVANT]. Any programme implications: [E.G. "the contractor should note this response and factor the steel lintel procurement timeline into their programme"]. Write a response that: answers the question directly and completely, references the relevant drawings or documents, notes any programme implications, and maintains a clear formal record. Tone: professional and precise.Section 5: Client Communication & Presentations (Prompts 21–25)
Client communication — from the design presentation through construction updates to the final handover — shapes the client experience as much as the building itself. These prompts help you communicate your design thinking compellingly and keep clients informed and confident throughout the project lifecycle.
21. Design Presentation Script
Structure your design presentation as a compelling narrative — not just a drawing review.
✦ Client Communication & Presentations
Write a presentation script outline for an architectural design presentation to a client. Presentation stage: [E.G. "Stage 2 Concept Design," "Stage 3 Developed Design"]. Project: [DESCRIPTION]. Core design concept: [DESCRIBE IN YOUR WORDS]. Key design moves to present: [LIST 4–6 SPECIFIC ELEMENTS — e.g. "the relationship between the house and the garden," "the approach to natural light," "the material palette and why it was chosen," "the floor plan organization and how it responds to the brief"]. Client concerns or priorities to address directly: [LIST — e.g. "they are concerned about the cost," "they've asked about the planning risk"]. Write a presentation script outline with: (1) Opening — the concept in one or two sentences that set the emotional register before a drawing is shown, (2) Site and context — how the design responds to where it sits, (3) The plan — how the spaces work for their life, (4) The section / experience — how you move through the building and how light works, (5) Materials and specification direction, (6) Cost and programme overview, (7) Planning position, (8) Close — what you are asking the client to approve or agree today, and what happens next. Under 400 words. Tone: confident and narrative — a great design presentation tells a story; it doesn't just show drawings.22. Post-Presentation Follow-Up Email
Keep momentum after a design presentation with a follow-up that confirms what was agreed and what happens next.
✦ Client Communication & Presentations
Write a follow-up email to send after a design presentation meeting with an architectural client. Client name: [NAME]. Presentation stage: [E.G. "concept design"]. What the client responded positively to: [DESCRIBE — brief notes]. What they asked to revisit or change: [DESCRIBE]. What was agreed or approved: [LIST — what is confirmed and can move forward]. Outstanding actions: [LIST — who does what, by when — include both your actions and the client's]. Next stage and timeline: [DESCRIBE — what happens next and when]. Write an email that: opens by referencing the meeting positively, confirms what was approved and what will be revised, lists outstanding actions clearly with owners and deadlines, describes what happens next, and closes with a clear note on timing. Under 200 words. Tone: organized and forward-moving — this email should make the client feel the project has clear momentum and is in capable hands.23. Progress Update Email During Construction
Keep clients informed and confident during the construction phase without creating unnecessary anxiety.
✦ Client Communication & Presentations
Write a construction phase progress update email to an architectural client. Client name: [NAME]. Project: [DESCRIPTION]. Reporting period: [E.G. "week ending [DATE]" or "month of [MONTH]"]. Progress this period: [LIST — what has been completed or is substantially advanced]. Works in progress / next two weeks: [LIST — what is happening now and immediately next]. Any issues or delays: [DESCRIBE IF ANY — be factual, describe the issue and the resolution or mitigation plan clearly]. Any decisions or approvals needed from the client: [LIST — be specific about what is needed and by when]. Current programme position: [E.G. "the project remains on programme for a [DATE] practical completion" OR "the project is [X weeks] behind programme; the contractor's recovery programme is attached"]. Write an update that: gives a clear, organized snapshot, addresses any issues honestly with a mitigation plan, asks for any required client decisions clearly with deadlines, and closes on a forward-looking note. Under 200 words. Tone: confident and organized — clients should feel informed and reassured, not anxious.24. Client Approval Request for a Design Decision
Request a specific client approval clearly so design progress isn't held up by vague sign-off processes.
✦ Client Communication & Presentations
Write an email to an architectural client requesting approval for a specific design decision. Client name: [NAME]. Project: [DESCRIPTION]. Decision to be made: [DESCRIBE CLEARLY — e.g. "approval of the revised external material palette following the planning officer's pre-application feedback"]. Options or the recommended approach: [DESCRIBE — either a single recommendation with reasoning, or 2–3 options with a clear recommendation]. Relevant drawings or documents: [LIST — what is attached or referenced]. Why this needs to be confirmed now: [E.G. "we need to confirm the material specification to coordinate the structural engineers' drawings ahead of the planning submission on [DATE]," "the contractor needs a confirmed answer to proceed with procurement"]. Deadline for the decision: [DATE — with reason if relevant]. Write an email that: introduces the decision clearly and concisely, explains the options or presents the recommendation with reasoning, states why a timely response is needed, provides any necessary drawings or reference material, and asks for a clear yes/no or selection. Under 175 words. Tone: organized and direct — the best client relationships have a clear approval process; this email establishes it.25. Handover Letter at Practical Completion
Close the project professionally with a handover letter that celebrates the outcome and sets up the next phase.
✦ Client Communication & Presentations
Write a project handover letter to send to a client at practical completion of an architectural project. Client name: [NAME]. Project: [DESCRIPTION]. Date of practical completion: [DATE]. What was delivered: [BRIEF SUMMARY — the scope of the works]. Defects liability period: [DURATION AND END DATE — e.g. "12 months from today, ending [DATE]"]. What to do if defects arise: [E.G. "please notify us directly and we will issue an instruction to the contractor for making good"]. Operation and maintenance manuals / building user guides: [WHERE THESE ARE LOCATED — e.g. "a full O&M manual has been provided to you directly by the contractor; it is also uploaded to [LINK]"]. Warranties and guarantees: [SUMMARY — e.g. "structural warranty from LABC: 10 years from today; flat roof membrane guarantee from [INSTALLER]: 20 years"]. Retention: [NOTE THE POSITION — e.g. "a retention sum of [$AMOUNT] is held by the client, payable at the end of the defects liability period subject to satisfactory making good of any defects"]. Write a letter that: marks the completion of the project warmly and professionally, confirms the handover information clearly, sets up the defects period with clear instructions, and closes with an expression of pride in what has been built together. Under 300 words. Tone: warm and professional — this letter is the final impression of the project.Section 6: Business Development (Prompts 26–30)
Growing an architectural practice requires consistent business development writing — award submissions, practice profiles, social media posts, referral requests, and newsletters. These prompts help you present your work compellingly and build the visibility that attracts the right clients.
26. Award Submission Write-Up
Write a compelling award submission that communicates your design thinking to a panel of judges.
✦ Business Development
Write an architectural award submission for a completed project. Award category: [E.G. "Residential New Build," "Sustainable Design," "Small Project of the Year"]. Project: [DESCRIPTION — e.g. "a new family home on a challenging urban infill site"]. Design concept and key idea: [DESCRIBE — the central idea that drives the whole design]. The brief / challenge: [WHAT THE CLIENT NEEDED — the problem the design solves]. Design response: [DESCRIBE THE ARCHITECTURE — the key moves, how they solve the brief, the spatial and material qualities of the building]. Sustainability approach: [DESCRIBE — if applicable]. Client outcome: [HOW THE PROJECT HAS BEEN RECEIVED — client feedback, any notable outcomes]. Why this project deserves to win: [BE SPECIFIC — what makes this project exceptional in its category]. Photographs available: [LIST KEY IMAGES AVAILABLE]. Maximum word count: [TYPICALLY 500–800 WORDS — specify]. Write a submission that: opens with the central idea and why it matters, tells the story of the design clearly and with conviction, uses specific and evocative language to communicate what makes this building special, and makes a clear case for why it deserves to win in its category. Tone: authoritative and compelling — award judges read dozens of submissions; this one should stand out.27. Practice Profile for a New Business Opportunity
Write a compelling practice profile that positions your firm for a specific new business opportunity.
✦ Business Development
Write an architectural practice profile for submission as part of a new business opportunity or expression of interest. Practice name: [NAME]. Practice size: [E.G. "8 person practice"]. Founded: [YEAR]. Design focus: [DESCRIBE — your practice's specialism and approach]. Key completed projects: [LIST 3–4 — project name, type, value, completion date, and one-sentence description of why it is relevant to this opportunity]. Relevant expertise: [DESCRIBE — specific skills, experience, or knowledge relevant to this opportunity]. Key personnel: [LIST — roles and a brief sentence on each]. Approach to client collaboration: [DESCRIBE — how you work with clients]. Sustainability credentials: [IF RELEVANT]. Write a practice profile of 350–500 words with: (1) an opening that states who you are and why this opportunity is a natural fit, (2) a brief statement of design philosophy, (3) relevant project experience with named examples, (4) key personnel and their relevance, (5) a closing statement that makes a clear case for being considered. Tone: confident and specific — generic practice profiles lose opportunities; this one should feel like it was written specifically for this brief.28. Social Media Project Reveal Post
Write a compelling project reveal post that showcases your design thinking and attracts ideal clients.
✦ Business Development
Write a LinkedIn or Instagram project reveal post for a completed architectural project. Project type: [E.G. "new residential house," "office renovation," "school extension"]. Design concept in one sentence: [YOUR DESCRIPTION]. Key design moves or standout elements: [LIST 2–3 — e.g. "the double-height entrance hall that draws light from above," "the board-formed concrete feature wall," "the rooftop terrace with views across the city"]. The client brief in one sentence: [E.G. "a family who wanted a home that connects them to the landscape without sacrificing warmth or privacy"]. Your practice name or handle: [@HANDLE]. Write a post that: opens with a visual or conceptual hook (not "We are delighted to share..."), tells the brief story of the design concept and key moves in 4–6 sentences, uses specific architectural language without being inaccessible, ends with a question or observation that invites engagement from peers or potential clients, and includes 5–8 relevant hashtags. Under 200 words. Tone: confident and genuine — your project reveal posts are part of your practice's identity; they should sound like the architect who designed the building, not a press release.29. Client Referral Request Email
Ask a satisfied client to refer you to their network in a way that feels genuine, not transactional.
✦ Business Development
Write a client referral request email to send to a satisfied architectural client. Client name: [NAME]. Project completed: [DESCRIPTION]. What you're most proud of from the project: [BRIEF — e.g. "delivering a complex site challenge on programme and within budget while producing a building they are genuinely proud of"]. Who you'd love to be introduced to: [DESCRIBE YOUR IDEAL NEXT PROJECT TYPE — e.g. "homeowners planning a significant extension or new build," "commercial property developers interested in workplace design"]. Any referral incentive or arrangement: [DESCRIBE — or note if there is none]. Write an email that: is warm and direct, acknowledges the successful project genuinely before making any ask, describes your ideal referral in specific terms (so they know who to think of), makes the ask simple ("if anyone comes to mind — a conversation is all it takes"), and expresses genuine appreciation for any introductions they can make. Under 175 words. Tone: personal and professional — the best referrals come from clients who trusted you completely; this email should feel like it comes from that relationship.30. Newsletter for Existing Clients and Contacts
Write a practice newsletter that keeps your network warm and positions your practice as active and excellent.
✦ Business Development
Write a quarterly practice newsletter to send to existing clients, consultants, and contacts. Practice name: [NAME]. Content to include: [LIST — e.g. "a recently completed project," "a current project on site," "a planning success we're proud of," "a team update (new hire, promotion, qualification)," "an industry topic or reflection the practice wants to share"]. Project highlight: [NAME AND BRIEF DESCRIPTION]. Current project on site: [NAME AND BRIEF DESCRIPTION — what stage, what's exciting]. Team update: [DESCRIBE — if any]. Industry reflection or comment: [TOPIC AND YOUR POSITION — e.g. "our thoughts on the new permitted development changes," "why we're excited about mass timber and what it could mean for residential construction"]. Call to action: [E.G. "if you're considering a project, we'd love to have a conversation," "follow us on Instagram for project updates"]. Write a newsletter of 300–400 words with a clear header for each section. Tone: confident, warm, and professional — the best practice newsletters feel like a genuine communication from people who love their work, not a marketing mailout. Let the personality of the practice come through.Get all 30 prompts
Unlock the full list — plus 100+ more prompts for every profession — for just $19
Unlock Now — $19Instant download · Digital product — no shipping or physical delivery.
Get the AI Productivity Prompt Pack →
The AI Productivity Prompt Pack includes 100+ copy-paste prompts for architects, designers, consultants, and service professionals — client communication, project management, business development, and more. One payment, instant download.
Get the AI Productivity Prompt Pack — $19 →The most successful architectural practices combine exceptional design with exceptional communication — clear proposals that win the right work, planning applications that succeed because they make the case compellingly, and client relationships that endure because every update and presentation is handled professionally. These 30 prompts support the written layer of that work from initial brief to final handover. For a broader foundation in AI-powered professional productivity, our guide to ChatGPT prompts for project managers covers the documentation and communication workflows that run across every complex project, and how to automate your business with AI covers end-to-end systems beyond individual prompts.