How Town Planning Works | TPW-0123 — The Zoning Code Rewrite: How a City Rebuilds the Rulebook Without Breaking Every Existing Parcel, Permit and Plan

Series ID: TPW-0123

A zoning code usually does not become complicated in one dramatic moment.

It becomes complicated politely.

A parking amendment is added because one corridor has a problem. A new housing type is inserted because state law changes. A sign rule is patched after litigation. A flood standard is copied into a special section. A design district is added. A transit overlay is created. A definition is revised in one chapter but not another. A new use appears that nobody imagined when the original code was written. A variance becomes so common that staff begin treating it as routine. A plan changes, but the zoning map does not. A development-review checklist grows until applicants need a consultant merely to know which document controls.

Ten years later, every amendment may be individually defensible and the code as a whole may still be difficult to use.

This is regulatory sediment.

A zoning code rewrite is the deliberate attempt to remove that sediment and rebuild the operating system of land-use regulation so that plans, maps, definitions, standards, procedures, graphics and administrative responsibilities work together again.

The topic is not theoretical. In 2026, cities across North America were actively commissioning major code rewrites and development-review reforms. Ann Arbor paired a new comprehensive plan with a rewrite of its Unified Development Code and a development-review improvement report. Burnaby brought a new zoning bylaw into effect on 1 July 2026 after its first comprehensive rewrite in more than sixty years. Oakley, Evanston, Olathe, Wheaton and other jurisdictions were also seeking code-modernisation work during the year. The common signal is clear: many cities have reached the point where patching individual provisions is no longer enough.

The reader job: know when amendment has become system debt

This article has one specific job: explain how a city can rewrite a zoning or land-development code without losing lawful continuity, creating accidental development rights, freezing useful existing places or producing a beautiful new document that staff cannot administer.

Several neighbouring articles already own individual mechanisms. Zoning and Compatibility owns the broad question of which uses belong together. The Plan Stack owns the hierarchy between plans and development control. The Objective Code owns measurable development standards. The Form-Based Code owns one alternative organising logic. The Zoning Interpretation owns how administrators resolve ambiguity under the law that already exists.

The Zoning Code Rewrite owns a different question: when the entire rulebook has become harder to use than the planning problems it is supposed to solve, how do you rebuild the system without losing everything that still works?

A rewrite is not a giant copy-edit

Some communities begin code reform by correcting spelling, consolidating definitions and improving formatting.

Those tasks matter. They are not a rewrite.

A genuine rewrite asks whether the code’s structure still matches the plan, the market, the built environment, current law and the staff capacity available to administer it.

That means the project may change district families, permitted uses, housing types, lot standards, parking rules, review procedures, definitions, approval thresholds, overlay systems, mapping conventions, graphics and administrative delegation. It may repeal districts that no longer serve a distinct purpose. It may replace discretionary approval with objective standards. It may move technical standards out of zoning into engineering manuals. It may merge separate ordinances into a unified development code.

The document becomes shorter only if the underlying regulatory system becomes simpler.

The rewrite begins with a forensic audit, not a blank page

The old code contains institutional memory.

Some awkward clause may exist because a court struck down an earlier version. A strange setback may protect a utility corridor. A special use category may reflect a historic conflict between homes and a working industrial district. A procedural step may have been added after a public scandal or infrastructure failure.

Deleting rules because they look old can recreate the problem that made the rules appear.

The first stage should therefore be forensic. For each major part of the code, ask:

What planning problem was this rule trying to solve?
Does the problem still exist?
Is zoning still the correct instrument?
Is the rule legally necessary?
Does it duplicate another code?
How often is it used?
How often is relief requested?
Does staff interpret it consistently?
Does the rule produce the physical result the plan wants?
Does the market avoid otherwise desirable projects because compliance is impractical?
Does the rule create inequitable burdens on small projects or particular neighbourhoods?

A rewrite should understand the old machine before disassembling it.

The comprehensive plan should be the policy owner

A zoning rewrite should not become a second comprehensive plan negotiated through technical tables.

The plan should already establish the large policy choices: where growth should go, what housing range is needed, which employment areas matter, how centres and corridors should function, which environmental assets require protection, what transport pattern is desired, how infrastructure should be sequenced and which resilience goals matter.

The code then translates those policy choices into legally administrable rules.

This distinction matters because zoning is powerful. If the rewrite invents major policy changes without plan-level deliberation, technical drafting can quietly become policy-making.

Ann Arbor’s 2026 procurement demonstrates the cleaner sequence: a new comprehensive plan establishes the long-term growth vision; the Unified Development Code rewrite is then tasked with implementing that vision. Burnaby similarly coordinated its new zoning bylaw with the Burnaby 2050 Official Community Plan and provincial housing changes.

But the plan can also be too vague to code

A plan may say “create vibrant mixed-use neighbourhoods” without defining intensity, street role, housing capacity, transition or infrastructure assumptions.

The code team then discovers that the plan is not specific enough to support a zoning map.

This is not a reason to let drafters invent policy silently. It is a reason to create a policy-resolution process during the rewrite. Where the code requires a decision the plan did not make, identify it explicitly, return it to the appropriate policy body, document the choice and then code the result.

A rewrite should expose policy gaps, not hide them in definitions.

Start with the zoning map and the text together

Some code projects rewrite the text first and leave the map for later.

That can be dangerous because district language and mapped geography are one system.

A district that sounds sensible in the abstract may produce strange outcomes once applied to thousands of real parcels. A new high-density district may land on shallow lots that cannot physically achieve the intended form. A mixed-use district may be mapped across functioning industrial land. A conservation district may include ordinary blocks that do not share the characteristics the standards assume.

Map and text should iterate together.

District proliferation is a symptom worth testing

Many older codes contain a long staircase of districts: R-1A, R-1B, R-1C, R-2, R-2A, R-3, C-1, C-1A, C-2, C-3, M-1, M-2 and numerous special districts.

Some distinctions are meaningful. Others differ by one number in one table.

Every district creates administrative cost. Staff must explain it, map it, maintain it and manage transitions to adjacent districts. Applicants may seek rezonings simply to move one step up the staircase.

During a rewrite, compare district purpose before comparing standards. If two districts have the same planning job and nearly the same development form, they may not need to remain separate.

Consolidation can reduce rezoning pressure and make the zoning map easier to read.

Use tables should be rebuilt around real activities

Older codes often contain use names that no longer match contemporary business models.

What is a data centre? A fulfilment facility? A cloud kitchen? A co-working space? A microbrewery with food service? A research laboratory with light production? A childcare centre inside an office building? A live-work unit? A maker space?

If staff repeatedly force new activities into old categories, the rewrite should update the taxonomy.

But adding a new category for every business trend creates another problem. The stronger approach often defines broad use groups by measurable land-use effects—traffic, noise, hazardous material, operating hours, customer turnover, outdoor storage or residential sensitivity—then identifies examples without making the examples exhaustive.

Definitions are infrastructure

Definitions look boring until two departments use the same word differently.

“Floor area,” “lot,” “frontage,” “height,” “story,” “dwelling unit,” “family,” “gross area,” “habitable space,” “accessory use,” “major development” and “alteration” can determine millions of dollars of development capacity.

The rewrite should create one definition owner for each technical concept. If building code, subdivision regulations and zoning use different definitions intentionally, state why. If the difference is accidental, reconcile it.

Do not define the same term differently in three chapters unless the differences are necessary and obvious.

Graphics should carry legal meaning carefully

Modern codes use diagrams because diagrams can explain setbacks, frontage, height, parking placement and measurement far faster than prose.

But every graphic must have a declared legal status.

Is it binding? Illustrative? An example of one compliant configuration? A measurement convention?

If the drawing and text disagree, which controls?

A code rewrite is the moment to eliminate decorative diagrams that imply requirements the ordinance does not actually contain.

The dimensional table should describe an achievable building

A code can allow a floor-area ratio, height and lot coverage that cannot physically coexist once setbacks, parking, fire access, stormwater and open-space requirements are applied.

This is one of the most common hidden failures in development regulation: nominal capacity and buildable capacity diverge.

The rewrite should test representative parcels in three dimensions. For each district, create several ordinary lot types and ask whether the intended development can actually fit.

The existing Floor Area Ratio article explains why one capacity number does not decide building shape. A rewrite should ensure all the other controls do not quietly erase the capacity the plan intended.

Real-parcel testing is regulatory unit testing

Software engineers test code before deployment.

Planning codes deserve the same discipline.

Select corner lots, narrow lots, deep lots, irregular lots, sloping parcels, small commercial sites, existing apartment buildings, industrial properties, heritage buildings and parcels near district boundaries. Run the proposed standards as though a real application had arrived.

Where does interpretation become necessary? Which combinations fail? Which standards duplicate another department? Which parcels become unexpectedly nonconforming?

The purpose is not to eliminate every exception. It is to discover systematic failures before thousands of parcels inherit them.

Every common variance is feedback

A variance should address unusual hardship.

If eighty per cent of applicants need relief from the same setback, parking rule or sign standard, the hardship is no longer unusual.

Variance data should be one of the rewrite team’s most valuable datasets.

Map variance requests by topic and district. Calculate approval rates. Read the findings. Interview staff and applicants. If a rule routinely produces successful variances, either the standard is wrong, the district is mapped badly or the approval pathway is mismatched to the planning issue.

A rewrite can move routine relief into objective flexibility and restore the variance process to genuinely exceptional cases.

Conditional use should not become ordinary use by habit

The same logic applies to conditional or special uses.

If a use is approved almost every time with the same conditions, ask whether it should become permitted by right subject to those objective standards.

If it is frequently denied because impacts vary dramatically by site, the discretionary pathway may still be appropriate.

The existing Conditional Use Permit article owns the mechanics of that decision. The rewrite should decide which uses actually belong in that lane.

Parking reform should be tied to the transport plan

Parking standards are often among the oldest and most consequential parts of a code.

A rewrite should not simply lower or remove ratios because parking reform is fashionable. It should examine location, transit access, curb management, shared parking, housing cost, disability access, freight, pickup and delivery and the desired street pattern.

Where minimums are removed, the city may need stronger curb and loading management. Where parking remains required, ratios should reflect actual demand rather than inherited convention.

The Parking Equation becomes an input to code architecture, not a standalone table update.

Housing reform needs more than adding one new use

A city may legalise duplexes while leaving lot coverage, setbacks, parking and floor area calibrated only for detached houses.

The new housing type becomes legal on paper and infeasible in practice.

Modern housing reform therefore needs a bundle test: use permission, lot geometry, building envelope, parking, access, subdivision, utilities, fire code, ownership form and approval procedure.

Current 2026 state-level housing reforms in the United States provide a live example of why this matters. Higher-level laws increasingly require local jurisdictions to allow ADUs, multiple units per lot or housing in places previously restricted to nonresidential uses. A local code rewrite must implement those requirements coherently rather than inserting one statutory sentence into an old system.

State or national law should be treated as a moving dependency

A code rewrite can take two years.

Higher-level law can change during those two years.

The project should therefore maintain a legal-change register. Which enacted laws are not yet effective? Which regulations are pending? Which court decisions affect definitions, notice, housing, signs, religious uses, telecommunications or takings? Which requirements have implementation deadlines?

The draft should be tested against both current law and known future effective dates.

A code adopted already obsolete is a failed implementation project.

Nonconformities are the transition layer between old and new

A major rewrite will create nonconforming lots, structures and uses even if no one on the ground changes anything.

That is inevitable.

The important question is what lawful existing owners may do next.

Can a building be maintained? Expanded? Rebuilt after disaster? Change tenants? Change from one nonconforming use to another? Add accessibility improvements? Add energy upgrades? Add housing units?

The rewrite should make those answers explicit. The existing Nonconforming Use article explains the mechanism in detail.

Do not accidentally make the best existing neighbourhood illegal

A powerful code audit is to test beloved existing places against the proposed rules.

Can the main street that everyone praises be rebuilt under the new code? Can its narrow shopfronts, mixed uses, small lots and limited parking comply? Can the historic apartment blocks? Can the corner shops? Can the courtyard houses?

If the answer is no, the city should know why.

Sometimes the old place contains conditions that should not be repeated. But often the mismatch reveals that the code celebrates one urban pattern in policy while regulating another in law.

Overlay districts should be audited for regulatory sediment

Overlays often begin as surgical fixes.

Over time, they can become a shadow code layered over the base map.

During a rewrite, list every overlay, its purpose, geography, adoption date and active standards. Ask whether the issue remains spatially selective. If a rule now applies almost everywhere, perhaps it belongs in the base code. If multiple overlays regulate the same subject, they may need consolidation.

The Overlay Zone article provides the full audit logic.

A unified development code can reduce document fragmentation

Some jurisdictions regulate zoning, subdivision, signs, landscaping, parking and development procedure in separate ordinances adopted decades apart.

A unified development code can bring related land-development rules into one architecture.

The advantage is not merely convenience. Definitions can be shared. Procedures can use one decision hierarchy. Cross-references can be reduced. Applicants can see the whole development path in one system.

But unification should not drag every technical manual into zoning. Street specifications, engineering details and construction standards may still belong in specialised documents maintained by the departments that own them.

Code architecture should follow reader jobs

Many codes are organised around the history of how they were drafted.

A modern rewrite can organise around the questions users actually ask:

What is my zoning?
What can I do here?
How much can I build?
What site and building standards apply?
Is there an overlay?
What approval do I need?
Who decides?
What drawings and studies are required?
How do I appeal?
What happens if my building is already nonconforming?

The ordinance should allow a user to move through those questions without decoding the organisational chart of city hall.

The development-review matrix should be written before the procedures chapter

List every application type and identify the decision-maker, required notice, hearing, findings, appeal route, review time target and whether the decision is administrative or discretionary.

Then look for anomalies.

Why does a minor sign adjustment require a board hearing while a much larger site plan is administrative? Why do three application types use different notice periods for no clear reason? Why does one department approve a feature another department later rejects?

The matrix reveals procedural complexity that prose can hide.

Decision authority should match the amount of judgment required

If the code contains objective standards and the application either complies or does not, staff can usually administer the decision.

If the decision requires balancing competing policy values or applying broad findings, a board or elected body may have a legitimate role.

A rewrite should not send routine compliance to political hearings merely because that is how the old code evolved.

Nor should it delegate genuinely legislative choices to staff without clear standards.

Findings should be written so evidence can answer them

“The proposal is compatible with the neighbourhood” sounds useful until two reasonable people disagree.

What does compatibility mean? Height? Noise? Traffic? Building placement? Operating hours? Transition? Public realm?

The rewrite should narrow discretionary findings enough that applicants know what evidence matters and decision-makers can explain why the record supports the result.

Vague findings do not create flexibility. They create unbounded interpretation.

Pre-application review should solve uncertainty, not create a second approval system

Many cities offer pre-application meetings.

These can be extremely valuable when multiple departments identify issues early. They become problematic when applicants receive informal promises that later reviewers do not honour or when pre-application advice becomes effectively mandatory but is not governed by clear service standards.

A rewrite should state what pre-application advice can and cannot bind, which departments participate, what information the applicant must provide and how written advice is recorded.

Completeness review is a hidden source of delay

An application cannot be reviewed if essential information is missing.

But completeness can become a loop where one department requests new information after another department has already declared the application complete.

The rewrite should standardise submittal requirements, create one completeness decision where law permits, distinguish mandatory information from review comments and ensure checklists correspond to actual code requirements.

Applicants should not be required to submit studies because “we usually ask for this.” The requirement should have an owner.

Technical manuals need version control

Modern development regulation often relies on manuals for streets, stormwater, landscaping, lighting or design.

If those manuals can change administratively while the zoning code remains fixed, the system needs version control.

Which version applies to an application already filed? Where is the effective date? Who can amend the manual? Is public notice required? Does the manual contain standards that should legally be in the ordinance?

A rewrite should not simplify the code by moving complexity into documents nobody can find.

Cross-department conflicts should be treated as code defects

The planning code may encourage narrow streets while the fire standard requires wide turning geometry. The landscape code may require trees where utilities prohibit planting. The zoning code may require active frontage while loading standards demand large service openings on the same street.

Applicants often discover these contradictions after design has begun.

The rewrite team should run interdisciplinary block tests with planning, fire, utilities, transport, stormwater, building, accessibility and public works staff. The goal is not to make every department abandon its mission. It is to resolve conflicts before they reach the permit counter.

Digital readiness changes how rules should be written

A code designed only for a printed book can hide relationships in prose.

A code designed for digital use benefits from explicit structure: one parcel has one base zone, perhaps several overlays, a defined set of dimensional standards, a list of permitted uses, a decision pathway and linked definitions.

This structure makes it easier to build parcel lookups, application checklists and automated validation for simple objective rules.

Digital readiness does not mean turning planning judgment over to software. It means writing the objective parts clearly enough that software can assemble them and leaving human judgment where judgment is genuinely required.

Machine readability exposes ambiguous drafting

A human planner may understand that “generally” means one thing in practice and another phrase is treated as advisory.

A machine cannot infer institutional folklore safely.

When a code team tries to represent standards as structured data, vague relationships become obvious. Is this requirement mandatory? Does it apply to all uses or only new buildings? Which district inherits which standard? What happens if an overlay conflicts with the base zone?

Even if a city never automates review, machine-readability testing can improve human readability.

Accessibility should be tested as a user experience

A code can be legally precise and practically inaccessible.

Can a homeowner find the rule for an accessory structure without reading 600 pages? Can a small business learn whether a use is allowed? Can a resident understand what a proposed rezoning changes? Can a person using a screen reader navigate the online tables?

Code usability affects equity because complexity transfers advantage to people who can afford specialist help.

Plain language should not remove legal precision

“Write simply” is good advice until necessary distinctions disappear.

The goal is not casual language. The goal is clear legal language.

Shorter sentences help. Defined terms help. Tables help. Graphics help. Active voice helps. But a legally important condition still needs to be stated precisely.

A rewrite should remove unnecessary complexity, not necessary meaning.

Public engagement should focus on choices, not page-by-page drafting

Asking residents to comment on 700 pages of draft ordinance is not meaningful engagement.

Engagement works better when organised around decisions: Should small apartments be allowed on these corridors? Should parking minimums remain? How should building height transition near lower-scale housing? Which industrial areas should be protected? How should flood risk change development standards?

Once policy choices are understood, technical drafting can translate them into code.

Draft sections should still be public. The engagement architecture should recognise that not every resident wants to become a zoning lawyer to express a planning preference.

Use before-and-after parcel examples

The public often struggles to understand what a table change means.

Show representative parcels.

Under the old code, this lot allows one detached house with a large setback. Under the proposed code, it could also support a duplex or fourplex inside a similar building envelope. Under the old commercial district, housing is prohibited. Under the new mixed-use district, housing is allowed above shops. Under the old parking rule, twelve spaces are required. Under the proposed rule, parking is market-determined near transit.

Examples make policy visible without pretending every parcel will build to the maximum.

Capacity modelling should accompany major map changes

If thousands of parcels gain development capacity, what is the theoretical build-out? What is a more realistic market build-out? Where would infrastructure pressure appear? Which areas have school, sewer, water or transport constraints?

The code rewrite should not assume that zoning capacity becomes construction immediately. It should still understand the order of magnitude created by the new map.

This connects directly to The Concurrency Test. Land-use rights and infrastructure capacity must eventually meet in the same town.

Housing feasibility should be tested, not assumed

A rewrite can legalise more housing while making construction more expensive through design, open-space, parking or material requirements.

Run prototype projects. Test common lot sizes. Estimate how many units fit under the full stack of standards. Ask developers, housing providers, architects and lenders where the scheme becomes unfinanceable.

Feasibility analysis should not dictate all planning policy. It should reveal when the city believes it has legalised a housing type that the code still makes nearly impossible to build.

Small builders need different attention from megaprojects

Large developers can hire planning lawyers, traffic engineers and entitlement teams.

A homeowner adding an accessory dwelling unit cannot.

Code complexity therefore has a distributional effect.

For common small projects, create standard pathways, diagrams, permit-ready options or simple objective rules where appropriate. Reserve complex discretionary review for projects that genuinely create complex effects.

Legal review should happen throughout, not at the end

Sending a finished 700-page draft to counsel two weeks before adoption is not legal quality control.

Lawyers should review structure, delegation, notice, findings, vested rights, nonconformities, signs, telecommunications, fair-housing implications, religious-land-use issues, takings risk and procedural requirements as the relevant sections are built.

Legal review is strongest when it helps design the system, not merely mark up the final wording.

Do not let legal fear produce unusable language

The opposite failure is a code written entirely as defensive legal prose.

A rule can be legally cautious and still impossible for ordinary users to understand.

The code team should include planners, legal counsel, administrators and actual users. Precision and usability are not opposing values when drafting is good.

The adoption ordinance needs a transition plan

On the effective date, real applications will already be in process.

Which code applies to applications filed yesterday? What about a project with zoning approval but no building permit? What about phased developments? What about expired approvals? Can an applicant elect to use the new code?

Transition provisions should be drafted before adoption, not improvised afterward.

The existing Entitlement Clock provides the logic for expiration and vesting questions.

Staff training is part of the law becoming real

A code is not implemented when council adopts it.

It is implemented when permit technicians, planners, engineers, inspectors, lawyers and applicants begin making thousands of small decisions under it.

Training should use real applications. Ask staff to process a home addition, a mixed-use building, an industrial expansion, a subdivision, a nonconforming use and a variance under the new system.

If experienced staff reach different answers, the code is not ready.

Applicant training matters too

Architects, engineers, surveyors, builders and planning consultants carry operational knowledge into the system.

Publish crosswalks from old districts to new districts. Provide redlines. Create worked examples. Hold technical workshops. Explain new submission standards and decision pathways.

Confusion during transition is not proof that the old code was better. It is a reason to manage change intentionally.

The first year should be treated as a calibration period

No rewrite survives first contact with reality perfectly.

Track questions, interpretations, failed applications, recurring variances, unexpected nonconformities and sections that require repeated legal advice.

Create a public correction log. Distinguish clerical fixes from policy amendments. Bundle noncontroversial technical corrections rather than waiting years for the code to accumulate a new sediment layer.

Interpretation logs should become maintenance data

Every formal zoning interpretation reveals a place where the code did not produce one obvious answer.

Some ambiguity is unavoidable. Repeated ambiguity is a maintenance problem.

Maintain an interpretation register and review it annually. If the same question appears repeatedly, amend the text rather than requiring every future applicant to discover the same interpretation.

Appeals reveal where administrative trust is weak

A high appeal rate can mean many things: unclear code, controversial policy, inconsistent staff interpretation or a review body willing to substitute its judgment routinely.

The rewrite should examine appeal topics, not merely outcomes.

The Zoning Appeal article explains why the administrative record and standard of review matter. Rewrite data should use those appeals as diagnostic evidence.

Enforcement should be rewritten alongside permissions

A regulation that cannot be observed or enforced should be questioned.

If a condition requires a certain operating practice, who checks it after occupancy? If landscape must remain, who inspects it five years later? If affordable units are required, where is the compliance record? If outdoor storage is limited, what evidence proves a violation?

The rewrite should align standards with monitoring capacity.

Do not write more conditions than the city can remember

Project-specific conditions accumulate across decades.

A future owner may not know they exist. Staff may not know where the old approval file is. Digital permit systems may not link conditions to the parcel.

Where a condition is common, convert it into a standard. Where project-specific conditions remain necessary, record them in a parcel-facing system that survives staff turnover.

Performance standards can replace some use-list anxiety

Some land-use conflicts are better regulated by effects than labels.

Noise, vibration, glare, emissions, truck activity, outdoor storage and operating hours can often be measured or bounded directly.

APA has long identified performance zoning as one of the major zoning-system families, and current 2026 code-rewrite procurements continue to request performance-based standards where they can encourage desired development while avoiding impractical prohibitions.

A rewrite need not become a pure performance code. It can use performance standards selectively where they solve a problem more directly than a long list of prohibited uses.

Form standards should be used where form is the public problem

If the planning objective is active frontage, building placement, street enclosure or parking location, regulate those things.

Do not rely on use categories to produce a physical form indirectly.

Many modern codes are hybrid for this reason: conventional use controls where compatibility matters, form standards where public-realm outcomes matter, performance standards where measurable external effects matter.

The rewrite should choose tools by planning job rather than ideological purity.

The code should know which rule owns which problem

Noise can be regulated by zoning, nuisance law, environmental rules or operating permits.

Building energy can be addressed through zoning incentives or energy code. Stormwater can be in zoning, engineering standards or environmental ordinances.

Duplication creates conflict.

During a rewrite, assign each major regulatory outcome an owner. If another ordinance already controls the problem effectively, zoning may only need a cross-reference or site-planning interface.

A code crosswalk protects institutional memory

Create a table mapping every old section to its new destination: retained, revised, merged, moved or repealed.

This crosswalk helps lawyers, staff, applicants and courts understand continuity.

It also prevents accidental loss. If an old environmental standard has no new destination, the team must decide whether it was intentionally repealed or simply forgotten.

A map crosswalk matters just as much

When districts are consolidated or renamed, every parcel needs a defensible mapping logic.

Do not rely on automatic one-to-one conversion if the new district has materially different purpose or capacity.

Map changes should be based on the adopted plan, parcel context, existing development, infrastructure and intended future form.

The map is where abstract policy becomes property-specific.

Parcel-level quality control is essential before adoption

Run automated checks where possible.

Parcels with no zone.
Parcels with overlapping base zones.
Isolated tiny zoning polygons.
District boundaries that split buildings unexpectedly.
Parcels newly made nonconforming.
Large capacity increases near known infrastructure constraints.
Mapping changes inconsistent with the future land-use map.
Overlay boundaries that no longer match source datasets.

A zoning map can look correct at city scale and contain hundreds of parcel-scale errors.

The city should model administrative workload under the new system

A rewrite can simplify rules while accidentally increasing workload.

For example, more flexible mixed-use zoning may reduce rezoning applications but increase site-plan reviews. Removing parking minimums may reduce variance hearings but increase curb-management work. Replacing design discretion with detailed objective standards may require more technical plan checking.

Estimate application volumes, staff hours and specialist skills before adoption. A code that needs twice the review capacity the department possesses will not perform as drafted.

Planning fees and code complexity are connected

Review cost is partly a function of application complexity and code clarity.

If every application requires repeated interpretation and interdepartmental negotiation, planning service costs rise.

Current 2026 fee reforms in England explicitly connect planning authority resources, service standards and timely decision-making. A code rewrite that reduces unnecessary review steps can therefore improve both applicant cost and public administrative capacity.

Adoption is a migration, not a publication event

Think of the new code as a software migration.

Data must move. Old parcel records must connect to new zones. Forms must be updated. Websites must change. Staff training must happen. Fee schedules may need revision. Application portals must use new categories. Templates, checklists and decision letters must match the new law.

If the city publishes the ordinance and leaves every operational system unchanged, applicants will experience two codes at once: the legal one and the administrative one.

A rewrite should include a decommission plan for obsolete material

Old webpages, PDFs, application forms and staff handouts can remain online for years.

Search engines continue sending users to them.

Archive old material clearly. Redirect old code links where possible. Stamp superseded guidance with effective dates. Maintain historical copies for legal research without allowing them to masquerade as current rules.

Maintenance should be designed before the new sediment starts

Every code will need amendments.

The goal is not to freeze the new document. It is to prevent amendment from recreating fragmentation.

Establish a maintenance protocol: annual technical amendments, periodic policy updates, interpretation review, legal-change monitoring, map correction procedures and version control. Require amendments to identify which definitions, tables, diagrams and cross-references they affect.

A rewrite is successful when the code remains coherent five years later.

Worked example: a city with 47 districts and 31 overlays

Imagine a city whose zoning code began in 1965.

It now contains 47 base districts, 31 overlays, separate sign and subdivision ordinances, parking ratios copied from a 1980 manual, three different definitions of floor area and a design-review process created through a series of policy memos.

The comprehensive plan calls for more housing near transit, preservation of productive industrial land, reduced car dependence and faster infill approval.

The rewrite team begins by inventorying every district and overlay. Twenty base districts have nearly identical purposes and are consolidated into eleven. Four overlays whose standards now apply citywide are moved into the base code. Six obsolete overlays are repealed. The remaining overlays are redrawn from current hazard and heritage datasets.

The use table is rebuilt around broader activity groups with performance standards for noise, outdoor storage and truck activity. Transit districts remove parking minimums and add frontage standards. Industrial districts retain stronger use controls to protect production. Missing-middle housing types become permitted in several residential districts, and dimensional standards are recalibrated so the new types actually fit ordinary lots.

Site-plan review becomes administrative when projects comply with objective standards. Conditional uses are reduced to activities whose impacts genuinely vary by site. Variance data is used to rewrite standards that previously generated routine relief.

Before adoption, the team runs 150 parcel tests and discovers that a proposed rear setback makes courtyard housing infeasible on shallow lots. The rule is corrected. A map audit finds 73 parcels split by new district boundaries and fixes 68 mapping errors before public hearing.

After adoption, the city tracks interpretations and variances for twelve months. Technical amendments fix ambiguous height measurement and an unintended parking rule for childcare centres.

The result is not a perfect code. It is a code with a maintenance system.

A zoning code rewrite audit

Policy owner: Which adopted plan decisions is the rewrite implementing?
Legal inventory: Which higher-level laws and cases constrain the code?
District purpose: Does every district have a distinct planning job?
Map integrity: Does each parcel receive the intended district?
Overlay audit: Are overlays still necessary, current and non-duplicative?
Use taxonomy: Do categories describe current activities without over-specialising?
Definitions: Are important terms singular, precise and coordinated across codes?
Capacity: Do dimensional standards allow the development intensity the plan intends?
Parcel testing: Have real lot types been used to test the draft?
Variance data: Which standards repeatedly need relief?
Conditional uses: Which discretionary approvals have become routine?
Form: Are public-realm outcomes regulated directly where they matter?
Performance: Can measurable impacts replace some use-list restrictions?
Parking: Do standards match transport and curb policy?
Housing: Are newly legal housing types physically and procedurally feasible?
Nonconformities: What happens to lawful existing uses, lots and structures?
Procedures: Is each application assigned to the right decision-maker?
Findings: Can evidence actually answer discretionary criteria?
Completeness: Are application requirements standardised and code-based?
Cross-department rules: Have fire, utilities, streets, drainage and zoning been tested together?
Digital readiness: Can parcel rules be assembled from structured data?
Accessibility: Can non-experts find the rules that apply to common projects?
Legal review: Is counsel involved throughout the drafting process?
Public engagement: Are residents asked about policy choices rather than technical minutiae?
Feasibility: Have representative development prototypes been tested financially and geometrically?
Workload: Can the planning department administer the new system with available staff?
Transition: Which rules apply to pending and vested projects on the effective date?
Training: Have staff and regular applicants processed sample applications under the new code?
Crosswalk: Can every old section and district be traced to a deliberate new outcome?
Maintenance: Is there an annual process for corrections, interpretations and legal updates?

The rewrite is successful when the city can stop explaining the code with folklore

Old codes accumulate oral tradition.

“We never apply that section.”

“That table means something different from what it says.”

“Ask Maria; she knows how we interpret that frontage rule.”

“Technically it requires a variance, but the board always approves those.”

Those sentences are signs that the actual planning system has drifted away from the written one.

A strong rewrite closes that gap.

It turns policy into clear districts. It makes the map and text agree. It gives each rule an owner. It converts routine exceptions into ordinary standards. It protects lawful continuity. It tests the new system on real parcels. It aligns procedure with the amount of judgment required. It creates digital and human readability. It includes the staff who will administer it. It plans for correction after adoption.

A zoning code is not finished when it is elegantly written. It is finished when different people can use it repeatedly and reach the same lawful answer without needing to know the history of every patch that came before.