Building Code Compliance Checks with AI
Building code work is high-stakes, high-volume, and perfectly suited to AI — provided you are relentless about verifying citations. The IBC, IEBC, IMC, IPC, IFC, IECC, IRC, and ICC A117.1 together contain thousands of provisions, and a typical commercial project touches several hundred of them. AI turns hours of code-book flipping into minutes of targeted reading. This lesson shows you how to use AI for code work without getting burned by a hallucinated section number.
What You'll Learn
- How to structure code questions so AI gives you usable answers
- Why you must upload the actual code PDF for reliable answers
- A workflow for producing a formal code analysis document
- How to spot and correct AI code errors before they become problems
The Core Rule
If it is not in the code document, it is not the code. Never cite a code section based solely on AI output. Always open the actual code book (or its PDF) and confirm.
This applies doubly when the AI confidently quotes language. AI regularly invents paragraph numbers that sound right (e.g., "per IBC 1010.1.9.5") but do not exist.
The Upload-the-Code Approach
The most reliable way to use AI for code work is to upload the actual code section as a PDF into Claude or ChatGPT. Then:
I am uploading IBC 2021 Chapter 10 (Means of Egress) as a PDF. My project is a 3-story fully-sprinklered Group B office building, 14,500 sf per floor, 145 occupants per floor. Answer the following based only on the content of the PDF: (1) minimum number of exits per floor (cite section), (2) maximum travel distance, (3) maximum common path of travel, (4) minimum exit width, (5) required corridor rating, (6) dead-end corridor limit. If the PDF does not contain the answer, say so — do not guess.
When you give AI the source document, hallucinations collapse. The AI becomes a very fast index of the code you uploaded.
The Code Analysis Document
Every commercial project needs a code analysis — typically on sheet G-001 or as a separate code summary. AI is excellent at drafting this.
Draft a Code Analysis summary for the cover sheet G-001. Project: {type, address}. Applicable codes: {list editions and local amendments}. Include: (1) Occupancy Classification (IBC 302), (2) Construction Type (IBC 601), (3) Allowable Area and Height (IBC 503, 504, 506, 508), (4) Automatic Sprinkler Requirement (IBC 903), (5) Fire-Resistance Ratings (IBC 601, 705, 706, 707, 708, 709, 711), (6) Means of Egress (IBC 1004, 1005, 1017), (7) Accessibility (ICC A117.1-2017), (8) Plumbing Fixtures (IPC Table 2902.1 or UPC Table 4-1 as applicable), (9) Energy Code (IECC 2021 or ASHRAE 90.1-2022). Format as a clean table. Flag every number where I need to fill in a project-specific value.
The output is a professional-grade template. You fill in the project numbers and verify each citation.
Occupancy and Construction Type
Occupancy classification sets the rest of the project in motion. A careful AI prompt:
My project is a 14,000 sf facility with: (a) retail sales of firearms and ammunition, (b) indoor gun range, (c) classroom space for safety training. Classify this under IBC 2021 Chapter 3. If a mixed-occupancy analysis is required (IBC 508), outline the separation requirements and allowed approach (separated vs. non-separated). Cite the relevant IBC sections.
Mixed-occupancy analysis is one of the highest-value AI tasks because it involves tracing through multiple sections. Verify every citation before you commit.
Fire Ratings and Assemblies
Fire-rated assembly verification is safety-critical, so be extra careful:
For a Type II-B, fully-sprinklered 4-story Group B office building, what fire-resistance rating is required for: (a) the structural frame, (b) exterior walls, (c) fire barriers separating the exit enclosure, (d) corridor walls, (e) shaft enclosures more than 4 stories. Cite IBC 601, 705, 707, 708, 713. Then recommend a UL fire-rated assembly listing for each (list the UL design number and components). Do not invent UL design numbers — if you are unsure, write "verify UL listing" instead of a number.
Telling the AI explicitly "do not invent" is effective. Always verify UL design numbers at database.ul.com.
Accessibility Compliance
Accessibility is heavily jurisdiction-specific (ADA at the federal level, state codes, CBC Chapter 11B in California, etc.):
Apply ICC A117.1-2017 and ADA 2010 to a single-user accessible restroom design. My layout is 6'-0" x 8'-0" net clear. Check: (1) clear floor space at fixtures, (2) turning space, (3) grab bar locations and heights, (4) lavatory knee/toe clearance, (5) WC centerline, (6) door maneuvering. Which sections of ICC A117.1-2017 does each requirement come from?
For California, always append: "Also identify any stricter requirement under CBC Chapter 11B."
Energy Code Compliance
IECC 2021 is a wall of tables. AI is excellent at navigating.
My project is in climate zone 4A, a commercial Group B building. Summarize IECC 2021 Commercial Provisions requirements for: (1) envelope U-factors and SHGC (Chapter 4), (2) building mechanical minimum efficiencies (Chapter 4, Section C403), (3) lighting power density maximums, (4) required controls (occupancy, daylight, time-of-day). Present as a one-page checklist for the MEP engineer.
Always confirm whether your jurisdiction uses IECC 2021 or ASHRAE 90.1-2022 as the compliance path.
Existing Building Code Work
IEBC work is nuanced and a common AI trap.
My project is an existing 1972 commercial building undergoing a Level 2 alteration per IEBC 2021 Chapter 5 for 40% of floor area. Outline: (1) which current code provisions apply to the altered area, (2) which do not, (3) fire-safety and accessibility upgrade thresholds, (4) any required structural evaluation. Cite IEBC sections.
Always verify: "existing building" scope triggers are where AI most often loses track of the exact section.
Plan Check and Permit Review
When a plan checker comments, use AI to help draft responses:
Plan check comment: "Provide fire-resistance-rated assembly UL design for corridor walls per IBC 1020.1." Draft a response letter that: (1) cites the specific sheet and detail where the rating is shown, (2) confirms compliance with the code section, (3) references the manufacturer's UL design, (4) closes politely. Professional tone, short.
Creating a Jurisdiction-Specific Reference
For firms working repeatedly in one city, build a Claude Project or Custom GPT with that jurisdiction's amendments baked in. Upload:
- The base IBC
- The local amendments document
- Zoning ordinance
- Historic district or overlay guidelines if applicable
Now every project query runs against a pre-loaded context of your city's code. This drops hallucination rate dramatically.
The Verification Protocol
For every AI code answer before it goes into a drawing or report:
- Open the actual code book (ICC Digital Codes subscription is worth the $150/year)
- Go to the cited section
- Confirm the language matches the AI summary
- Confirm the edition matches what your jurisdiction has adopted
- Check the local amendments document for overrides
- Document the verification in the project code analysis
Key Takeaways
- Never trust an AI code citation without opening the actual code book
- Uploading the code PDF to Claude or ChatGPT dramatically reduces hallucinations
- Use AI to draft the full code analysis document, then verify every citation
- Build jurisdiction-specific Claude Projects or Custom GPTs with local amendments
- Life-safety code interpretation always gets a qualified human review before stamping