AI for Architects and Designers: Practical Workflows

Architecture and design work involves producing clear briefs, researching site conditions and precedents, developing and comparing options, and communicating choices to clients. AI can support every one of those tasks: drafting a brief from a set of requirements, summarizing research across multiple sources, describing how design options respond to project requirements, and preparing presentation copy. The design judgments and the professional responsibility belong to the architect or designer.

The most common problem in a longer project is losing track of what was decided and why. Tools like fenbs keep the approved requirements, ruling-out decisions, and project context in one place, so the next session, the next team member, or the next client review starts from the current agreed state rather than reconstructing it.

Brief development and requirement review

A project brief defines the goals, constraints, user requirements, site parameters, and regulatory context. Gaps in a project brief produce problems once work begins. AI can review a draft brief and flag categories that are missing or underspecified: user groups, maintenance requirements, accessibility standards, sustainability goals, or planning constraints.

Ask AI to review against specific criteria. "Review this project brief for gaps in the accessibility requirements section" produces more actionable feedback than a general review request. The architect evaluates which gaps matter and revises requirements accordingly before design options are developed.

Brief development also helps when requirements come from multiple sources: client aspirations, technical standards, planning conditions, and budget constraints. AI can help you reconcile those requirements, identify conflicts between them, and draft project brief language that captures what was agreed.

Research and precedent analysis

Architecture and design research covers building types, materials, construction methods, planning contexts, and comparable projects. AI can summarize what is publicly known about a building type, describe typical approaches to a specific problem, and identify questions worth investigating further. That summary speeds up the desk research phase.

Precedent analysis benefits from AI assistance when the scope is large. Describing a set of precedent projects and asking AI to identify common approaches, unusual choices, and lessons relevant to the current brief produces a starting point for the architect's own analysis. AI describes; the architect evaluates and adapts.

For code and regulatory research, AI can summarize what a particular code section requires or explain how planning policy typically applies to a given situation. Verify every regulatory reference against the actual document before relying on it in a submission or design decision.

Option development and comparison

Generating options is a core part of design work. AI can help describe options in writing, explain how each responds to the project requirements, and identify the trade-offs between them. That written analysis is useful for internal reviews, client presentations, and record-keeping.

A useful prompt for option comparison is to describe two or three options, the project requirements they are responding to, and ask AI to describe what each prioritizes and where each creates risks or trade-offs. That output gives the design team a starting point for evaluation and gives the client a clear explanation of why options differ.

Keep a record of rejected options with the reasons. When a client revisits a direction that was already discussed, the record shows what was considered and why a different approach was chosen. That prevents re-doing work and keeps the design process moving forward.

Client presentations and communication

Client communications in architecture and design need to translate technical decisions into clear explanations. AI can draft that explanation: describing a design choice, explaining how it responds to project requirements, and summarizing the implications for cost, program, or future flexibility. The architect reviews for accuracy and adds the specific knowledge the AI does not have.

Presentation notes and handout text are also useful tasks for AI. Describe the design option, its key features, and the decision it addresses, and ask for a summary suitable for a client briefing document. Review for accuracy before including it in any client material.

Professional practice resources from the AIA↗ (opens in a new tab) cover communication standards, contract requirements, and the responsibilities that govern the architect-client relationship. AI can help you communicate more clearly; it does not change the professional obligations that govern the relationship.

Regulatory review and planning submissions

Architecture projects are governed by building codes, planning policy, and accessibility regulations, with different requirements applying at each stage of design development. AI can support the research side of compliance work: summarizing what a specific code section requires, explaining how planning policy typically applies to a given building type, and identifying which regulations are likely relevant before the formal submission process begins. That initial research layer reduces the time spent finding the starting point before the licensed architect makes the professional judgment calls.

Planning applications and permit submissions require clear statements of how the proposed design complies with applicable requirements. AI can help draft the compliance narrative: describing how the design meets a specific code requirement, how the proposal relates to the local planning policy context, and what justifies any departure from standard requirements. The architect confirms the accuracy of that narrative against the actual regulation and the specific design before it becomes part of any formal submission.

Accessibility compliance under the Americans with Disabilities Act and applicable building codes involves specific dimensional and clearance requirements that vary with occupancy type and building use. AI can summarize what a particular accessibility section requires, describe the typical approach to meeting it, and flag areas of the design where compliance is worth verifying. Every accessibility requirement should be confirmed against the actual code section before it shapes a design decision, since code editions and local amendments vary by jurisdiction.

Zoning regulations governing setbacks, height limits, allowable uses, and parking requirements are another area where AI can support initial research. Describe the site, the proposed use, and the applicable zone, and AI can summarize what the ordinance typically requires and flag questions worth raising with the planning department. Zoning interpretations are often jurisdiction-specific and sometimes contested; direct engagement with the planning authority is how those questions get resolved definitively.

When a design revision follows a planning approval, drafting the explanation of what changed, why it changed, and how the revision still meets the original approval conditions is writing-intensive work. AI can produce a first draft of that change justification from a description of the revision and the relevant approval conditions. The architect reviews for accuracy and adds any site-specific context the AI cannot supply. Keeping those justifications in the project documentation prevents the need to reconstruct them during a later review or appeal.

The applicable code edition, local amendments, and the authority having jurisdiction all determine what actually governs a project. AI can describe the general regulatory framework and the typical way a requirement is read, but the relevant authority provides the definitive interpretation for a specific project and site. For any question that affects a formal submission or requires a licensed professional's sign-off, the architect's professional judgment and direct authority contact remain the authoritative route.

Recording the sequence of regulatory decisions made during a project, which code interpretation was applied, what the authority confirmed, and when, forms part of the professional record the architect maintains. AI can help structure that log as decisions are made, producing a clear timeline of compliance actions. That record is useful for the architect's own files, for the client's building documentation, and for any future work on the project that requires understanding the basis for decisions made under regulatory constraints.

How to do this with fenbs

fenbs gives an architecture or design project a record that travels with it through all stages. The setup is lightweight and works for a single practitioner or a project team.

1. Create a free account. A personal board works for a solo practitioner; a team board works when multiple people need access. Personal boards are free with no credit card required.
2. Add a project for each engagement. Write a project summary, the client goals, the key constraints, and the current phase as the project description so every session starts from the same point.
3. Record approved decisions in Decisions and rules: approved requirements, ruled-out options, and the reasons for each change in direction. Include who made each decision and when.
4. Connect a supported AI app from Integrations. Ask the connected assistant to read the project context before each session so it understands the project goals and approved direction.
5. Track design tasks on the board. Move them from To Do to In Progress and then to Completed with notes on what was resolved and what changed. That record becomes part of the project documentation.