Analysis Β· LIHTC

LIHTC Opportunity Finder

Colorado jurisdictions (cities, towns, CDPs) with QCT (Qualified Census Tract) and/or DDA (Difficult Development Area) designations, ranked for 4% bond and 9% competitive LIHTC targeting. Sortable by last placed-in-service year, HNA need score, and population. Combines funding-recency, housing need (Scorecard v2 composite), basis-boost eligibility (IRC Β§42(d)(5)(B)), and population β€” re-weighted per round (4% bonds emphasise scale, 9% emphasises geographic gap).

Screening tool only. Opportunity scores are a starting point for site identification. Final LIHTC site selection requires a formal CHFA-required PMA, market study, and developer underwriting. All data is public (CHFA/HUD LIHTC, HUD QCT/DDA designations, ACS, CHAS, TIGER place-tract spatial joins) β€” no proprietary signals.

βœ“ Data source: LIHTC projects pulled live from CHFA's public Housing Tax Credit Properties layer β€” 926 projects through 2025 (the 2025 awards have just been added). The recency score uses CHFA's AwardYear field, which is when CHFA reserved the credits (typically 2–3 years before placed-in-service). For saturation/recency scoring this is the better signal than HUD's lagged YR_PIS β€” a 2024 award means "there's a deal coming" even if construction hasn't completed. ComplianceStatus tracks whether the project is already placed in service. Methodology Β§3 Dim 2 β†’
Loading data…
What does "opportunity score" mean? Each Colorado place gets a 0–100 score answering: given the deal type you picked above, how attractive is this jurisdiction for a developer searching for the next LIHTC project? Higher = more pursuit-worthy. The score blends 5 signals (housing need Β· LIHTC saturation gap Β· federal basis-boost Β· renter scale Β· civic readiness) with weights that re-tune by deal type. The summary card on the right tells you which weights are active right now. Full methodology ↓
β€” of β€” jurisdictions
Score Jurisdiction Type County Last funded Projects Need p Pop. Capture Civic Prop 123 Progress Alt scores
Loading…

How this locator works

A LIHTC locator answers "where should a developer spend scarce time looking for the next deal?" It is not a site-screen β€” it narrows 482 Colorado jurisdictions to a credible shortlist of 5–15. Everything below the jurisdiction level (parcel, utilities, zoning, environmental) requires site work. Full methodology β†’

The three questions the locator separates

  1. Where is housing need acute? β€” high cost burden, deep AMI gap, severe rent burden
  2. Where is a deal executable? β€” basis-boost eligibility, civic readiness, population scale
  3. Where is competition light? β€” funding-recency headroom, LIHTC saturation gap

The locator never collapses these into a single black-box score. You see why a jurisdiction rises and can re-weight the dimensions for your own deal strategy.

The universe β€” which jurisdictions get scored

Starts with Colorado's 482 incorporated places, towns, and CDPs (TIGER 2024). Each target deal type then filters this universe differently. Today's implementation ranks the 158 jurisdictions with QCT and/or DDA designation (basis-boost eligible). Target state adds preservation, workforce-resort, and Prop 123 deal types with relaxed designation requirements.

Target deal typeUniverse filterCO count
9% Competitiveβ‰₯1 QCT tract OR DDA county158
4% Bond (basis-boost)β‰₯1 QCT tract OR DDA county158
PreservationLIHTC w/ expiration ≀ 2030~20 (planned)
Workforce / ResortResort county subset, pop β‰₯1,000~15 (planned)
Prop 123 LocalProp 123 βœ“ AND (comp plan OR HNA OR housing lead)~80 (planned)

How each jurisdiction is scored

Every Colorado place gets five 0–100 scores. The scores answer five questions a developer asks about any deal site. They're blended into a composite using weights that change depending on what kind of deal you're trying to do (see the deal-type table below).

  1. Housing Need β€” how stressed is the rental market here?
    Combines what share of renters and owners pay more than 30% of income on housing, what share pay more than 50% (severe burden), and how many low-income households can't find an affordable place at their income. Then ranked against every other Colorado jurisdiction, so a score of "87" means this place is the 87th-percentile most-stressed market in the state.
    Data: HUD's CHAS housing-cost dataset (2018–2022) + Census American Community Survey rent-burden tables. (technical detail: tenure-blended cost burden + severe burden + AMI gap, percentile-normalized; CHAS Table 7 + ACS DP04 GRAPI/SMOCAPI)
  2. Recency β€” how long since the last LIHTC deal closed here?
    A community that hasn't received a CHFA award in 15+ years has more geographic-balance headroom under CHFA's framework. Score caps at 25 years (anything older, or never funded, scores the max). For 9% Competitive deals this is one of the larger contributors because CHFA's QAP gives explicit weight to geographic distribution.
    Data: CHFA's live property feed β€” 926 Colorado projects from 1987–2025. We read CHFA's "Award Year" rather than HUD's "Year Placed in Service" because an award reserved in 2024 represents committed CHFA capital in the community, even if construction has not yet started β€” and that reflects the same signal CHFA's own QAP weighs when balancing geographic distribution.
  3. Basis Boost β€” does the IRS give this place a bigger budget?
    The federal LIHTC statute (IRC Β§42) gives a 30% bigger eligible-basis cap to deals in federally-designated low-income areas. That translates to roughly $3–5M of extra equity on a typical 60-unit project β€” a hard math line, not a soft preference. Score: 100 if the place is in both a Qualified Census Tract (QCT) and a Difficult Development Area (DDA); 60 if just one; 0 if neither.
    Data: HUD's 2026 QCT designation list (224 Colorado tracts) + HUD's 2026 DDA list (10 Colorado nonmetro counties).
  4. Population β€” is the renter base big enough to fill the building?
    A 60–100 unit project needs to lease up to ~95% in 12–18 months. Score scales from 0 (places under 500 people) to 100 (15,000+). Most important for 4% bond deals which usually need 100–200 units absorbing quickly; less critical for 9% deals which can be smaller (40–60 units) in a tighter market.
    Data: CHAS households at or below 100% AMI Γ— 2.5 average household size β€” a proxy until raw ACS B01003 population is wired in.
  5. Civic Readiness β€” is the local government actually ready to support a deal?
    Seven yes/no checks against what makes a deal smooth: did the place file a Prop 123 commitment with DOLA, do they have a current Housing Needs Assessment, do they have a comprehensive plan, do they have an inclusionary-zoning ordinance, do they run their own affordable-housing fund, do they have a housing authority, and are there affordable-housing nonprofits active here? The more yeses, the higher the score (out of 100). A Prop 123 filing is referenced in CHFA QAP scoring criteria; the other six matter for permit timelines, letters of support, and soft-debt sources to stack with the LIHTC equity.
    Data: hand-curated policy scorecard (547 Colorado jurisdictions Γ— 7 dimensions) + DOLA's Prop 123 commitment list (217 jurisdictions filed) + the local-resources directory.

Two more signals show up as columns but not in the composite score β€” Market Capture (the gap between FMR market rent and LIHTC 60% AMI max rent β€” tells you whether the deal can pencil at 60% AMI or needs a deeper mix) and Prop 123 status (filed / not filed / N/A for CDPs). Both surface in the table so you can screen on them; they're not bundled into the score because they're decision-critical thresholds rather than smooth gradients.

Does HUD FMR match CHFA's rent requirement?

No β€” they're related but different numbers. CHFA does publish annual Multifamily Rent & Income Limits tables (released ~30 days after HUD's MTSP income-limit announcement), but those tables are CHFA's derivative output β€” not an independent source. They're computed from HUD's published 4-person AMI for the county using the Β§42 formula:

LIHTC monthly rent ceiling = AMI4-person Γ— tier_pct Γ— 0.30 Γ· 12

The "Capture" column compares HUD FMR (the 2BR Fair Market Rent for vouchers/Section 8) against this LIHTC 60% AMI 2BR ceiling. FMR is the best free public proxy for actual market rent, but it's an APPROXIMATION:

  • FMR is published at the HUD-defined "FMR area" level β€” a metro or non-metro county group. In CO, Denver-Aurora-Lakewood Metro FMR covers Denver + 9 surrounding counties at one number.
  • LIHTC AMI is published per county β€” Adams and Denver share an AMI but a rural CO county has its own (much lower) AMI.
  • FMR is biased low for rural markets β€” HUD intentionally sets it at the 40th percentile of recent gross rents. In rural CO, this can run $50-200/mo below the LIHTC 60% ceiling, producing a NEGATIVE capture.

Bottom line: negative capture is a warning, not a no-go. CHFA still wants a project to lease up at the LIHTC ceiling β€” they require a Project Market Analysis (PMA) by an approved analyst to verify achievable rent. Use Capture as a screen; verify with a real market study (CHFA-approved PMAs run ~$15K-40K) before committing to a deal in a low-FMR market.

Per-deal-type weighting (re-tuned live by your target selection)

Different deal types succeed on different signals. The locator doesn't use one fixed weighting β€” it re-tunes the formula based on which round you're trying to compete in. Here's what each deal type is actually optimizing for, in plain English:

9% Competitive β€” geographic-gap is the differentiator

9% deals are scarce β€” Colorado gets roughly 30–40 awards a year for hundreds of applicants. CHFA's Qualified Allocation Plan explicitly rewards geographic distribution and underserved-market scoring categories, so the single biggest predictor of success is "this jurisdiction hasn't been funded recently." Need still matters (CHFA scores deeper income-targeting), but a high-need market that just got two awards last cycle is harder than a moderate-need market that hasn't seen LIHTC in 15 years. Population and civic readiness matter less than for other deal types because 9% awards go through CHFA's most rigorous diligence β€” they evaluate readiness during application rather than relying on pre-screening.
Heaviest: Need (30%) + Recency (22%) + Civic (18%)

4% Bond β€” population scale is the differentiator

4% bond deals are non-competitive (you "buy your way in" via private-activity bonds), so saturation matters less. What kills 4% deals is not enough scale to absorb the transaction. Bonds carry fixed costs (issuance fees, trustees, legal, ongoing compliance) that only pencil at 100+ units; smaller deals can't carry that overhead. A 60-unit 4% bond deal in a 1,500-person town typically doesn't work; the same project on 9% credits often does. Population is therefore the dominant factor. Civic readiness matters more than for 9% because the local jurisdiction has to issue the private-activity bonds β€” they need an active housing finance authority or a willing partner.
Heaviest: Population (30%) + Need (25%) + Civic (18%)

Preservation β€” basis-boost stacking is the differentiator

Preservation deals refinance and re-syndicate existing LIHTC properties whose initial 15-year compliance period is ending. The economics depend almost entirely on the subsidy stack: you're combining 4% acquisition/rehab credits with expiring LIHTC, possibly Rental Assistance Demonstration (RAD), maybe HOME or CDBG, and a refi of the existing permanent loan. Basis-boost eligibility (QCT/DDA) is the biggest single lever. Recency matters less because preservation deals deliberately target a sub-market with proven existing absorption β€” the LIHTC units already exist and are already leased. Population matters less because you're working with an existing project's footprint. Civic readiness matters for the refi entitlement (some jurisdictions require new public hearings on preserved deals).
Heaviest: Basis/Subsidy (35%) + Civic (20%) + Need (20%)

Workforce / Resort β€” scale + civic capacity (resort towns punch above their weight)

Resort and workforce-housing markets (Aspen, Steamboat, Vail, Crested Butte, Durango) have severe need but tiny populations. They've adapted by building strong civic housing strategies β€” dedicated funds, employer partnerships, strong housing authorities. A typical workforce deal involves bond financing (so scale matters), a local employer or resort backing the offer, and a sophisticated public-private entitlement path. Basis-boost is less of a differentiator because resort markets often don't qualify for QCT and only some are in DDA counties. The lock is execution capacity: can this town actually deliver a 100-unit bond deal in 24 months?
Heaviest: Need (25%) + Population (25%) + Civic (20%)

Prop 123 Local β€” civic readiness IS the gate

Prop 123 (HB22-1304) created two state-funded affordable-housing programs that require local jurisdictions to commit to a 3% annual baseline expansion of affordable housing stock before they can access state dollars. Without the commitment, no Prop 123 deal happens β€” full stop. So the differentiator isn't need or market size, it's "has this jurisdiction done the local-policy work to unlock the state funding stack?" Prop 123 βœ“, comp plan βœ“, housing lead βœ“, housing authority βœ“, local funding βœ“, IZ ordinance βœ“ β€” those seven civic-capacity flags decide whether a deal is even legally possible. Basis-boost matters less because Prop 123 dollars don't require federal QCT/DDA designation. Need still matters (the funds prioritize high-need markets), but readiness gates everything.
Heaviest: Civic (30%) + Need (25%) + Basis/Subsidy (20%)

Balanced (Any) β€” exploratory, no specific lens

For exploratory work when you haven't picked a deal type yet. Roughly equal distribution across all five dimensions surfaces jurisdictions that score well on multiple dimensions rather than one. Use this when scouting CO for new deal opportunities and want a broad list to narrow from.
Balanced: ~20% each

The numerical table below summarizes these weights. The highlighted cells in each column show the heaviest dimension(s) for that deal type.

How to read this table

Each column is a deal type you might pursue. Each row is a scoring dimension. The cell value is the percentage of the composite score that the dimension contributes when that deal type is selected. Every column sums to 100%.

Read down a column to see what the locator values for that deal type. Read across a row to see how a single dimension's importance shifts from one deal type to another. The cells with the highlighted value flag the heaviest dimension(s) for that deal type β€” the signal that's most likely to separate winners from losers in that strategy.

What each column / row means β†’

Columns β€” deal types:

  • 9% Competitive β€” annual capped-allocation tax credits awarded by CHFA through a competitive scoring round. Roughly 30–40 awards/year statewide. Geographic distribution is heavily scored in the QAP.
  • 4% Bond β€” non-competitive credits paired with tax-exempt private-activity bonds. No award cap, but bond issuance costs and underwriting standards favor larger projects (100+ units).
  • Preservation β€” 4% acquisition/rehab deals refinancing existing LIHTC properties at Year-15 (compliance period ending). The opportunity is the existing subsidy + occupancy, not new construction.
  • Workforce-Resort β€” bond deals in mountain/resort communities (Pitkin, San Miguel, Summit, Eagle, Routt, Garfield, La Plata, Grand) where severe workforce pressure meets small population.
  • Prop 123 Local β€” state-funded deals via HB22-1304's Affordable Housing Financing Fund or Support Fund. Requires the jurisdiction to have filed a Prop 123 commitment with DOLA.
  • Balanced β€” no specific lens; weights all dimensions roughly equally for exploratory scouting.

Rows β€” scoring dimensions:

  • Need β€” tenure-blended cost burden + severe burden + AMI gap, percentile-normalized against CO peer jurisdictions (see Β§3 Dim 1 above).
  • Recency / Competition β€” years since the jurisdiction's last LIHTC project was placed in service (25-year cap, never-funded = max).
  • Basis / Subsidy β€” strength of the subsidy stack: QCT-only or DDA-only = 60, both = 100, neither = 0 (IRC Β§42(d)(5)(B) basis boost).
  • Population / Feasibility β€” bucketed by HHs ≀100% AMI Γ— 2.5: under 500 = 0, 500–2k = 30, 2k–5k = 60, 5k–15k = 85, β‰₯15k = 100.
  • Civic Readiness β€” count of 7 binary civic-capacity dimensions (Prop 123 βœ“, comp plan, HNA, IZ, local funding, housing authority, nonprofits) divided by known dims, Γ—100.

Example read β€” column "Prop 123 Local" has Civic Readiness at 30% (highlighted, heaviest). That tells you: when you pick the Prop 123 Local target, the score will rise most for jurisdictions with strong civic capacity, even if their need or LIHTC saturation is moderate. The same dimension contributes 18% in the 9% Competitive column β€” meaningful but secondary to housing-need depth and saturation gap, because CHFA's competitive round will also evaluate civic readiness during its own due diligence.

Row badges β€” what "R1" and "W" mean β†’

R1  CHFA 2026 Round One award. Bridge-file signal that the jurisdiction landed one or more awards in the CHFA 2026 R1 announcement (2026-05-21). The live ArcGIS feed lags 2–3 months behind round announcements, so this is a fresh-news flag that disappears when the live feed catches up. Hover the badge to see the award count.

W  Communities likely returning to CHFA in a near-term round. A planning aid for a developer's own outreach calendar β€” surfaced when four publicly observable signals all align in the same community: years since last CHFA-supported award against the community's prior CHFA history, documented housing need (top quintile or top decile in data/hna/ranking-index.json), policy readiness (Prop 123 commitment, dedicated housing revenue, adopted HNA), and multi-phase project sequencing visible in CHFA's portfolio (regex over CHFA project names β€” e.g., a previously awarded "Phase II" suggests a "Phase III" partnership conversation may be active). When all four align, the public-records signal is "this community may already be back in conversation with CHFA β€” worth tracking in near-term monitoring."

Important context: CHFA's public records show award history, not application history. The W badge is therefore a proxy for likely repeat-conversation timing β€” never a prediction of how CHFA will score any specific application, and never a claim that a specific applicant is filing again. Use it for respectful public-records monitoring, not to second-guess CHFA's process. See data/policy/chfa-watchlist.json for the per-community evidence trail.

Dimension 9% Competitive 4% Bond Preservation Workforce-Resort Prop 123 Local Balanced
Need30%25%20%25%25%25%
Recency / Competition22%12%15%15%10%20%
Basis / Subsidy15%15%35%15%20%15%
Population / Feasibility15%30%10%25%15%20%
Civic Readiness18%18%20%20%30%20%

These weights are live in the composite today β€” all five dimensions including Civic Readiness, all six deal types. The F9 rebalance (2026-05-26) lifted civic from 10–15% to 18–20% on 9% / 4% / Workforce-Resort because local Prop 123 commitment, IZ ordinance, housing-authority infrastructure, and soft-debt match proved to matter more than the original 4-dimension model credited. CDPs (unincorporated places) get a βˆ’8 composite adjustment on incorporation-sensitive targets (9% / 4% / Workforce-Resort / Balanced) because they lack independent permitting authority. See methodology doc Β§4 for full derivation.

Confidence β€” surface uncertainty, don't hide it

Every score carries a confidence rating reflecting input quality. Confidence does not change the composite β€” it changes how the result is presented.

  • β˜…β˜…β˜… High β€” all five dimensions from direct data; civic β‰₯ 5 of 7 dims filled; no major fallback used
  • β˜…β˜… Medium β€” at least one dimension uses a fallback OR civic 3–4 of 7 OR population is a proxy
  • β˜… Low β€” multiple fallbacks OR civic <3 of 7 OR major dimension missing entirely

Confidence pills next to every metric are sprint-1 work; today the locator surfaces this as table column hover-tooltips and detail-panel inline notes.

How to use the result β€” a developer's decision flow

  1. Filter. Pick a target deal type. Locator re-weights + re-filters.
  2. Read top 10. Sort by composite. Skim reasons (does the rise make sense?) and risks (does any flag disqualify?).
  3. Cross-check civic. Strong scores but no Prop 123 + no housing lead + no comp plan = harder to execute. Flag for early conversation.
  4. Funnel forward to HNA. Click "πŸ“‹ Open HNA" β€” verify locator signal matches deeper needs picture.
  5. Funnel forward to PMA. Click "πŸ—ΊοΈ Run market analysis" β€” verify rental demand, comparable rents, amenities, no infrastructure or environmental risk.
  6. Build a concept. Click "πŸ’΅ Build deal concept" β€” test 9% (30–60 units, 30/50/60 AMI) vs 4% (100–200 units, 50/60/80 AMI). See which pencils.
  7. Export memo. Take it to your pipeline meeting. (planned)

Output bands

These bands describe where each community sits in a public-data readiness lens β€” not a public ranking of communities. Every community can move between bands as plans, partnerships, and funding postures evolve.

ScoreBandLetterInterpretation
85–100HighA / A-Active partnership conversation β€” proceed to PMA
70–84HighB+ / BBuilding together β€” confirm community civic readiness
55–69MediumB- / C+Worth a deeper read; the right deal type makes the difference
40–54MediumC / C-Long-horizon signal; a clear local housing theme would be needed
25–39LowDTiming not aligned right now β€” recent CHFA activity in the area or community scale
0–24Not-readyFNot the right round to pursue unless a specific local opening exists

What this locator does NOT do

Be honest about scope. The locator is a jurisdiction-level screen, not site-screening or underwriting.

Out of scopeWhyWhere to go instead
Parcel readinessNo parcel data layerCounty Assessor + zoning lookup
Utility / water / sewer capacityNo data layerDistrict-by-district inquiry
Floodplain / wildfire / wetlands / slopeNo env layerFEMA, USFS, USACE
Zoning compatibilityNo layerLocal planning department
Walkability / transit / grocery accessLayer exists, not yet wired inHNA Site Selection Score page
Detailed AMI / unit-mix recommendationOut of scopeLIHTC Concept Recommender (PMA page)
Capital stack sizingOut of scopeDeal Calculator
CHFA pipeline / NOFA timingManualCHFA QAP + award announcements

Caveats & known data quirks

  1. HUD YR_PIS = 8888 placeholders (in-pipeline projects) are excluded from recency.
  2. Project-to-jurisdiction matching uses PROJ_CTY string equality β€” a misspelled PROJ_CTY ("Ft Collins" vs "Fort Collins") misses match. Fuzzy-match is a backlog item.
  3. Population is approximate β€” derived from CHAS HHs ≀100% AMI Γ— 2.5 avg HH size, not direct ACS B01003. Resort areas with high second-home stock are actually closer to the renter-base truth via HH proxy than via B01003.
  4. QCT-place membership requires tract's share of place > 5% OR place's share of tract > 20%. Sliver overlaps don't claim a QCT.
  5. DDA designation in CO is county-based (all 10 CO DDAs are nonmetro counties); all jurisdictions in DDA counties inherit the designation.
  6. Civic-capacity coverage is sparse. ~70% of jurisdictions have populated scorecard records; ~30% rely on county-level inheritance.
  7. Recency uses YR_PIS (placed in service) which lags awards by 2–3y. A jurisdiction with 2024 awards but no PIS yet looks "stale." CHFA-pipeline integration is a backlog item.

Data sources

  • HUD QCT 2025 β€” 224 CO tracts (data/qct-colorado.json)
  • HUD DDA 2025 β€” 10 CO nonmetro counties (data/dda-colorado.json)
  • CHFA HousingTaxCreditProperties_view (live) β€” 926 CO projects 1987–2025 (data/chfa-lihtc.json; HUD LIHTCDB fallback data/market/hud_lihtc_co.geojson with 716 projects through 2020)
  • HUD CHAS 2018–2022 β€” county-level (64) + tract-level (1,447 records)
  • TIGER 2024 β€” place-tract spatial join (data/hna/place-tract-membership.json)
  • DOLA Prop 123 commitments β€” 217 filings (data/policy/prop123_jurisdictions.json)
  • Housing policy scorecard β€” 547 jurisdictions Γ— 7 civic dimensions (data/policy/housing-policy-scorecard.json)
  • Local resources β€” housing leads, authorities, advocacy URLs (data/hna/local-resources.json)