Building an AI-ready
architecture firm

A practical guide to evolving your architecture practice with artificial intelligence—for firms of every size, at every stage.

Developed by the AIA AI Task Force

Start the assessment →
4
Maturity Levels
13
Core AI Terms Explained
7
Policy Frameworks
4
Workflow Patterns

How to use this toolkit

This toolkit is a practical, step-by-step resource designed to help architecture firms of every size adopt AI responsibly. Start by assessing your firm's current maturity, then move through AI literacy, policy development, and change management at your own pace.

quiz

1. Assess

Take the 5-question maturity quiz

school

2. Learn

Build AI literacy with core concepts

policy

3. Plan

Develop policy and ethical frameworks

trending_up

4. Implement

Manage change across your firm

The AIA AI Task Force is a group of architects, technologists, and AIA staff working to help the profession navigate AI adoption. Learn more about the AI Task Force at AIA.org → (opens in new tab)

1

Assess your firm's AI maturity

Start here—find your level before deciding what to do next

Answer these five questions honestly. You'll get a maturity level and personalized next steps. Many firms straddle levels—focus on where the majority of your practices fall.

Question 1 of 5

AI Policy & Awareness

Does your firm have a written AI policy or guidelines for staff?

Question 2 of 5

Tool Usage

How does your team currently use AI tools?

Question 3 of 5

Documentation & Training

How does your firm track and train around AI use?

Question 4 of 5

Verification & Quality Control

How does your firm verify AI-generated outputs before use?

Question 5 of 5

Culture & Leadership

How does firm leadership approach AI adoption?

Your AI Maturity Assessment

Based on your answers

Level 1

Ad hoc experiments

Informal use, no policy, no documentation.
Next: Acknowledge what's happening and adopt a basic policy.

Level 2

Emerging practice

Short policy, a few use cases, informal sharing.
Next: Standardize workflows and build verification into templates.

Level 3

Integrated practice

AI in core workflows, regular training, documented patterns.
Next: Look for places AI can change the underlying process, not just speed it up.

Level 4

AI-first firm

Workflows and roles rethought around AI.
Next: Experiment at the edges while maintaining strong governance and ethics.

2

General AI literacy

Key terms, concepts, and the mindset you need

lightbulb

The most important concept

Mastering today's AI vocabulary isn't the goal. Developing the capacity to learn continuously as the vocabulary evolves is. The edge of your understanding is your most valuable asset.

Core terms—click to expand

Artificial Intelligence
Core ▼
Systems that perform tasks typically requiring human intelligence—perception, decision-making, language, pattern recognition.
Architectural ApplicationDesign assistance tools, automated documentation, project analysis software, and increasingly, systems that can execute complex multi-step tasks with minimal oversight.
Generative AI (GenAI)
Core ▼
AI systems that create new content—text, images, 3D models, code—based on patterns learned from existing data. Includes ChatGPT, Claude, Midjourney, DALL-E, Microsoft Copilot.
Architectural ApplicationGenerate renderings from text descriptions, draft specification sections, create design variations, produce marketing content, write meeting summaries.
Large Language Model (LLM)
Core ▼
AI trained on massive text to understand and generate human language. It learns statistical relationships between words and predicts the most likely response to your prompt.
Architectural ApplicationQuery building codes, draft specifications, summarize meeting notes, write RFI responses, research precedents. Major LLMs: GPT-4 (OpenAI), Claude (Anthropic), Gemini (Google).
AI Agent
Advanced ▼
A system that can plan, make decisions, use tools, and take multi-step actions to accomplish goals with minimal human oversight. Unlike simple chatbots, agents can break complex tasks into steps, search for info, run calculations, check their own work, and adapt.
Architectural ApplicationExample: Agent receives "Prepare a zoning analysis for this site" and independently researches codes, analyzes site conditions, generates diagrams, identifies required variances, and produces a summary report.
Hallucination
Risk ▼
When an AI model produces confident, fluent output that is simply wrong, fabricated, or unsupported. This is not a bug—it is a structural feature of current AI models.
Critical ActionYour policies should assume hallucinations WILL occur and specify verification steps before relying on outputs. The control is how and where you rely on them—not a setting you can turn off.
Prompt/Prompt Engineering
Core ▼
The instructions given to an AI system, and the skill of crafting them effectively. Think of it as "how to brief a junior staff member"—clear prompts with context and constraints dramatically change output quality.
Prompt ProgressionBasic: "Design a house" → Better: "Design a 2,500 SF single-family house" → Professional: "Generate three massing studies for a 2,500 SF passive house on a 0.25-acre lot with southern exposure..."
RAG (Retrieval-Augmented Generation)
Advanced ▼
A pattern where the AI first retrieves relevant documents from a private collection (your office standards, past specs), then uses only those to answer a question. It narrows what the model can see—safer and cheaper than training a new model.
Why it mattersThis is the realistic way for firms of any size to "use our own knowledge"—without building or training a whole new AI model. Ideal for office standards, detail libraries, and project manuals.
Training Data
Risk ▼
The information used to teach an AI system. Much AI training data includes copyrighted work. Uploading your details to "improve the tool" may grant rights you didn't intend—read vendor agreements carefully.
The IP AnalogyAI doesn't store copies of buildings in a file cabinet—it atomizes training data into statistical relationships, much like how your own brain learned from hundreds of buildings you've studied over your career.
Context Window
Risk ▼
How much text an AI can "hold in mind" at once—its working memory. If you upload a long document and it exceeds the context window, the model may never have "seen" key pages without warning you.
Common MistakeAssuming "I uploaded it, so the AI considered it." Always verify that critical sections were actually processed, especially with long specs, contracts, or multi-page uploads.
Machine Learning (ML)
Core ▼
A subset of AI where systems learn patterns from data rather than following explicit programming. Instead of writing rules for every scenario, you feed thousands of examples and the system learns.
Architectural ApplicationPowers tools that analyze past projects to suggest layouts, predict construction costs, or identify design conflicts—"based on your last 50 projects, you typically need X SF for circulation."
Agentic AI
Advanced ▼
AI systems that operate with a degree of autonomy—planning multi-step workflows, using external tools, making intermediate decisions, and self-correcting without human input at every stage. Agentic AI goes beyond chat-style Q&A: it can orchestrate sequences of actions to achieve a goal you define.
Architectural ApplicationAn agentic workflow could receive a site address and autonomously pull zoning data, generate setback diagrams, flag variances, draft a preliminary zoning narrative, and compile everything into a summary—tasks that would normally require hours of manual research across multiple sources.
MCP (Model Context Protocol)
Advanced ▼
An open standard that lets AI models connect to external tools, data sources, and services through a common interface—like a USB-C port for AI. Instead of each AI vendor building custom integrations, MCP provides a single protocol so any compliant model can interact with any compliant tool.
Why It Matters for FirmsMCP means your AI assistant could connect directly to Revit, your specification library, project management software, or building code databases through standardized plug-ins—without waiting for each vendor to build a bespoke integration. It reduces lock-in and accelerates the ecosystem of AI tools available to architects.
WebMCP
Advanced ▼
An extension of MCP that runs over the web, allowing AI models to discover and use remote services hosted by third parties—similar to how a browser discovers and loads websites. Where MCP connects AI to local tools on your machine, WebMCP connects it to cloud-hosted tools and APIs anywhere on the internet.
Why It Matters for FirmsWebMCP could let an AI agent seamlessly query a materials database, pull real-time energy pricing, or check permit status with a municipality—all without your firm building or maintaining those connections. As the standard matures, expect a growing marketplace of AEC-specific services that AI tools can tap into on demand.

"The edge of your understanding is your most valuable asset. Knowing what you don't know is critical. Thinking you know something when you don't is dangerous."

— Eric Cesal, Harvard Graduate School of Design, AIA AI Task Force
3

Policy, ethics, contracts, and legislation

Frameworks for responsible AI use in professional practice

warning

Why "set and forget" won't work

AI capabilities are advancing rapidly and unpredictably. A policy written today will be addressing obsolete capabilities within a year. This section is designed for continuous adaptation—not annual review.

It is also written to stand on its own. Wherever it draws on AIA's existing positions or the AIA Code of Ethics & Professional Conduct, the relevant content is summarized here so the toolkit can serve as a single reference, with citations to the source documents for verification.

Why your firm needs an internal AI policy

An internal AI policy is not a one-time document. It is a living statement of how your firm intends to use, govern, and supervise AI tools across projects. Whatever specific tools or restrictions you adopt today will change. The principles below—accountability, confidentiality, verification, and ethical humility—are designed to outlast the tool churn.

These principles also map directly onto duties the profession already recognizes. The AIA Code of Ethics & Professional Conduct (2024) requires that members demonstrate reasonable care and competence (Rule 1.101), maintain client confidentiality (Rule 3.401), exercise responsible control over signed and sealed work (Rule 4.102), and avoid misleading clients about results that can be achieved through their services (Rule 3.301). The advent of AI does not change these duties—it raises the bar on how an architect satisfies them.

Core principles

1. Professional responsibility cannot be delegated

No matter how capable AI becomes, licensed architects remain responsible for all work product. Whatever AI produces, an architect signs. You must understand what AI did, not just that it worked. You must be able to explain and defend the decisions reflected in the work.

Code anchor: Rule 4.102 (responsible control); AIA Public Policy I.C.3.

2. Client confidentiality does not change

Code of Ethics Rule 3.401 prohibits members from knowingly disclosing information that clients have asked them to keep confidential. Entering confidential project information into a public AI tool may constitute a violation of that rule, regardless of whether the output is helpful. Enterprise versions may offer verified data-handling commitments—but these vary widely. Treat any tool whose terms you have not personally verified as a public tool.

Default position: assume anything you input into an unverified AI tool could be used to train future models or otherwise leave your control.

3. Quality control remains human

All AI output requires verification. The level of effort should match the work's stakes, as set out in the risk-tier framework below. The principle is straightforward: AI may inform a deliverable, but the architect's reviewed and verified work is the deliverable.

4. Build ethics review into your policy

Ethical positions in this toolkit are provisional. Hard positions today may become untenable as both technology and practice evolve. Build review into your policy, not just into your projects. The Ethics Framework tab addresses this in more depth.

extension

AI is increasingly inside the tools you already use

Modern design, rendering, modeling, code-checking, specification, and document-management software increasingly invoke AI capabilities—sometimes locally, sometimes through cloud services—without a separate "AI mode" the user has to opt into. A firm's policy cannot be predicated on identifying every AI invocation. Base policy on the outputs and decisions AI is contributing to, not on whether a specific feature is technically AI. If an output influences a decision a licensed professional is responsible for, the principles in this section apply.

AI-use risk tiers

The following framework applies the principle of matched effort to stakes. It is a working tool, not a closed taxonomy.

Risk tier Typical uses Review required Who approves
Low Risk Draft emails, meeting notes, task lists, early image ideation, formatting, spell-check. Quick reasonableness check. No project record required. Any staff member.
Medium Risk Zoning and code summaries, draft narratives, schedule boilerplate, options studies. Check against trusted sources. Note in the project record for significant uses. Project Architect or Project Manager.
High Risk Life-safety analysis, accessibility compliance, final code interpretation, stamped deliverables. AI is exploratory only. Final work must be independently re-verified. The architect's reviewed and verified work—not the AI output—is the deliverable. Document the use in the project record. Licensed design professional (Architect of Record).

⚠️ If an AI use does not clearly fit a category, treat it as higher risk.

✅ Guidance on Approved Applications

  • Research and information synthesis (with verification).
  • Draft text for internal use.
  • Visualization and rendering.
  • Meeting notes and summaries.
  • Precedent research and analysis.
  • Project scheduling and planning, with verification.

🚫 Guidance on Current Restrictions

  • Inputting confidential client information into AI tools that are not covered by a verified data-handling agreement.
  • Public AI tools used with confidential client data, regardless of intent.
  • Replicating the recognizable design work or visual style of other architects.
  • Presenting AI output as human-created where disclosure is appropriate.
  • Sealing documents without thorough human review.
  • Using AI as the primary decision-maker in employment decisions.
  • Relying on AI-generated code references, citations, or precedents without independent verification.
assignment

Policy review cadence

Review quarterly: review AI capability changes, update risk assessments, and document new use cases. Continuously: when significant new capabilities emerge, when issues arise, or when gaps are identified.

Designate a person, not a committee, to track AI developments. Quarterly reviews that belong to everyone tend to belong to no one.

description Sample firm AI policy templates

Two downloadable Word templates that put the principles above into a working firm policy. Both reflect the AIA Code of Ethics anchors used throughout this section. Choose the version that fits your firm's needs—the policy is size-agnostic, so the difference is depth, not firm size.

⚠️ Both templates are starting points. Adapt to local laws, project contracts, and your insurance carrier's requirements, and have your final policy reviewed by legal counsel and your professional liability insurer before adoption.

Disclosing AI use to clients

Client relationships will increasingly involve AI in ways that need to be managed thoughtfully—but not ritualistically. The right disclosure posture depends on the role AI played, the contract under which the work is being performed, and the client.

When clients ask: a useful framing ▼
When clients raise concerns about AI, it can help to offer perspective. Professional baseball players use video analysis, defensive analytics, and biomechanical modeling—tools that did not exist a generation ago. The game is still played by humans, and the burden of performance still falls on them. AI in architecture is similar: an analytical and generative tool. Professional judgment, accountability, and licensure remain unchanged.

When and how to disclose AI use

There is not yet a settled professional standard for disclosing AI use to clients, and the right answer is project-specific. The following posture is defensible across most engagements.

1. Read the contract first▼
A growing number of owner-supplied agreements—especially federal, institutional, and large corporate contracts—include specific provisions on AI use, AI-generated content, training-data restrictions, ownership of AI-assisted work, and required disclosures. Honor those provisions. They override any general firm policy. The Contract Language tab covers what to look for.
2. Disclose substantive AI involvement▼
Disclose when AI played a substantive role in a deliverable that the client will rely on. Examples include AI-generated renderings presented as project visualizations, AI-assisted code or zoning analysis that informed a design decision, and AI-generated text incorporated into a report or specification. Disclosure does not need to be formal in every case—a clear note in a transmittal or in the deliverable itself is often sufficient.
3. Be candid if asked▼
If a client asks how AI is being used on their project, answer plainly. Concealing routine, low-risk AI use creates more risk than disclosing it. Code of Ethics Rule 3.301 requires candor about the results that can be achieved through the architect's services and prohibits misleading representations.
4. Do not bill one client for R&D that benefits all clients▼
When a client funds experimentation that will improve the firm's capabilities for future work, the project should benefit. This is a long-standing principle of professional practice and is consistent with the candor required by Rule 3.301.

When the client raises AI

Some clients—particularly those whose own business is being reshaped by AI—will want to talk about it. When they do, useful questions include:

  • How is your organization approaching AI?
  • Do you anticipate AI changing your near- or medium-term capital project needs?
  • Are there AI-related concerns or restrictions we should know about for this project?

A hotel operator exploring robotic housekeeping, a healthcare client modeling AI-assisted clinical workflows, or a corporate client rethinking office space around AI-augmented teams all have a direct interest in how AI may shape their building program. In those cases, the conversation is a service to the client, not an imposition. For projects where the client has not raised AI, an unprompted conversation about technology adoption strategy is generally not warranted.

balance

The problem with ethical certainty

It is not possible to take hard ethical positions based on what architecture and AI are today and expect those positions to remain valid as both evolve. Ethics in the age of AI must be provisional—not in the sense of moral relativism, but in recognition of genuinely new territory.

anchor

Anchor: the AIA Code of Ethics & Professional Conduct

Every AIA member is bound by the AIA Code of Ethics & Professional Conduct. The Code does not yet address AI by name—most professional codes do not—but its existing Canons and Rules already govern much of what the AI conversation is actually about. The principles below extend the Code's existing logic into the AI context. They do not replace it.

The Code is structured into three tiers: Canons (broad principles), Ethical Standards (more specific goals), and Rules of Conduct (mandatory; violations are grounds for discipline). The Rules most relevant to AI use are summarized here and cross-referenced in the AIA Resources tab; the full Code is available at aia.org (opens in new tab).

Core ethical commitments

1. Human flourishing is the goal ▼
Architecture exists to serve human wellbeing—safety, health, comfort, dignity, community, meaning. AI should enhance that goal, not substitute for it. Efficiency gains from AI matter only if they serve human flourishing. The question of what serves people remains primary even when AI offers other optimizations.

This commitment is consistent with Canon I of the Code of Ethics, which calls on members to thoughtfully consider the social and environmental impact of their professional activities, and with Ethical Standard 1.5, which directs members to design buildings and spaces that enhance human dignity and the health, safety, and welfare of the public.
2. Transparency about what we do not control ▼
When AI plays a significant role in design or documentation, clients and stakeholders have a right to understand how decisions affecting them were made. This includes disclosing AI-generated visualizations, explaining when AI assisted in analysis, and being honest about AI's limitations in understanding context.

This commitment is anchored in the Code of Ethics, Ethical Standard 3.3, and Rule 3.301 (candor and truthfulness): members may not intentionally or recklessly mislead clients about the results that can be achieved through their services. The Client Disclosure tab translates this into practical guidance.
3. Intellectual property remains unsettled—proceed carefully ▼
Much AI training data includes copyrighted architectural work used without permission. The legal status of AI-generated design elements remains unclear in most jurisdictions, and the U.S. Copyright Office has indicated that purely AI-generated content is not eligible for copyright protection.

Best current practice: maintain meaningful human creative involvement in all significant design decisions; do not use AI to replicate another firm's distinctive style; document the human contribution to the creative process so authorship is defensible.

Code of Ethics Rule 2.101 prohibits members from knowingly violating the law in the conduct of their professional practice, including the federal Copyright Act. AIA Public Policy II.B.1 (Copyright Protection) also affirms AIA's support for copyright protection of the architect's work and other intellectual property.
4. Bias does not disappear—it gets encoded ▼
AI trained on historical data will reflect historical biases—in design defaults, in construction practices, and in who has historically had access to what kinds of buildings. Where the profession has systemic problems with access, equity, or representation, AI trained on the profession's work will perpetuate and may amplify them.

This is not a reason to avoid AI. It is a reason to be explicit about designing for equity. Areas where bias most often surfaces in practice include programming and space-typology assumptions, accessibility defaults, and the depiction of people, neighborhoods, and contexts in AI-generated visualizations.

Code of Ethics Rule 1.401 prohibits harassment and discrimination based on race, religion, national origin, age, disability, caregiver status, gender, gender identity, or sexual orientation. Ethical Standard 2.4 (Environmental Equity and Justice) extends this commitment to the design of the built environment. AIA Public Policy II.C.6 (Equity, Environmental Justice, and Land Use) likewise supports equitable advancement of public health priorities, including for vulnerable populations.
edit_note

The fundamental challenge

Contract language around AI is advancing faster than the professional standards that underpin it. In a typical year, a firm is more likely to encounter AI clauses in contracts presented to it than to draft AI clauses into its own agreements. The guidance below covers both: how to think about AI provisions when you encounter them, and how to address AI in agreements you do draft.

Do not write AI contract language based solely on a toolkit. Work with attorneys who understand professional liability and AI in your jurisdiction.

Practical contract guidance

1. Read AI clauses already in your contracts▼
Owner-supplied agreements increasingly contain AI provisions. Identify them before signing. They will govern the project regardless of any internal firm policy. Common provisions include:
  • Prohibitions on training third-party models with project data.
  • Required disclosures of AI use to the owner.
  • Restrictions on or prohibitions of AI-generated deliverables.
  • Ownership and licensing terms for AI-assisted work product.
  • Indemnities related to AI-generated content.
  • Audit rights and recordkeeping obligations.
These provisions are appearing most often in federal, institutional, healthcare, and large corporate contracts, and are migrating into smaller agreements. Treat them as material terms that warrant the same review as insurance, indemnity, and standard-of-care provisions.
2. Maintain clear human accountability▼
Whatever AI is involved, contracts should establish that licensed professionals remain responsible for work product, that human judgment governs all significant decisions, and that professional standards apply regardless of tools used. This is consistent with Code of Ethics Rule 4.102 (responsible control) and is something clients and courts already understand.
3. Be thoughtful about disclosure language▼
There is no consensus on how much AI disclosure contracts require. Calibrate to the engagement: client sophistication and expectations, the significance of AI's role in the work, professional liability insurance requirements, and the firm's values around transparency. Avoid disclosure language so broad that it cannot be meaningfully complied with—for example, blanket disclosure of any tool that uses AI features, when AI is now embedded in many ordinary software products.
4. Address verification and quality control explicitly▼
Where appropriate, contracts can specify that AI-assisted work receives appropriate verification, that quality-control procedures meet professional standards, and how errors or deficiencies are addressed. Explicit language protects both parties by establishing that AI use does not reduce professional oversight.
5. Keep intellectual property language flexible▼
Given unsettled IP law regarding AI-generated work, maintain standard IP ownership clauses, acknowledge legal uncertainty, and ensure ongoing human creative input to support IP claims. Where the U.S. Copyright Office has determined that purely AI-generated content cannot be copyrighted, warrant carefully—do not warrant ownership of work the firm cannot demonstrate is the product of human authorship.
6. Coordinate subconsultant AI use▼
Flow-down is real. An architect who has agreed to a "no AI use," "disclosure of AI use," or "no training on project data" clause with an owner needs to push that requirement down to engineers, renderers, specification writers, and specialty consultants. Subconsultant agreements should require disclosure of significant AI use, establish expectations for verification, coordinate professional liability coverage, and maintain clear accountability chains across the project team. Verify compliance—do not assume it.

Legislation in this space is moving quickly and inconsistently. By the time this toolkit is read, specifics will have changed. The orientation below is therefore not a summary of current law but a posture for staying current.

newspaper

Stay current on AI news

Implementation of AI requirements is downstream of legislation. Knowing that a bill is likely to pass in a few months can give a firm a multi-month lead time to prepare practice changes that competitors will scramble to make at the deadline.

public

Watch other jurisdictions

The United States and the European Union have adopted different legislative philosophies. Federal and state governments are often at odds. Legislation tends to migrate—provisions that pass in California may appear in Australia or in another U.S. state shortly after, and vice versa.

account_balance

Get involved

The most direct way to affect legislation is to help write it. Architects bring unique expertise on how buildings, codes, professional liability, and AI intersect. AIA engages on AI policy at the federal level and through state and local components; members can contribute through AIA Government Affairs channels and through their state component's advocacy work. Engagement at the state and local levels, where practice regulation is determined, is especially valuable.

gavel

Watch adjacent fields

AI liability and accountability will be litigated in medicine and law before they are settled for design professionals. The case law that emerges will give architects early signals about how similar questions are likely to be resolved for the design professions. Insurance carriers will closely track these cases; firms should do the same.

eco

AI's environmental footprint

AI carries a real environmental cost—energy and water for both training models and the inference that occurs every time a tool is used. That cost is acknowledged in AIA's AI Position Statement (PDF, opens in new tab), which lists environmental impact among the concerns the profession should weigh as it adopts AI.

Detailed measurement remains challenging, and there is not yet an established baseline for comparing the environmental cost of AI-assisted workflows against the traditional methods they replace. The toolkit's posture is to provide factual information rather than make definitive claims while the picture continues to develop.

What is reasonably well understood

  • Training large models is energy- and water-intensive, with most of the cost borne by model providers rather than by individual firms.
  • Inference—each query, image generation, or run of an AI feature—also consumes energy. At firm scale, the cumulative effect is non-trivial.
  • Cloud-hosted AI services pass their footprint through to the firms that use them. As AI features become embedded in mainstream design software, that footprint flows into ordinary practice.
  • Vendors differ significantly in disclosure, infrastructure, regional energy mix, and whether they offer environmental impact reporting.

What is not yet well measured

There are no established baselines yet for several questions firms will reasonably ask. Naming the gaps is itself part of an honest treatment of the topic:

  • How to attribute AI-specific energy and water use within a firm's broader cloud and software footprint.
  • Whether AI-assisted workflows reduce or increase total project-lifecycle environmental cost compared with traditional methods. The baseline for that comparison does not yet exist.
  • How model size, training cycles, and deployment patterns shape the per-query cost.
  • How to compare across vendors with different infrastructure, regions, and disclosure practices.

What firms are doing today

Some firms have committed to tracking energy consumption related to AI and cloud computing, and others are committing in their strategic plans to do so as the methodology matures. Common starting points include:

  • Adding AI energy use to existing carbon accounting frameworks where the data is available.
  • Asking AI vendors for environmental impact data and including it in vendor selection criteria.
  • Disclosing AI energy use in firm sustainability reporting alongside other operational impacts.
  • Committing in firm strategic plans to track AI-related energy and reporting on progress as practice develops.

No single firm has fully solved measurement. Sharing approaches across the profession—how firms attribute, track, and report AI environmental impact—will accelerate the development of a workable baseline. AIA encourages members to share examples of environmental tracking measures so the profession can learn collectively.

balance

Environmental impact is one factor among several

Firms developing AI policies should weigh environmental impact alongside other broader factors: accountability, transparency, equity, data privacy, and human-AI interaction. The Internal Policy, Ethics Framework, Client Disclosure, and Contract Language tabs treat each of these. A defensible firm AI policy reflects all of them, with environmental impact considered explicitly rather than as an afterthought.

campaign

AIA's posture and further reading

The AIA AI Position Statement (PDF, opens in new tab) identifies environmental impact among the concerns the profession should track as AI adoption advances. As measurement methodology develops, this section will be updated with practical guidance and examples firms can adopt.

This toolkit summarizes the AIA Code of Ethics and AIA Public Policy provisions most relevant to AI use, serving as a single working reference. Members are responsible for the source documents in their full text. The tables below map toolkit topics to those source provisions for verification and deeper reading.

AIA Code of Ethics & Professional Conduct — relevant provisions

Topic in this toolkit Code provision What it requires
Reasonable care and competence with new tools Rule 1.101 Members must demonstrate a consistent pattern of reasonable care and competence and apply the technical knowledge and skill ordinarily applied by architects of good standing in the same locality.
Bias, equity, and non-discrimination Rule 1.401; E.S. 2.4 Members shall not engage in harassment or discrimination on protected bases. Ethical Standard 2.4 directs members to promote fairness and to advise clients of obligations to environmental equity and human health.
Copyright, IP, and unlawful use of others' work Rule 2.101 Members shall not knowingly violate the law in the conduct of their professional practice. The Commentary specifically references the federal Copyright Act, which prohibits copying architectural works without the copyright owner's permission.
Competence to undertake services using AI Rule 3.102 Members shall undertake to perform professional services only when they (with their consultants) are qualified by education, training, or experience in the specific technical areas involved.
Candor about what AI can and cannot deliver Rule 3.301 Members shall not intentionally or recklessly mislead existing or prospective clients about the results that can be achieved through their services.
Confidentiality of client data with AI tools Rule 3.401 Members shall not knowingly disclose information that would adversely affect their client or that they have been asked to keep in confidence, except as otherwise allowed or required by the Code or applicable law.
Responsible control over AI-assisted deliverables Rule 4.102 Members shall not sign or seal drawings, specifications, reports, or other professional work for which they do not have responsible control—defined as the degree of knowledge and supervision ordinarily required by the professional standard of care.
Recognizing the work of colleagues, not replicating others' style with AI Rule 5.301 Members shall recognize and respect the professional contributions of their employees, employers, professional colleagues, and business associates.

AIA Public Policies and Position Statements—relevant provisions

Topic in this toolkit AIA Public Policy What AIA's position holds
Responsible control and the architect's role I.C.1; I.C.3 AIA supports a uniform definition of the practice of architecture and holds that licensed architects are uniquely qualified to take responsible control for the coordinated integration of building systems from project inception to completion.
Maintaining professional competence as tools change I.B.1; I.B.3 AIA supports continuing education for licensure renewal and supports research and development of materials, technologies, and practices that advance the needs of clients and the public and protect health, safety, and welfare.
Copyright protection for architectural work II.B.1 AIA supports copyright protection for architects' work and other intellectual property to prevent unauthorized use.
Open standards and interoperability for AI/BIM tools II.B.7 AIA holds that industry-supporting software must facilitate, not inhibit, project planning, design, construction, commissioning, and lifecycle management—supported by non-proprietary, open standards for auditable information exchange.
Qualifications-based selection and uncompensated AI proposals II.B.4 AIA supports public procurement based on qualifications rather than fees or bids, and opposes any requirement for uncompensated design solutions as part of the QBS process.
Project delivery and team collaboration II.B.3; III.A.4 AIA supports collaborative project delivery characterized by early and consistent involvement of owners, architects, engineers, constructors, fabricators, and end users—and a coordinated teamwork approach across project participants.
Equity and bias in design decisions informed by AI II.C.6 AIA advocates for policies that support the equitable advancement of public health priorities, including the protection of vulnerable populations and equitable protection of human health.

Source documents and further reading

Members are encouraged to consult these source documents directly:

update

Note on currency

AI capabilities, AIA positions, and the legal landscape are all evolving. Where this toolkit summarizes a Rule of the Code of Ethics or an AIA Public Policy, the source document governs in the event of any inconsistency or after subsequent amendment. The Code of Ethics is current as of February 1, 2024; the Public Policies cited here are drawn from the April 2024 Directory.

4

Change management

Culture, operations, and workflows—the human side of AI adoption

construction

This isn't the BIM transition

For those who remember the CAD or BIM transitions—this will not be that. Those had a steady state to arrive at. AI has no steady state. There is no stable destination—only continuous adaptation.

The culture shift required

bolt

Fast-learning as competitive advantage

Architecture school trains people in fast-learning—synthesizing new knowledge rapidly, iterating based on critique. That skill, devalued in traditional practice, is exactly what AI adoption demands. Recognize it, reward it, and make learning time visible on schedules.

science

Embrace micro-scale innovation

Don't bet the firm on transformation. Run low-stakes experiments first: AI for meeting notes (low risk), AI visualization on pro-bono projects before paying clients, AI specs on renovations before new construction.

shield

Create psychological safety

People won't experiment if they fear looking stupid, wasting time, or being replaced. Make 3–4 hours per week of non-billable experimentation visible on schedules. Hold "Show Your Failures" sessions monthly. Leadership goes first.

psychology

Address professional anxiety honestly

Don't reassure your team that everything will be fine. Have an honest conversation: AI will change architectural work. Some tasks that take hours will take minutes. The question isn't whether to engage—it's how to engage in ways that serve your values.

school

Protect the apprenticeship

AI can produce a competent-looking deliverable without the learner ever doing the reasoning. Be explicit about which tasks junior staff must still do by hand to build judgment—massing studies, code research, initial detailing—even when AI could shortcut them. Treat AI as a review partner for juniors, not a replacement for the work that teaches them to think like architects.

"Your expertise matters more now, not less—because you're what catches AI's mistakes. Your design thinking matters—because AI can generate options but can't decide what's worth pursuing."

— AIA AI Taskforce Guidance

What architecture brings to AI

Long time horizons

Buildings last 50–100 years. Architects think in generational terms that AI models don't.

Physical and Spatial Intelligence

Understanding how space shapes behavior and experience in ways AI cannot truly replicate.

Human-centered design

Deep orientation toward how design affects the humans who inhabit it.

Values as anchor

In a field changing faster than anyone can understand, professional values provide stability.

database

Data readiness is AI readiness

AI runs on data. A firm's existing files, archives, and operational records are not the same as a curated data foundation—they're typically a mix of useful information, redundant copies, obsolete material, and content that adds noise rather than value. Bringing AI into a firm without addressing this layer first is a common reason early AI initiatives produce disappointing results. Data security and governance are practical prerequisites to AI readiness, not optional add-ons.

"Most firms don't have 40 years of data. They have 40 years of files."

— Nicholas Kramer, LEED AP

Files vs. data—and why the distinction matters

Files are documents—drawings, specs, photos, emails, deliverables—produced and stored as work product. Data is structured, queryable, and consistent enough that systems can use it programmatically. AI tools can do interesting things with files; they do far more useful things with data.

Most firms will not convert decades of files into clean data, and they don't need to. The practical goal is to make the firm's most-used knowledge accessible: standards, details, specs, lessons learned, project performance. Start there.

Data literacy is a prerequisite to AI literacy

Before staff can use AI well, they need a baseline understanding of:

  • What data the firm has (and doesn't have).
  • Which sources are authoritative vs. duplicated.
  • Which information is confidential and which is routine.
  • How to recognize when an AI tool is missing context that exists somewhere in the firm.

This is not primarily a technical skill—it is a practical literacy any architect can build. The Section 2 (AI Literacy) glossary terms Training Data, RAG, and Context Window are useful pairings.

Address ROT—Redundant, Obsolete, Trivial

Most firm archives contain a substantial volume of redundant copies, obsolete versions, and trivial content (auto-saves, drafts, ephemera) that does not represent firm knowledge. Reducing ROT improves AI tool output and lowers security and storage cost. Larger firms can use enterprise data-discovery services to scan at scale; smaller firms can do meaningful cleanup with naming conventions and periodic archive reviews.

✅ Do

  • Start with a few high-value content categories (standards, details, specs).
  • Establish one authoritative source per content type.
  • Run periodic archive reviews tied to project closeout.

🚫 Don't

  • Try to clean everything before doing anything else.
  • Treat ROT cleanup as a one-time project.
  • Build elaborate taxonomies the firm cannot sustain.

Scale-appropriate guidance

Data governance looks different at different firm sizes. The principles are constant; the implementation is not. The guidance below is pitched at what is practical at each scale rather than the academic ideal. The toolkit is meant to address the meat of making it happen, not just the framework.

Sole proprietors and firms under 10

  • Organize archives by client / year / phase with consistent naming.
  • Separate active project data from archived.
  • Decide what stays local vs. what goes to cloud.
  • Goal: "findable," not enterprise-grade.
  • One annual archive cleanup session.

Mid-size firms (10–100)

  • Inventory what data lives in which systems (Revit, PM, CRM, shared drives).
  • Establish authoritative sources per content type.
  • Document a basic retention schedule.
  • Designate one person (not a committee) for data ownership.
  • Quarterly archive reviews tied to project closeout.

Large firms (100+)

  • Designate data ownership across practice groups.
  • Implement enterprise data-discovery and classification tools.
  • Build a data classification scheme for confidentiality and retention.
  • Coordinate IT, Legal, and Risk on data policies.
  • Tie data governance to AI tool procurement decisions.
build

Practical over academic

This subsection deliberately favors practical starting points over comprehensive frameworks. The "academic side" of data governance is well covered elsewhere; the gap firms most often describe is in the meat of making it happen—what to do Monday morning. The guidance above is intentionally pitched at that level.

The fast-learning firm: Operational framework

1

Dedicated learning time

3–4 hours per person per week of non-billable AI experimentation. Make it visible on schedules—not "squeeze it in." Leadership participates too.

2

Systematic knowledge capture

Document successful workflows and failure modes. Share knowledge across the team. Build prompt libraries and checklists that can be reused.

3

Regular learning sessions

Monthly 30-minute sessions sharing what worked and what didn't. "Show Your Failures" sessions normalize experimentation. Focus on learning, not blame.

4

External connection

Stay connected to the broader professional community. AIA, peers, and professional networks provide early signals about what's working and what's not.

Governance ownership

AI governance fails when it's everyone's job and therefore no one's. Assign named owners for each domain so decisions move and accountability is clear.

Domain Primary owner Supporting
Tool selection & procurementIT / OperationsDesign leadership
Acceptable use policyOperations and LegalHR
Output verification standardsDesign leadershipQA/QC lead
Client disclosure & consentPrincipal-in-chargeLegal
Data protection (client & project)IT / LegalProject managers
Professional liability & standard of careRisk / LegalPrincipals

Operational shifts to expect

Verification gates

Add verification gates where AI-generated content enters deliverables—specs, code summaries, renderings. Document who signed off.

PM review role

PMs take on a new review role: confirming AI use is disclosed in the project record and verification was proportional to risk.

Structured curriculum

Replace ad-hoc learning with a structured curriculum: prompt basics, verification discipline, tool-specific workflows.

Job descriptions

Update roles for staff who review AI output—critical evaluation becomes an explicit, named responsibility, not an afterthought.

Getting real about ROI

ROI on AI in architecture is real but rarely comes from the line item you expect. Hours saved on drafting matter less than wins from faster fee proposals, fewer RFIs, and tighter coordination. Track the downstream metrics, not just tool utilization.

payments

AI saves time on generation—verification takes time too

Net benefit exists only if total time (generation + verification) beats the traditional approach. Don't treat AI time savings as pure savings—always include verification time when estimating and scheduling. Verification should not be rushed just because generation was fast.

analytics

Measuring what actually matters

Track hours saved per task type, error rates in AI-assisted versus traditional work, staff confidence and comfort over time, and client satisfaction. Be honest about what is working and what is not. Scale successes, abandon failures, iterate on maybes.

AI is changing architect workflows in four distinct patterns. Understanding which pattern you're using—and its verification requirements—is essential for maintaining quality and managing risk.

Available now: in production use at multiple firms today. Emerging: working prototypes with firms piloting in 2026.

1

AI-Assisted Generation with Human Curation

AI generates options; humans select and refine

Available Now
Human
Brief + Prompt
→
AI
Generate Options
→
Human
Curate + Refine
→
Human
Develop + Verify

Best for: Design exploration, specification drafting, rendering ideation, programming options. The human remains the creative decision-maker. AI accelerates the generative phase, but the work is in the filtering: keeping the three options that solve the actual program; discarding the seven that look good but violate code, budget, or brief.

AEC examples: massing options for a mixed-use site, Division 01 spec boilerplate drawn from past projects, first-pass rendering exploration for client workshops.

Verification focus: confirm selected options meet zoning, FAR, setback, and program. Catch the code violations before they reach the client.

Risk note: the architect of record remains responsible for code compliance and design integrity regardless of AI involvement. Document your curation and verification process.

2

AI-Enabled Analysis with Human Interpretation

AI processes data; humans make meaning

Available Now
Human
Define Question
→
AI
Analyze Data
→
Human
Interpret Results
→
Human
Apply Judgment

Best for: Zoning analysis, code research, energy modeling, cost estimating. AI can process information at speeds humans can't. But interpreting what the analysis means in context—what to do about it—remains a human task.

AEC examples: BIM QA/QC (scanning models for missing parameters, mis-typed families), clash-detection prioritization, first-pass egress and accessibility review, daylight and energy analysis summaries.

Verification focus: cross-check model inputs against the actual Revit file. AI summaries of simulation output often round assumptions or miss edge conditions. For code research, verify citations against the jurisdiction's current adopted edition—AI routinely cites superseded IBC sections.

Risk note: an analysis summary is not a legal interpretation. Code determinations and life-safety conclusions still require licensed judgment and, where appropriate, AHJ confirmation.

3

AI-Drafted Content with Human Verification

AI creates first drafts; humans verify accuracy

Available Now
Human
Provide Context
→
AI
Draft Content
→
Human
Verify Facts
→
Human
Edit + Finalize

Best for: Technical specifications, project narratives, RFI responses, proposal writing. Remember: hallucinations are structural features of current AI—all factual claims require verification, especially in technical specifications with product names and code references.

AEC examples: spec writing from past projects, RFI drafting, project narrative for proposals, executive summaries of consultant reports.

Verification focus: check spec language against manufacturer data sheets—AI invents product names and ASTM numbers. Confirm every code citation. Verify every claim of past project scope or fee.

Risk note: specs become contract documents. A fabricated product name or wrong ASTM reference that reaches a set of drawings is a professional liability exposure. Verification is not optional.

4

Autonomous Design

AI completes multi-step tasks with minimal oversight

Emerging
Human
Define Goal
→
AI Agent
Plan Steps
→
AI Agent
Execute + Iterate
→
Human
Review + Approve

AEC examples (emerging): end-to-end zoning analysis from a parcel address, multi-option site plans with automated setback and FAR checking, full consultant-report triage with flagged action items.

warning

Approach with caution

Agents introduce new failure modes: endless loops, wrong tool use, silent mistakes. Quality control needs rethinking. Professional liability implications are significant and unresolved. Any massing or site plan output must be validated for setback, FAR, and height compliance before presentation. Start with simple, well-bounded tasks before moving toward full autonomous workflows.

Verification checklists by task type

📋 Specifications

  • Product names and model numbers accurate
  • Installation procedures correct
  • System coordination verified
  • Current edition standards cited

📖 Code Research

  • Citation verified against actual code
  • Correct jurisdiction confirmed
  • Edition/amendment year correct
  • Interpretation accuracy checked

🖼️ Renderings

  • Buildability confirmed
  • Materials accurately represented
  • Scale not misleading
  • Context honest (site, surroundings)

What you owe the client

AI use changes five things your contract and client conversations should address. These apply regardless of which workflow pattern you use.

Disclosure

Share AI's role with clients where it meaningfully shapes the work they rely on. Transparency builds trust.

Authorship

The architect of record stamps the drawings. AI does not reduce that responsibility.

Reliance

Clients rely on your judgment, not the tool's output. Verify before you present.

Standard of care

Using AI does not lower the standard. It may raise it as AI usage increases.

Data

Know what client information is entering which tool, and whether that tool trains on it.

flag

Where to start for firms under 25 people

A practical five-step starting sequence when change management feels bigger than the firm can absorb:

  1. Pick one workflow this quarter. Proposal writing or spec drafting are the lowest-risk entry points.
  2. Assign an owner. One principal, not a committee. Their job: choose the tool, write the one-page use policy, set the verification standard.
  3. Train on it. Two hours, all staff, same tool.
  4. Measure one thing. Hours saved, errors caught, or proposals sent. Just one.
  5. Review in 90 days. Keep, expand, or kill.
→

Key takeaways and path forward

What actually matters for your firm, for yourself, and for the profession

The hard truths

1

AI is changing architectural practice fundamentally

This isn't just new software. It's a reorganization of the design process—what work allows AI intervention and automation and what doesn't. Human involvement will always remain; the capacities may just look different.

2

Some current roles will lose relevance; new ones will emerge

This is uncomfortable and unavoidable. Architects who actively learn and apply AI will be better positioned than those who don't.

3

Nobody has this figured out yet

Everyone is in research and development mode, including the firms and people who appear most confident. Anyone claiming definitive answers is oversimplifying.

4

The pace of change will likely accelerate

Don't expect to reach a new equilibrium where you can stop adapting. The goal is building adaptive capacity, not mastering today's tools.

5

Incremental adaptation may not be enough

The profession may need to fundamentally reimagine the practice model, not just improve tools within the existing model.

6

The economics of practice are shifting

AI may reduce the cost of producing deliverables, challenging traditional fee structures and value propositions. Firms that rethink how they price and deliver value—not just how they produce work—will be better positioned.

The capabilities that endure

bolt

Fast learning

Be willing to rapidly acquire and apply new capabilities—the core architectural skill AI demands

waves

Adaptive thinking

Have comfort with uncertainty and continuous change. This is not a destination, but a posture

search

Critical evaluation

Know what to trust, what to question, and what to verify

balance

Professional judgment

Make sound decisions under ambiguous conditions

groups

Human-centered design

Maintain a focus on people flourishing amid technical change—the core purpose of architecture

explore

Values-based practice

Work from clear principles even when methods are uncertain—a constant anchor

hub

Systems thinking

Understand how tools, workflows, and decisions interact across a project. This will be essential as AI reshapes the design process

Your next steps

For your firm

  • 01Start with 2–3 targeted, low-risk experiments
  • 02Build learning systematically—allocate dedicated time
  • 03Develop verification instincts and checklists
  • 04Create a culture of psychological safety for experimentation
  • 05Stay connected to the broader professional community and share lessons learned

For yourself

  • 01Develop fast-learning as an intentional capability
  • 02Build comfort with uncertainty—not knowing is okay
  • 03Clarify your values so they can anchor you during change
  • 04Maintain human judgment skills—don't outsource them
  • 05Think critically—neither reject nor accept AI uncritically

For the profession

  • 01Engage honestly with challenges—don't minimize them
  • 02Share knowledge openly—this is better figured out collectively
  • 03Address long-standing problems AI is now making visible
  • 04Engage with legislation at state and local levels
  • 05Maintain focus on human flourishing as the north star
Share feedback