Start with the problem, not the preferred answer

“Eliminate parking minimums” is a policy option. It is not, by itself, a diagnosis. An implementation process starts by naming the condition the city is trying to improve: a vacant upper floor that cannot be reused because a new use triggers a parking ratio; an expensive multifamily project near frequent transit; a downtown where customers cannot find short-stay parking even though long-stay employee vehicles occupy the curb; or a main street where loading activity conflicts with travel lanes.

That distinction matters because different problems need different tools. A zoning minimum determines what a private project must construct off street. A curb-management program determines how publicly controlled street space is allocated. A development-code amendment may be part of the answer, but it will not replace a loading zone, a permit program, an accessible route, or good signs.

Stage 1: establish a baseline

Before drafting an ordinance, build a record of current conditions. Oregon’s Department of Land Conservation and Development advises communities to begin parking-reform work with data on existing conditions, community engagement, and options exploration; adoption can then combine development-code amendments with a parking-management plan.[2]

Use observations that match the dispute. A once-a-year count will not explain a restaurant district’s Friday-evening demand. A single downtown block will not stand in for a transit corridor. The goal is not perfect data; it is a transparent baseline that enables a before-and-after comparison.

Stage 2: separate the two systems

U.S. Department of Transportation guidance groups parking reforms across zoning changes, smart-parking tools, and repurposing strategies, while emphasizing that communities should choose approaches suited to their needs.[5] That framing helps avoid a common mistake: changing a building rule while leaving a genuine curb-management problem unanswered.

Stage 3: build the public record before the hearing

A technically sound proposal can still fail if residents and businesses only encounter it at a formal hearing. The most useful engagement happens earlier, when the city can show maps, photos, occupancy observations, the existing code language, and several credible options. Oregon’s program specifically identifies assessment, outreach, signage, wayfinding, meters, permits, parking benefit districts, and enforcement among the tools communities may consider.[2]

This is also where an agency should identify impacts that simple parking counts miss. Ask disability advocates about accessible routes and drop-off conditions. Ask delivery workers about loading windows. Ask transit riders about stop access. Ask small businesses about customer turnover rather than assuming every business wants the same rule. Engagement does not mean every request becomes code; it means the decision record reflects the people who will use the system.

Stage 4: draft the ordinance and the operating plan together

The code should say precisely what changes. Does it repeal all minimums? Cap ratios? Exempt affordable housing, small sites, mixed-use ground floors, historic buildings, or a defined geography? Does it allow shared parking? Does it remove a change-of-use trigger? The operating plan should say what happens outside the lot line: which streets receive time limits, loading zones, permits, pricing, wayfinding, or monitoring.

Washington’s 2025 law illustrates the value of specificity. It establishes limits and exemptions, preserves ADA-related accessible parking, allows temporary or time-restricted parking, and includes safety and location-based exceptions.[3] Local governments do not need to copy that policy, but they should write their own decisions with comparable clarity.

Stage 5: design accessibility and loading into the rule

Accessibility should be a design input from the beginning. Where parking or passenger-loading zones are provided, the relevant accessibility standards still apply. The U.S. Access Board explains that accessible passenger loading zones are required in particular circumstances, including where designated loading zones are provided, and that the loading area and access aisle must connect to an accessible route.[6]

That is why a complete implementation team often includes planning, transportation, public works, permitting, accessibility, and enforcement staff. Each owns a different piece of the user experience. A policy can reduce an off-street requirement and still fail if its loading zone is unusable, its accessible route is blocked, or its curb signage is unintelligible.

Stage 6: phase, communicate, and monitor

Implementation begins after adoption. The city needs staff instructions, permit-review checklists, updated zoning and map interfaces, plain-language public materials, curb signs where operations change, and a way to handle edge cases. A phased rollout can be useful when a city wants to learn in a defined district before applying a model more broadly. It should be designed as a real test, with a date, baseline, and public evaluation—not as an indefinite holding pattern.

Monitoring is not a public-relations exercise. It is what gives elected officials and the public a basis to decide whether a rule should be expanded, revised, or paired with another tool. The EPA describes flexible parking policy as a way to balance parking needs with broader community goals; the measures should therefore include the goals the city said it cared about, not only a total-space count.[1]

A practical 90-day launch sequence

The schedule will vary by jurisdiction, notice requirements, and proposal scope. What matters is that the public can see the sequence: evidence first, choices second, action third, evaluation afterward.

Implementation checklist

Bottom line

Parking reform is not complete when a council adopts new numbers in a table. It is complete when the code, curb, access plan, staff procedures, public information, and monitoring system work together. The best implementation processes are specific enough to resolve everyday questions—where can people load, who can park, what is required of a project, how will access work—and flexible enough to adapt when evidence shows a problem.

That combination lets a city move beyond the false choice between “more parking everywhere” and “no management at all.” It can right-size private requirements while actively managing public space for the people and activities that depend on it.