Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Subdivision Ordinance topic
No spam. Unsubscribe anytime.
Louisa supervisors send subdivision-rule changes to planning commission, adopt private-roads protocol
Summary
Supervisors unanimously voted to send proposed subdivision-ordinance changes addressing VDOT participation to the Planning Commission and approved a new county protocol for private roads and unfinished subdivisions after discussion about VDOT site visits, third‑party engineering requirements and bond sufficiency.
Get email alerts on the Subdivision Ordinance topic
No spam. Unsubscribe anytime.
The Louisa County Board of Supervisors voted unanimously Monday to forward proposed changes to the county subdivision ordinance to the Planning Commission for review and to adopt a draft protocol for handling private roads and incomplete subdivision bonds.
The measures follow several supervisors’ complaints that the Virginia Department of Transportation (VDOT) has reduced on‑site participation in subdivision reviews and often declines to sign plats or visit sites, leaving the county and applicants without field‑level guidance.
“We have updated that information … and we have since had some individuals share some concern that requiring a third party engineer is gonna cost additional fees,” said Mister Goodwin, county staff, noting packet materials that include a proposed requirement for third‑party review firms and references to VDOT’s Subdivision Street Acceptance Requirements. “One of the things they still require is that a third party engineer does all the inspections and certifications.”
Supervisor comments and staff discussion focused on three issues: whether VDOT will continue making field visits and signing plats, the county’s proposed requirement that developers use a third‑party engineering reviewer chosen from a county list, and how to handle bonds where developers have abandoned projects or where bonds are now decades old.
Supervisor comments recounted cases where VDOT requested driveway and access relocations without conducting a site visit, then declined to sign plats, prompting calls for the county to remove VDOT’s signature from the plat‑approval step or otherwise clarify roles. “If they’re not gonna sign plats and then not come into the field to review them, then why are we sending it to them?” a speaker said during discussion.
On private roads, the board approved a draft protocol that establishes a sequential process: (1) determine whether a road bond exists; (2) request a preliminary VDOT evaluation; (3) compare the bond amount to a professional estimate; (4) where funds suffice, release bond proceeds to a contractor chosen by property owners; (5) if insufficient, ask residents whether a property‑owners association (HOA/POA) will accept funds or form an HOA; and (6) if neither option is available, use available bond funds to make improvements within the bond amount and end county involvement. The draft makes clear the county will not use public funds to construct roads on private property where no bond exists.
Board members also discussed practical constraints: many bonds are old and underestimate current construction costs; some bonds have been called by banks; and VDOT’s reduced field presence creates uncertainty about whether VDOT will perform requested preliminary evaluations.
The motion to forward the subdivision‑ordinance change to the Planning Commission passed unanimously. The board also voted unanimously to adopt the draft private‑roads protocol as presented and directed staff to continue drafting ordinance updates and coordination language for future bond requirements.
The board did not set a timetable for the Planning Commission review; staff said ordinance language changes must return to the board after the Planning Commission’s recommendation.
Votes at a glance: the board unanimously approved the motion to forward the subdivision ordinance change to the Planning Commission (motion passed), unanimously approved the private‑roads protocol (motion passed), and later unanimously approved a separate policy document about work‑group and committee expectations (see separate article).

