"Our site sits inside Rochester's city limits — do we file with Minnesota Housing or with the city, and what score does the Self-Scoring Worksheet actually have to show before any of that matters?"
One statewide portal, but not always one front door
Minn. Stat. §462A.222, subd. 1 lets a city or county become a Suballocator — its own HTC Allocating Agency — if it meets one of a short list of tests: a city of at least 50,000 population with a Housing and Redevelopment Authority; a city located in three or more counties with an HRA; a county of at least 100,000 population with an HRA; or, separately, the city of Minneapolis or the city of Saint Paul designating the Minneapolis/Saint Paul Housing Finance Board to receive its reserved credit. That is the statutory universe of who *can* hold Suballocator status — it is broader than the set of cities actually exercising it today.
The current Amended 2026-2028 QAP is specific about who has actually entered a Joint Powers Agreement (JPA) with Minnesota Housing, under which Minnesota Housing performs the HTC allocation and compliance monitoring on the Suballocator's behalf: "These Suballocators currently are the cities of Duluth, St. Cloud and Rochester." For a for-profit applicant, that JPA status is the whole ballgame in Round 1 — the QAP states plainly that "except for the nonprofit set-aside, Minnesota Housing will not accept applications for developments located within the jurisdiction of Suballocators in Round 1 unless the Suballocator has entered into a Joint Powers Agreement with Minnesota Housing or has returned all their HTCs to Minnesota Housing." A for-profit applicant with a site inside a Suballocator jurisdiction that has *not* signed a JPA and has *not* returned its credit must apply directly to that Suballocator, on that Suballocator's own process — not through Minnesota Housing's Consolidated RFP portal at all. A nonprofit applicant gets a materially different rule: it may apply simultaneously to the Suballocator and to Minnesota Housing's own nonprofit set-aside.
The Metropolitan Council is easy to overstate here. It is not itself a Suballocator and does not appear in the QAP's list of entities holding a credit reservation or issuing IRS Form 8609s. Its statutory role, unchanged in substance since it was first assigned by October 1, 1990, is narrower: Minn. Stat. §462A.222, subd. 4 tasks the Metropolitan Council with developing and submitting to Minnesota Housing "a plan for allocating tax credits... in the metropolitan area, based on regional housing needs and priorities," done "in consultation with the agency and representatives of local government and housing and redevelopment authorities." That is a planning and consultation function feeding into how Minnesota Housing itself administers the Metropolitan Area pool — a materially different thing from Duluth, St. Cloud, or Rochester's actual allocating authority under their JPAs.
| Pool | Definition |
|---|---|
| Metropolitan Area | The seven counties over which the Metropolitan Council has jurisdiction (Minn. Stat. §473.121, subd. 2): Anoka, Carver, Dakota (excluding the cities of Northfield and Cannon Falls), Hennepin (excluding the cities of Hanover and Rockford), Ramsey, Scott (excluding the city of New Prague), and Washington |
| Greater Minnesota | Any area of the state not included in the Metropolitan Area as defined above |
The dollar split between the two pools is set annually by a statutory formula tied to each area's share of certain public-assistance caseloads (Minn. Stat. §462A.222, subd. 1a) and republished on Minnesota Housing's website — the QAP itself does not print a fixed current-year percentage, and a percentage sourced from an older year's materials should not be assumed current.
Round 1's set-asides and ceilings, and the very different shape of Round 2
Round 1 is a forward-selection round offered through the Multifamily Consolidated RFP, with selections generally made the year before the credit's actual allocation year. Within it, federal law reserves 10% of the state's credit ceiling for the Nonprofit Set-Aside, which Minnesota Housing and its Suballocators may agree to expand by another 5% (15% total) in a given year; a separate Rural Development/Small Project set-aside is fixed by dollar amount for each year of the current QAP — $500,000 in 2026, $525,000 in 2027, and $525,000 in 2028 — for projects with an RD financing commitment or application, or a small (24-or-fewer-unit) project in a Rural/Tribal Designated Area. Minnesota Housing also caps new-construction competition indirectly: it sets a preservation allocation ceiling of two-thirds of each geographic pool (Metro and Greater Minnesota), excluding the RD/Small Project and Nonprofit set-asides, reserving the remaining third of each pool's general credit for new construction unless qualifying new-construction proposals simply aren't available.
Round 2 is a different competitive world entirely. It pools all remaining or returned credit from Round 1 — excluding credit returned for a reallocation request — into one unified, statewide amount with no Metropolitan Area/Greater Minnesota split and no set-asides at all, except that the RD/Small Project set-aside is carried forward until it is exhausted or no eligible applications remain, and the Nonprofit set-aside is carried forward only if Minnesota Housing did not meet the federal 10% requirement in Round 1. All Suballocator-jurisdiction projects may apply directly to Minnesota Housing in Round 2 regardless of JPA status, and a project with a prior HTC award that is now facing an annual shortfall of between 5% and 33.33% of its qualified HTC amount gets priority over other Round 2 and waiting-list applicants.
The Self-Scoring Worksheet minimum is a gate, not a target
Chapter 5.C of the QAP sets three different point floors, and an application that doesn't clear its floor is not eligible for HTCs from the state's credit ceiling at all — this is a threshold, not a ranking adjustment. A general 9% application must be eligible for no less than 80 points on the Self-Scoring Worksheet; the RD/Small Projects set-aside carries its own, much lower floor of 30 points; and an application seeking HTCs associated with tax-exempt volume-limited bonds needs no less than 40 points. The QAP's own text does not print a maximum possible score — that scale lives in the companion Self-Scoring Worksheet document itself, which this research pass did not independently review, so no maximum-points figure is asserted here.
The 26 Selection Criteria named in Chapter 5.C run from population- and need-based categories (Large Family Housing, Senior Housing, Permanent Supportive Housing for High Priority and Other Homeless, People with Disabilities, Preservation, Rental Assistance) through location and program-fit categories (Access to More Affordable Housing, Workforce Housing Communities, Transit and Walkability, Qualified Census Tracts/Community Revitalization or Tribal Equivalent Area, Rural/Tribal) to team- and cost-facing categories (Multifamily Award History, BIPOC/Women-owned Business Enterprises, Financial Readiness to Proceed/Leveraged Funds, Intermediary Costs, Innovative Construction Techniques, Universal Design, Enhanced Sustainability) plus two named non-scoring selection criteria (Sponsor Characteristics; Public Housing waiting lists). A separate, shorter list of five Preference Criteria — Serves Lowest Income Tenants/Rent Reduction, Rental Assistance, Long-Term Affordability, QCT/Community Revitalization or Tribal Equivalent Areas, and the non-scoring Eventual Tenant Ownership preference — exists specifically to break point ties, not to add to the base score.
| Order | Tie breaker |
|---|---|
| 1st | Greater number of Preference Criteria points |
| 2nd | Project includes an Eventual Tenant Ownership component |
| 3rd | Project is in a city, township, or Tribal reservation that has not received an HTC allocation from the annual credit ceiling in the last two years |
| 4th | Highest percentage of funds secured, awarded, or committed (Financial Readiness to Proceed/Leveraged Funds) |
| 5th | Lowest percentage of intermediary costs (Intermediary Costs criterion) |
| 6th | Determined by lot |
What actually has to be in the package, beyond the score sheet
The controlling checklist lives in the Multifamily Customer Portal, not in the QAP's own text — the QAP repeatedly points applicants to the Portal's Application Checklist, the Multifamily Consolidated RFP Standards, and the Scoring Guide rather than enumerating every exhibit itself. An Intent to Apply is required in advance of the full application. Every 9% and 4% project must complete a comprehensive market study before an Allocation or Award is made, conducted under IRC §42(m)(1)(A)(iii) by a disinterested party at the developer's own expense and approved by Minnesota Housing; staff separately runs its own market review of in-house occupancy data and may ask an applicant to adjust unit mix before scoring. Applicants must sign a certification agreeing to use the local HRA's or PHA's waiting list to fill vacant units, consistent with federal preference requirements. On receipt of an application, Minnesota Housing is required by federal law to notify the chief executive officer of the local jurisdiction where the project is planned — a real opportunity for local comment before selection, not a courtesy notice sent afterward. No project may be split into two or more applications within a single funding round to game the process; Minnesota Housing will return every resulting application, with fees forfeited, if it determines ownership entities, GP/managing-member relationships, sponsor ties, or site contiguity add up to one project filed as several. Much of what is submitted becomes public data under Minnesota's own Government Data Practices Act, Minnesota Statutes chapter 13.
Clearing the score floor does not end the review. A project must also pass Design Review — certifying compliance with the development features in Chapter 5 of Minnesota Housing's Rental Housing Design/Construction Standards before it can even be scored and ranked — a Development Team Review weighing the team's capacity, prior compliance record with Minnesota Housing and the IRS, and experience managing similar housing, and a Site Review that can include an actual site inspection against four stated principles (Linkage, Jobs, Land Use, Transportation) and six environmental factors (noise; flood plains and wetlands; site safety; toxic and hazardous waste; underground storage tanks; asbestos and lead-based paint). Proposals that pass all of that still face a Multifamily Underwriting Standards review, a Financial Feasibility determination under IRC §42(m)(2), and a Development Cost Review for reasonableness — any of which can result in the application being revised, its score reduced, or the project dropped from further processing in the current cycle.
Fees apply at nearly every gate, but the QAP does not print the dollar amounts
Chapter 8 of the QAP names eight fee categories tied to an HTC application's lifecycle — Application Fee, Supplemental Application Fee (for a Round 2 resubmission underwritten by Minnesota Housing in Round 1), Reservation Fee, Allocation Fee (carryover, 8609, or reallocation), Application Late Fee, Preliminary Determination Fee (for bond-financed 42(m) applications), Monitoring Fee (an annual, per-unit fee through the compliance and extended-use periods), and Transfer of Ownership Fee — and states that all fees are non-refundable and will not be adjusted if the final HTC amount is later reduced, recaptured, or goes unused. What the QAP does not do is print a single dollar figure for any of them: it repeatedly directs applicants to "the Multifamily Loan Programs and Housing Tax Credit Fee Schedule" as the actual source of current amounts. This research pass did not independently obtain that fee schedule, so no specific dollar figure is stated here — a number carried over from an old cycle's materials should be re-verified against the current schedule before it is quoted to a developer.
Where this goes wrong
- Assuming every Minnesota project applies straight to Minnesota Housing. In Round 1, a for-profit applicant with a site inside a Suballocator's jurisdiction that has not signed a Joint Powers Agreement with Minnesota Housing (currently Duluth, St. Cloud, and Rochester have JPAs) and has not returned its credit must apply directly to that Suballocator — except through the nonprofit set-aside.
- Overstating the Metropolitan Council's role as a credit-allocating "regional suballocator." Minn. Stat. §462A.222, subd. 4 tasks it only with developing and submitting a metro-area distribution plan in consultation with Minnesota Housing and local government/HRA representatives; the current QAP does not list it as a Suballocator, and nothing reviewed in this research pass shows it issuing 8609s or holding its own credit reservation the way Duluth, St. Cloud, or Rochester do under their JPAs.
- Treating the Self-Scoring Worksheet's point floor as a soft target. An application below 80 points (30 for the RD/Small Project set-aside, 40 for a tax-exempt-bond-associated application) is not eligible for HTCs from the state's credit ceiling at all under Chapter 5.C — it is a pass/fail gate applied before ranking, not a factor weighed alongside other strengths.
- Assuming Round 2 preserves Round 1's geography or set-asides. Round 2 combines all remaining and returned credit into one unified statewide pool with no Metropolitan Area/Greater Minnesota split and (absent the specific carry-forward conditions for the RD/Small Project and Nonprofit set-asides) no set-asides — a project competitive within Round 1's Greater Minnesota pool can face a completely different applicant field in Round 2.
- Splitting one site into multiple applications to work around round or set-aside limits. The QAP explicitly bars dividing a single project into two or more applications within one funding round, and will return every resulting application — with all fees forfeited — once Minnesota Housing determines, from ownership, GP/managing-member, sponsor, or site-contiguity facts, that a multiple application exists.
- Quoting a specific application, reservation, or late fee dollar amount from an old cycle's materials. The QAP describes the fee categories and when each is due but explicitly defers the actual dollar figures to a separately published, periodically updated Fee Schedule — a stale number should be re-verified before it reaches a developer.
- Treating the local chief executive officer notice as a formality that happens after selection. Minnesota Housing is required by federal law to notify the CEO of the project's local jurisdiction on receipt of the application, creating a real window for local government comment before Minnesota Housing selects the project — not a post-selection courtesy copy.
- Assuming a tax-exempt bond/4% deal follows the Round 1/Round 2 calendar. Bond-financed applications run on a year-round pipeline gated by a 42(m) application that must be filed at least 60 days before bond issuance, entirely separate from the Consolidated RFP's spring Intent-to-Apply and summer full-application deadlines.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies
