Entitlement pathway election — Minnesota

Two separate enabling statutes — and a population cutoff keyed to a 1950 census, not today's

Minnesota's zoning authority runs through two different chapters depending on whether the zoning body is a city or a county. Minnesota Statutes Chapter 462, the Municipal Planning Act, is the enabling statute for cities. Section 462.357, subdivision 1 grants "a municipality" — defined elsewhere in the chapter to include both statutory and home rule charter cities — the authority to regulate, by ordinance, lot coverage, density, building height and bulk, use, and a long list of other zoning-adjacent matters "for the purpose of promoting the public health, safety, morals, and general welfare."

County zoning runs through a separate chapter, Chapter 394, and it is not universal. Section 394.21, subdivision 1 authorizes county planning and zoning activity only for "any county in the state having less than 300,000 population according to the 1950 federal census." That threshold is fixed to a specific historical census, not to a county's current population — a screening tool should not infer county zoning authority (or its absence) from today's population figures. Confirm which counties actually fall outside Chapter 394 authority directly, since the operative fact is the 1950 count, not a current estimate; unorganized territory and any county that has instead adopted zoning under a special or local law can also fall outside this general framework, and either should be checked directly with the county rather than assumed from the general rule.

One further wrinkle sits inside Chapter 394 itself and applies statewide regardless of population: subdivision 1a bars a county, "regardless of population," from enacting or enforcing an ordinance that eliminates or terminates an otherwise-lawful existing use through amortization — a relevant fact for any acquisition/rehab deal relying on a legal nonconforming use continuing at a site.

No statewide preemption exists — three straight sessions of a real attempt have failed

Minnesota has no equivalent of Florida's Live Local Act or a state-mandated by-right multifamily allowance. A genuine legislative push for one — commonly called the "missing middle" bill and, in its most recent form, the Minnesota Starter Home Act — has now failed in three consecutive legislative sessions: 2024, 2025, and again in 2026. The 2026 version, HF 3895/SF 4123 in the 94th Legislature, combined several land-use reform concepts into one bill (by-right duplexes/triplexes/townhomes and accessory dwelling units in areas zoned single-family, limits on aesthetic mandates such as required porches or minimum garage size, and restrictions on parking minimums), and stalled in a House committee on a 7-5 roll call vote just ahead of the legislature's own March 27, 2026 committee-deadline cutoff. The League of Minnesota Cities and other local-government advocates opposed it as an unfunded override of local zoning control.

This history matters directly for pathway election: a Minnesota screening or underwriting tool should not model any statewide density or use entitlement as pending or imminent. Every entitlement in Minnesota is still won parcel-by-parcel, city-by-city (or county-by-county, subject to the Chapter 394 population cutoff above), under whatever local zoning ordinance and comprehensive plan currently govern the site.

Minnesota Housing's actual lever: a 2-point QAP incentive for jurisdictions that already loosened zoning

In the absence of state preemption, Minnesota Housing built its own financial incentive directly into the Self-Scoring Worksheet: the "Local Actions to Support Housing" criterion, worth 2 points, effective for the 2026 Multifamily Consolidated RFP/2027 HTC round and after. Unlike most of the worksheet's site-location criteria, this one scores the jurisdiction's own zoning code rather than the site itself, and an applicant may claim it by showing the jurisdiction meets one or more of eight listed pro-housing zoning practices.

The Metropolitan Land Planning Act: the Metropolitan Council's real regulatory teeth

Phase 1 draws a sharp line between the Metropolitan Council's narrow, consultative role in HTC allocation and its separate, genuine regulatory authority over land use — and that authority is exactly what belongs in entitlement pathway analysis. Under the Metropolitan Land Planning Act, Minnesota Statutes §§ 473.851 to 473.871, every local governmental unit inside the seven-county Metropolitan Area must prepare and submit a comprehensive plan to the Metropolitan Council, and the Council reviews it for compatibility with other local plans and conformity with the Council's own metropolitan system plans. If the Council concludes a local plan (or an amendment to one, including a site-specific rezoning that requires a comprehensive plan amendment) is "more likely than not to have a substantial impact on or contain a substantial departure from" the metropolitan system plans, it can require the jurisdiction to modify that plan.

That is a real, standalone entitlement risk for a metro-area site whose rezoning requires a comprehensive plan amendment — the local zoning approval is not the only body with a say; the Council's own consistency review sits on top of it for any of the seven Metropolitan Area counties. A screening or diligence tool should track this as a separate approval layer from the underlying municipal or county rezoning itself, not assume that City Council or County Board approval alone closes out zoning risk on a metro-area site with a comprehensive-plan-level change.

The same Metropolitan Council also administers the Livable Communities Act programs, including the Livable Communities Demonstration Account (LCDA) Transit Oriented Development grants — directly referenced inside Minnesota Housing's own Self-Scoring Worksheet, which awards Transit and Walkability points for sites within a half-mile of a planned or existing transit stop where "planned stations include those eligible for Metropolitan Council [LCDA] Transit Oriented Development (TOD) Grants." That is a genuine, confirmable connection between Metropolitan Council programming and HTC site scoring — it runs through the LCDA grant program and the QAP's transit criterion, not through HTC allocation itself.

Bond financing: the entitlement-issuer map does not match the Suballocator map

A 4% HTC deal financed with tax-exempt volume-limited bonds needs an issuer, and Minnesota's private activity bond volume cap is allocated under an entirely separate statute — Minnesota Statutes Chapter 474A — from the one governing HTC Suballocators. Under § 474A.03, subdivision 2a, exactly four entities receive an automatic annual "entitlement" allocation of bonding authority, each in a fixed dollar amount set by statute, rather than having to compete for volume cap from the state's general pools.

The QAP itself confirms the issuer can be someone other than Minnesota Housing: its Determination of Bond Issuer requirement applies "if the issuer of the bonds is not Minnesota Housing," requiring evidence that the issuer allocated a portion of the state's volume cap to the project and made its own determination that the requested HTC amount doesn't exceed what's needed for financial feasibility. A recent real-world example — a November 2024 Minnesota Housing TEFRA notice — shows Minnesota Housing itself acting as issuer for developments across several different Suballocator and non-Suballocator cities (Duluth, Carver, Rochester, Waite Park) in a single combined bond issuance, which is a common and efficient path precisely because those cities are not bond entitlement issuers themselves.

TEFRA hearings: the "applicable elected representative" changes with who's issuing

Federal law (IRC § 147(f)) requires tax-exempt private activity bonds — including the residential rental bonds behind Minnesota's 4% HTC deals — to be approved by "the applicable elected representative" of the issuing governmental unit after a public hearing following reasonable public notice (the TEFRA hearing, named for the Tax Equity and Fiscal Responsibility Act of 1982). Who that elected representative is depends entirely on who the issuer is, and Minnesota's answer differs by issuer type.

A real Minnesota Housing TEFRA notice from November 2024 shows the mechanics in practice: notice published November 8, 2024 for a hearing held November 19, 2024 — an 11-day gap — covering five separate developments in five different cities (Duluth, Carver, Rochester, Waite Park) in one combined notice, each with its own stated maximum bond principal amount, signed by Minnesota Housing's Commissioner. Federal law only requires "reasonable" public notice (Treasury regulations set a floor of at least several days, not a fixed two weeks), so a local issuer's own bond counsel may set a longer practice window than Minnesota Housing's own; don't assume Minnesota Housing's notice period is the state-mandated minimum, and confirm the applicable notice period with the specific issuer and its bond counsel for a given deal.

One further trap specific to conduit issuance: IRC § 147(f)(2) requires host approval — approval by the governmental unit with jurisdiction over the area where the project is actually located — whenever that differs from the issuer's own jurisdiction. A real example of this in Minnesota: a City of Cottage Grove resolution approving the issuance of bonds by the City of St. Paul Park for a project, because the issuing city and the site's host city were different governmental units. A deal where a county HRA or a neighboring city acts as issuer for a project physically located in a different city should budget for two separate TEFRA-adjacent approvals — the issuer's own, and the host jurisdiction's — not one.