"Is this site already zoned to build what I want, and is there still money left in my region this year?"
What screening actually looks like in Nevada
The Nevada Housing Division (NHD), part of the state Department of Business & Industry, runs LIHTC on two separate tracks: the 9% competitive process, decided once a year against a fixed statewide pool, and the 4% tax-exempt-bond process, decided project by project against the Nevada Board of Finance's own bond calendar. A site headed for 9% and a site headed for bonds are screened against different clocks from day one, and the 2026 QAP documents a live, mid-cycle example of why that matters: after Congress passed H.R. 1 (the One Big Beautiful Bill Act) in 2025 and lowered the bond-financing test from 50% to 25% of aggregate basis, NHD returned bond deals to a first-come, first-served basis for any project clearing the scoring and readiness thresholds — a rule a screening tool built on an older QAP would simply miss.
| Step | What it involves |
|---|---|
| Parcel record | Pull the parcel from the county assessor, or from the one statewide DWR layer that stitches all 17 jurisdictions together |
| Zoning as gate | Confirm the site is already zoned for the proposed use with no discretionary approval outstanding — NHD's own threshold test, not a density lookup |
| By-right check | Confirm whether the local jurisdiction has adopted its NRS 278.02071 by-right multifamily ordinance yet, and what conditions it attaches |
| Flood hazard | Check FEMA flood |
| Environmental | Screen NDEP's site-cleanup and LUST records, which sit behind a free-account login and have no API |
| Phase I ESA | Line up a Phase I Environmental Study no more than two years old as of the application deadline |
| Market study | Commission a study meeting the 2.5-mile (urban) / 5-mile (rural) radius standard — a comparable-occupancy or competitive-impact finding can make the whole application ineligible |
| Geographic account capacity | Check what's actually left in the site's Clark, Washoe, or Other Counties account after set-asides and forward commitments |
| Cost anchor | Check the flat total-development-cost-per-unit cap for the site's county bucket |
| Comparable awards | Check NHD's own reservation lists, published in XLSX |
The money behind that geographic-account row is thinner than the state's headline number suggests, and the arithmetic is worth walking through before falling for it.
A Clark County site isn't competing against $14.6 million; it's competing for a share of roughly $2.55 million, after everyone ahead of it in the waterfall has already been paid — in a program where the maximum a single applicant can receive from that whole 2026 pool, across every project it touches, is $1,500,000 (Section 12.1).
Two decisions come out of screening in Nevada, as in California and Texas: whether to pursue the site, and what to put in the option or contract. Nevada's tiebreaker (Section 7.5) is a straight ratio — ten-year credit request divided by total project cost, lowest percentage wins — decided by the whole capital stack rather than land price specifically, with a lottery under NAC 319.990 if the ratio still ties. Searching the full 2026 QAP for "appraisal" or "appraised" turns up exactly one hit, in Section 8.1(8), and it applies only to a Qualified Contract bond deal. There is no Nevada equivalent of California's rule discounting a tiebreaker term when purchase price exceeds appraised value; the discipline on an inflated land price runs entirely through the flat total-development-cost cap in Section 6.4, which excludes land, and the 15%-of-eligible-basis developer-fee ceiling in Section 6.6.
The parcel layer: one real statewide service, with a legal catch
Every Nevada county keeps its own assessor parcel data, the same as any state. But Nevada has something California's own screening brief documents as missing entirely: a single agency that standardized county parcels into one statewide service. The Nevada Division of Water Resources publishes a "County_Parcels_in_Nevada" ArcGIS REST MapServer, built from data supplied by the Nevada State Demographer, covering all 16 counties plus the independent city of Carson City — 17 jurisdictions in one schema.
| Field | What it carries |
|---|---|
| APN | Assessor parcel number |
| SiteCity | Not populated by every county |
| Website | Link out to the originating county assessor's record |
| Acres | Parcel size |
| County | Source county |
| SourceDate | Per-county vintage |
| PIN | Secondary parcel identifier |
The service's own metadata does not agree with itself on vintage. The MapServer's root-level description lists 10/22/2024 as the update date for sixteen of the seventeen jurisdictions; the individual parcel layer's own description field, one level down in the same service, instead reads "Last Updated Oct 2022." Those cannot both be true of the same dataset, and a pipeline that trusts whichever description it reads first will report the wrong age for the entire state's parcel data.
The same service description also carries a legal claim worth stating plainly rather than folding into terms nobody reads: it states the underlying data "cannot be shared outside the department as directed by NRS 250," specifically ruling out sharing even with another state agency, while permitting ordinary uses like printing a map for a permit file. NRS Chapter 250 is Nevada's county-assessor confidentiality chapter — the same category of statute California's own guide flags for home-address confidentiality. Whatever that restriction actually reaches, the agency asserting it is also answering unauthenticated REST queries against the same data over the open internet, and a tool built on top of that endpoint should treat the redistribution question as unresolved rather than settled by the fact that the query succeeded.
Zoning is a threshold gate, and the rules under it just changed
Section 6.10 of the 2026 QAP does not ask a screening tool to look up a zone code and a density table the way California's or Texas's guides do. It asks a binary question: is the site appropriately zoned, with no discretionary permit necessary, such that only an administrative building-permit review remains. A site that needs a rezone, a variance, a conditional-use permit, or any other discretionary approval cannot meet this threshold requirement as written — which makes Nevada site screening an entitlement-pathway question before it's a density question.
That threshold got measurably easier to clear for one category of site in 2025, and the change is specific to this program year. NRS 278.02071, added by the 2025 Legislature, requires every Nevada city and county to adopt an ordinance authorizing by-right multifamily or mixed-use residential development on any parcel zoned for commercial use, with a compliance deadline of March 1, 2026 — about fifteen weeks before the 2026 QAP's own June 15 application deadline (May 1 is only when the 2026 application window opens, not the deadline). The statute carves out airport-zoned land and the Tahoe Regional Planning Compact area, and does not reach land zoned industrial. A companion statute, NRS 278.02072, separately requires each jurisdiction to adopt an expedited, incentivized approval process for what NRS 278.0105 defines as "attainable housing."
Neither statute hands a developer an unconditional win. NRS 278.02071 explicitly lets each jurisdiction establish its own standards and requirements to qualify for by-right treatment, which means the ordinance's actual text — not the statute's existence — determines whether a given commercially zoned parcel clears Section 6.10. Because the statutory deadline lands so close to the application deadline, whether a specific city or county has adopted a compliant ordinance at all, and on what terms, is a fact to confirm jurisdiction by jurisdiction rather than assume from the statute's passage. Unlike Texas's Chapter 218, Nevada's statute sets no statewide floor on density, height, or parking — it guarantees a process, not a yield.
Hazard and environmental layers: flood is open, contamination is not
Flood-hazard screening in Nevada runs on the same federal layer California's own screening brief documents: FEMA's National Flood Hazard Layer, public and unauthenticated, with flood zones on layer 28 of the NFHL MapServer. Nothing about Nevada changes that.
| Layer | Access |
|---|---|
| FEMA National Flood Hazard Layer | Public, unauthenticated, federal |
| NDEP Nevada Environmental Activities (site cleanup, LUST, corrective-action cases) | Searchable online only after creating a free account; no API; exports limited to quarterly HTML/CSV/PDF; per the agency's own description, most historical case data still exists only in physical files, reachable through a public-records request |
That access pattern is the same structural fact California's guide documents for DTSC and GeoTracker, just enforced with a login wall instead of an HTTP 403: the hazards most likely to end a Nevada deal — contamination discovered after site control, at Phase I or Phase II — sit behind exactly the barrier a screening product cannot see past. An absence of hits on the open layers says nothing about what NDEP's own case files hold.
Site control means two different things in this QAP
Site control shows up twice in the 2026 QAP, and the two appearances reward different things. Section 6.8, the threshold every application must clear, accepts a fully executed purchase contract or option, a government commitment to transfer the property, or a recorded deed — in substance the same menu California and Texas both use — with its own term attached: the Initial Term must run at least through December 31 of the reservation year, and cannot be conditioned on anything requiring the seller's further consent. Section 7.3.2, five points inside the scoring rubric, asks something narrower and easy to miss: those points go only to an application where an entity holding a general-partner or managing-member interest in the ownership entity already holds fee-simple title to the site, or — for Tribal housing, a Public Housing Authority, or a rent-to-own project specifically — a lease of 50 years or more (15 to 20 years for rent-to-own). An ordinary option or purchase contract, the instrument that satisfies the Section 6.8 threshold, earns zero points under Section 7.3.2. A developer counting on those five points needs to have actually closed on the land, through an affiliated entity, before applying — not merely locked it up.
Nevada also runs its own state tax credit alongside the federal one — the Nevada Transferable State Tax Credit, authorized by NRS 360.830 through 360.870 and detailed in Appendix C of the QAP, sized on a sliding scale up to $4,000,000 for a project of 201 or more units. It carries a site-control deadline of its own, separate from the LIHTC program's: within 270 days of the Division's written TSTC reservation notice, the sponsor must show it has purchased and holds fee-simple title to the project site. Pursuing TSTC financing means committing, at the point of applying for that credit, to convert an option into a closing well before most 9% deals reach carryover.
Cost caps, the basis boost, and a competitive check with no fixed radius
| County bucket | Most project types | Rent-to-Own & Tribal Housing |
|---|---|---|
| Clark County | $350,000 | $530,000 |
| All Other Counties (including Washoe, and USDA) | $370,000 | $540,000 |
Washoe County gets its own 29% share of the credit pool under Section 2.5's geographic accounts, but for this cost cap it falls into the same "All Other Counties" bucket as everywhere outside Clark — the three-way split that allocates credits and the two-way split that caps cost are not the same map.
Section 11's eligible-basis boost is also structured differently from California's. Both let a qualifying project use 130% of eligible basis, but where California gates its version of that increase behind a specific dollar threshold on the county's unadjusted 9% two-bedroom basis limit, Nevada opens the same 130% boost through seven independent doors: the Other Counties geographic category, an Opportunity Zone or a census tract that isn't CDBG-eligible, the USDA-RD set-aside, Special Needs housing, Supportive Housing, deferring at least 30% of the developer fee, or a high- or moderate-income tract as defined by the Federal Financial Institutions Examination Council. Bond-financed 4% deals are the exception: Section 11 limits their boost eligibility to an actual federally designated DDA or QCT, with none of the state-specific doors 9% deals get.
Nevada has no fixed-mileage de-concentration statute of the kind Texas writes into law. Section 6.1's threshold requirements can make an application ineligible outright if a comparable project runs under 90% occupancy, or if the new project would cause a significant adverse financial effect on other publicly funded projects — and Appendix A's Market Study Guide defines the relevant radius for that judgment as a function of population density rather than a stated number of miles, on top of a flat 2.5-mile market-area radius in urban areas and 5 miles in rural ones. That leaves the actual competitive-conflict call inside the market study itself, prepared by an analyst from NHD's own approved list, rather than inside a GIS query a screening tool could run on its own.
Nevada's negative-points equivalent lives in Section 16: beyond outright rejection for appearing on a federal, state, or local debarred list, the Division can reject an application or cut its score by up to 10 points across eleven enumerated grounds — an incomplete application, a material misrepresentation, a prior default or foreclosure on a HOME, NHTF, LIHTC, or bond deal, a felony conviction or fraud investigation, and similar compliance failures. A separate, flat 3-point deduction applies to any application that requests a waiver of any QAP requirement, for any reason.
Where this goes wrong
- Treating an executed purchase contract or option — which satisfies the Section 6.8 site-control threshold — as if it also earns the Section 7.3.2 scoring points. Those 5 points require fee-simple title already held by the GP/managing-member entity, or a qualifying long-term lease for Tribal, PHA, or rent-to-own deals.
- Assuming a favorable purchase price protects a 9% application the way it does in California. The 2026 QAP does not tie acquisition price to appraised value anywhere in the 9% competitive process; the document's sole appraisal reference (Section 8.1(8)) applies only to a Qualified Contract bond deal.
- Reading the DWR statewide parcel service as a general-purpose county dataset. Its own metadata states the data cannot be shared outside the department under NRS 250, including with another state agency, even though the REST endpoint answers public queries.
- Trusting the parcel layer's vintage without checking both description fields. The MapServer's root description lists most counties as refreshed 10/22/2024; the individual layer's own description instead reads "Last Updated Oct 2022" — the two disagree inside the same service.
- Assuming Esmeralda County has native digital parcels. It doesn't; the state's own layer sources Esmeralda from a commercial vendor (Regrid) instead.
- Treating coordinates from the statewide parcel layer as WGS84. They're published in EPSG:26911 (NAD83 UTM Zone 11N).
- Assuming a commercially zoned site automatically clears the QAP's Section 6.10 threshold because of NRS 278.02071. The statute lets each jurisdiction set its own qualifying standards, and its March 1, 2026 compliance deadline sits weeks before the 9% application deadline — whether a given city or county has actually adopted a compliant ordinance has to be checked directly.
- Confusing NRS 278.02071 (by-right multifamily on commercial land) with a density or height guarantee. The statute authorizes by-right process; it sets no statewide minimum density, unlike Texas's Chapter 218.
- Presenting NDEP's contamination and LUST data as queryable the way FEMA flood data is. The Nevada Environmental Activities system requires a free account, has no API, and much of its older material exists only as physical records reachable through a public-records request.
- Assuming a project's 9% tiebreaker position is set at LOI. Nevada's tiebreaker (Section 7.5) is a credit-request-to-total-project-cost efficiency ratio decided by the whole capital stack, not by acquisition price alone.
- Pursuing the Nevada Transferable State Tax Credit without accounting for its own site-control deadline. Appendix C Section D5 requires fee-simple title within 270 days of the TSTC reservation notice — a harder deadline than the LIHTC program's own site-control threshold.
- Modeling the Section 11 eligible-basis boost as gated the way California's Opportunity Area bump is. Nevada's 130% boost opens through seven independent doors with no dollar-based county gate; bond deals, unlike 9% deals, only get the boost inside an actual DDA or QCT.
- Treating the market study's competitive-impact check as a fixed-mileage rule. Section 6.1 can make an application ineligible over comparable-project occupancy or financial harm to other publicly funded properties, but the QAP defines the radius as a function of population density, not a stated number of miles.
- Screening a Clark County site against the state's total $14.6 million 2026 estimate. After forward commitments and set-asides, the Clark County geographic account for new 9% awards is roughly $2.55 million, and that number is fixed before any single application is scored.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies
