Application assembly and submission — Wisconsin

The three-gate funnel: Concept, Full Application, Application Two

Every application for a Competitive Credit (9% or State-paired-4%) starts with a Project Concept submission -- a narrative, proposed unit mix and population target, evidence of site control, and Development Team overview and experience forms. WHEDA reviews concepts for Development Team eligibility (including verifying nonprofit-led project status), applies location-based threshold and scoring screens, and can eliminate projects at this stage if a single market is overrepresented among submitted concepts. Only applicants who clear Project Concept review may submit a Full Application.

A Full Application requires the complete Multifamily Application (MFA) workbook, every applicable item on the Threshold and Scoring Checklists embedded in the MFA, and whichever appendices apply to the deal (HUD-financed developments trigger Appendix N; Rural Development deals trigger Appendix O; Section 811 PRA units trigger Appendix S, and so on). WHEDA reviews for completeness -- Section 42 occupancy and rent-restriction basics, an ownership interest held by the applying organization (public and tribal housing authorities excepted), the same development team as at Concept stage, and no unresolved environmental or administrative proceedings -- and allows a pre-defined five-business-day cure period for administrative deficiencies WHEDA itself identifies. WHEDA then ranks applications by the applicant's self-score plus WHEDA's own assigned Development Team score, within each set-aside, and reviews top-down until credit is exhausted.

Winning does not end document production. Recipients have ten calendar days to accept a Reservation of Credit by returning an executed Reservation Agreement and paying the Reservation Fee. No later than 180 days after Reservation, WHEDA conducts "Application Two" -- a re-review of financial feasibility and revised costs to set the final credit amount, which can move from what was reserved based on updated eligible basis and equity-gap analysis. That process, and everything after it through the 10% test, construction start, and the final 8609 application, is covered in Phase 9 of this guide.

Threshold gates that eliminate applicants before scoring ever matters

WHEDA's market evaluation threshold applies to every application, including tax-exempt-bond deals: WHEDA may reject an application outright for insufficient market demand, an inappropriate site, negative impact on existing multifamily housing already in the market area, or overconcentration -- multiple applications in the same market meeting all other conditions but competing for the same limited demand. Financial feasibility is a second, independent threshold: WHEDA can reject or reduce a Credit request at any stage for infeasibility, an excessive Credit request, or a budget it judges inadequate or excessive against its own maximum-development-cost formula (location-, unit-count-, and project-specific, with public/tribal housing authorities using Choice Neighborhoods or NAHASDA funding exempted). WHEDA can also reject a 9% application it believes could reasonably be done instead with 4% credit and tax-exempt financing, testing that judgment against its own current tax-exempt loan rates, longer amortization, a subordinate second mortgage, a different credit type, a modified unit mix, or deferred developer fees.

Development Team eligibility is its own threshold gate, and it reaches individuals, not just entities: WHEDA runs a background check on every individual holding ownership in the managing member or general partner, and anyone found to have unpaid Wisconsin taxes or child support makes the entire project ineligible for an award -- nonprofit organizations are exempt from this specific check, but their individual officers are not automatically shielded if they hold a disqualifying ownership stake elsewhere in the structure. WHEDA separately evaluates every applicant for a history of noncompliance or unsatisfactory performance in the Housing Tax Credit Program and will notify a team at risk of negative points or outright ineligibility before it commits to a Full Application. Management agents must be WHEDA-certified and appear on the current year's Approved Management Agents list; contractors at every tier must hold current Wisconsin registration and licensure.

A distribution rule buried in the "Requirements for All Credit Types" section applies across every scoring category and income band at once: within each income band a project serves, no fewer than 10% of each bedroom size offered in the project may be designated at that income band -- a proportionality test that can silently invalidate an otherwise attractive unit mix if a developer optimizes bedroom count and AMI targeting independently rather than together.

Market study requirements: a WHEDA-approved provider, an identity-of-interest certification, and a 6-month shelf life

Appendix A requires an independent third-party market study for every Housing Tax Credit development and for most other WHEDA-financed developments (new construction, acquisition/rehab, or adaptive reuse), prepared only by a provider on WHEDA's own published approved-provider list. Every study must carry the provider's certification that no identity-of-interest relationship exists between any officer, director, board member, or authorized agent of any development team member and any other development team member -- financial interest, business partnership, family relationship, or advancing funds or items of value all count as disqualifying identity-of-interest facts under the QAP's own five-part definition.

Studies go "stale" after 6 months. A stale study can be updated by the original provider rather than fully redone, but WHEDA will not accept an updated study more than 18 months after its original date -- concretely, a study submitted for a 2026 application can support an updated 2027 resubmission of the same project, but the same project reapplying in 2028 needs a wholly new study. An update must identify and analyze any new competing developments not covered in the original report, changes in market occupancy and rents, and any other significant economic or demographic shift, and can be submitted as a letter attached to the original report rather than a fresh full study.

WHEDA's own reservation in Appendix A is worth repeating verbatim in spirit: meeting these minimum guidelines "does not ensure acceptance of the study" -- WHEDA can still weigh market factors outside the study itself and deny an application on that independent judgment.

Scoring: a 180-point table, a 65-point floor WHEDA can move, and a three-tier tiebreaker

Two structural scoring rules are easy to trip on. First, a project scoring points under "Tribal, Rehabilitation & Neighborhood Stabilization, or Counties without Recent Awards" is categorically barred from also scoring points under "Areas of Opportunity" -- the two top-line categories are mutually exclusive, not additive. Second, for scattered-site projects, at least two-thirds of units must sit in a single area to be eligible for points at all -- a scattered site that spreads its units too thin forfeits scoring eligibility across the board, not just in location-based categories.

Applicants self-score, and WHEDA layers its own assigned Development Team score on top before ranking within each set-aside; WHEDA will not award points where required documentation is missing, insufficient, or in an unacceptable form, and will not allow any scoring changes once a Reservation has been executed. Where two or more applications tie and there is not enough credit to fund them all, Appendix C resolves the tie in a fixed three-step order: first, preference to an award that would be the only one that year for its developer, co-developer(s), applicant, owner, general partner, and managing member; second, preference to the county with the fewest 9% awards over the previous five cycles; third, a lottery.

Fees due at application, and the flexibility clause worth knowing about

One flexibility clause is worth building into any deadline-tracking tool rather than treating the calendar as absolute: "WHEDA may accept late applications if it has not received an adequate quantity of quality applications." That is a real, stated exception -- not a guarantee a late application will be accepted, but a genuine basis for WHEDA discretion a developer should know exists rather than assuming a missed deadline is automatically fatal.