Entitlement pathway election — Virginia

Dillon's Rule, precisely: Virginia localities have only what the General Assembly gives them

Virginia is one of the states that follows Dillon's Rule as a strict default: a local governing body's powers extend only to those (1) granted in express words by the General Assembly, (2) necessarily or fairly implied from an expressly granted power, or (3) essential and indispensable to the locality's declared purposes — not those merely convenient. A well-established corollary softens the third prong somewhat: where the General Assembly has granted a power but not specified the method of exercising it, a locality retains reasonable discretion over how to implement that power. Zoning survives Dillon's Rule scrutiny only because the General Assembly has affirmatively and broadly delegated it — nothing about zoning authority is inherent to Virginia counties, cities, or towns the way it might be treated in a home-rule state.

The practical consequence for entitlement screening is the mirror image of a home-rule state's problem: instead of asking "does this locality's charter or ordinance-making tradition let it do X," the question in Virginia is always "did the General Assembly say localities may do X" — and if the answer isn't a clear statutory yes, the locality's attempt to regulate that way is vulnerable to challenge regardless of how long the practice has gone unquestioned locally.

Title 15.2, Chapter 22: the enabling statute underneath every local zoning ordinance

The general zoning enabling authority for Virginia's counties, cities, and towns sits in Title 15.2, Chapter 22 ("Planning, Subdivision of Land and Zoning"), with Article 7 specifically headed "Zoning." The core grant of power, §15.2-2280, authorizes a locality to "classify the territory under its jurisdiction or any substantial portion thereof into districts" and to regulate land uses (agricultural, business, industrial, residential, floodplain), physical structures (height, bulk, size, location), space and lot-size requirements, and the excavation or mining of natural resources — whatever the locality determines is "best suited to carry out the purposes" of the zoning article. Section 15.2-2283 ties that authority directly to the locality's comprehensive plan, requiring zoning ordinances to be "designed to give reasonable consideration" to it.

Virginia has no CEQA-style state environmental-review statute layered on top of local zoning or site-plan approval the way California does — a screen built against a California or similar checklist should not expect to find an analogous state-level environmental-review gate here. Federal environmental review (NEPA, Section 106, and similar) still applies wherever a federal funding source or federal action is present, entirely independent of anything Virginia's own zoning statute requires.

What Virginia Housing actually asks for: certification, not entitlement narrative

The QAP's own zoning threshold is narrow and binary rather than a scored readiness narrative: "written evidence satisfactory to the authority (i) of proper zoning or special use permit for such site or (ii) that no zoning requirements or special use permits are applicable" (13VAC10-180-50(D)(5)). On its face, that requires zoning to already be proper at the site — not merely in process — and the Manual's operational version confirms that reading: the required Zoning Certification must state the zoning classification "without substantive modification," signed no more than three months before the Application deadline by the locality official or a Virginia-registered professional civil engineer (Manual §6.6.13). Unlike some states' threshold checklists, there is no separate accommodation in the QAP's own text for a governmental letter merely describing a path and timeline to future zoning approval in lieu of the certification itself.

A separate, additive 10-point scoring item rewards "written evidence satisfactory to the authority of unconditional approval by local authorities of the plan of development or site plan for the proposed development or that such approval is not required" (13VAC10-180-60(E)(1)) — a distinct, typically later-stage local process from the zoning classification itself. A site can be properly zoned and still be short of this points item if its plan of development or site plan has not yet cleared unconditional local approval.

HB 888: a new, already-effective statewide floor under local parking minimums

The 2026 General Assembly session produced Virginia's first real statutory dent in local zoning discretion in this area: House Bill 888, codified as new Va. Code §15.2-2209.4 and amending §15.2-2279, caps how much off-street parking a locality may require near transit. Within one-half mile of a qualifying Metrorail station or certain local bus service, a locality may not require more than 0.5 parking spaces per dwelling unit for multifamily or mixed-use residential development, or more than 1 space per unit for one- and two-family dwellings or townhouses — and it may not impose a higher requirement as a condition of development approval, nor adopt or enforce a zoning ordinance exceeding those caps. Localities over 20,000 in population must also establish an administrative process letting a developer obtain at least a 20% reduction in minimum parking for residential, multifamily, or mixed-use projects that aren't near transit. A narrow carve-out lets localities over 600,000 in population — currently only Fairfax County — impose higher minimums near locally managed bus stops, provided they still offer their own reduction process. Governor Spanberger signed HB 888 in April 2026, and it took effect July 1, 2026 — meaning it is already binding on every Virginia locality as of this research, not a future consideration.

This is meaningfully narrower than a Live Local Act-style preemption: HB 888 only caps parking minimums, and only near transit (or, for the administrative-reduction requirement, only in larger localities generally). It says nothing about use, height, density, or by-right approval — a site still has to clear the locality's own zoning classification and any discretionary approval process the way it always did. What changes is one specific, previously local, cost-driving variable.

SB 531: a by-right ADU mandate that mostly doesn't reach a LIHTC family or senior deal — yet

Senate Bill 531 (2026 Session), patroned by Sens. Kannan Srinivasan and Saddam Salim after several earlier bipartisan attempts failed in prior sessions, requires every locality to permit accessory dwelling units by-right in districts zoned for single-family homes, caps ADU permit fees at $500, bars setback requirements larger than those applied to the primary dwelling, and eliminates any requirement that an ADU's occupants be related to the primary household. Governor Spanberger signed it in mid-April 2026, but the law does not take effect until July 1, 2027 — a full year after HB 888's already-live parking caps.

For most standard multifamily LIHTC deals, SB 531 doesn't change the entitlement pathway directly — it governs single-family-zoned accessory units, not the multifamily or mixed-use zoning classifications the bulk of Virginia's tax-credit pipeline uses. Its relevance to this phase is more structural than immediate: it is a concrete, dated signal that the General Assembly has become willing to narrow Dillon's Rule zoning discretion by statute where it previously left the question entirely to localities, and it is worth tracking for any scattered-site, missing-middle-adjacent, or small-unit-count product that might genuinely use single-family-zoned parcels once the mandate takes effect.

TEFRA: the federal public-hearing gate underneath every bond-financed 4% deal

Separate from anything Virginia's own zoning statute requires, every tax-exempt private activity bond — including the bonds behind a 4% LIHTC deal — has to clear the federal TEFRA public-approval requirement at 26 U.S.C. §147(f): the bond issue is not a qualified private activity bond unless it receives public approval, either through the "applicable elected representative" following a public hearing for which reasonable notice was given, or by voter referendum. Virginia Housing's own practice, evidenced by its own published hearing notices, is to conduct this hearing itself, on an omnibus basis covering many developments' bonds in a single notice and a single hearing rather than one hearing per project — a materially different administrative pattern from a locally issued conduit bond, where a city or county's own governing body typically holds the hearing and gives the approval.

What this research could not confirm is the specific identity of the "applicable elected representative" who provides the formal §147(f) approval following Virginia Housing's hearing for its own bond issues — whether that is the Governor (consistent with the general federal treatment of a statewide issuer under the Treasury regulations implementing §147(f), where a bond issuer with jurisdiction over an entire state typically looks to the Governor or the state legislative body for approval) or some other designated official or body. The QAP separately requires that the QAP itself be adopted "subject to public approval in accordance with rules similar to those in §147(f)(2) of the IRC" (13VAC10-180-40) — a distinct process from the bond-specific TEFRA hearing described above, and one that should not be confused with it. Confirm the specific bond-approval chain directly with Virginia Housing's Legal Division or rental lending team before relying on an assumed procedure for a given bond-financed deal.

What is contested, draft, or unverified

Several items surfaced in this research that could not be fully resolved and should be verified directly before being relied on in an application or a screening tool: (1) whether a broader 2026 by-right multifamily-in-commercial-zones bill (reported as introduced by Sen. Schuyler VanValkenburg and Del. Dan Helmer) actually passed and was signed, as distinct from the parking (HB 888) and ADU (SB 531) bills that clearly did; (2) the precise identity of the "applicable elected representative" completing TEFRA approval for a Virginia Housing-issued bond, discussed above; (3) whether Virginia Housing's own bond issuances draw against the same DHCD-administered private-activity-bond volume-cap allocation that governs locally issued conduit bonds, or operate under a separate allocation entirely; and (4) whether any 2026 General Assembly legislation reached comprehensive-plan mandates or by-right multifamily use more broadly than the parking and ADU measures confirmed here. None of these should be assumed resolved in either direction without checking the current Code of Virginia and Virginia Housing's own current bond materials directly.