Can I use ChatGPT to look up local code and permitting requirements?

General-purpose AI tools are unreliable for local code research in two specific ways. First, they struggle to disambiguate jurisdictions with similar names and aren't tied to the current, adopted version of a specific code, so they can return requirements from the wrong place or an outdated cycle. Second, they frequently confuse a use that is 'conditional' (allowed with a discretionary permit) with one that is 'prohibited,' or invent a permitting pathway that doesn't exist. For determinations that gate real projects, an unsourced answer that may be hallucinated is a liability rather than a shortcut.

Why does ChatGPT get jurisdiction questions wrong?

Two reasons. The underlying data is the open internet, which mixes jurisdictions, editions, and outdated documents, so the model can't reliably tell which specific authority having jurisdiction or code cycle applies to a given site — the classic failure is not distinguishing between similarly named places like different Orange Counties. And local code requirements often aren't on the public internet in searchable form at all; they live in scanned PDFs, supplementary documents, or records that have to be requested, none of which a general model has reliably ingested.

What makes a dedicated code platform different from a general AI tool?

A dedicated compliance data platform differs from a general AI tool in what it's built on and how it answers. Instead of searching the open internet at query time, it works from a maintained, jurisdiction-specific corpus — gathered from ordinances, amendments, state code, fire criteria, and ancillary documents, validated, and kept current. Answers are laddered to the correct authority having jurisdiction and code cycle and cite the exact source text, so they can be verified and defended rather than taken on faith. The tradeoff is coverage: a platform covers the jurisdictions it has built out, where a general tool will attempt any question but without the same reliability.

← Part of: Commercial Clean Energy Guide

Copilot vs. code research

Can you use Copilot or ChatGPT for local code and permitting research?

Q: Why can't I just search the code or Google it myself?

Manual searching is the most common fallback, and for many jurisdictions it's the only thing that works — but it's slow and incomplete. Codes are often published as non-searchable PDFs, requirements are scattered across the ordinance, fire jurisdiction, state administrative code, and ancillary documents, and confirming that a requirement doesn't exist means reading the whole relevant code. Experienced researchers frequently conclude that the only reliable manual method is going document by document by hand, which doesn't scale across a portfolio or a new market.

Q: What about filing a FOIA request for the requirements?

FOIA requests get authoritative answers directly from the jurisdiction, which is valuable when information isn't published or is ambiguous. The drawback is speed and repeatability: a FOIA request is a lengthy process and has to be repeated per jurisdiction, so it works as a targeted tool for filling gaps but not as a way to scope requirements across many jurisdictions quickly.

For commercial and industrial (C&I) clean-energy teams, getting local code and permitting requirements right is the difference between a project that moves and one that stalls at permit. Here's an honest comparison of the methods teams use — general AI tools, manual research, FOIA, and dedicated platforms — and exactly where each one breaks.

Last updated: July 6, 2026

From Fordje — AI code and compliance data for commercial and industrial clean-energy projects.

Part of the Commercial Clean Energy Guide.

Can I use Copilot or ChatGPT to look up local code requirements?

Not reliably, and the failure mode is specific. General AI tools struggle to disambiguate jurisdictions with similar names and aren't tied to the current adopted code, so they return requirements from the wrong place or an outdated cycle. They also confuse a conditional use (allowed with a discretionary permit) with a prohibited one, or invent a pathway that doesn't exist. For a determination that gates a real project, an unsourced answer you can't trace to code text is a liability.

Teams that have tried it describe the same pattern: the tool is confident, fast, and wrong in ways that are hard to catch — mixing up conditional and prohibited, hallucinating a permit type, or answering for the wrong jurisdiction entirely. It can be a useful "better Google" for orienting yourself, but it can't be the source of record for a requirement you're going to build against.

Why does a general AI tool get jurisdiction questions wrong?

Two reasons. Its underlying data is the open internet, which mixes jurisdictions, editions, and outdated documents, so it can't reliably tell which AHJ or code cycle applies to a given site — the classic version is failing to distinguish between similarly named places, like assuming the wrong Orange County. And local requirements are often to find through the layers of municipal websites; they live in scanned PDFs, supplementary documents, or records that must be requested.

That second point is the deeper one. Even a perfect model can only answer from what it can access, and a large share of local code lives outside what's been cleanly published online. When the authoritative source is a scanned PDF, a fire jurisdiction's separate criteria, or a council action that hasn't been codified, a general tool has nothing reliable to draw from — so it fills the gap with a plausible guess.

Why isn't manual research or Googling enough on its own?

Manual research is the most common fallback and, for many jurisdictions, the only thing that actually works — but it's slow and incomplete. Codes are often poorly searchable websites or non-searchable PDFs, requirements are scattered across the ordinance, fire jurisdiction, state administrative code, and ancillary documents, and proving that a requirement doesn't exist means reading the entire relevant code. The reliable manual method is going document by document by hand, which doesn't scale.

Experienced researchers tend to arrive at the same conclusion: they tried AI, they tried searching, and the only approach that held up was manual, by-hand review of every document. That's defensible and accurate — and it's exactly why it becomes the bottleneck when a team tries to scale across a portfolio or move into a new market, where the same hours-per-jurisdiction effort has to repeat dozens of times.

The time, detail and ambiguity often lead to a "submit and pray" method, where teams simply submit a permit to find out what was wrong, and continue to submit until they get it right. Its expensive and time consuming.

The specific case of confirming a jurisdiction's silence — the exhaustive read to prove no pathway exists — is covered in how to confirm a jurisdiction allows your project when it's not in the code.

ChatGPT vs manual research vs FOIA: which is best for code lookup?

Each common method trades off accuracy, speed, sourcing, and how well it scales. The honest summary: general AI is fast but unsourced and error-prone; manual research is accurate but slow; FOIA is authoritative but lengthy; a dedicated platform is fast and sourced within the jurisdictions it covers.

Method	Strength	Where it breaks
General AI (ChatGPT, Copilot)	Fast, conversational, good for orientation	Wrong jurisdiction/cycle; confuses conditional vs prohibited; no citations
Manual PDF / web research	Accurate; the reliable way to prove a negative	Slow; doesn't scale across jurisdictions or markets
FOIA request	Authoritative, direct from the jurisdiction	Lengthy; must be repeated per jurisdiction
Calling the AHJ	Fast when you reach the right person	Inconsistent, undocumented, person-dependent
Dedicated code platform	Fast, sourced, comparable across jurisdictions, kept current	Limited to the jurisdictions it has built out

What makes a dedicated platform different?

A dedicated regulatory data platform differs from a general AI tool in what it's built on and how it answers. Instead of searching the open internet at query time, it works from a maintained, jurisdiction-specific corpus — gathered from ordinances, amendments, state code, fire criteria, and ancillary documents, validated, and kept current. Answers ladder to the correct AHJ and code cycle and cite the exact source text, so they can be verified rather than taken on faith.

Where Fordje fits. Fordje is an AI code and regulatory data platform built specifically for this problem in commercial and industrial clean energy. It doesn't query the open internet — it maintains a validated, jurisdiction-specific corpus gathered from ordinances, amendments, state administrative code, fire-jurisdiction criteria, and the ancillary documents that explain how a code is applied, all laddered to the right authority having jurisdiction and code cycle. Every answer cites its source text, so a requirement is one you can verify and defend, and the data updates as codes change.

What about filing a FOIA request for the requirements?

FOIA is required when codes aren't currently available on a municipal website. Requests get authoritative answers straight from the jurisdiction, which is valuable when information isn't published or is ambiguous. The drawback is speed and repeatability — a FOIA is a lengthy process and has to be repeated per jurisdiction, so it works as a targeted tool for filling specific gaps, not as a way to scope many jurisdictions quickly.

Is any AI reliable for code research, or none of it?

The distinction isn't AI versus no AI — it's what the AI is grounded in. A general model answering from the open internet is unreliable for local code. An AI system grounded in a maintained, validated, jurisdiction-specific corpus with citations is a different thing: the AI handles language and retrieval, but the answer traces to real source documents rather than to the open web.

How do I verify an answer about a code requirement?

The test is whether you can trace it to the exact section of the adopted code or document it came from, for the correct jurisdiction and cycle. An answer you can't source can't be defended to a planning department — which is why citation back to source text, not just a confident response, is the thing that makes a code answer usable.

← Back to: Commercial Clean Energy Guide