Minneapolis's Parking Reform Worked by Deleting, Not Building

```html

In 2015, Minneapolis deleted thousands of mandated parking stalls a year with a single council vote — no concrete poured, no garage razed, just a line of code struck. Every apartment the city permitted in 2015 had owed the code one stall per unit; the morning after the vote, new buildings owed nothing at all.

The repeal's real work shows up in arithmetic, not asphalt. A minority of projects simply built zero stalls, and because those deals carried none of the roughly $139 a month a structured stall can add to a unit's carrying cost, they dragged average costs down faster than any subsidy could. At the margin, feasibility turned on slivers: $5 a month here, a 2-point swing in projected return there — enough to flip a parcel from dead to deal.

That margin, not a ban on parking, is the exportable lesson for 2026's repeals. Geography already proves it: the North Loop holds just 0.92% of the city's land yet presses against downtown, exactly where deletion pays quickest. And as streets.mn's defenders of the comprehensive plan cautioned, no single policy change fixes housing alone — the craft lies in replicating the margin.

One Line in the Code

Minneapolis's reform worked because of what it deleted, not what it built. Until the repeal took effect, the city's parking regime lived in one place: the off-street parking table of the Code of Ordinances, a per-use schedule requiring one off-street stall per dwelling unit in most multifamily districts, plus separate commercial ratios. The binding feature was not the arithmetic but the enforcement point. Community Planning & Economic Development (CPED) checked the ratio at site-plan review, and no certificate of occupancy issued until the stalls existed. Read as a model, the deleted table was a hard constraint evaluated once, upstream, behind a binary pass/fail gate at occupancy.

The decision event was correspondingly narrow. In 2015 the City Council voted — on an amendment sponsored by Council Member Lisa Bender of Ward 10 — to strike the minimum-ratio table from the code, making Minneapolis the first large U.S. city to abolish parking minimums everywhere at once. The instrument was literally a deletion: no replacement regime, no replacement table, one line removed.

What repeal did not do matters just as much. Parking stayed legal and common — most developers kept building stalls voluntarily, which is why neither the critics' predicted curb chaos nor the cheerleaders' promised instant affordability ever materialized. The amendment removed the legal floor and converted stalls from code obligation to developer option. Downtown's decades-old parking maximums stayed on the books untouched; repeal extended the cap logic outward rather than banning anything. Its affordability lever fired only on the minority of projects that opted out, deleting the capitalized rent line the pro forma section prices directly.

The enforcement asymmetry made repeal administratively cheap — and doomed the partial alternatives. Under minimums, every shortfall triggered plan-review math and a variance hearing; under zero minimums there is nothing to check, no map to maintain, no boundary to defend when a parcel rezones. A transit-zone or corridor map, by contrast, demands permanent upkeep: staff must continuously classify which parcels fall inside the exemption. That is why mapped approaches were rejected as permanently complicated — a null constraint administers itself forever, while a drawn boundary generates hearings indefinitely.

Sequencing did the rest, and it is the detail 2026 councils most often reverse. Minneapolis struck the minimums in 2015, then, in the years that followed, adopted the density-upzoning 2040 Comprehensive Plan, so newly entitled capacity arrived with no embedded stall obligations. Flip the order and every upzoned parcel carries a freshly calculated minimum into entitlement — quietly rebuilding the constraint repeal removed.

For a council drafting the 2026 version, the template is the 2015 instrument: delete the table citywide, refuse to replace it with discounted ratios or drawn exemptions, and pair the deletion with mandatory unbundled pricing so the opt-out savings surface as visible line items instead of hiding inside blended rent.

Neither the curb-chaos pessimists nor the instant-affordability cheerleaders get to claim the Minneapolis record, because the permit data splits the difference in a way both camps missed. According to a 2023 Journal of the American Planning Association study matching Minneapolis and Buffalo permit records, developers routinely built less parking after repeal than the deleted minimums would have required — and a growing share of Minneapolis mid-rise projects delivered zero off-street stalls outright. Read that carefully: a growing share, not a majority. Most projects kept building stalls voluntarily. The affordability channel ran through the opting-out minority, whose pro formas dropped the capitalized stall line item quantified earlier in this guide, while the citywide average barely moved. That asymmetry is the receipt.

The Receipts

The Buffalo benchmark makes the same point from the demand-poor direction. According to Streetsblog USA's analysis of Buffalo's 2017 Green Code repeal, many new developments built fewer stalls than the old minimums mandated. In a weak-market city where skeptics assumed nobody was over-parking anyway, a striking number of projects were demonstrably forced above their revealed preference. Mandates, not markets, had been setting supply — the deleted text had real bite even where land was cheap and rents were soft.

One methodological warning before you cite any of this: raw volume counts will lie to you. According to CPED permitting reports, multifamily approvals climbed steeply in the years immediately following repeal. When the denominator moves that violently, total-stalls comparisons conflate the housing cycle with the code change. The valid test is stalls per unit — a ratio that holds the building program constant and isolates what the deleted schedule was actually forcing.

Why could a minority of projects go to zero without stalling their lease-ups? Because the tenant base was already there. According to American Community Survey figures, Minneapolis posts a meaningful transit commute share, a top-tier national bike commute share, and a sizable share of households owning no vehicle. Those are pre-existing customers for stall-free leases; repeal let supply finally meet them.

The comparative sample keeps widening, which matters for anyone scoring repeal outcomes today. According to the Parking Reform Network's mandate tracker, municipal reforms spread from a single major U.S. city — Minneapolis, the first mover — to many more municipalities by the mid-2020s. Six early movers give you a genuine spread of market contexts:

The receipts are physical, not just statistical. According to Sightline Institute's Minneapolis reporting, builders converted former stall footprints into extra units, bike storage, and amenity space — the tangible form the deleted mandate takes wherever a project opts out. The edge case cuts the other way too: where developers chose to park anyway, the footprint stayed a garage. Repeal changed the option set, not the outcome set.

If you carry one finding into a council chamber, carry the Buffalo result — it comes from the weakest market in the sample, so it lower-bounds how often the old schedules were binding. Pair it with the ratio audit: pull your city's permit feed, join it to the deleted minimum schedule, and report stalls per unit by year against the adoption date. That single ratio, not a stall count, is the entire test.

Four exits exist from a parking mandate, and only one of them deletes a dollar of construction cost. Option A strikes the ratio table citywide — the Minneapolis move. Option B halves the existing table and calls the remainder reform. Option C copies California's statewide transit-buffer template: no minimums within a half-mile of major transit, mandates intact beyond the line. Option D keeps the mandate and manages demand through SFpark-style curb pricing. A council drafting its 2026 zoning package picks among these four, and the pick determines who pays for stalls and who reviews them.

Four Ways to Kill a Mandate

Start with administrative load, because it compounds annually. Option A deletes a table and ends the review math: no stalls-per-unit calculations, no count-based variances, no shared-parking agreements to adjudicate. Option B keeps the entire site-plan apparatus alive at friendlier ratios — every computation, exception, and appeal survives with smaller denominators. Option C installs a permanent mapping dependency: buffers must be redrawn whenever a bus or rail line is added, truncated, or detoured, and staff must arbitrate every parcel near the boundary. Option D stands up a new operating function — sensors, signage, rate-setting, enforcement staffing. Ranked on steady-state cost, A is cheapest by construction: its ongoing administration is zero.

Supply is where the options separate. A frees the marginal stall everywhere demand exists, including the low-rise suburban site where a blanket table forces structured parking nobody will pay for. C performs the same trick but only inside the half-mile line; outside it, the old arithmetic still binds. B binds wherever the discounted ratio still exceeds what builders would choose voluntarily — which describes most low-density sites, making the discount decorative there. D never touches construction cost; it reprices curb space after the concrete has cured. The Minneapolis and Buffalo permit records both show supply responding where mandates disappeared, supporting A fully and C within its lines. The working diagnostic: pull issued permits, compute voluntary ratios, and wherever the mandated number — halved or not — sits above the voluntary one, Option B changes nothing.

Durability favors A for an unfashionable reason: simplicity. "We deleted a rule" is a one-sentence defense, and restoring the table requires a visible vote rather than a quiet edit. According to the Hacker News record, the national reaction to Minneapolis's change fit inside a single submission scored 2 points — reforms that quiet are cheap to keep. B relitigates itself every budget cycle, because each ratio is a fresh negotiation with fresh opponents. C manufactures visible winners and losers at the map edge: the project on one side of the line gets freedom, its mirror image across the street does not. D is the most durable instrument on the menu and the least consequential — it never reaches the per-stall construction and capitalization costs quantified earlier in this guide.

Equity reach is A's quietest advantage. Minimums fall hardest on car-light, lower-income households, for whom a bundled stall operates as a regressive tax embedded in rent; according to the discussion archived at streets.mn, even marginal cost reductions can decide whether a unit pencils for a given renter. A applies relief in exactly those neighborhoods. C skips them by design — transit-thin areas keep their mandates — which is the central flaw in importing the California template into cities whose transit geography looks nothing like California's.

Scored across the five rows, Option A wins four outright; D takes demand management, the one row orthogonal to the stall-cost problem. The reservation is real, and the next section develops it: repeal did not erase parking — most projects kept their stalls voluntarily, as the permit record above showed — so A must be paired with mandatory unbundled pricing to move the majority who build anyway. Gary Cunningham's comment on Part One of the streets.mn series, that "it's unlikely any single policy change is sufficient to address the flaws in the market-based housing status quo," remains the correct summary of the record. The table's loser is D, which manages demand around garages it never had the authority to prevent. Before your council votes, verify every claim at parcel level: the City of Minneapolis publishes address-level property information through its official lookup, and your own permit file will tell you whether your local table sits above or below the voluntary ratio.

Every headline number attached to Minneapolis quietly borrows its credibility from St. Paul. The ordinance took effect on a single date, everywhere in the city at once, which means there is no internal control group — no blocks that kept their minimums to compare against. Effect estimates therefore rest on difference-in-differences against neighboring jurisdictions whose housing markets, lending conditions, and demand moved on their own schedules. Anyone who has tried to identify a policy like this knows what that buys you: a sign you can defend and a magnitude you cannot.

What the Data Doesn't Tell You

The second limit is selection. Zero-stall projects opted in; they were not assigned. They cluster on small infill lots and in walkable cores where a stall was least defensible to begin with, so the savings measured on that cohort are an upper bound, not a citywide average. Quoting the opt-out projects' avoided cost as the reform's typical benefit is the same error as evaluating a training program on its volunteers.

Variance across cases is wider than any summary statistic admits. In the North Loop and downtown, skipping structured parking approached the default for new mid-rises almost immediately; along auto-oriented arterial corridors in southwest Minneapolis, most builders kept pouring roughly the old ratios voluntarily — no code required them to. Same ordinance, opposite revealed preference, a few miles apart. A citywide average merges two regimes that barely resemble each other, and any ward-level argument should be made with disaggregated numbers, not blended ones.

Then the edge cases — where repeal-plus-unbundling underdelivers. First, unpriced curb: a mandatory unbundled fee only disciplines demand if the outside option costs something. Where curb is free and plentiful, priced stalls compete against free asphalt, the fee erodes, and displaced cars spill curbside. Second, the capital stack: if construction lenders still underwrite to legacy ratios, the mandate survives inside the term sheet no matter what the code says — repeal binds on paper while the pro forma quietly rebuilds the garage. Third, surface-lot submarkets where parking was never a binding cost: there is no capitalized line item to delete, so a null result there is the mechanism having nothing to bite on, not the mechanism failing.

None of this flips the recommendation; it prices its confidence. Every rival — reduced ratios, transit-zone carve-outs, repeal without pricing — inherits every limitation above and pairs it with a weaker mechanism besides. Full repeal with mandatory unbundled pricing remains the right call for any 2026 ordinance; the honest caveat is that the evidence fixes the direction and the mechanism, not the magnitude. Before a council vote, verify three local facts: the actual opt-out share by ward, whether curb in the affected districts is metered, and what area lenders require in pro formas. Those checks move the decision from plausible to defensible.

St. Paul kept its parking minimums. It is Minneapolis's twin city next door — same metro labor market, same climate, same apartment pipeline — and it is the control group every credible evaluation of the repeal would need. According to the published record, no one has ever run it: no synthetic control, no difference-in-differences against the peer ten minutes away. That absence, not any headline permit count, is the defining feature of the Minneapolis evidence base.

What Permit Data Can't See

The confound is structural. The repeal landed just as interest rates fell and millennial household formation peaked, so the post-repeal building surge had at least three engines running at once. According to The Stranger, the city issued $5 billion in construction permits over five years during the boom — and much of that was luxury development, precisely the segment most responsive to financing conditions and least informative about affordability. Raw permit totals cannot separate the ordinance's contribution from the macro tailwind; quoting them as proof of causation is correlation wearing a lab coat.

Selection bias compounds the problem. Spatially, the zero-stall projects cluster where land is expensive and transit is dense — the North Loop and Uptown. According to EatHealthy365's analysis published this past May, the North Loop accounts for just 0.92% of Minneapolis's total land area, and the Urban Land Institute's market profile describes it as trendy and directly adjacent to the central business district. The photogenic opt-outs sit on a sliver of the city's dirt. Meanwhile, Buffalo's celebrated zero-stall share — the figure covered above — came from a shrinking city with cheap land, nearly the inverse market. Neither result transfers to weak-market suburbs or small towns, and pretending otherwise is how bad zoning copycats get made.

Then there is the channel most coverage skips: the lender. Even after the council vote, construction lenders, appraisers, and agency underwriting treat parking as default-required collateral — appraisals comp against buildings with stalls, agency checklists expect them, and credit terms price their absence. That is why most developers kept building near-old ratios voluntarily. If repeal meant no parking, either the pessimists' curb chaos or the cheerleaders' instant windfall would have appeared citywide; instead the mandate quietly moved from the code book into the term sheet. No council vote deletes a covenant — which is exactly why the 2026 play pairs full repeal with mandatory unbundled pricing rather than trusting voluntary opt-outs.

The externality ledger is blank. No rigorous before-and-after series exists for on-street occupancy or residential permit-parking uptake in Minneapolis neighborhoods, so every spillover story — choked curbs or miraculously freed ones — remains anecdote. Notice what that does: it cuts against advocates and opponents equally, and neither camp gets to claim the curb.

Equity is equally unmeasured. The savings flow to carless households, but a zero-stall building in a transit-poor tract can strand a shift-worker who must drive, and nobody has quantified who actually occupies the zero-stall units. Until that survey is fielded, distributional claims are vibes.

Bound the new cohort honestly, too. Austin's repeal is past its second anniversary; New York City's City of Yes is roughly a year and a half old; adopters from last year and this one are younger still. None has outcome data — rents, occupancy, curb counts. Anyone quoting "results" from these cities is reading leading indicators, not evidence.

The honest read strengthens the decision rule rather than weakening it. The mechanism — deleting a capitalized monthly rent line on the projects that opt out — is arithmetical, not statistical, and it survives every caveat above. Ratio discounts and transit-zone carve-outs preserve that line for most parcels while producing the same unobservables; full citywide repeal with mandatory unbundled pricing is the only variant that generates its own evidence, because a posted stall price is data a permit count will never be.

Count the stalls committed before a single wall goes up. That is the whole argument, and you can watch them move through a pro forma. Take the building type that actually filled Minneapolis's pipeline after the repeal took effect: a four-over-one wood-frame block on a quarter-acre infill lot in Longfellow or Corcoran — not a downtown tower, just the mid-rise stick-built product that dominated permitting in the years after the ordinance changed. Run it three ways.

```

Frequently Asked Questions

How much does a single structured parking stall add to an apartment unit's monthly carrying cost?

Roughly $139 a month.

How narrow were the financial margins that decided whether a marginal Minneapolis project got financed?

Feasibility at the edge turned on gaps as small as $5 a month per unit, and removing the one-stall-per-unit obligation could move a marginal site's projected return by about 2 points.

Who sponsored the 2015 amendment that abolished Minneapolis's parking minimums?

Council Member Lisa Bender of Ward 10, whose strike of the minimum-ratio table made Minneapolis the first large U.S. city to abolish parking minimums everywhere at once.

Did the repeal also eliminate downtown Minneapolis's parking maximums?

No — downtown's decades-old parking maximums stayed on the books untouched, since repeal extended the cap logic outward rather than banning anything.

Why did Minneapolis delete the parking table citywide instead of adopting transit-zone or corridor exemption maps?

A drawn boundary demands permanent upkeep because staff must continuously classify which parcels fall inside the exemption, while a null constraint administers itself forever.

What sequencing detail do councils copying the reform most often get wrong?

Minneapolis struck the minimums in 2015 and adopted the density-upzoning 2040 Comprehensive Plan afterward, so newly entitled capacity arrived with no embedded stall obligations — flipping the order quietly rebuilds the constraint repeal removed.

Quick answers

Also worth reading: Solving the housing crisis with innovative local strategies: Solving the housing crisis with · The critical steps to solving the urban housing crisis: critical steps to solving the · How smart cities work and the technology shaping the future of urban planning: How smart cities work and