Zoning should be a linter.
Who This Matters To (And Why)
Critical: Developer,Architect,City. These parties make or lose money directly based on this thesis.
Important: GC,Engineer,Banker. These parties execute decisions shaped by this thesis.
Context: Investor,Inspector,Broker. These parties need to understand it to avoid friction.
Highest typology impact: Multifamily,Office,Mixed Use,Urban Planning. Lower impact: Retail,Industrial.
Zoning should be a linter. Run your design against the rules before you submit.
How It Shapes Development
Zoning should be a linter because a linter is a tool that checks code for style and correctness violations in real time, as the code is written, before it is compiled or deployed. A zoning linter would check a building design for zoning compliance in real time, as the design is developed, before it is submitted for permit. Setback violation: flagged immediately. FAR exceedance: flagged immediately. Parking shortfall: flagged immediately. Use not permitted in zone: flagged immediately. The designer fixes violations as they occur rather than discovering them at permit submission after months of design work.
Current zoning compliance works like compiling without a linter. The designer writes the code (produces the design) without automated feedback. The compiler (permit reviewer) finds the errors at submission. Compilation fails. The designer fixes errors and resubmits. In software, this workflow was abandoned in the 1990s when linters became standard. In architecture, it remains the dominant workflow in 2025 because zoning codes are not machine-readable and design tools do not integrate zoning compliance checking.
A zoning linter requires two inputs: a machine-readable zoning code and a building model with geospatial registration. The machine-readable zoning code is a structured dataset of requirements for each parcel: permitted uses, FAR limits, height limits, setbacks, parking ratios. The geospatially registered building model knows which parcel it sits on and can query the zoning dataset for applicable requirements. The linter compares the model's parameters against the requirements and flags violations. This is technically achievable with current BIM and GIS technology. The gap is the machine-readable zoning code, which most jurisdictions do not have.
Zoning linters change the designer's relationship to the code. A designer who gets immediate feedback when they violate a setback learns the setback intuitively through repeated interaction. A designer who only finds out about the setback violation at permit submission learns the code through expensive failure. The linter makes code literacy part of the design workflow rather than a prerequisite. Designers who have always worked with zoning linters design within constraints naturally, without needing to hold every requirement in their heads simultaneously. The tool extends their working memory to include the full regulatory context.