Editorial Policy

Data Sourcing Methodology

All zoning and permit data on PropertyZoned is sourced exclusively from official municipal codes, city ordinances, state legislation, and government-published documents. We do not accept data from third-party data vendors, real estate platforms, news articles, or other aggregation services.

Primary sources include:

• Official municipal code repositories (Municode, American Legal Publishing, Sterling Codifiers, city-hosted platforms)
• City and county building department fee schedules and handouts
• Planning department published guidelines and zoning summaries
• State legislation affecting local zoning preemption (particularly ADU and affordability laws)
• City council adopted ordinances (accessed via official meeting records and clerk portals)

Every data point on PropertyZoned includes a source URL and specific code section reference (e.g., “Austin City Code § 25-2-899”) so visitors can independently verify the information. We also display a last-verified date on every data page so visitors know when the data was confirmed accurate.

Verification Process

Zoning data is not static — ordinances are amended, state laws preempt local rules, and fee schedules are updated on no fixed schedule. Our verification process is designed to reflect the current state of the law, not just the state at the time of initial research.

1. 1
   Source identification

   We identify the authoritative legal source for each data point — the specific section of the municipal code, the specific state statute, or the specific fee schedule document. Secondary sources are used only to locate primary sources.
2. 2
   Data extraction

   Data is extracted directly from the official source document. We record the exact code language, then structure it into our standardized schema. AI tools assist with structuring and formatting — never with interpreting ambiguous code language.
3. 3
   Ambiguity resolution

   When official code language is ambiguous or internally contradictory, we note the ambiguity on the page and recommend contacting the local planning department directly. We do not resolve ambiguity through interpretation.
4. 4
   Cross-reference check

   For ADU rules and home business regulations — areas with frequent state preemption — we cross-reference local code against active state legislation to flag potential conflicts and note which law controls.
5. 5
   Date stamping and citation

   Every verified data point receives a source citation (URL + code section) and a verification date. These are displayed on every data page.
6. 6
   Periodic re-verification

   Our target schedule: Tier 1 cities (top 25) re-verified quarterly, Tier 2 (cities 26–50) semi-annually, Tier 3 (cities 51–100) annually. Any city that adopts a major zoning ordinance change is prioritized for review within 60 days of the effective date, regardless of tier.

Correction & Update Policy

Zoning codes change. PropertyZoned will inevitably carry data that has become outdated since it was verified. Our correction process is designed to surface and fix these errors quickly.

How to Report an Error

Every data page on PropertyZoned includes a “Report Outdated Information” button. Clicking it opens a pre-addressed email to contact@propertyzoned.com. When reporting, please include the specific data point you believe is outdated and, if possible, a link to the official source showing the current rule.

Our Response Timeline

• All correction reports are reviewed within 14 business days
• Reports with a clear official source link are prioritized and reviewed within 5 business days
• Verified errors are corrected within 30 days of verification
• Corrections update the page's last-verified date and source citation
• We do not silently delete data — corrections are noted in our internal change log

AI Disclosure

Specifically, AI tools are used for:

• Converting raw municipal code language into structured JSON data fields
• Identifying the relevant section of a code document for a specific query type (e.g., finding the ADU section within a 500-page zoning code)
• Formatting permit fee schedules into consistent table structures
• Drafting summary language that describes official rules in plain English — always reviewed against the source

AI tools are explicitly prohibited from: generating zoning rules, permit fees, or regulatory thresholds; filling in data gaps where no official source can be found; and resolving ambiguous code language through interpretation.

What We Don't Do

PropertyZoned has clear boundaries that define what we are and what we are not:

• We don't provide legal advice
  PropertyZoned is an informational resource. Nothing on this site constitutes legal advice. For specific property questions, consult a licensed land use attorney.
• We don't quote municipal code verbatim at scale
  Municipal codes are copyrighted works. We summarize and structure official data in our own words, citing the source section, rather than reproducing entire code sections.
• We don't claim to be a government resource
  PropertyZoned is an independent third-party platform. We are not affiliated with, endorsed by, or sponsored by any government agency, city, county, or state.
• We don't publish data without a source
  If we can't cite an official source for a data point, we don't publish it. We'll note that a rule 'varies by zone' or 'requires direct inquiry' before we'll publish an uncited number.
• We don't make property-specific recommendations
  City-level zoning data cannot tell you what applies to your specific parcel — overlay zones, HOA rules, and parcel-level conditions vary. Always verify with your local planning department before acting.

Questions about our editorial standards? Contact us or email contact@propertyzoned.com.