Essay: The Zoning Code as Living Document

Zoning as a living regulatory tool.

A zoning code is not a plan. A plan describes a vision. A code makes it real — or fails to. It is the instrument through which everything a community aspires to in its general plan either becomes buildable, livable, and implementable, or remains aspiration on paper.

Most zoning codes fall short of this standard. Not because they are written carelessly, but because they are written for a city that no longer exists, or for a simplified version of the city that never existed at all. They are organized around categories that made sense decades ago, administered through processes that accumulate complexity over time, and applied uniformly across places that are fundamentally unlike each other.

The result is regulation that is simultaneously too rigid and too permissive. Too rigid in the places where flexibility would enable good outcomes. Too permissive in the places where nuance is needed to prevent bad ones. And too complex — everywhere — for the property owners, builders, city staff, and community members who need to use it.

A zoning code that works needs to do five things:

Translate vision into standard. Every policy in a General Plan needs a regulatory mechanism — a standard, a use permission, a process requirement that makes it actionable. A vision without a code is a wish. A code without a vision is just rules.
Be legible to the people who use it. Property owners, small builders, community members, city staff, and elected officials should not need a planning attorney to understand what is allowed on their property. Legibility is not a design preference. It is a democratic requirement.
Be buildable. A code that produces beautiful diagrams and unbuildable projects has failed. Standards need to be tested against the economics of development — what can actually be financed, constructed, and occupied by the range of people a community wants to serve.
Be legally sound. Every standard needs to be defensible, consistent with state law, clear in its intent, and written in a way that leaves minimal room for arbitrary interpretation. Vague standards invite litigation. Redundant standards invite contradiction.
Adapt over time. The city a code is written for will change. Technology will change. Climate will change. Demographics will change. A code that cannot adapt becomes an obstacle — requiring constant variance, exception, and amendment to accommodate a reality it was not designed to serve.

The Shock Test

We did not develop our approach to zoning in a stable environment. The city we worked in, one of the most politically dynamic in the country, did not cooperate with the orderly assumptions of conventional zoning practice.

A global pandemic emptied offices, collapsed transit ridership, and accelerated housing demand in some neighborhoods while abandoning commercial space in others — revealing how many zoning codes were built around assumptions about how cities work that turned out to be fragile. Deepening housing unaffordability created mounting pressure to produce more units, faster, in more places. Wildfire — not as an abstract risk but as a lived reality — reshaped what it meant to plan for hillside development. Political volatility created pressure to use the zoning code as an instrument for resolving conflicts it was never designed to resolve.

These pressures did not break our approach to zoning. They refined it. They clarified what a code needs to be if it is going to hold up under pressure, and what needs to change when the world it was written for has changed.

The Modular System

Conventional zoning codes organize regulation around zones: R1, C2, M1. Each zone bundles together use permissions, density standards, setback requirements, height limits, and design standards into a single, indivisible package.

The problem with bundling is that it forecloses nuance. If you want to allow a different use mix on one block than another within the same zone, you need a new zone, a specific plan, an overlay, or a variance. Over time, the code accumulates until it becomes an artifact of its own history.

The modular system takes the bundle apart. Rather than organizing regulation around a single zone, we organize it around distinct regulatory components — each addressing a specific dimension of how a place functions:

Context Zone: The functional and physical character of the area: urban core, neighborhood corridor, residential edge, hillside, greenway-adjacent.
Form Standards: Building height, massing, footprint, lot coverage, and setbacks. Calibrated to the context zone and site conditions.
Frontage Standards: The relationship between building and street: active ground floor, stoopline, garage setback, landscaped transition.
Use Standards: What activities are permitted, conditionally permitted, or prohibited. Calibrated to context rather than applied uniformly.
Density Standards: Floor area ratios, unit counts, and employment density thresholds. Calibrated to transit connectivity and infrastructure capacity.

Each component can be adjusted independently. The modularity is what makes the system simultaneously specific and flexible: specific because each component is calibrated to context, flexible because the components can be combined and recombined to address conditions that a conventional bundled zone cannot accommodate.

The philosophy that underlies our approach to zoning is rigor with flexibility. Rigor means standards that are objective, legally sound, tested against buildability, and connected to explicit policy intent. Standards that mean something and can be applied consistently. Flexibility means a modular architecture that allows the code to address complexity without creating it.

A code built on these principles should be responsive to the conditions of its moment — the housing crisis, the climate imperative, the equity demands that communities are making of their regulatory systems — while being written in a way that allows it to evolve as those conditions change. The city will keep changing. The code needs to be built for that.

A zoning code built on these principles produces something that conventional codes rarely achieve: trust. Trust from property owners, who can understand what is allowed on their land. Trust from builders, who can design to objective standards. Trust from community members, who can read the code and see their values reflected in it. Trust from city staff, who can administer the code consistently. Trust from decision-makers, who can apply the code's intent without feeling that every decision is a political negotiation.

That trust is not a soft outcome. It is the condition under which good planning actually happens — where the regulatory system becomes a tool for building the community's vision rather than an obstacle to it.

This is what it means for a code to fit the place it governs. And it is what the Shared City requires: a regulatory system built with the same rigor, flexibility, and contextual intelligence that our analysis brings to every scale of the work. A code that reflects the place. A place that can trust its code.