Two ways to write the rules
Conventional zoning starts with use. A district is labeled residential, commercial or industrial, and the code lists which activities are allowed in each, with size limits added on top. The main question it asks is “what will happen here?”
A form-based code starts with physical form. It focuses on what the building and street look like and how they relate to each other: building height, how close a facade sits to the sidewalk, where the front door goes, how much of the ground floor is windows, and how parking is handled. The main question it asks is “what will this place feel like?” Use is still regulated, but usually in a looser, simpler way.
Neither is purely one thing. Most conventional codes include dimensional rules, and most form-based codes include some use rules. The difference lies in which approach organizes the code and where the detail goes.
What a form-based code typically contains
Details differ, but common elements include:
- A regulating plan. This map assigns each street or block to a category based on its desired character rather than its use. The categories might range from rural-feeling edges to dense urban cores, an idea sometimes organized as a “transect.”
- Building form standards. For each category, standards set the build-to line, height range in stories, width, and how tall the ground floor should be.
- Frontage types. These describe how a building meets the street, such as a stoop, porch, shopfront or forecourt, and which types are allowed in each category.
- Street standards. Lane widths, sidewalk widths and tree spacing are specified so private buildings and the public street work as a whole.
- Building types. Some codes define permitted types, such as a courtyard building or a small apartment house, and describe their shape.
- Illustrations. Diagrams are central. Many form-based codes use more drawings and fewer paragraphs than a traditional code.
A side-by-side thought experiment
Imagine a corridor with a mix of older shops, small houses and a low apartment building. Under a conventional code, this corridor might be divided into a commercial strip district and a residential district. A shop could not open in the residential part, and the commercial part might require large setbacks and off-street parking in front, producing a car-oriented look even though the street was once compact.
Under a form-based code, the whole corridor might be treated as a single walkable category. The code would require buildings to sit near the sidewalk, have entrances facing the street, and stay within a height range. A building could contain homes, offices or shops, and the code would care chiefly that its shape fits the street. The result tends to feel more consistent, though the specific outcomes depend on how the code is written and what the market delivers.
Why communities choose them
- Predictable street character. Residents who care about how a block looks may prefer rules that say what a building must resemble rather than rely on use labels.
- Flexible use. Because use is regulated lightly, it is easier for a house to become an office or a shop, supporting mixed-use zoning and adaptation over time.
- Less need for discretion. Clear form standards can allow staff to approve compliant projects without lengthy hearings, which may reduce uncertainty compared with subjective design review boards.
- Walkability. Rules about building placement and frontage are often written to support walkable neighborhoods.
Limits and criticisms
Effort and cost to adopt. Writing a form-based code takes extensive survey work, mapping and public involvement, often through multi-day workshops. Smaller cities may lack the staff and budget. Hiring consultants can be expensive.
Mapping is hard. Assigning each block to a category requires judgment about its future character. Mistakes can lock in outcomes that do not suit the site.
Some use issues remain. A nuisance use, such as a noisy industrial operation, can still harm neighbors regardless of building shape. Many form-based codes retain use restrictions for exactly this reason. Industrial zoning remains largely use-based in many places.
Aesthetic specificity. Detailed frontage and building rules can feel prescriptive and, if they require particular materials or styles, can raise costs.
Not a guarantee of affordability or quality. Form-based rules do not by themselves produce affordable housing or good architecture. A code can allow modest apartments yet still see few built if financing or costs are unfavorable.
Mixed adoption. Many cities use form-based standards only in selected districts, such as downtowns or corridors, alongside conventional zoning elsewhere. That can create two systems that applicants must navigate. Some places adopt hybrid codes that blend both.
Evidence is limited. There are enthusiastic advocates and thoughtful skeptics. Rigorous comparisons of outcomes are harder to find than descriptions of intent, so claims that one approach consistently outperforms the other should be treated cautiously.
How they relate to other tools
A form-based code can take the place of a conventional district in an area, or work as an overlay on top of base zoning. It still sits under the comprehensive plan and still needs legal adoption through the usual process. Exceptions, such as variances, still exist, though a code with well-calibrated standards may need fewer of them.
Choosing between approaches
Form-based codes suit places where character and walkability are the key concerns and where mixing uses is wanted. Conventional use-based zoning suits places with strong needs to separate hazardous or disruptive activities. Many communities end up using elements of both. The better question is not which label to use, but which concerns matter most on a given street and which tool addresses them with the least complexity.