A BILL to amend and reenact § 33.2-357 of the Code of Virginia, relating to local highway system funding; revenue-sharing funds; funding cycle.
HB539 amends Virginia’s revenue-sharing program for local highway systems by changing the funding cycle and related administration for local transportation projects. The bill keeps the existing structure that allows the Commonwealth to match local funds for highway improvement, construction, reconstruction, and maintenance, but it adds a clearer annual application process and preserves the ability of localities to request funds for projects in their own jurisdiction, in other localities, or for subdivision streets eligible for state system inclusion.
The bill also reinforces how projects are prioritized and managed. It directs the Board to prioritize previously funded projects first, then projects tied to the Statewide Transportation Plan or that accelerate a locality’s capital plan, and then pavement resurfacing and bridge rehabilitation projects that do not meet maintenance performance targets. It retains requirements that localities enter into contracts with the Department, begin projects promptly, and risk reallocation of funds if projects are not initiated within two subsequent fiscal years. The bill leaves in place the overall annual cap on Commonwealth funding, subject to appropriation, while clarifying that unused capacity may be redistributed at the Board’s discretion.
HB539 would amend § 33.2-357 of the Code of Virginia, affecting the state’s local highway revenue-sharing program administered by the Commonwealth Transportation Board and the Department of Transportation. The bill would not create a new program, but it would alter the timing and administration of applications and allocations, potentially changing when localities can seek funds and how quickly projects must move forward. Local governments, especially those relying on state matching funds for road, bridge, and maintenance work, would be the primary affected parties.
No committee transcript or recorded vote information is available, so there is no direct evidence of support or opposition in the provided materials. Based on the bill text, the measure appears procedural and administrative rather than controversial, suggesting it is intended to improve predictability and accountability in the revenue-sharing process. The fact that it was left in the Transportation Committee indicates it did not advance, but the record provided does not explain whether that was due to policy disagreement, timing, or other legislative considerations.
The main points of potential contention are likely to be the funding cap, the reallocation of unused funds, and the stricter timing requirements for project initiation. Localities that want more flexibility may object to the requirement that projects begin within one year and risk reallocation after two fiscal years, while others may support those provisions as a way to ensure funds are used efficiently. Another possible issue is the priority structure, which favors previously funded projects and certain maintenance and plan-based projects, potentially limiting access for localities with different needs or less-developed project pipelines.