"This parcel sits in Minneapolis — do I apply to Minnesota Housing or to the city, and does that change how the site actually scores?"
Minnesota Housing plus seven Suballocators — not a regional set-aside system
Minnesota Housing (the Minnesota Housing Finance Agency) is the state's primary HTC Allocating Agency, but Minnesota Statutes sections 462A.221 to 462A.225 also let certain cities and counties become Suballocators — separate Allocating Agencies that run their own HTC competition inside their own jurisdiction. Under section 462A.222, subdivision 1, eligibility was originally limited to cities with a population of at least 50,000 with a housing and redevelopment authority (HRA), cities located in three or more counties with an HRA, and counties with a population of 100,000 or more with an HRA — and a city or county only qualified if it submitted a written request to the agency within 45 days after June 2, 1987. A qualifying city or county may designate its HRA as the receiving agency, and Minneapolis or Saint Paul specifically may designate the Minneapolis/Saint Paul Housing Finance Board to receive credits on behalf of each city.
As of Minnesota Housing's own current Housing Tax Credit Contact Information sheet, seven Suballocators are active: Dakota County (Dakota County Community Development Agency), the City of Duluth, the City of Minneapolis, St. Cloud (St. Cloud Housing and Redevelopment Authority), the City of Saint Paul, the City of Rochester, and Washington County (Washington County Housing and Redevelopment Authority). That contact sheet is the actual current list — Minnesota Housing's QAP text itself says only that it "will post updates to Suballocator information on Minnesota Housing's website," so a screening tool should treat that page, not a static roster, as the source of truth.
| Jurisdiction | Administering entity | Has a Joint Powers Agreement with Minnesota Housing? |
|---|---|---|
| Dakota County | Dakota County Community Development Agency | No — self-administers |
| City of Duluth | City of Duluth Planning & Development | Yes — Minnesota Housing performs the allocation and compliance monitoring |
| City of Minneapolis | Community Planning and Economic Development (CPED) | No — self-administers |
| City of St. Cloud | St. Cloud Housing and Redevelopment Authority | Yes — Minnesota Housing performs the allocation and compliance monitoring |
| City of Saint Paul | Department of Planning and Economic Development (PED) | No — self-administers |
| City of Rochester | City of Rochester | Yes — Minnesota Housing performs the allocation and compliance monitoring |
| Washington County | Washington County Housing and Redevelopment Authority | No — self-administers |
The QAP itself only names Duluth, St. Cloud and Rochester as the Suballocators currently under a Joint Powers Agreement. For those three, Minnesota Housing effectively runs the process even though the city is still the credits' legal Suballocator. Confirm current status directly — a Suballocator can enter or exit a Joint Powers Agreement, and the QAP text says explicitly that updates will be posted on Minnesota Housing's site rather than fixed in the QAP.
That split matters for where an application actually goes. In Round 1, a for-profit applicant with a site inside a Suballocator's jurisdiction must apply directly to that Suballocator unless it has a Joint Powers Agreement (in which case Minnesota Housing runs it) or has already returned its credits to Minnesota Housing; Minnesota Housing will not accept a Round 1 application for a site inside a self-administering Suballocator's territory outside the nonprofit set-aside. So a site in Minneapolis, Saint Paul, Dakota County or Washington County in Round 1 goes to that jurisdiction's own department — Minneapolis CPED, Saint Paul PED, Dakota County CDA, or the Washington County HRA — using that jurisdiction's own application process, timeline and (frequently) its own local scoring add-ons, not Minnesota Housing's Multifamily Customer Portal. A site in Duluth, St. Cloud or Rochester functionally goes through Minnesota Housing's own process because of the Joint Powers Agreement. Everywhere else in the state, and every nonprofit applicant regardless of location, applies to Minnesota Housing directly.
Round 2 resets that: all HTCs Suballocators haven't committed or allocated must be returned to Minnesota Housing before the Round 2 deadline, and in Round 2 all projects located in Suballocator jurisdictions — including the self-administering four — may apply directly to Minnesota Housing instead. A site that loses in Minneapolis's own Round 1 competition is not dead; it becomes eligible for Minnesota Housing's statewide, unified Round 2 pool, which runs without geographic set-asides.
Correcting a natural assumption: the Metropolitan Council is not a Suballocator
It is a reasonable guess that the Metropolitan Council — the regional planning body for the seven-county Twin Cities area — sits alongside Minnesota Housing as an allocator of credits, the way some states run a true regional-authority model. Minnesota Housing's own QAP definitions do not support that. The QAP defines "Suballocator(s)" as "any Allocating Agency, other than Minnesota Housing, authorized by the state of Minnesota and Section 42 to allocate HTCs in Minnesota," and the Metropolitan Council is not on Minnesota Housing's list of Suballocators or their contact sheet. Minnesota Statutes section 462A.222 gives the Council exactly two roles in the HTC program, and neither one is allocating credits to a project.
| Role | What the statute actually says |
|---|---|
| Defining the Metropolitan Area pool boundary | "Metropolitan Area" is defined by cross-reference to Minnesota Statutes, section 473.121, subdivision 2 — the area over which the Metropolitan Council has jurisdiction: Anoka, Carver, Dakota (excluding Northfield and Cannon Falls), Hennepin (excluding Hanover and Rockford), Ramsey, Scott (excluding New Prague) and Washington counties. This only sets which of the two statewide geographic pools (Metropolitan Area vs. Greater Minnesota) a site's credits are drawn from. |
| Co-drafting the metro distribution plan (subd. 4(a)) | "The Metropolitan Council, in consultation with the agency and representatives of local government and housing and redevelopment authorities, shall develop and submit to the agency a plan for allocating tax credits... in the metropolitan area, based on regional housing needs and priorities." The agency (Minnesota Housing) may then amend that plan after consulting the Council. This is a planning input into how Minnesota Housing structures its own distribution — it is not the Council awarding credits to a project. |
The Council does have real, independent regulatory authority over local zoning and comprehensive plans in the same seven counties under the separate Metropolitan Land Planning Act (Minn. Stat. §§ 473.851–473.871) — that authority belongs to Phase 3 (entitlement pathway), not to HTC allocation. Conflating the two is an easy, and consequential, mistake.
Two geographic pools, and the score threshold a site has to clear before any of this matters
Underneath the Suballocator layer, Minnesota Housing's own share of the state's credit ceiling is split into two general pools under Minn. Stat. § 462A.222, subd. 1a: the Metropolitan Area pool and the Greater Minnesota pool ("Greater Minnesota" is simply the QAP's term for everything outside the Metropolitan Area). The split between the two pools is not fixed — it tracks the two regions' relative share of the state's public-assistance caseload (Minnesota Family Investment Program, General Assistance, Minnesota Supplemental Aid and Supplemental Security Income recipients, as reported annually by the Department of Human Services), and Minnesota Housing updates that allocation using new demographic data in early 2025, 2026 and 2027 across the life of the Amended 2026-2028 QAP.
Before any site-specific scoring matters, a project has to clear one of three point floors on the Self-Scoring Worksheet, and the floor depends on funding type: 80 points for a project competing for 9% credits from the state's credit ceiling, 40 points for a project seeking credits in association with tax-exempt volume-limited bonds, and 30 points for a project applying through the Rural Development (RD)/Small Project set-aside. A site that scores well on location criteria but can't clear its applicable floor never reaches the ranking stage at all.
The site-selection scoring items — including a criterion literally named "Location Efficiency"
Minnesota's Self-Scoring Worksheet does not use a QCT-and-DDA-driven site table the way some states do. Its location-relevant points sit inside a group the worksheet itself calls "Increasing Housing Choice" plus a second group on community and economic development, and several of them are three-tier systems that reward a site's community context rather than its census-tract designation alone.
| Criterion | Points | What it actually measures |
|---|---|---|
| Access to More Affordable Housing | 2 to 6 | Three-tier system based on a community's percentile rank for cost-burdened renters or for having a low share of affordable rental housing relative to all housing, per the Methodology Guide |
| Workforce Housing Communities | 3 to 6 | Whether the site sits in or near (within 5 miles in the Metro Area, 10 miles in Greater Minnesota) a Top Job Center, a Net Five-Year Job Growth Community, an Individual Employer Growth Community (100+ net jobs added by one employer in 5 years), or a Long Commute Community |
| Transit and Walkability | 1 to 9 | Access-to-transit and Walk Score thresholds that differ by geography (Metropolitan Area; Greater Minnesota urbanized areas over 50,000 population; Greater Minnesota rural/small-urban areas). For rural and small-urban areas specifically, the worksheet's own text says applicants "may claim Location Efficiency by having access to route deviation service or demand response/dial-a-ride and walkability" — Location Efficiency is Minnesota Housing's own term for that specific rural transit-and-walkability test, not a statewide site-quality label |
| Rural/Tribal | 4 to 8 | A tiered scale keyed to the population of the community outside the Metropolitan Area (≤2,000 down to >10,000), with Tribal Reservations, Dakota Communities and Tribal trust lands automatically Tier 1 |
| Qualified Census Tracts/Community Revitalization or Tribal Equivalent Areas | 3 | A QCT project must be part of a concerted community revitalization plan to qualify — being in a QCT alone is not enough for these points — or the project sits in a Tribal Equivalent Area, which qualifies solely on geography |
| Equitable Development | 3 | Requires a Qualified Stakeholder Group (QSG) — an independent body separate from the development team, with at least three members of the Community Most Impacted, engaged at least twice before submission — documented through a required narrative and a signed letter from the QSG |
| Community Development Initiative | 3 | The project must contribute to a broader, locally driven initiative with active stakeholder engagement that contains more components than the project itself |
| Local Actions to Support Housing | 2 | New for the 2026 Multifamily Consolidated RFP/2027 HTC round and after — points if the project's jurisdiction meets one or more listed pro-housing zoning practices (see Phase 3) |
Several of these criteria carry a "Hold Harmless" provision: an applicant not selected in one cycle of the Amended 2026-2028 QAP's three application cycles can reapply in the next cycle using either its prior cycle's scores or newly calculated scores for the Increasing Housing Choice criteria (Access to More Affordable Housing, Workforce Housing Communities, Transit and Walkability) — but may not mix scores from two different cycles on the same application.
None of this is a fixed-point site table the way some states run QCT/DDA scoring. A screening tool built for Minnesota has to carry the percentile-tier methodology (published separately in Minnesota Housing's Methodology Guide, not in the QAP or worksheet text itself) rather than a flat address lookup, and it has to track which application cycle a prior, unsuccessful score belongs to before assuming Hold Harmless applies.
Basis boost: federal QCT/DDA is broad, Minnesota's own boost is narrow and targeted
The federal basis boost works in Minnesota exactly as IRC § 42(d)(5)(B) provides everywhere: a building in a HUD-designated Qualified Census Tract or Difficult Development Area qualifies for a 30% increase in eligible basis, and Minnesota Housing's QAP points applicants to HUD's own QCT/DDA table generator and map, with the caution that annual HUD redesignations mean a site's status can change between application, allocation, bond issuance and placed-in-service dates.
Minnesota Housing's own state-designated basis boost, authorized under IRC § 42(d)(5)(B)(v), is materially narrower than a state boost like Colorado's discretionary boost. It is not available on a general financial-feasibility showing — the QAP requires the project to independently qualify under one of three specific Selection Criteria first (Permanent Supportive Housing for People with Disabilities or High Priority Homeless Households, Preservation, or Tribal sponsorship/significant Tribal financial contribution), and only then must the application separately demonstrate a genuine funding gap that the boost is sized no larger than necessary to close. A site that is simply expensive to build does not qualify for Minnesota's state boost on that basis alone; it has to fit one of the three named categories first.
Environmental and hazard screening, and where the income/rent numbers actually live
For a first-pass hazard screen, the Minnesota Pollution Control Agency's own "What's in My Neighborhood" tool is the state's queryable environmental-conditions layer — contaminated and formerly contaminated sites, open and closed landfills, hazardous waste disposal sites, petroleum storage tank and leak sites, and permitted or registered facilities, available through MPCA's web map and as an OGC web map service on the Minnesota Geospatial Commons. MPCA's own disclaimer is worth carrying into any tool built on it: a site's appearance in the database — a permit, a registration, a closed enforcement action — does not by itself mean the property poses a risk; it is a lead to investigate, not a verdict. FEMA's National Flood Hazard Layer remains the federal floodplain baseline, unauthenticated and queryable the same way it is in every state.
Income and rent limits are not separately published by Minnesota Housing as an agency-specific table the way some states run their own memo. The QAP directs applicants to HUD's own published income limits, with Minnesota Housing maintaining a Rent and Income Limits page on its own website that organizes the current HUD figures by Minnesota county. A screening tool should treat that page, refreshed on HUD's annual cycle, as the canonical source rather than caching a static table — and should carry forward into Phase 2 that gross rent for HTC compliance purposes is reduced by a utility allowance whenever the tenant pays utilities directly, calculated under IRS Treasury Regulation 1.42-10 (detailed in Phase 2).
Where this goes wrong
- Assuming the Metropolitan Council is a Suballocator or otherwise allocates HTCs directly. Minnesota Housing's own QAP definitions give the Council exactly two roles — defining the Metropolitan Area boundary and co-drafting the metro distribution plan in consultation with Minnesota Housing — neither of which is awarding credits to a project. It is not on Minnesota Housing's list of Suballocators.
- Treating Minnesota's Suballocator system as a California-style regional apportionment. It is a jurisdiction-by-jurisdiction designation under Minn. Stat. § 462A.222 covering exactly seven current Suballocators (Dakota County, Duluth, Minneapolis, St. Cloud, Saint Paul, Rochester, Washington County), not a fixed set of regional pools with guaranteed shares.
- Applying to Minnesota Housing directly for a Round 1 site inside a self-administering Suballocator's jurisdiction (Minneapolis, Saint Paul, Dakota County, or Washington County). Minnesota Housing will not accept that application in Round 1 outside the nonprofit set-aside; it has to go to the Suballocator's own department.
- Missing that Duluth, St. Cloud and Rochester are Suballocators in name but are functionally processed by Minnesota Housing under a Joint Powers Agreement — treating them the same as the four self-administering Suballocators (with their own separate local applications) wastes time chasing a local process that doesn't exist for those three cities under current arrangements. Confirm current JPA status before assuming either way.
- Assuming a site's location inside a QCT automatically earns the QCT/Community Revitalization Selection Criterion points. The worksheet requires the QCT project to also be part of a concerted community revitalization plan — geography alone is not sufficient outside a Tribal Equivalent Area.
- Reading Minnesota's state-designated basis boost as a general financial-feasibility gap-filler the way some states' discretionary boosts work. Minnesota's boost requires the project to first independently qualify under the Permanent Supportive Housing, Preservation, or Tribal Selection Criteria, and only then demonstrate a funding gap — an otherwise-expensive but unrelated project doesn't qualify no matter how large its gap is.
- Applying the Increasing Housing Choice Hold Harmless provision across two different application cycles' scores on one application. The Self-Scoring Worksheet is explicit that an applicant may use either the prior cycle's or the current cycle's scores for Access to More Affordable Housing, Workforce Housing Communities, and Transit and Walkability, but may not mix and match the two.
- Confusing Minnesota Housing's "Location Efficiency" language with a statewide site-scoring term. In the current Self-Scoring Worksheet it appears specifically inside the Transit and Walkability criterion for Greater Minnesota rural and small-urban areas (route deviation/demand-response service plus walkability) — it is not a separate, general scoring category.
- Treating a hit in MPCA's "What's in My Neighborhood" database as proof of contamination. MPCA's own materials state plainly that appearing in the tool — a permit, a registration, a closed enforcement matter — does not necessarily mean a property poses a risk; it flags something to investigate further, not a disqualifying fact.
- Assuming the 9%/40-point/30-point Self-Scoring Worksheet thresholds are interchangeable. A project's applicable minimum score floor (80, 40, or 30 points) depends on which funding type it is competing for — 9% credit ceiling, tax-exempt bond 4% credits, or the RD/Small Project set-aside — and applying the wrong floor misreads whether a site's projected score is actually competitive.
- Not distinguishing the seven-jurisdiction HTC Suballocator map from the separate, four-entity tax-exempt bond volume-cap entitlement-issuer map under Minn. Stat. § 474A.03 — they do not cover the same jurisdictions, and confusing the two during site screening can misdirect a bond-financed deal's early planning. See Phase 3.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies