Building-Code Context in the Analysis
Before some AI tasks run, Estimatics looks up building-code requirements for the job's ZIP code and damage type and gives them to the AI. Which tasks use it, which don't, and why it is not an authority.
4 min read
Code-driven work is some of the most commonly missed scope: items a visual inspection won't show but the code requires.
Estimatics doesn't hand you a code checklist. It does something quieter. Before certain AI tasks run, it looks up building-code requirements for the job's ZIP code and damage type and adds them to what the AI reads. The AI's output has had the code for that location in view.
This runs on every plan. It's not a paid add-on and not a screen you open.
How it works
- It takes the job's ZIP code and damage type. If the job has no ZIP code or no damage type, there's no lookup.
- It asks the AI to find the current residential code requirements for that combination.
- If that lookup returns nothing usable, it falls back to generic IRC guidance for the damage type.
- It keeps the result for 90 days, so the same ZIP code and damage type aren't looked up again on every job.
You never see the result as a list, and you never approve it. It shapes what the AI writes. It doesn't add estimate lines on its own.
Which AI tasks use it
| AI task | Uses code context |
|---|---|
| Photo analysis (automatic on upload, or "Analyze selected photos" on iPhone) | ✓ |
| AI Walkthrough findings | ✓ |
| Esti, the job assistant | ✓ |
| AI-written report sections: Executive Summary, Damage Findings, Cause & Origin | ✓ |
| Area analysis ("Analyze · N left" on an area) | — |
| AI Narrative (Analyze → "Narrative") | — |
| "Build with AI" in Estimate | — |
"Build with AI" doesn't use this ZIP-code lookup, but the reason it writes for a line can still cite a code section or standard from the AI's general knowledge. Check those the same way.
Esti and the AI-written report sections also read industry standards (IICRC) for the job's damage type. When Esti shows "Cross-checking codes and protocols…", this is what it's reading. You can ask it directly, for example "What IICRC protocol applies here?"
→ Esti, your job assistant · How findings work
What it is not
It is not an authority. It's an AI lookup, not a curated, state-by-state rules database maintained by code experts. Codes change on adoption cycles and vary by jurisdiction, sometimes between two towns in the same county.
It does not decide your scope. Nothing is added to an estimate because the code context mentioned it. Every line in your scope is one you or "Build with AI" put there, and that you reviewed.
It is not a substitute for checking. If you're going to support a code-driven item in a claim, confirm it against the official, currently adopted code for that jurisdiction first, and cite that, not Estimatics.
What to do with it
Read the AI's output knowing it had code context. Treat anything code-related the way you'd treat a colleague's reminder: worth checking, not worth citing. Then check it, and cite the code itself.
A code item you can't support in the adopted code weakens the file more than leaving it out would have.
How findings work
What the AI does with your photos, and how you review it.
Validation and what's missing
Line checks and gaps in the estimate before it goes out.
Evidence coverage
Where the file is thin, area by area.
AI disclosure
Which model does what, and the limits we publish.
Last updated: October 2026 · Questions? Email support@aiestimatics.com
Last updated: October 2026 · Feedback on this article