Clean-energy permitting
How to confirm a jurisdiction allows your C&I project when it's not in the code
Commercial and industrial (C&I) solar, battery storage, and EV-charging projects routinely hit jurisdictions whose zoning code says nothing about the technology. Here's how to determine whether a project is permitted, conditional, or simply has no pathway — and why proving the last case is the slowest part of early-stage diligence.
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.
How do I confirm a county allows my project when it's not in the zoning code?
When a code doesn't name your technology, you have to determine which of four situations you're in: the use falls under an existing category, it's allowed by right, it's allowed conditionally with a discretionary permit, or there's no defined pathway at all. Establishing which requires reading the full ordinance and use table — and confirming that no pathway exists is the hard part, because a code's silence is not the same as a prohibition.
This is the defining problem of early-stage clean-energy diligence. A developer with an option on a piece of land can usually answer the easy questions quickly — what's the zone, what's the setback. The expensive question is the open-ended one: is there a path to approval here at all, and if so, how discretionary is it? That answer determines whether a site is worth pursuing, and getting it wrong means carrying a project for months before discovering it was never feasible.
Why can't I just search the code for what I need?
Because the answer usually isn't in one place, and often isn't searchable at all. Many jurisdictions publish zoning as maps or non-searchable PDFs, so a keyword search for "battery" or "solar" returns nothing even when a relevant requirement exists. And requirements are scattered across documents that don't reference each other.
In practice, the relevant rules for a single project can live in any of these:
- The use table, which may classify your technology under a broader category rather than naming it.
- A separate overlay district with its own added requirements.
- A fire code adopted by reference, often administered by a separate fire jurisdiction that layers its own criteria on top of the municipal ordinance.
- A state administrative code that governs where the local code is silent — frequently where energy-storage and larger C&I requirements actually live.
- A council-approved ordinance or moratorium that hasn't been codified yet, so it appears in meeting minutes but not in the published code.
Searching one of these and stopping is how a project team concludes a use is unregulated when it isn't — or assumes it's allowed when a moratorium quietly says otherwise.
How do I prove a project use isn't allowed when the code doesn't mention it?
Proving a negative is the slow part. When a code has a clear process you read the steps and move on, but to responsibly conclude that no pathway exists you have to review the entire relevant code to rule out every place the answer could hide — across ordinance, fire code, state administrative code, and council records. That exhaustive search is what can take hours per jurisdiction.
This asymmetry is why early-stage permitting feels like an opaque risk cloud. The work isn't reading a known rule; it's confirming the absence of one, and then deciding whether the gap means "build here, it's unregulated" or "avoid this, there's no path." It's also a huge time sink for project, engineering and permitting teams: spending hours per jurisdiction just to establish that something is not in the code.
Is Copilot or ChatGPT accurate for checking local code and permitting requirements?
Not reliably, and the failure mode is specific. General AI tools can't tie an answer to the current adopted version of a particular jurisdiction's code, and they routinely 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 seven-figure project, an unsourced answer you can't trace to code text is a liability.
The deeper issue is sourcing. A code determination is only useful if you can point to the exact section it came from, because a planning department will ask. An answer without a citation can't be defended, and one that's confidently wrong about conditional-versus-prohibited can send a project down a pathway that was never available — which is why teams that have tried general AI for this describe it as fast, confident, and wrong in ways that are hard to catch. For a fuller comparison of the research methods, see ChatGPT vs. manual code research.
How do clean-energy teams research local code requirements today?
Most clean-energy developers and permitting consultants do some combination of the following, each with a cost:
- Manual PDF review — the most thorough and the most time-consuming; the only reliable way to prove a negative, but it doesn't scale across a portfolio.
- FOIA requests to local governments — gets authoritative answers, but the turnaround is slow and the process repeats per jurisdiction.
- Calling the AHJ — fast when you reach the right person, but inconsistent and undocumented.
- General AI tools — fast but unsourced and prone to the conditional-vs-prohibited error above.
Where Fordje fits. Fordje is an AI code and regulatory data platform for commercial and industrial clean-energy projects. It does this jurisdictional research up front and keeps it current: gathering the full document set for a jurisdiction — ordinance, use table, fire and overlay requirements, state administrative code, and the supplementary documents that explain how a code is actually applied — and laddering them from local to county to state to the adopted national codes, so the right requirement is pulled from the right place. Every answer cites the exact source text, so a "permitted, conditional, or no pathway" determination is one you can defend to a planning department, not a guess you have to re-verify.
Related questions
How do I find out if a city allows a solar, storage, or EV project before I buy the land?
Resolve four things for the specific authority having jurisdiction: whether the use is named in the code at all, whether it's by-right or conditional, whether a discretionary permit like a CUP is triggered, and whether anything outside the ordinance — fire criteria, a state administrative rule, or an uncodified moratorium — applies. The answer should come from the adopted code for that jurisdiction, not a national standard or a general search.
What use category does a city put solar or battery storage under?
It varies. A jurisdiction may classify the same system as a utility use, an industrial use, a substation, or a power-generation use — or have no category at all, leaving it to interpretation. The classification drives which permits and setbacks apply, so resolving it is often the first real question on a project, and it frequently requires reading past the use table into definitions or prior permits.
What does it mean when a use is "conditional" versus "prohibited" versus "not addressed"?
A permitted (by-right) use needs only a standard building permit. A conditional use is allowed but requires a discretionary permit such as a CUP, adding review time and studies. A prohibited use is explicitly disallowed. A use that's simply not addressed is the ambiguous case — no defined pathway — which can force a developer into a state-level override process or a slow, case-by-case interpretation with planning staff.
How can I find a jurisdiction with workable code to use as a model?
When a target jurisdiction has no usable pathway, teams often look to a nearby or peer jurisdiction in the same state that has already adopted clear regulations for the same technology, then present that as a model to the planning department. The catch is that the model code has to be both relevant and genuinely well-written, and it has to be in the same state — which means researching several jurisdictions in parallel.
Does a project's permitting pathway change mid-project?
Yes. Solar and storage projects often run one to two years — jurisdictions update their codes throughout, and State Administrative updates bring an additional layer of complexity. These can result in a mid-project change to energy-storage requirements that force a redesign. This is why teams track not just the current requirements but changes to them, ideally before a permit is submitted rather than at the point of rejection.