Brainfile › Guides › Claude Code for Architects
🏛 Architecture Firms 📐 Drawing Standards 📋 Code Compliance 🗂 Project Memory

Claude Code for Architects: Your AI-Powered Architecture OS

Architects produce more written documentation than most people realize — zoning analyses, basis of design narratives, specification sections, RFIs, client presentation narratives, and building code compliance summaries. Claude Code with Brainfile loads your firm's jurisdiction, project history, drawing standards, and documentation format at every session start — so every document you produce reflects your actual project, not a generic starting point.

Start Monthly — $99/mo → Annual Plan — $999/yr
📅 Updated May 2026 ⏱ 14 min read Covers: 5 architecture workflows · Building code research · RFI drafting · Spec writing · Client communication · Project documentation
Table of Contents
  1. The Architecture Documentation Problem
  2. The Architecture OS: What Brainfile Loads
  3. 5 Architecture Use Cases
  4. Before / After Table
  5. CLAUDE.md Setup for Architecture Firms
  6. Frequently Asked Questions

The Architecture Documentation Problem

Architecture is a documentation-heavy profession. From the moment a project is commissioned to final certificate of occupancy, an architect produces hundreds of written deliverables: zoning analysis memos, basis of design narratives, CSI specification sections, RFIs, submittal transmittals, meeting minutes, contractor correspondence, and owner reports. Industry estimates suggest architects and their staff spend 35–45% of billable hours on project documentation that is not drawing production.

Every time you open an AI tool for help, you start over. You re-explain the project type, re-state the jurisdiction, re-describe the occupancy classification, and re-define the construction type. The result is generic output that does not reflect your actual building code version, does not match your firm's specification format, and reads nothing like the client communication voice your firm has spent years refining.

35–45%
of architect time spent on documentation, not drawing production
2–4 hrs
average time to draft a CSI specification section from scratch
15 sec
to get a building code compliance answer with jurisdiction pre-loaded

Building code research is the single biggest documentation time drain. A standard compliance question — setback requirements, occupancy separation, egress path width — requires pulling the correct code version, finding the relevant section, interpreting it against your specific project parameters, and writing a clear summary. With Claude Code and the Architecture OS, your jurisdiction, project type, occupancy group, and construction type are already loaded. Compliance questions take seconds, not hours.

Brainfile solves the context problem that makes AI tools mediocre for professional work. Your CLAUDE.md loads your firm's drawing standards, communication voice, jurisdiction, active project parameters, and specification format at every session start — automatically. Claude knows your practice as well as your most experienced project manager does, from the first prompt of every session.

The Architecture OS: What Brainfile Loads

The key insight: CLAUDE.md is a persistent instruction file that Claude reads at the start of every session. The Architecture OS fills it with your firm's standards, project context, jurisdiction parameters, and documentation formats — so Claude produces work product that matches your actual practice, not generic AI boilerplate.

📐

Drawing Standards OS

Sheet numbering conventions, layer naming protocols, title block format, drawing scale standards, revision tracking format, and BIM naming standards — so every narrative and specification Claude writes aligns perfectly with your actual drawing output and project filing system.

📧

Client Communication OS

Your firm's voice and tone, standard email structures for owner correspondence, meeting summary format, presentation narrative style, and client-facing documentation standards — consistent, professional communication across every team member and every project.

🏗

Code Compliance OS

Active jurisdiction (IBC version plus local amendments), adopted energy code, ADA and accessibility standard version, zoning ordinance references, occupancy group and construction type for current projects — so every compliance question is answered in the right framework without re-explaining the project.

🗂

Project Memory OS

Active project list with type, scope, client, phase, and key parameters. Past project precedents for spec sections and code research. Firm-specific boilerplate for basis of design narratives, specification front matter, and standard RFI language — accumulated practice intelligence, always available.

5 Architecture Use Cases

Use Case 1: Zoning Research and Analysis

Zoning due diligence is one of the first deliverables on any new commission and one of the most time-intensive. You need to pull the correct zoning ordinance, identify the use classification, map out dimensional requirements, flag special overlays, and write a clear summary memo for the owner. With the Architecture OS loaded, Claude knows your project location, proposed use, and zoning code reference — zoning analysis memos go from a half-day task to a focused 45-minute effort.

Zoning Analysis Memo

"Write the zoning analysis memo for our mixed-use project at [address]. Zoning district: B-2 General Business. Proposed use: retail ground floor, 24 residential units above. Pull setback, FAR, height, parking, and use permission requirements."

Claude generates a structured zoning analysis memo in your firm's format: use permissions, dimensional standards (setbacks, FAR, height limit, lot coverage), parking requirements, and special conditions — organized for owner presentation. You review and add local AHJ nuances.

⏱ 45 min vs 3–4 hours from scratch

Overlay and Special District Research

"This site is in the downtown historic overlay district. Research the additional design standards that apply: facade treatment, window-to-wall ratio, signage, material requirements, and the AHJ approval process for design review."

Claude generates a structured overlay requirements summary, flags the additional approval pathway, and drafts the design criteria checklist your team needs to track compliance through schematic and design development phases.

⏱ Saves 2+ hours of overlay research per project

Use Case 2: Building Code Compliance Research

Building code research is where the Architecture OS pays for itself fastest. With your jurisdiction, IBC version, occupancy classification, and construction type pre-loaded, Claude answers standard compliance questions in 15 seconds — not 45 minutes. Egress path widths, occupancy separation requirements, accessible route design, means of egress travel distance, fire suppression thresholds — all answered instantly in your project's framework.

Occupancy Separation Research

"We have an A-2 restaurant on the ground floor and B office on floors 2 and 3 in the same building. IBC 2021, Type VB construction, non-sprinklered. What occupancy separation assembly is required? Is incidental use possible?"

Claude cross-references IBC Table 508.4 and Section 508.3, gives you the required separation rating, flags whether incidental use applies to your configuration, and summarizes the fire barrier or fire partition requirements with specific IBC section references — in under 30 seconds.

⏱ 30 sec vs 45 min of code research

Egress Compliance Checklist

"Generate the egress compliance checklist for our 4-story office building: 12,000 SF per floor, 200 occupants per floor, B occupancy, Type IIA construction, fully sprinklered. IBC 2021 with Illinois amendments."

Claude generates a complete egress checklist: occupant load calculations, minimum number of exits, travel distance limits, common path limits, corridor width requirements, exit discharge, and emergency lighting — organized as a working checklist your team can annotate through construction documents.

⏱ 20 min vs 2+ hours of code assembly

Use Case 3: Specification Writing

Specification writing is the most documentation-intensive phase of most projects, and the output quality varies enormously depending on who is writing. CSI MasterFormat sections require deep technical knowledge, consistent format, and project-specific editing of boilerplate. The Architecture OS loads your specification format, standard front matter language, and past project precedents — so Claude drafts specification sections that match your firm's standard and your project parameters.

CSI Specification Section Draft

"Draft Section 03 30 00 Cast-in-Place Concrete for our 4-story office building. Structural concrete, standard exposure conditions, Chicago climate. Include Part 1 General (submittals, quality assurance), Part 2 Products (mix design, admixtures), Part 3 Execution (placement, curing, protection)."

Claude generates a complete three-part CSI specification section in your firm's format, with project-specific mix design requirements for your climate zone, your standard submittal language, and your quality assurance requirements — a solid first draft your specs writer edits for project specifics, not creates from scratch.

⏱ 30 min review vs 2–3 hours from scratch

Basis of Design Narrative

"Write the basis of design narrative for our building envelope system: EIFS over metal framing, thermally broken curtain wall at lobby, TPO roofing with R-30 continuous insulation. Climate zone 5A, Energy Code ASHRAE 90.1-2019."

Claude generates a structured basis of design narrative that documents the system selections, performance targets, energy code compliance path, and design rationale — the kind of owner-facing document that protects your firm and communicates design intent clearly to contractors.

⏱ 40 min vs 3 hours manual drafting

Use Case 4: RFI Generation and Response Drafting

RFIs are a daily part of construction administration. Writing clear, professionally worded RFIs takes time — especially when you are managing 30 active RFIs across multiple projects simultaneously. The Architecture OS loads your standard RFI format, project parameters, and communication voice — so Claude drafts RFIs and RFI responses in your format, referencing the correct drawing sheets and specification sections, in minutes instead of hours.

RFI Draft

"Draft RFI #47. The contractor is asking for clarification on the waterproofing termination detail at the below-grade wall where it meets the slab edge. Reference: Sheet A-501, Detail 4. Spec Section 07 13 00. The detail shows termination at 6 inches AFF but doesn't specify the termination bar assembly."

Claude drafts a complete, professionally worded RFI in your format: project reference, drawing and spec reference, clear question, and a suggested response option for you to evaluate — saving you the formatting and professional language drafting while you focus on the technical resolution.

⏱ 5 min vs 25 min per RFI

RFI Response with Code Reference

"Contractor is asking via RFI #52 whether they can substitute Type X gypsum board for Type C in our rated corridor assembly. The assembly is a 1-hour fire partition. Respond with the code basis and our decision."

Claude researches the equivalency under the current fire partition standard, drafts the RFI response in your format with the technical rationale and code reference, and flags any conditions on the substitution — a complete, professionally written response ready for your signature.

⏱ 10 min vs 45 min with code research

Use Case 5: Client Presentation Narratives

The narrative that accompanies a schematic design presentation — the design concept statement, the project approach, the sustainability story — takes longer to write than the diagrams it accompanies. The Architecture OS loads your firm's voice, the client brief, and the project's design intent. Claude drafts presentation narratives that actually sound like your firm, not like a generic architecture AI tool.

Schematic Design Narrative

"Write the schematic design narrative for our mixed-use project. Design concept: activate the corner with a double-height retail volume, step the residential mass back from the street to create a planted terrace at level 2. The client brief emphasizes community connection and daylight."

Claude generates a structured presentation narrative: concept statement, design response to the brief, key moves, sustainability approach, and phasing summary — in your firm's voice. The kind of narrative that makes a design presentation land with an owner and communicate your firm's expertise clearly.

⏱ 25 min vs 2 hours writing

Monthly Owner Report

"Write the monthly owner report for [Project Name]. Phase: Design Development. Progress this month: completed structural coordination, finalized exterior material selections, submitted for building permit. Issue: steel lead times are 20 weeks, flagged for owner. Next steps: coordinate MEP drawings, prepare bid package."

Claude generates a professional monthly owner report in your format: phase status, completed work, active issues with recommended actions, next steps, and schedule impact analysis — consistent, clear, and ready for your review before sending to the client.

⏱ 15 min vs 1 hour manual drafting

Before vs. After: What Changes

TaskWithout BrainfileWith Brainfile Architecture OS
Building code compliance checkPaste code text, re-explain project, wait for generic answer — 45 minJurisdiction, occupancy, and construction type pre-loaded — answer in 15 seconds
Zoning analysis memo3–4 hours pulling code, interpreting, drafting memo from scratch45 min reviewing Claude's draft in your firm's format
CSI specification section2–3 hours writing from master spec with project edits30 min reviewing a complete first draft in your format
RFI drafting20–25 min per RFI, inconsistent format across team members5 min per RFI, consistent firm format with drawing and spec references
Client presentation narrative2 hours writing, often sounds generic or rushed25 min reviewing Claude's draft in your firm's voice
Re-explaining project to AI10–20 min per session, every session, every team memberZero — Architecture OS loads project context automatically

CLAUDE.md Setup for Architecture Firms

Core CLAUDE.md Structure

# Architecture OS — [Firm Name] ## Firm Profile Name: [Firm Name] Project types: [Commercial / Residential / Mixed-Use / Institutional] Primary jurisdictions: [City, State — IBC year + local amendments] Specification format: CSI MasterFormat [year] ## Active Jurisdiction Building code: IBC [year] + [State/City] amendments Energy code: ASHRAE 90.1-[year] / IECC [year] Accessibility: ADA 2010 + ICC A117.1-[year] Zoning: [Municipality] Zoning Ordinance [year] ## Drawing Standards Sheet numbering: A-[series] (A-001 = Site, A-101 = Floor Plans) Layer naming: [Standard — AIA, NCS, or firm-specific] Title block: [Firm standard fields] Revision format: [Delta triangle + Rev number] ## Communication Voice Owner correspondence: Professional, direct, proactive about issues RFI language: Technical, neutral, non-accusatory Presentation narratives: Concept-first, owner-friendly, minimal jargon ## Active Projects [Project Name] — [Type], [Phase], [Occupancy], [Construction Type] [Project Name] — [Type], [Phase], [Occupancy], [Construction Type]

brain/ Directory Structure

brain/ standards/ drawing-standards.md # Sheet numbering, layer naming, title block specification-format.md # CSI format, standard front matter language rfi-format.md # RFI agent, response format compliance/ jurisdiction-codes.md # Active code versions, local amendments occupancy-groups.md # Common project types and their occupancies accessibility.md # ADA + ICC A117.1 reference points projects/ active-projects.md # Current commissions with key parameters precedent-specs.md # Past spec sections for reuse and reference communication/ voice-guide.md # Firm voice, client communication tone boilerplate.md # Standard letters, transmittal language

Setup time: Most architecture firms have the core OS running in 30–45 minutes. Start with jurisdiction and drawing standards — those two files alone transform the quality of every compliance answer and document Claude produces. Add project history and precedent specs in the second pass to unlock the full time savings on specification writing.

Frequently Asked Questions

Does Claude Code understand architectural software like Revit or AutoCAD?
Claude Code does not open native CAD or BIM files directly. What it does is maintain persistent context about your drawing standards, layer conventions, sheet numbering protocols, and BIM naming standards — so every narrative, specification, or RFI it writes aligns with your actual drawing output and project filing system. Many firms use Claude to generate descriptive text and specs that accompany drawings, not to replace the CAD workflow itself.
Can Claude Code read and interpret building codes?
Yes. You paste the relevant building code section as context, and Claude interprets it against your project parameters. With the Architecture OS, your project type, occupancy classification, and jurisdiction are pre-loaded — so compliance checks happen in the right framework automatically. Firms use this for IBC, local amendments, accessibility (ADA/ICC A117.1), energy codes, and zoning ordinances. Always verify interpretations with your local AHJ for final permitting decisions.
How does Brainfile help with code compliance research?
The Code Compliance OS pre-loads your jurisdiction, project type, occupancy group, and construction type into every Claude session. When you ask a compliance question, Claude already knows the framework — you do not need to re-explain the project every time. Firms report cutting building code research time by 60–70% for standard compliance checks. Complex interpretive questions still require AHJ confirmation, but the initial research and summary drafting goes dramatically faster.
Can multiple team members at a firm use the same Architecture OS?
Yes. The Architecture OS lives in your project repository — any team member who opens it in Claude Code gets the same context: your drawing standards, project history, jurisdiction, client communication tone, and specification format. Project leads set up the OS once; the whole team benefits automatically. No more inconsistent emails to clients or specifications written in different styles across team members.
Does Brainfile follow AIA best practices for documentation?
The Architecture OS can be configured to align with AIA documentation formats, CSI MasterFormat specification sections, and standard AIA contract language patterns. Your CLAUDE.md defines the documentation standard your firm follows — Claude then generates all written output to that standard. Firms configure this once during setup, and every specification section, RFI, and transmittal follows the same format automatically.
What architectural documents can Claude Code draft with Brainfile?
With the Architecture OS loaded: zoning analysis memos, basis of design narratives, CSI MasterFormat specification sections, RFIs and RFI responses, submittal transmittals, meeting minutes, client presentation narratives, building code compliance summaries, contractor correspondence, and monthly owner reports. The OS loads your firm voice, project data, and documentation standards — so drafts require editing, not rewriting from scratch.

Build Your Architecture OS Today

Load your jurisdiction and drawing standards. See the difference on your first compliance question.

Monthly — $99/mo → Annual — $999/yr

$99/mo · No compute costs · Runs in your environment · Cancel anytime