AI prompts for architects.

You are helping an architect organize project discovery notes. Convert the source notes below into a concise project brief.

Project context:
- Project type: [PROJECT TYPE]
- Location: [LOCATION]
- Current design stage: [STAGE]
- Intended reader: [CLIENT / INTERNAL TEAM / CONSULTANTS]

Source notes:
[PASTE NOTES]

Structure the brief under these headings: project purpose, users, spatial requirements, priorities, constraints, budget information provided, programme information provided, sustainability ambitions, approvals or stakeholders mentioned, decisions already made, open questions, and next actions.

Do not invent dimensions, budget, regulations, site facts or client preferences. Put missing information under “Open questions.” Keep the language precise and suitable for client review.

Before you use it: Confirm that every stated requirement came from the client or another approved source.

Act as a project information editor, not the project architect. Build a draft space programme using only the approved requirements below.

Project type: [PROJECT TYPE]
Users and occupancy information: [USERS]
Known spaces and requirements: [PASTE REQUIREMENTS]
Known area target, if any: [AREA TARGET OR “NOT PROVIDED”]

Return a table with: space, purpose, primary users, quantity, area provided in the source, adjacency needs, environmental or privacy needs mentioned, fixed equipment mentioned, and questions to resolve.

Do not calculate or recommend code minimums. Do not invent areas or technical performance requirements. Mark all missing values as “To be confirmed,” then provide a prioritized list of briefing questions.

Before you use it: Check areas, occupancy and technical requirements against the signed brief and applicable standards.

Create a site-analysis research plan for an architectural project. This is a checklist for gathering evidence, not a substitute for survey or professional advice.

Project type: [PROJECT TYPE]
Site location and context already known: [KNOWN CONTEXT]
Design questions we need the analysis to inform: [QUESTIONS]

Organize the plan into: access and movement, orientation and daylight, wind and weather exposure, topography, views, neighbouring scale and character, vegetation and ecology, utilities and servicing, noise, privacy, heritage or cultural context, planning information to verify, and survey information required.

For each category, provide: what to observe, what to photograph or record, what source to verify, and which design decision it may influence. Clearly label anything location-dependent as requiring local verification.

Before you use it: Use verified surveys, authority records and specialist reports as the source of truth.

Help an architecture team define a precedent research brief.

Project: [PROJECT TYPE AND SHORT DESCRIPTION]
Design stage: [STAGE]
Questions the team is trying to answer: [QUESTIONS]
Constraints or themes: [CONSTRAINTS]

Create five focused precedent research lenses. For each lens, state: the design question, evidence to collect, comparison criteria, what would make a precedent relevant, and how the finding could influence this project.

Then create a consistent precedent-study template with fields for verified source, architect, location, completion date, building type, scale, drawings or photographs reviewed, transferable principle, and limits of comparison.

Do not invent precedent projects or citations. If examples are requested later, require verifiable sources.

Before you use it: Verify project credits, dates and performance claims using primary sources before presenting them.

Using only the approved project information below, draft a set of project-specific design principles.

Approved brief and constraints:
[PASTE APPROVED INFORMATION]

Create 6–8 principles. For each principle provide:
1. A short, active title.
2. The client or project need it responds to.
3. What the principle means spatially or operationally.
4. Evidence the team could use to test whether an option supports it.

Avoid generic statements such as “create a beautiful building.” Do not introduce new client priorities. End with a short section titled “Tensions to resolve” identifying where the approved priorities may compete with one another.

Before you use it: Have the project lead confirm that the principles reflect the approved brief before using them to judge design work.

Draft an architectural concept narrative from the verified design decisions below.

Project and audience: [PROJECT / AUDIENCE]
Central design idea: [IDEA]
Site response: [VERIFIED SITE RESPONSE]
Spatial sequence: [SEQUENCE]
Material and environmental approach: [APPROACH]
Important constraints the design resolves: [CONSTRAINTS]

Write:
- a 40-word concept statement;
- a 180-word presentation narrative;
- five concise slide captions.

Use clear architectural language without exaggeration. Explain cause and effect: which project need led to which design move. Do not add sustainability, performance or planning claims that are not present in the source information.

Before you use it: Compare the narrative with the current drawings so it describes the design that actually exists.

Help me prepare a neutral comparison of architectural options. Do not choose a winner.

Project priorities and agreed criteria:
[PASTE CRITERIA]

Option A:
[DESCRIPTION AND VERIFIED INFORMATION]

Option B:
[DESCRIPTION AND VERIFIED INFORMATION]

[ADD MORE OPTIONS IF NEEDED]

Create a comparison table showing how each option responds to every agreed criterion. Separate verified evidence from assumptions. Include trade-offs, information still needed, and decisions that require client, consultant or project-lead input.

End with five questions that would make the next review meeting more decisive.

Before you use it: Ensure the comparison uses equivalent evidence and does not disguise subjective judgement as measured performance.

Create a client presentation agenda for an architectural design review.

Meeting objective: [OBJECTIVE]
Current stage: [STAGE]
Material available: [DRAWINGS / MODELS / COST INPUT / PROGRAMME]
Decisions needed from the client: [DECISIONS]
Known concerns or sensitivities: [CONCERNS]
Meeting length: [TIME]

Create a timed agenda that begins with the agreed brief, explains what has changed, presents only the information needed for each decision, and finishes with confirmed actions.

For every agenda item provide: purpose, material to show, one plain-language speaking point, decision or feedback needed, and time allocation. Flag topics that should be handled by a specialist consultant.

Before you use it: Check that the meeting requests decisions the client is equipped and authorized to make.

Convert the source notes below into draft architectural project meeting minutes.

Meeting: [MEETING NAME]
Date and attendees: [DETAILS]
Source notes or transcript:
[PASTE NOTES]

Organize the output into: purpose, key discussion points, confirmed decisions, actions, information required, risks or blockers raised, and items deferred.

Create an action table with action, owner exactly as stated, due date exactly as stated, and source-note reference. If an owner or date was not agreed, write “Unassigned” or “Not agreed.” Do not infer decisions from discussion. Add a final section listing ambiguous statements that need confirmation before the minutes are issued.

Before you use it: A meeting attendee should verify decisions, owners and dates before circulation.

Prepare a consultant coordination agenda using the project information below.

Design stage and next milestone: [STAGE / MILESTONE]
Consultants attending: [DISCIPLINES]
Current drawing or model issue dates: [INFORMATION]
Open coordination items: [PASTE ITEMS]
Known changes since the last meeting: [CHANGES]

Group the agenda by building or system interface rather than by consultant. For each item provide: issue, affected disciplines, source drawing or information, decision needed, information owner, dependency, and required date if supplied.

Prioritize items that block the next milestone. Do not propose technical solutions or assign responsibility unless the source information does so.

Before you use it: Verify ownership and technical scope against appointment documents and the current responsibility matrix.

Draft a request for information from the verified issue details below.

Project and package: [PROJECT / PACKAGE]
Relevant drawing, specification or model reference: [REFERENCE]
Observed conflict or missing information: [ISSUE]
Location: [LOCATION]
Programme impact already identified: [VERIFIED IMPACT OR “NOT ASSESSED”]
Response required by, if agreed: [DATE]

Use this structure: subject, reference documents, concise description of the issue, exact information requested, reason the response is needed, attachments to include, and response date.

Keep the wording neutral. Do not assign fault, invent contractual consequences, propose an unapproved technical solution or calculate delay. Add a short checklist of evidence the author should attach before issue.

Before you use it: The contract administrator or responsible project professional should approve the wording before issue.

Create a design change summary from the approved information below.

Previous design state: [DESCRIPTION / REFERENCES]
Current design state: [DESCRIPTION / REFERENCES]
Reason for change: [APPROVED REASON]
Disciplines, rooms or packages affected: [KNOWN EFFECTS]
Decisions already approved: [APPROVALS]
Items still being assessed: [OPEN ITEMS]

Write a concise change summary with: change description, reason, affected information, known coordination consequences, cost or programme input received, approvals, outstanding checks, and required actions.

Separate confirmed impacts from potential impacts. Do not estimate cost, programme, compliance or technical performance.

Before you use it: Confirm that the summary matches the current revision status and formal change-control process.

Create a draft scope outline for an architectural fee proposal. This is a commercial drafting aid, not legal advice.

Client and project: [DETAILS]
Project stage or stages: [STAGES]
Services requested: [SERVICES]
Known deliverables: [DELIVERABLES]
Programme information: [PROGRAMME]
Known consultant responsibilities: [RESPONSIBILITIES]
Commercial assumptions supplied: [ASSUMPTIONS]

Structure the draft as: project understanding, scope by stage, deliverables, meetings included, client information required, consultant interfaces, exclusions, assumptions, change-control approach, programme dependencies, and commercial items requiring completion.

Do not invent fees, contractual terms, statutory duties or insurance commitments. List unresolved commercial questions at the end.

Before you use it: Have an authorized director or commercial adviser review scope, exclusions and appointment terms.

Create an outline for a planning or design statement using only the verified project information below.

Jurisdiction and application type: [DETAILS]
Project description: [DESCRIPTION]
Site and context evidence: [EVIDENCE]
Design development and response: [DESIGN INFORMATION]
Verified policy references supplied by the project team: [REFERENCES]
Consultation completed: [CONSULTATION]

Propose a logical section structure. Under each section, list the project evidence, drawings or verified policy material needed to support it. Identify missing evidence and questions for the planning adviser.

Do not invent policies, policy wording, application requirements, precedent decisions or claims of compliance. Quote nothing unless it appears in the supplied source material.

Before you use it: A qualified local planning professional should verify requirements, policy interpretation and final claims.

Draft an architectural project case study from the verified information below.

Project summary: [SUMMARY]
Client-approved facts: [FACTS]
Brief and constraints: [BRIEF]
Design response: [RESPONSE]
Team role and services: [ROLE]
Verified outcomes or feedback: [OUTCOMES]
Intended use: [WEBSITE / AWARD ENTRY / PROPOSAL]

Write a title, 40-word summary, 250-word case study, and six image captions. Use this narrative sequence: challenge, reasoning, design response, collaboration, and verified outcome.

Do not invent performance data, client quotes, awards, dates, team credits or claims of impact. Mark missing evidence with a bracketed note rather than smoothing over it.

Before you use it: Confirm client permission, project credits, photography rights and every outcome claim before publishing.