When you open SiteAI on a parcel, ZoneAI automatically pre-fills the zoning parameters — minimum lot size, minimum width and depth, setbacks, and density limits — based on the applicable zoning code for that parcel. Most of the time, these values are accurate and you can run the plan as-is. But sometimes you'll want to adjust them. Here's how to think about it.
When to Trust ZoneAI's Values
ZoneAI pulls its data from the local jurisdiction's zoning ordinance. If the parcel is in a standard residential zone with a clearly written code, the pre-populated values are generally reliable and you should start with them. Running an initial plan with ZoneAI's values gives you a baseline that reflects what the code actually allows — a defensible starting point before you introduce any assumptions.
When to Override the Pre-Populated Values
There are several situations where manually adjusting the zoning inputs makes sense:
You're modeling a rezoning scenario. If you believe the parcel can be rezoned to a higher density, enter the target zoning parameters instead of current ones. This shows you what the site could yield if the rezoning is successful — useful for conversations with landowners about future value.
The jurisdiction has updated its code recently. Zoning data is regularly updated, but there can be a lag between when a municipality amends its ordinance and when that change is reflected in the data. If you know a code update has occurred, verify the current setbacks and dimensions directly with the jurisdiction and enter them manually.
There's a specific agreement or variance in play. If the project involves a pre-negotiated density bonus, a planned development agreement, or a variance you're anticipating, the code values won't reflect that — enter the actual parameters you're designing to.
ZoneAI shows no data or generic values. In areas where zoning data is limited, ZoneAI may fall back to default values. If the pre-filled numbers look generic (very round numbers that don't match local code), verify them against the municipality's actual ordinance before running a plan.
How to Check ZoneAI's Values
Before adjusting, open ZoneAI on the parcel and review the zoning summary — it shows the specific code language and source. If the setbacks and dimensional standards in ZoneAI match what you see in the ordinance, the SiteAI pre-fill is trustworthy. If there's a discrepancy, use the ordinance as your source of truth and enter those values manually in SiteAI.
Documenting Your Assumptions
If you've adjusted zoning inputs from the ZoneAI defaults, note that in your project record so your team knows the plan was modeled on non-standard assumptions. When you export a SiteAI PDF report, the zoning inputs used are included in the report — so any stakeholder reviewing the output can see exactly what parameters drove the yield count.
SiteAI is available on Expert and Enterprise plans. Not on Expert or Enterprise yet? Talk to your account team.