City Council Meeting — Agenda Packet
City of Charlottesville · Charlottesville City County · City Council · meeting of Nov 2, 2026 · Agenda packets
Open the original document More from City of Charlottesville
This document is no longer listed on City of Charlottesville's website. We kept the copy we read.
Text
Extracted automatically from the original. Tables and formatting may not survive; the original document is authoritative.
City Council Meeting Agenda
November 2, 2026
City Hall Council Chamber
605 E. Main St.
Charlottesville, VA 22902
Juandiego R. Wade, Mayor
Natalie Oschrin, Vice Mayor
Jen Fleisher
Michael K. Payne
J. Lloyd Snook, III
Kyna Thomas, Clerk
4:00 PM Opening Session
I. Call to Order/Roll Call
II. Agenda Approval
III. Reports
1. Report: Fleet and Equipment Replacement Program and Phased Electric Vehicle
Transition
2. Presentation: City Development Code Clean-Up 2026 Cycle
5:30 PM Closed Meeting (if called)
6:30 PM Business Session
IV. Moment of Silence
V. Announcements
VI. Recognitions/Proclamations
• Recognition: Charlottesville Tree Week: November 1-7, 2026
VII. Community Matters Public comment for up to 16 speakers (limit 3 minutes per speaker). Preregistration
available for first 8 spaces at https://www.charlottesville.gov/692/Request-to-Speak;
speakers announced by Noon on meeting day (9:00 a.m. sign-up deadline).
Additional public comment at end of meeting. Comments on Public Hearing items
are heard during the public hearing only.
VIII. Consent Agenda* The consent agenda consists of routine, non-controversial items whereby all items
are passed with a single motion and vote. Individuals speaking during Community
Matters may address items on the Consent Agenda.
3. Minutes: July 20, 2026 regular meeting; September 9, 2026 joint Council-CRHA Board
work session; October 19, 2026 regular meeting
4. Resolution: Resolution to Appropriate the Victim Witness Grant - $313,698 (2nd reading)
5. Resolution: Resolution for Blue Ridge Health District Carryover Request - $18,000 (2nd
reading)
6. Resolution: Resolution to appropriate funding from the Virginia Department of Housing and
Community Development FY2027 Continuum of Care Capacity Building Funds -
$25,000 (2nd reading)
7. Resolution: Resolution to Appropriate Revenue from Participation in Energy Load Reduction
Program in the Amount of $12,375.53 (2nd reading)
8. Resolution: Resolution to Appropriate funds from the Sentara Foundation to the Department
of Human Services for the Westhaven CARES Center - $7,000 (1 of 2 readings)
Page 1 of 225
9. Resolution: Resolution Considering a Special Exception Permit Application for 835 West
Main Street, 843 West Main Street, and 847 West Main Street (PL-26-0126)
10. Resolution: Marijuana Marketplace Local Ordinance Zoning Text Amendment Initiation
Resolution Adoption
IX. City Manager Report
• Report: City Manager Report
a. Report: City Manager’s Quarterly Work Plan Update
X. Action Items
11. Ordinance: Ordinance Amending and Re-Ordaining Chapter 14 (Licenses), Section 14-24
(Tax Incentives for Technology Businesses) to Extend Eligibility Period for Five
Years to December 31, 2031 (1 of 2 readings)
12. Resolution: Resolution to Appropriate $67,667 from the City's low-barrier shelter operations
fund to SupportWorks Housing for Vista 29 (1 of 2 readings)
13. Resolution: Resolution Authorizing a Performance Agreement Supporting Friendship Court
Phase Three (3) Redevelopment Efforts
14. Resolution: Resolution Endorsing the 2027 Legislative Program for the Thomas Jefferson
Planning District
XI. General Business
15. Report: Botanical Gardens of the Piedmont Construction Update
XII. Community Matters (2)
XIII. Adjournment
Page 2 of 225
MEETING GUIDELINES
• This is an in-person meeting with an option for the public to participate electronically by
registering in advance for the Zoom webinar at www.charlottesville.gov/zoom. The meeting may
also be viewed on the City's streaming platforms and local government Channel 10. Individuals
with disabilities who require assistance or special arrangements to participate in the public
meeting may call (434) 987-1267 or submit a request via email to ada@charlottesville.gov. The
City of Charlottesville requests that you provide 48 hours’ notice so that proper arrangements
may be made.
• The presiding officer shall ensure that individuals address their comments to City Council at
appropriate times, in accordance with the meeting agenda and Council’s Rules of Procedure.
• No person who is not a member of the city council shall orally address it until leave to do so
has been granted by the city council or until invited to do so by the mayor. (City Code sec.2-71)
• Remarks and actions that disrupt the progress of the Council meeting, and remarks from
persons other than councilors, the City Manager, the City Attorney, or a presenter for an Agenda
Item are not permitted.
• The presiding officer shall call an individual to order, including a councilor, when that individual
goes afoul of these rules. The following are examples of remarks and behavior that are not
permitted:
i. Interrupting a speaker who is addressing Council at the speaker's microphone, or
interrupting a speaker who has otherwise been invited to address Council during
Community Matters or a Public Hearing
ii. Interrupting a councilor who is speaking
iii. Shouting, and talking (either individually or in concert with others) in a manner that
prevents a speaker or a Councilor from being heard or that otherwise hinders the
progress of the meeting
iv. Blocking paths for emergency exit from the meeting room; engaging in any conduct that
prevents a member of the audience from seeing or hearing councilors during a meeting;
standing on chairs or tables within the Council meeting room
v. Threats or incitement of violence toward councilors, City staff or members of the public
vi. Engaging in conduct that is a criminal offense under the City Code or the Virginia Code
vii. Campaigning for elected office
viii. Promotion of private business ventures
ix. Using profanity or vulgarity
x. Personal attacks against Councilors, City staff or members of the public
xi. Behavior which tends to intimidate others
• During a City Council meeting the presiding officer shall have control of the Council Chambers
and the connecting halls and corridors within City Hall, and any other venue where a Council
meeting is being held. In case of any conduct described above, the presiding officer may take
measures deemed appropriate, including but not limited to suspending the meeting until order
is restored, ordering areas to be cleared by the Sergeant at Arms, or requiring any individual to
exit the meeting room and adjacent premises (connecting halls and corridors.)
Page 3 of 225
Policy Briefing Summary
City Council
Regarding: Fleet and Equipment Replacement Program and Phased Electric
Vehicle Transition
Staff Contact(s): Mike Crowley, Kristel Riddervold, Director of the Office of Sustainability
Presenter: Steven Hicks, Director of Public Works
Date of Proposed
Action:
November 2, 2026
Issue
The City of Charlottesville, Virginia's ("City"), Fleet and Equipment Replacement Program ("Program")
takes a responsible, phased approach to maintaining dependable vehicles and equipment while
advancing the City's climate goals. Replacement decisions are based on condition, safety, reliability,
service needs, and cost, not age or mileage alone. Fleet has reviewed the FY26–FY31 replacement
schedule to identify opportunities for electric vehicles (EVs) and the charging infrastructure needed to
support them. Updated projections identify twenty-four (24) EV acquisitions for FY28–FY30. The
schedule guides recommendations and investment over time, without committing the City to a full fleet
conversion within a short period.
Background / Rule
Fleet Maintenance keeps the City’s vehicles and equipment safe, reliable, and available for daily
operations. The Division has twelve (12) full-time positions and maintains approximately 710 vehicles
and pieces of equipment through preventive maintenance, inspections, repairs, and service scheduling.
The City’s fleet currently includes fourteen (14) EVs: one (1) Capital Development vehicle, three (3)
Facilities Maintenance vehicles, one (1) Fire vehicle, one (1) Neighborhood Development Services
vehicle, one (1) Office of Sustainability vehicle, one (1) Parks & Recreation vehicle, two (2) Police
vehicles, two (2) school buses, and two (2) Transit buses. This inventory includes the two (2) recently
delivered Transit buses anticipated to enter service in fall 2026. A recent Cadmus Fleet Electrification
Study ("Study") reviewed 588 vehicles within the broader inventory, including 341 light-duty vehicles
and 247 medium and heavy-duty vehicles.
The proposed Fleet and Equipment Replacement Policy ("Policy") covers general service, public
safety, emergency, commercial, and specialized vehicles and equipment. It establishes a consistent
process for evaluating age, mileage, condition, repair history, safety, and operational requirements,
with replacement criteria appropriate to each type of asset. For general light-duty vehicles, ten (10)
years or 150,000 miles are review points, not automatic replacement deadlines. Vehicles may remain
in service longer when safe, reliable, and cost-effective or be replaced sooner when condition or
service needs warrant it. The Policy also supports selecting the appropriate vehicle for the work and
reassigning underused assets before purchasing replacements.
The original FY26–FY31 Capital Plan Schedule identified forty-five (45) potential EV replacements,
providing context for earlier purchases and planned replacements through FY31. Updated projections
identify nine (9) EV acquisitions in FY28, ten (10) in FY29, and five (5) in FY30. Identifying a vehicle as
a potential EV replacement does not mean it needs immediate replacement. Vehicles that remain
Page 4 of 225
safe, reliable, and in good condition will continue in service, with EV options considered when
replacement is warranted. These projections update the earlier schedule rather than add to it.
Alongside the planned EV purchases, the FY28 Program includes requests for public safety vehicles,
school buses, work trucks, and heavy equipment. These requests reflect the broader responsibility to
maintain dependable vehicles and equipment across City operations. Each request will be evaluated
through the City's annual Budget process based on condition, utilization, and service needs.
These projections update the earlier schedule rather than add to it. The FY26–FY31 schedule also
informed the proposed FY28 Capital Improvement Program ("CIP") request for charging infrastructure,
including the number of chargers and priority locations needed to support existing and planned
EVs. City Staff will continue coordinating replacement timing and charging needs as Departmental
requirements and budgets are reviewed.
This year, the City placed three (3) take-home EVs into service for public safety use. These vehicles
provide practical experience with range, charging, reliability, and performance under daily operating
conditions.
Electrification progress extends beyond the light-duty fleet. Two (2) battery-electric school buses have
been in service since January 2026. The City received $409,968 through the U.S. Environmental
Protection Agency’s Clean School Bus Program to assist with the purchase, and Dominion Energy’s
Electric School Bus Infrastructure Program provided the charging equipment. Installation of the
dedicated Transit charging equipment has been completed. In addition to the two (2) recently
delivered buses, two (2) more battery-electric Transit buses are anticipated for delivery by April 2027.
Analysis
The City's climate goals are to reduce community-wide greenhouse gas emissions to forty-five percent
(45%) below 2011 levels by 2030 and reach carbon neutrality by 2050. Fleet electrification contributes
to those goals. A phased approach supports continued progress, while maintaining reliable services
and addressing the needs of the entire fleet.
The City does not replace its entire fleet at one (1) time. Vehicles and equipment have different ages,
conditions, workloads, and useful lives. Keeping serviceable assets in operation avoids unnecessary
purchases and spreads replacement costs over time. When an asset is due for replacement, Fleet and
the operating Department compare available options based on the work performed, mileage, operating
schedule, reliability, charging needs, environmental benefits, and cost over its useful life.
The updated FY28–FY30 projections include sedans, SUVs, pickup trucks, and full-size work vans
across multiple Departments. Vehicle purchases must be coordinated with charging infrastructure and
funding, so each vehicle can be placed into dependable service when delivered. Planning considers
where vehicles park, the time available for charging, and daily service demands. This work proceeds
alongside replacement planning for the rest of the fleet. Refuse trucks, and other specialized
equipment, must meet requirements for load capacity, operating hours, and service
demands. Available EV models and charging arrangements may not yet meet every
requirement. Where an EV is not practical, Fleet will recommend an appropriate hybrid or fuel-efficient
conventional replacement, while continuing to evaluate electric alternatives.
The Study informs these decisions; it does not establish a limit on future EV adoption. Vehicles outside
the near-term EV schedule remain part of the regular replacement Program and remain eligible for
future EV consideration. Recommendations will be updated as technology, vehicle availability, pricing,
charging capacity, and funding opportunities change.
Financial Impact
Page 5 of 225
The projected purchase cost for the twenty-four (24) EVs identified for FY28–FY30 totals $1,204,000:
FY28: Nine (9) vehicles totaling $456,000, including sedans or small SUVs, two (2) full-size
work vans, and three (3) pickup trucks;
FY29: Ten (10) vehicles totaling $483,000, including sedans or SUVs and five (5) pickup
trucks; and
FY30: Five (5) vehicles totaling $265,000, including sedans or SUVs and two (2) full-size work
vans.
Additional FY28 vehicle and equipment requests total $2,438,000. These include two (2) Sheriff’s
vehicles, one (1) mini-excavator, one (1) tandem dump truck, one (1) E-450 van, one (1) wheel loader,
eleven (11) marked Police vehicles, nine (9) unmarked Police vehicles, one (1) F-450 truck, and three
(3) school buses. The total also includes $180,000 for Fire Department vehicles and/or equipment.
Combined with the $456,000 projected for nine (9) EVs, the identified FY28 vehicle and equipment
requests total $2,894,000. This total excludes charging infrastructure and represents acquisition
requests rather than the Division’s full Maintenance and Operating Budget.
These figures represent projected EV purchase costs, not the additional cost above comparable fuel-
powered replacements. Final acquisitions and expenditures remain subject to Budget approval,
vehicle availability, Departmental needs, and pricing at the time of purchase.
EV purchase costs vary by vehicle type. The Study estimated that an electric passenger car could cost
approximately $1,500 more than a comparable fuel-powered vehicle, while a large electric SUV could
cost approximately $18,000 more. These examples provide context for potential purchase premiums;
they are not current quotes or a uniform premium across the projected acquisitions. Lower energy and
maintenance expenses may offset part of the investment over time. The Study presented life-cycle
cost analysis estimating that replacement with EVs would yield an average of $2,800 in savings per
vehicle over a ten (10)-year period. The extent of those savings depends on the vehicle, mileage,
charging costs, and operating conditions. Financial savings are not a requirement for every EV
purchase. Fleet will compare acquisition, operating, and charging costs alongside service needs and
environmental benefits, so each recommendation identifies the investment needed to support the City’s
climate goals.
A separate FY28 CIP request includes approximately $390,000 for charging infrastructure at additional
City fleet locations: $225,000 for approximately seventeen (17) Level Two (2) chargers and $165,000
for one (1) fast charger. Design costs for the fast charger are excluded from this estimate and are
expected to be covered through previously approved funding. The charging request will be evaluated
separately through the CIP process and is not included in the $2,894,000 vehicle and equipment total.
The vehicle projections and charging estimates do not represent the full cost of the City’s EV
transition. Purchases and infrastructure investments will be coordinated through the annual Budget
process alongside other fleet and equipment replacement needs. The City will continue pursuing
grants and other outside funding to reduce local costs.
Recommendation
None. This item is presented to City Council for information and discussion.
Recommended Motion (if Applicable)
Not applicable. No Motion required.
Page 6 of 225
Attachments
1. Fleet EV Council Work Session 11 2 26
Page 7 of 225
Fleet and equipment
replacement program
Phased EV transition
Charlottesville Council Work Session 11.2.26
CITY OF CHARLOTTESVILLE · PUBLIC WORKS
Page 8 of 225
Fleet program and replacement policy
2
Fleet Maintenance has 12 full-time positions and maintains
about 710 vehicles and pieces of equipment
Condition, safety, reliability, service needs, and cost guide
replacement decisions
General light-duty vehicles receive review at 10 years or
150,000 miles
Retain serviceable assets, right-size vehicles, and reassign
underused equipment
Page 9 of 225
Current EV inventory
3
Department or service EVs
Capital Development 1
Facilities Maintenance 3
Fire 1
Neighborhood Development Services 1
Office of Sustainability 1
Parks & Recreation 1
Police 2
School buses 2
Transit buses 2
Total 14
Page 10 of 225
The EV replacement schedule
4
The original FY26–FY31 capital plan
identified 45 potential EV replacements
Updated FY28–FY30 projections identify 24 EV
acquisitions
Potential EV candidates remain in service while safe,
reliable, and in good condition
Fleet considers EV options when replacement is warranted
Page 11 of 225
Progress in public safety and buses
5
Three take-home public safety EVs entered service
this year
Two electric school buses in service since January 2026
Two Transit buses delivered, with service anticipated in fall
2026
Transit chargers complete. Two more buses expected by
April 2027
Page 12 of 225
Climate goals and operational needs
6
Community-wide goals: 45% below 2011 emissions by
2030 and carbon neutrality by 2050
Replacement timing reflects each vehicle’s condition,
workload, and useful life
EVs must meet daily assignments and charging needs,
including for specialized equipment
Hybrid or fuel-efficient conventional replacements remain
options when needed
Page 13 of 225
Projected EV purchases
7
Fiscal year Vehicles Purchase cost
FY28 9 $456,000
FY29 10 $483,000
FY30 5 $265,000
Total 24 $1,204,000
Projected EV vehicle purchase costs. Charging costs are separate.
Page 14 of 225
FY28 vehicle and equipment funding
8
FY28 request Projected cost
Nine EVs $456,000
Other vehicles and equipment $2,438,000
Total vehicle and equipment requests $2,894,000
Vehicle and equipment requests only. Charging CIP is separate.
Page 15 of 225
Comparing vehicle costs
8
Passenger EV: approximately $1,500 more than a
comparable conventional vehicle
Large electric SUV: approximately $18,000 more
Lower energy and maintenance costs may offset part of the
investment
Savings are not a requirement for every EV purchase
Page 16 of 225
Proposed FY28 charging investment
9
$390,000 requested for additional fleet charging
Approximately $225,000 for 17 Level 2 chargers
Approximately $165,000 for one fast charger
Page 17 of 225
Recommendation and Council discussion
10
Continue the phased fleet and equipment
replacement program
Coordinate vehicle delivery with charging
readiness and annual funding
Update schedules as operating experience
grows and pursue outside funding
Page 18 of 225
Policy Briefing Summary
City Council
Regarding: City Development Code Clean-Up 2026 Cycle
Staff Contact(s): Matthew Alfele, City Planner
Presenter: Matthew Alfele, City Planner
Date of Proposed
Action:
November 2, 2026
Issue
Neighborhood Development Services ("NDS") Staff is presenting the second annual City Development
Code ("CDC") clean-up cycle. The proposed amendment package includes technical corrections,
administrative clarifications, state-law conformity updates, and targeted refinements intended to
improve implementation of the CDC, while maintaining its adopted policy framework.
Background / Rule
City Council adopted the CDC on December 18, 2023. The CDC implemented a more form-based
zoning framework and increased development capacity consistent with the City's 2021 Comprehensive
Plan. CDC amendments are intended to be an annual maintenance process to ensure that the
Ordinance remains effective and current as City Staff, Applicants, and the community gain experience
implementing its provisions. The 2026 CDC amendment package represents the second year of this
annual review cycle.
Throughout 2026, NDS Staff worked with the Planning Commission ("PC') through Work Sessions,
listening sessions, subcommittee meetings, and project-specific discussions to identify issues and
refine potential amendments. Feedback from PC Members, Applicants, property owners, preservation
stakeholders, development professionals, and City Staff informed the proposed amendment package.
The package includes approximately twenty-four (24) amendments addressing administrative
procedures, zoning standards, subdivision regulations, historic preservation processes, mapping and
graphic clarifications, and development review procedures. The amendments include technical
corrections, administrative clarifications, state-law conformity updates, and targeted revisions intended
to improve implementation of the CDC.
Analysis
The proposed amendment package combines technical corrections, administrative clarifications, state-
law conformity updates, and targeted refinements identified through CDC implementation. Examples
include updates to easement requirements, references to the Standards and Design Manual and
Appendices, clarification of standards eligible for Special Exception Permits, and other corrections
intended to improve consistency and usability throughout the CDC.
The package also includes amendments necessary to maintain conformity with recent changes in state
law, including updates related to accessory dwelling units. Additional refinements address topics such
as tree-removal review procedures, private streets, bicycle parking requirements for lodging uses,
active-depth standards, and the treatment of nonconforming buildings.
Collectively, the amendments are intended to improve administration of the CDC, eliminate
ambiguities, streamline review processes, and incorporate implementation lessons learned since
adoption of the Ordinance. NDS Staff anticipates bringing selected amendments forward at the
Page 19 of 225
December 8, 2026, Joint Public Hearing, with City Council consideration of adoption anticipated in
early 2027.
Financial Impact
Not applicable.
Recommendation
Not applicable.
Recommended Motion (if Applicable)
Not applicable.
Attachments
1. Presentation Code Amendment
2. Draft One-Pagers
Page 20 of 225
Department of
Neighborhood Development Services
City Council Presentation
Development Code Clean-Up
Cycle 2
November 2, 2026
Page 21 of 225
Development Code Amendments: Background
• Development Code Adoption
• Adopted December 18, 2023
• Implemented a more form-based zoning framework and increased development capacity
consistent with the 2021 Comprehensive Plan.
• Why Amend the Code?
• Staff has identified technical corrections, clarifications, and process improvements that
warrant updates to the Development Code.
• Ongoing Annual Review
• Development Code amendments are intended to be an annual maintenance process to
ensure the ordinance remains effective and current.
• 2026 represents the second year of this review cycle.
• Next Steps:
• Tonight: Presentation to City Council on this year's amendment.
• December 8, 2026: Joint Public Hearing on selected amendments.
• Early 2027: City Council adoption consideration.
• March 2027: Target effective date for adopted amendments.
Page 22 of 225
Select Examples of Technical Improvements
Page Section Existing Language or Issue Proposed Language
6-8 34-6.2.2 Platted easements and deeded
easements must be provided in
locations and dimensions required by
the City in order to:
Platted easements and deeded
easements must clearly identify easement
type and ownership and be provided in
locations and dimensions required by the
City in order to:
Throughout
the Code
Multiple Standards and Design Manual Standards and Design Manual and
Appendices
4-21 34-4.4.5.D.9.c In Residential (R-) zoning districts, when
the project fronts on an existing street
and…
In Residential (R-) and Residential Core
Neighborhood (RN-) zoning districts, when
the project fronts on an existing street
and…
5-54 34-5.2.15.A 1. The City Council may grant a
modification of any physical
dimensional standard…
2. A Special Exception Permits may be
granted for physical dimensional
standards…
1.The City Council may grant a
modification of any physical dimensional
or numerical standard…
2. A Special Exception Permits may be
granted for physical dimensional or
numerical standards…
Page 23 of 225
State Regulation Amendment
Bill General Changes that need to be made
SB 531 Virginia Code § 15.2-2292.3 will require localities to allow an accessory dwelling unit
by-right on lots with a single-family dwelling. Because RN-A currently permits only
one dwelling unit by-right, this amendment increases the base density from one to
two units and adjusts the Existing Structure Preservation bonus from two to three
units. These changes ensure compliance with state law while maintaining the
existing affordability incentive structure and avoiding conflicts with the Development
Code's current use of the term "ADU" for Affordable Dwelling Unit. See Amendment
A.8 for more detail.
Page 24 of 225
Select Examples of Refinements
Tree Removal Permit Clarification
Proposed Changes
• Replaces "properties" with "lots and parcels”.
• Clarifies that tree removal associated with Development Review is reviewed through
that process.
• Eliminates the need for a separate Tree Removal Permit when tree removal is already
being reviewed as part of a Development Plan or Final Site Plan.
Overview
This amendment is primarily a housekeeping and process-streamlining change. It updates
terminology for consistency with the Development Code and removes a redundant permit
requirement when tree removal is already reviewed through an existing development
approval process.
Page 25 of 225
Select Examples of Refinements
Private Streets
Proposed Changes
• Establish separate definitions for Public Streets and Private Streets.
• Require private streets to be located on a separate recorded lot or tract rather than
being created solely through an easement.
• Clarify that private streets must meet the same City design and bonding standards as
public streets.
Overview
This amendment clarifies how streets are defined and established within the Development
Code. It ensures that private streets are created and maintained using standards similar to
public streets, providing greater consistency in how development relates to street
frontages throughout the city.
Page 26 of 225
Select Examples of Refinements
Bicycle Parking Requirements for Lodging
Proposed Changes
• Create a separate bicycle parking standard for Lodging uses.
• Base short-term bicycle parking on non-lodging floor area rather than total building
size.
• Base long-term bicycle parking on the number of guest rooms.
Overview
This amendment updates bicycle parking requirements for hotels and other lodging uses
to better align parking requirements with actual demand. The revised standards are
tailored to lodging uses rather than applying the general commercial square-footage
formula.
Page 27 of 225
Select Examples of Refinements
Active Depth and Active Space
Proposed Changes
• Limit active depth requirements on primary streets to the first two stories.
• Update the definition of active space to clearly include residential living areas.
• Remove a redundant exemption related to single-unit buildings.
Overview
This amendment refines the active depth standards based on implementation experience
and Planning Commission feedback. The changes focus activation requirements where
they have the greatest streetscape impact while providing clearer guidance on what
qualifies as active space.
Page 28 of 225
Select Examples of Refinements
Nonconforming Buildings and Build-to Requirements
Proposed Changes
• Allow new buildings and structures in the side and rear yards of lots containing
nonconforming buildings.
• Remove size limitations on certain side and rear additions.
• Clarify how build-to width requirements apply before new front and side-street yard
conditions are established.
Overview
This amendment provides greater flexibility for infill development on lots with existing
nonconforming buildings. The changes simplify build-to regulations, remove unnecessary
constraints on additions, and make it easier to add buildings and dwelling units while
maintaining the intent of the City's frontage and urban design standards.
Page 29 of 225
Select Examples of Refinements
Food Trucks (Mobile Food Units)
Proposed Changes
• Remove the limitation that only one temporary use permit may be active on a property
at a time to allow multiple food truck to operate on the same property.
• Remove the allowance for a covered 10' x 10' condiment table
• Require applicants to identify where a mobile food unit will be located when not in
operation.
Overview
This amendment is intended to address operational issues that have emerged since
adoption of the Development Code's temporary use regulations. Current provisions allow
multiple food truck permits to be issued for a property while simultaneously limiting a site
to one active temporary use permit at a time, creating confusion for operators, property
owners, and staff. The proposed changes remove that conflict and provide greater
flexibility for commercial properties that may wish to host multiple mobile food vendors.
Page 30 of 225
Thank You
Page 31 of 225
Proposed Amendment
Util.10 & 11 – Easements
Section 34-6.2.2
Page: 6-7 thru 6-8
Amendment Log Util.10 & 11
Existing Language:
6.2.2 Easements
A. Platted easements and deeded easements must be provided in locations and
dimensions required by the City in order to:
1. Allow for adequate storm drainage facilities;
2. Allow for proper installation of water and sewer lines, whether immediately
proposed or necessary for adequate service in the future;
3. Allow for cross-access between properties;
4. Allow for adequate pedestrian and bicycle access;
5. Allow for adequate right-of-way for street types;
6. Allow for adequate public access; and
7. Allow for adequate slope for roadway construction.
B. Easement widths are specified by the Standards and Design Manual as necessary to
accommodate existing and future needs as well as construction and repair of
facilities. For drainage easements, the widths must be sufficient to accommodate
areas anticipated to be inundated by stormwater.
Proposed Language:
6.2.2 Easements
A. Platted easements and deeded easements must clearly identify easement type and
ownership and be provided in locations and dimensions required by the City in order
to:
1. Allow for adequate storm drainage facilities;
2. Allow for proper installation and maintenance of water , sanitary sewer ,
stormwater and gas facilities and sewer lines, whether existing, immediately
proposed or necessary for adequate service in the future;
3. Allow for cross-access between properties;
4. Allow for adequate pedestrian and bicycle access;
5. Allow for adequate right-of-way for street types;
6. Allow for adequate public access; and
7. Allow for adequate slope for roadway construction.
B. Easement widths are specified by the Standards and Design Manual and its
aAppendices as necessary to accommodate existing and future needs as well as
access for maintenance, construction and repair of facilities. For drainage
easements, the widths must be sufficient to accommodate and provide access to
areas anticipated to be inundated by stormwater.
Page 32 of 225
Proposed Amendment
Util.10 & 11 – Easements
Analysis:
The current Development Code lacks clarity and direction on the purpose, uses, ownership
and responsibility related to easements on subdivision plats. The proposed changes to
6.2.2.A provides additional guidance.
6.2.2.A subsections 1 & 2 are proposed to be combined for clarity, and include gas utilities
that were formerly missing so that water, sanitary sewer, stormwater and gas are mentioned
together for consistency with other proposed cleanup of the code.
6.2.2.B proposed language adds reference to the SADM appendices for utilities, and clarifies
the need for access and mentions maintenance along with construction/repair.
Page 33 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
Section 34-6.6
Page: 6-10 thru 6-12
Amendment Log Util.12, 13, 15 & 19
Existing Language:
6.6.1 Dedication of Infrastructure for Public Use
A. A project developer must dedicate to the City for public use every easement and right-
of-way located within the project, which has constructed or proposed to be
constructed any public street, curb, gutter, sidewalk, bicycle trail, drainage or
sewerage system, waterline as part of a public system, or other improvement
dedicated for public use and to be maintained by the City or another public agency,
as follows:
1. The City Council is not required to compensate the project developer for any
dedicated land or improvements.
2. The land and improvements to be dedicated must be set apart on the Final Plat
and must be identified by a note on the plat stating that the land is dedicated
for public use.
3. When a project abuts one side of an existing or platted street, the project
developer must dedicate at least 1/2 of the right-of-way necessary to make the
street comply with the minimum width required for the street as designated in
the Standards and Design Manual.
B. A project developer must dedicate to the City for public use all water and sewerage
facilities designed, constructed and approved to be dedicated as public water and
sewerage systems, and will require each project developer to establish an easement
on the land for such facilities, extending to any abutting property owned by the project
developer, if the facilities are required by this Development Code, as follows:
1. The City Council is not required to compensate the project developer for the
dedicated facilities or the establishment of any easement.
2. The facilities to be dedicated and any easement to be established must be
specifically identified and set apart on the Final Plat and must be identified by
a note on the plat stating that the facilities are dedicated to, and the easement
is established for, the City of Charlottesville.
3. All Final Plats containing proposed public easements must expressly
reference a declaration of the terms and conditions of such public easements
recorded with the subdivision plat in the City’s land records.
C. A project developer must establish easements for facilities for stormwater
management and drainage control, as follows:
Page 34 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
1. An easement for all stormwater management facilities and drainage control
improvements located on the property must be established whenever the
improvement is designed and constructed beyond a street right -of-way or
access easement and must extend from all drainage outfalls to an adequate
channel that satisfies minimum standards established by the Virginia
Department of Environmental Quality or the State Water Control Board, to the
boundary of the property.
2. An easement must be established along every natural stream, natural
drainage area to be preserved, and every man-made waterway located on the
property.
3. The area of each required easement must be sufficient, as determined by the
Subdivision Administrator, to: a.
a. Accommodate the facilities and the drainage characteristics from
each drainage outfall from a drainage control;
b. Allow access to a natural stream or man -made waterway to allow
widening, deepening, relocating, improving, or protecting the natural
stream or man-made waterway for drainage purposes; and
c. Meet applicable standards and requirements set forth within Water
Protection, Chapter 10 of the Code of the City of Charlottesville and the
Standards and Design Manual.
4. Each required easement must include a right of ingress and egress for
installation, maintenance, operation, repair and reconstruction of any
improvement within the easement. The Subdivision Administrator may require
that an easement be provided through abutting land under the same
ownership as the project.
5. The City Council is not required to compensate the project developer for any
easement or any improvements within the easement.
6. All Final Plats containing proposed public easements must expressly
reference a declaration of the terms and conditions of such public easements
recorded with the subdivision plat in the City’s land records.
7. No easement will be considered part of any required street width.
6.6.2 Dedication of Land for Public Use
A project developer may dedicate to the City any land within the project that is suitable for
parks, open space, stormwater management facilities and other public facilities, utilities
and other public or semipublic uses, as follows:
Page 35 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
A. The City Council is not required to compensate the project developer for the land
dedicated if the dedication is a gift, required by a proffer as part of a conditional
rezoning, required as a condition of a special use permit, variance or other approval,
or if the need for the land is substantially generated by the project. The determination
of whether the need for land is substantially generated by the project will be made in
the manner prescribed by 6.6.1. Dedication of Infrastructure for Public Use.
B. Land dedicated under this Section must be set apart on the Final Plat and identified
by a note on the plat stating that the land is dedicated for public use. The proposed
dedication will be subject to review as to consistency with the City’s Comprehensive
Plan, as required by Code of Virginia § 15.2- 2232.
C. A project developer’s proposed dedication of a stormwater management facility must
be reviewed and governed by the provisions of Water Protection, Chapter 10 of the
Code of the City of Charlottesville. No such dedication will be accepted unless and
until the City receives a financial guarantee, in the form of a bond or like surety, in an
amount sufficient for and conditioned upon the construction of such stormwater
management facilities in accordance with the standards and requirements set forth
within Chapter 10 and the Standards and Design Manual.
6.6.3 Reservation of Land
A project developer may reserve for future dedication to the City a part of the property
suitable for parks, schools, open space and other public facilities, utilities and other public
or semipublic uses, as follows:
A. The City Council is not required to compensate the project developer for the
reservation of land if the dedication is a gift, required by a proffer as part of a
conditional Zoning Map Amendment, required as a condition of a Special Use Permit,
Variance, or other approval, or if the need for the land is substantially generated by
the project. The determination of whether the need for land is substantially generated
by the project will be made in the manner prescribed by 6.6.1. Dedication of
Infrastructure for Public Use.
B. Land reserved under this Section must be set apart on the Final Plat and identified by
a note on the plat stating that the land is reserved for future dedication for public use.
C. The project developer may petition the City Council to release a reservation if the land
is not used for a public purpose, using the procedure set forth within Div. 6.7.
Administration.
D. Nothing in this Section precludes land being reserved for a public use which is not
included in the Comprehensive Plan, provided the land is acceptable to the City for
reservation.
Page 36 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
6.6.4 Transfer of Land Ownership
The recording of an approved Final Plat and deed of dedication will transfer dedicated land
and establish certain easements, as follows:
A. Recordation will operate to transfer, in fee simple, to the City that portion of the land
set apart on the plat and dedicated for public use.
B. Recordation will operate to transfer to the City any easement set apart on the plat and
dedicated to public use to create a public right of passage over the property.
C. Recordation will operate to transfer to the City, in fee simple, the water and sewer
facilities, and related easements, set apart on the plat and dedicated for public use.
D. Recordation will operate to terminate and extinguish all rights-of-way, easements or
other interests of the City in the property not shown on the plat, except that an interest
acquired by the City by eminent domain, by purchase for valuable consideration and
evidenced by a separate instrument of record, or streets, alleys or easements for
public passage subject to the provisions of the Code of Virginia § 15.2-2271 or 2272.
E. Recordation will not constitute acceptance of any improvement by the City.
Page 37 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
Proposed Language:
6.6.1 Dedication of Infrastructure for Public Use
A. A project developer must dedicate to the City for public use every easement and right-
of-way located within the project, which has constructed or proposed to be
constructed any public street, curb, gutter, sidewalk, bicycle trail, drainage or
sewerage system, waterline as part of a public system, or other improvement
dedicated for public use and to be maintained by the City or another public agency,
as follows:
1. The City Council is not required to compensate the project developer for any
dedicated land or improvements.
2. The land, easements, and improvements to be dedicated must be set apart on
the Final Plat and must be identified by a note on the plat stating that the land,
easement and/or improvement is dedicated for public use.
3. When a project abuts one side of an existing or platted street, the project
developer must dedicate at least 1/2 of the right-of-way necessary to make the
street comply with the minimum width required for the street as designated in
the Standards and Design Manual and Appendices.
B. A project developer must dedicate to the City for public use all water and sewerage
facilities water, sanitary sewer, stormwater and gas facilities designed, constructed
and approved to be dedicated for public ownership as public water and sewerage
systems, and will require each project developer to establish an easement on the
land for such facilities, extending to any abutting property owned by the project
developer, if the facilities are required by this Development Code, as follows:
1. The City Council is not required to compensate the project developer for the
dedicated facilities or the establishment of any easement.
2. The facilities to be dedicated and any easement to be established must be
specifically identified and set apart on the Final Plat and must be identified by
a note on the plat stating that the facilities are dedicated to, and the easement
is established for, the City of Charlottesville.
3. Each required easement must include a right of ingress and egress for
installation, maintenance, operation, repair and reconstruction of public
utility facilities within the easement.
4. All Final Plats containing proposed public easements must expressly
reference a declaration of the terms and conditions of such public easements
recorded with the subdivision plat in the City’s land records.
5. A project developer’s proposed dedication of public utility facilities for public
ownership must be reviewed and governed by the provisions of Utilities,
Chapter 31 of the Code of the City of Charlottesville. No such dedication will
be accepted unless and until the City receives a financial guarantee, in the
Page 38 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
form of a bond or like surety, in an amount sufficient for and conditioned upon
the construction of such public utility facilities in accordance with the
standards and requirements set forth within Chapter 31 and the Standards
and Design Manual and its aAppendices.
C. A project developer must establish easements for facilities for stormwater
management and drainage control, as follows:
(add the following after subsection 7)
8. A project developer’s proposed dedication of a stormwater management
facility for public ownership must be reviewed and governed by the provisions
of Water Protection, Chapter 10 of the Code of the City of Charlottesville. No
such dedication will be accepted unless and until the City receives a financial
guarantee, in the form of a bond or like surety, in an amount sufficient for and
conditioned upon the construction of such stormwater management facilities
in accordance with the standards and requirements set forth within Chapter
10 and the Standards and Design Manual and Appendices.
6.6.2 Dedication of Land for Public Use
A project developer may dedicate to the City any land within the project that is suitable for
parks, open space, utilities, stormwater management facilities, and other public facilities,
utilities and other public or semipublic uses in a manner consistent with 6.6.1. Dedication
of Infrastructure for Public Use, as follows:
A. The City Council is not required to compensate the project developer for the land
dedicated if the dedication is a gift, required by a proffer as part of a conditional
rezoning, required as a condition of a special use permit, variance or other approval,
or if the need for the land is substantially generated by the project. The determination
of whether the need for land is substantially generated by the project will be made in
the manner prescribed by 6.6.1. Dedication of Infrastructure for Public Use.
B. Land dedicated under this Section must be set apart on the Final Plat and identified
by a note on the plat stating that the land is dedicated for public use. The proposed
dedication will be subject to review as to consistency with the City’s Comprehensive
Plan, as required by Code of Virginia § 15.2- 2232.
C. A project developer’s proposed dedication of a stormwater management facility must
be reviewed and governed by the provisions of Water Protection, Chapter 10 of the
Code of the City of Charlottesville. No such dedication will be accepted unless and
until the City receives a financial guarantee, in the form of a bond or like surety, in an
amount sufficient for and conditioned upon the construction of such stormwater
management facilities in accordance with the standards and requirements set forth
within Chapter 10 and the Standards and Design Manual.
Page 39 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
6.6.3 Reservation of Land
A project developer may reserve for future dedication to the City a part of the property
suitable for parks, schools, open space , utilities, and other public facilities, utilities and
other public or semipublic uses in a manner consistent with 6.6.1. Dedication of
Infrastructure for Public Use, as follows:
A. The City Council is not required to compensate the project developer for the
reservation of land if the dedication is a gift, required by a proffer as part of a
conditional Zoning Map Amendment, required as a condition of a Special Use Permit,
Variance, or other approval, or if the need for the land is substantially generated by
the project. The determination of whether the need for land is substantially generated
by the project will be made in the manner prescribed by 6.6.1. Dedication of
Infrastructure for Public Use.
B. Land reserved under this Section must be set apart on the Final Plat and identified by
a note on the plat stating that the land is reserved for future dedication for public use.
C. The project developer may petition the City Council to release a reservation if the land
is not used for a public purpose, using the procedure set forth within Div. 6.7.
Administration.
D. Nothing in this Section precludes land being reserved for a public use which is not
included in the Comprehensive Plan, provided the land is acceptable to the City for
reservation.
6.6.4 Transfer of Land Ownership
The recording of an approved Final Plat and deed of dedication will transfer dedicated land
and establish certain easements, as follows:
A. Recordation will operate to transfer, in fee simple, to the City that portion of the land
set apart on the plat and dedicated for public use.
B. Recordation will operate to transfer to the City any easement set apart on the plat and
dedicated to public use to create a public right of passage over the property.
C. Recordation will operate to transfer to the City any easement set apart on the plat for
water, sanitary sewer, stormwater and gas facilities that are dedicated for public
ownership.
D. Recordation will operate to terminate and extinguish all rights-of-way, easements or
other interests of the City in the property not shown on the plat, except that an interest
acquired by the City by eminent domain, by purchase for valuable consideration and
evidenced by a separate instrument of record, or streets, alleys or easements for
public passage subject to the provisions of the Code of Virginia § 15.2-2271 or 2272.
E. Recordation will not constitute acceptance of any improvement by the City.
Page 40 of 225
Proposed Amendment
Util.12, 13, 15 & 19 – Fees & Dedications
Analysis:
The current Development Code is inconsistent in its references & requirements regarding
public utility infrastructure (and other public uses/improvements) throughout this section:
In 6.6.1.A, references to utilities are removed since they are already covered in 6.6.1.B. In
the subsequent terms, references to land, easements and improvements are updated for
consistency throughout.
In 6.6.1.B, the specific types of public utilities are clarified and expanded to include
stormwater and gas. In the subsequent terms, additions are made for (#3) describing the
requirements of the utility easements is added as item 3, which mirrors 6.6.1.C.4, and (#5)
outlining provisions for the dedication of public utility facilities referencing City Code, the
SADM and its appendices.
In 6.6.1.C, the provisions for the dedication of stormwater management facilities is moved
from 6.6.2.C (which concerns dedication of land) into th is section (#8) which is more
applicable (dedication of improvements).
In 6.6.2 and 6.6.3, the list of public uses is revised for clarity. Also, reference is made back to
6.6.1.
In 6.6.4, the proposed language clarifies that only the easements associated with utilities to
be owned & operated by the City (and not the facilities that will be contained within those
easements) are to be transferred to the City along with recordation of a plat, and removes
the “fee simple” re ference. This removes any potential contradiction with subsection E,
which states that recordation of a plat does not constitute acceptance of any improvement
by the City. The types of public utilities are also clarified and expanded to include stormwater
and gas.
Page 41 of 225
Proposed Amendment
Util.1 through 7 – Language
Section 34-All applicable sections
Page: All applicable pages
Amendment Log Util.1, 2, 3, 4, 5, 7,
General language and references to existing standards:
General language in Chapter 34 references the “Standards and Design Manual” forty-seven
(47) times throughout the document. The SADM also includes important appendices that
provide additional and important details and requirements, but it is frequently mentioned to
review staff that outside consultants were unaware of these Appendices.
Proposed language and references to existing standards:
Update all forty-seven references to the “Standards and Design Manual and Appendices”.
Existing Language:
1.1.3 Purpose and Intent
(E) Facilitate the provision of adequate police and fire protection, disaster evacuation, civil
defense, transportation, water, sewerage, flood protection, schools, parks, forests,
playgrounds, recreational facilities, airports and other public requirements;
Proposed Language:
1.1.3 E Purpose and Intent
(E) Facilitate the provision of adequate police and fire protection, disaster evacuation, civil
defense, transportation, water, sewerage system , sanitary sewer, storm water and gas
facilities, flood protection, schools, parks, forests, playgrounds, recreational facilities,
airports and other public requirements;
Existing Language:
4.6.3 Sanitary Sewer and Water Supply
(C) Public water and sanitary sewer service must be provided to each lot within a project,
consistent with the requirements of Chapter 31, Utilities of the Charlottesville City Code and
the Standards and Design Manual. Such systems must be constructed by t he project
developer to the point at which they will join public service lines. When a project does not
abut a public water or sanitary sewer system or main, the project developer is responsible
for extending the public water or sewer system or main from t he existing location to the
project site, and dedicate the extension of the public service line to the City.
Page 42 of 225
Proposed Amendment
Util.1 through 7 – Language
Proposed Language:
4.6.3 Sanitary Sewer and Water Supply
(C) Public water and sanitary sewer service must be provided to each lot within a project,
consistent with the requirements of Chapter 31, Utilities of the Charlottesville City Code and
the Standards and Design Manual and Appendices. Such systems must be constructed by
the project developer to the point at which they will join public service lines the public
portion of the utility system. When a project does not abut a public water or sanitary sewer
system or main, the project developer is responsible for extending the public water or sewer
system or main from the existing location to the project site, and dedicate the extension of
the public service lines public portion of the utility extensions to the City.
Existing Language:
4.6.7 Underground Utilities
All utilities, including but not limited to wires, cables, pipes, conduits and appurtenant
equipment for electricity, natural gas, water, sewer, telephone or similar service, must be
located within a project as follows:
Proposed Language:
4.6.7 Underground Utilities
All utilities, including but not limited to wires, cables, pipes, conduits and appurtenant
equipment for electricity, natural gas, water, sanitary sewer, stormwater, telephone or
similar service, must be located within a project as follows:
Existing Language:
4.6.7 Underground Utilities
(C) No utility easements or facilities, other than those of City -owned and operated utilities,
may be located within the right-of-way for any public street, except upon the approval by City
Council of a franchise ordinance or public right -of-way use permit or encroachment
agreement. If the project developer desires to construct in, on, under, or adjacent to any
public streets located in the project any natural gas, water, sewer or electric light or power
works, pipes, wires, fixtures or systems, they must present plans or specifications to the City
for approval.
Proposed Language:
4.6.7 Underground Utilities
(C) No utility easements or facilities, other than those of City -owned and operated utilities,
may be located within the right-of-way for any public street, except upon the approval by City
Council of a franchise ordinance or public right -of-way use permit or encroachment
Page 43 of 225
Proposed Amendment
Util.1 through 7 – Language
agreement. If the project developer desires to construct in, on, under, or adjacent to any
public streets located in the project any natural gas, water, sanitary sewer, stormwater,
electric light or power works, pipes, wires, fixtures or systems, they must present plans or
specifications to the City for approval.
Existing Language:
6.1.5 Construction Surety
(B) In either case, prior to issuance of any building permit, and prior to issuance of any permit
authorizing any land disturbing activity within the project, the project developer must provide
a financial performance guarantee for completion of the site -related improvements. Site -
related improvements include any of the following: public street, curb, gutter sidewalk,
bicycle trail, drainage or sewerage system, waterline as part of a public system, or other
improvement dedicated for public use and proposed to be maintained by the City or another
public agency; and other improvements required by this Development Code, and to be
financed by private funds, for: vehicular ingress and egress, including traffic signalization
and control, for public access streets, for structures necessary to ensure stability of critical
slopes, and for stormwater management facilities.
Proposed Language:
6.1.5 Construction Surety
(B) In either case, prior to issuance of any building permit, and prior to issuance of any permit
authorizing any land disturbing activity within the project, the project developer must provide
a financial performance guarantee for completion of the site -related improvements. Site -
related improvements include any of the following : public: street, curb, gutter sidewalk,
bicycle trail, water, sanitary sewer, stormwater, drainage or sewerage system, waterline as
part of a public system, or other improvement dedicated for public use and proposed to be
maintained by the City or another public agency; and other improvements required by this
Development Code, and to be financed by private funds, for: vehicular ingress and egress,
including traffic signalization and control, for public access streets, for structures necessary
to ensure stability of critical slopes, and for stormwater management facilities.
Page 44 of 225
Proposed Amendment
Util.1 through 7 – Language
Analysis:
The current Development Code lacks clarity and consistency with the language referring to
certain utilities and applicable standards. These amendments assure more consistency and
clear references to existing standards and requirements that are often overlooked due to
lack of reference.
Page 45 of 225
Proposed Amendment
Tree Removal Permit
Section 34-5.2.10.A.1
Page: 5-41
Amendment Log A.1
Section 34-5.2.10.A.1
Existing Language:
Tree Removal Permit. Applies to all properties and is required prior to the removal of any
tree with a diameter breast height (DBH) of 8 inches or more in accordance with 4.9.1. Tree
Preservation and Replacement
a. Trees of any size determined to be dead, dying, or hazardous by the Administrator
do not require a permit for removal.
Proposed Language:
Tree Removal Permit. Applies to all lots and parcels and is required prior to the removal of
any tree with a diameter breast height (DBH) of 8 inches or more in accordance with 4.9.1.
Tree Preservation and Replacement
a. Trees of any size determined to be dead, dying, or hazardous by the
Administrator do not require a permit for removal.
b. If a project is subject to Development Review, tree removal is reviewed within
that process, and no Tree Removal Permit is required.
Analysis:
The proposed amendment to Section 34-5.2.10.A.1 clarifies two important aspects of how
tree removal is regulated within the Development Code. First, the update replaces the term
“properties” with “lots and parcels, ” which improves consistency with the terminology
already used throughout the Development Code. The Code relies heavily on “lots, ”
“parcels, ” and other defined land-unit terms when establishing applicability for
development standards, review procedures, and submittal requirements. By making this
change, the Tree Removal Permit section now aligns with the established language
patterns of Chapter 34, reducing ambiguity and bringing the terminology into harmony with
the rest of the Code.
The second change addresses situations where an applicant is already undergoing
Development Review through a Development Plan or Final Site Plan. In current practice,
planners review all proposed tree removals associated with those applications to ensure
they comply with the applicable standards in Section 4.9.1, as well as any other relevant
portions of the Development Code. Because those removals are already being evaluated
within the Development Review process, requiring a separate Tree Removal Permit creates
an unnecessary second application for the same action. The proposed amendment
formally recognizes this by stating that when a project is subject to Development Review,
Page 46 of 225
Proposed Amendment
Tree Removal Permit
tree removal will be reviewed within that existing process, and no Tree Removal Permit is
required. This change does not alter the substantive standards for tree removal; it only
eliminates the redundant permit for projects that already undergo a comprehensive,
code-based review.
All other projects that are not subject to Development Review will continue to be required
to obtain a Tree Removal Permit before removing any tree eight inches DBH or greater.
Those applicants must still provide the information necessary to demonstrate that the
proposed removal complies with the applicable standards and exemptions described in
the Development Code. This maintains the existing protections and review requirements
for standalone tree removal while streamlining the process for projects already undergoing
a more extensive review. Overall, the amendment improves clarity, reduces duplicative
applications, and reinforces consistency in how land units and review processes are
referenced throughout the Code.
Page 47 of 225
Proposed Amendment
Private Streets
Section 34-7.2
Page: 7-21
Amendment Log A.2
Section 34-7.2
Existing Language:
Street. A public or private way that is publicly accessible and affords a principal means of
access to abutting property. Streets generally consist of roadways and streetscapes.
Proposed Language:
Street. A public or private way that is publicly accessible and affords provides a principal
means of access to abutting property and includes the roadway and associated
streetscape elements. Streets generally consist of roadways and streetscapes. Streets
shall meet the following criteria:
Public Street: A street located entirely within a publicly dedicated and accepted
right-of-way, under the ownership and maintenance of a governmental entity and
design per the City’s Standards and Design Manual.
Private Street: A street located on a separate, recorded lot or tract that is not part of
any abutting property. Private streets shall not be established solely by easement
across private property and must comply with the City’s Standards and Design
Manual and be bonded to the same standards as a Public Street during
construction. Ownership and maintenance shall be the responsibility of a private
entity such as a homeowners’ association or other legally binding documents.
Analysis:
The proposed amendment to Section 34-7.2 ensures both private and public streets are
established under the same standards. When private streets are permitted under
easements without separation from other property, the establishment of street lot lines per
Section 34-2.10.1.C is not clearly defined. Amending the definition of streets to ensure all
streets are separated from private land ensures development adjacent to all streets is
consistent and aligned with the purposes and intents of code sections regulating the form
of development along street frontages.
Page 48 of 225
Proposed Amendment
Administrator Review Authority
Section 34-5.1.6.B.2
Page: 5-9
Amendment Log A.5
Section 34-5.1.6.B.2
Existing Language:
2. Review Authority
The Administrator is responsible for review and recommendation regarding:
a. Comprehensive Plan adoption and amendments;
b. Review of Public Facilities;
c. Text amendments to this Development Code;
d. Map amendments to the official zoning map (rezoning);
e. Certificates of Appropriateness under Major Historic Review;
f. Variances;
g. Floodplain Variances;
h. Special Use Permits; and
i. Critical Slope Special Exceptions.
Proposed Language:
2. Review Authority
The Administrator is responsible for review and recommendation regarding:
a. Comprehensive Plan adoption and amendments;
b. Review of Public Facilities;
c. Text amendments to this Development Code;
d. Map amendments to the official zoning map (rezoning);
e. Certificates of Appropriateness under Major Historic Review;
f. Variances;
g. Floodplain Variances;
h. Special Use Permits; and
i. Special Exception Permits; and
ij. Critical Slope Special Exceptions.
Analysis:
Per the Summary of Review Authority in Section 34-5.1.1.1, the Administrator is
responsible for review and recommendation of Special Exception Permits. However, this
responsibility is not included in Section 34-5.1.6.B.2. Adding text to algin Section 34-
5.1.6.B.2 with Section 34-5.1.1. ensures consistency and clarity in the review process for
Special Exception Permits.
Page 49 of 225
Proposed Amendment
RN-A Reference in Streetscape Standards
Section 34-4.4.5.D.9.c
Page: 4-21
Amendment Log A.6
Section 34-5.1.6.B.2
Existing Language:
In Residential (R-) zoning districts, when the project fronts on an existing street and
adjacent property on either side of the project does not have an existing streetscape, the
Administrator may allow the project developmer to contribute to the streetscape fund,
maintained and administered by the City, an amount equivalent to the cost of the
dedication of land for and the construction of the streetscape on the property.
Proposed Language:
In Residential (R-) and Residential Core Neighborhood (RN-) zoning districts, when the
project fronts on an existing street and adjacent property on either side of the project does
not have an existing streetscape, the Administrator may allow the project developer
developmer to contribute to the streetscape fund, maintained and administered by the
City, an amount equivalent to the cost of the dedication of land for and the construction of
the streetscape on the property.
Analysis:
While the RN-A Residential Core Neighborhood zoning district is categorized as a
residential district under Article 34-2.2 along with R-A Residential A, R-B Residential B, and
R-C Residential C, the district is not included in the exception criteria for existing
streetscapes which are eligible for contribution to the streetscape fund in lieu of
construction.
Page 50 of 225
Proposed Amendment
State Changes to Planning Commission Authority
Section 34-6.7.1.A.2.a.iv
Page: 6-13
Amendment Log A.7
Section 34-5.1.6.B.2
Existing Language:
2. Authority
a. General
The functions and duties of the Subdivision Administrator under this Development
Code include:
i. Administration of provisions of this Development Code pertaining to the
subdivision of land;
ii. Delegation of any act authorized by this Development Code to be carried out by
the Subdivision Administrator to an appropriate designee;
iii. Enforcement of the provisions of this Development Code pertaining to the
subdivision of land; and
iv. Provision of expertise and technical assistance to the Planning Commission.
Proposed Language:
2. Authority
a. General
The functions and duties of the Subdivision Administrator under this Development
Code include:
i. Administration of provisions of this Development Code pertaining to the
subdivision of land;
ii. Delegation of any act authorized by this Development Code to be carried out by
the Subdivision Administrator to an appropriate designee; and
iii. Enforcement of the provisions of this Development Code pertaining to the
subdivision of land; and.
iv. Provision of expertise and technical assistance to the Planning Commission.
Analysis:
Virginia SB974 previously removed planning commission approval authority for the
administrative review process for subdivision review and assigned such authority solely to
a designated agent. The code amendment ensures the Development Code aligns with state
requirements.
Page 51 of 225
Proposed Amendment
State Regulations and RN-A Zoning
Section 34-2.2.1 and 34-2.2.3.A.2
Pages: 2-7 and 2-10
Amendment Log A.8
Section 34-2.2.1
Existing Language:
RN-A
25’ or 40’ lot width (min)
1 dwelling unit (max)
35’ height (max)
40’ building width (max)
Proposed Language:
RN-A
25’ or 40’ lot width (min)
2 dwelling unit (max)
35’ height (max)
40’ building width (max)
Section 34-2.2.3.A.2
Existing Language:
DENSITY
Base 1
With bonus:
Existing Structure Preservation 2
With bonus:
Affordable Dwelling Unit 6
Proposed Language:
DENSITY
Base 2
With bonus:
Existing Structure Preservation 3
With bonus:
Affordable Dwelling Unit 6
Analysis:
With Code of Virginia § 15.2-2292.3 now requiring all localities to permit an accessory
dwelling unit by-right on any single-family residential lot, Charlottesville must ensure that
every residential district—including RN-A—allows a principal dwelling and an additional
Page 52 of 225
Proposed Amendment
State Regulations and RN-A Zoning
unit without relying on discretionary bonuses. This new statewide mandate establishes a
clear baseline expectation: every lot must be able to host one accessory unit in addition to
the primary residence, and that allowance must be achievable by-right.
Under our current Development Code, the RN-A district provides only one dwelling unit by-
right, and any additional unit must come through a bonus mechanism. The most common
path is the existing structure preservation bonus, but that incentive applies only when a
building was constructed and occupied before December 18, 2023 and retains its primary
façade and envelope depth. On undeveloped RN-A lots, new subdivisions, or lots where
new construction replaces older structures, no qualifying building exists, so the
preservation bonus cannot be accessed. In those cases, the maximum by-right dwelling
count remains one, and a property owner cannot add a second unit unless it qualifies for
the Affordable Dwelling Unit bonus. Because the state law requires that every single-family
lot accommodate an accessory unit without depending on bonuses, RN-A’s one-unit base
becomes incompatible with § 15.2-2292.3 once the requirement takes effect.
At the same time, our Development Code already uses the term “ADU” exclusively to mean
“Affordable Dwelling Unit, ” and introducing a second meaning for “Accessory Dwelling
Unit” would create confusion, conflict with multiple code chapters, and complicate the
administration of affordability programs. Rather than redefining terminology or
restructuring the code’s use framework, the most straightforward and least disruptive
solution is to increase the RN-A base density from one unit to two. Doing so ensures that
every lot—regardless of development history—can support a principal dwelling and an
accessory unit as required by state law, while preserving the clarity of our existing
vocabulary and avoiding unnecessary revisions elsewhere in the code.
To maintain the purpose and value of the preservation bonus, it must be adjusted as well.
Increasing the preservation bonus from two units to three keeps it meaningful and
continues to reward projects that retain eligible existing structures. Keeping the Affordable
Dwelling Unit bonus at six units maintains the current affordability incentive structure
without interfering with the new state requirement. Together, these changes preserve
RN-A’s intent, keep the bonus hierarchy coherent, avoid introducing a new definition for
“ADU, ” and ensure that all RN-A lots comply with § 15.2-2292.3 by allowing an accessory
unit by-right.
Page 53 of 225
Proposed Amendment
Existing Structure Preservation Bonus Clarification
Section 34-2.10.6.A.2.e
Page: 2-117
Amendment Log A.9
Section 34-2.10.6.A.2.e
Existing Language:
e. When permitted by the Zoning District, a project utilizing the Existing Structure
Preservation Bonus for density will be deemed to comply with the Build-To requirements.
Proposed Language:
e. When permitted by the Zoning District, a project utilizing eligible for the Existing
Structure Preservation Bonus for density will be deemed to comply with the Build-To
requirements.
Analysis:
The current wording of this section creates confusion regarding the applicability of Build-To
requirements for developments with existing structures in a residential zoning district (R-A,
RN-A, R-B, and R-C). The amendment clarifies that existing structures meeting the
requirements of Section 34-4.2.1.C are deemed to comply with Build-to requirements
regardless of the application of bonus allowances per Section 34-4.2.1.B.
Page 54 of 225
Proposed Amendment
Alignment of Approval Processes
Section 34-5.2.16.C.2
Page: 5-57
Amendment Log A.11
Section 34-5.2.16.C.2
Existing Language:
C. Review and Decision Process
1. Administrative Review
The Administrator will review the application for a Critical Slopes Special Exception and will
provide a staff report and recommendation to Planning Commission in advance of the
public meeting. Prior to the preparation of the staff report, City staff may make
recommendations to the Administrator to include in the staff report.
2. Notice
Notice of the public meeting must be given in accordance with Code of Virginia § 15.2-
2204.
3. Planning Commission Review
The Planning Commission will review the application and report its findings and
recommendations to the City Council.
4. City Council Decision
a. The City Council will conduct a public meeting on the application. The City
Council may hold a joint public meeting with the Planning Commission.
b. If the City Council grants a Critical Slopes Special Exception, the Council can set
forth any reasonable conditions which apply to the approval granted.
Proposed Language:
C. Review and Decision Process
1. Administrative Review
The Administrator will review the application for a Critical Slopes Special Exception and will
provide a staff report and recommendation to Planning Commission in advance of the
public meeting. Prior to the preparation of the staff report, City staff may make
recommendations to the Administrator to include in the staff report.
2. Notice
Notice of the public meeting must be given in accordance with Code of Virginia § 15.2-
2204.
23. Planning Commission Review
The Planning Commission will review the application and report its findings and
recommendations to the City Council.
34. City Council Decision
a. The City Council will conduct a public meeting on the application. The City
Council may hold a joint public meeting with the Planning Commission.
Page 55 of 225
Proposed Amendment
Alignment of Approval Processes
b. If the City Council grants a Critical Slopes Special Exception, the Council can set
forth any reasonable conditions which apply to the approval granted.
Analysis:
The current wording of this section aligns with approval processes such as Special Use
Permits which require a public hearing and appropriate notice of public hearing(s).
However, Critical Slopes Special Exception Permits require a public meeting but not a
public hearing per Section 34-5.1.1. The code section recommended for removal creates
confusion as the referenced public hearing requirements do not apply to the Critical
Slopes Special Exception Permit. This removal aligns the Critical Slopes Special Exception
Permit section with the Special Exception Permit section in Section 34-5.2.15, which also
requires a public meeting but no public hearing.
Page 56 of 225
Proposed Amendment
Split Zoned Lots and Development Standards
Section 34-2.1.2.C
Page: 2-4
Amendment Log A.13
Section 34-2.1.2.C
Existing Language:
Where a Section is listed as applying, and the zoning district includes standards for that
requirement, all applicable standards must be met. The applicable standards may be
further modified by the applicability provisions for each set of standards in Div. 2.10. Rules
for Zoning Districts. Applicability may also be modified by Div. 5.3. Nonconformities.
Proposed Language:
Where a Section is listed as applying, and the zoning district includes standards for that
requirement, all applicable standards must be met. For split-zoned parcels (lots containing
multiple base zoning districts, excluding overlay districts), the more restrictive district
standards shall apply to the lot as a whole. The applicable standards may be further
modified by the applicability provisions for each set of standards in Div. 2.10. Rules for
Zoning Districts. Applicability may also be modified by Div. 5.3. Nonconformities.
Proposed Language to be removed:
Section 34-2.10.10.A.3.a.i
If a single building spans multiple zoning districts, the more restrictive Building Width
applies to the entirety of the building.
Analysis:
The Development Code does not currently provide clear direction on how district standards apply
to parcels that contain more than one base zoning district. While Section 34-2.10.10.A.3.a.i
addresses Building Width for structures spanning multiple zoning districts, other critical
standards—such as maximum building footprint, build-to requirements, height, and massing—
remain unaddressed. This creates ambiguity for applicants and staff when interpreting which
standards govern development on split-zoned parcels.
Because dimensional and form standards vary significantly between zoning districts, consistent
application is essential to maintaining predictable outcomes and ensuring equitable administration
of the Code. Establishing that the more restrictive district standard applies across the entirety of a
split-zoned lot provides necessary clarity and avoids selective application of standards based
solely on internal parcel boundaries. This approach also encourages applicants to resolve
underlying split-zoning conditions through appropriate zoning actions rather than relying on
fragmented standards during development review.
Page 57 of 225
Proposed Amendment
Split Zoned Lots and Development Standards
This amendment applies only to district standards and does not alter how uses are regulated under
Section 34-3.1. Each portion of a split-zoned lot may continue to accommodate uses permitted
within its respective zoning district. By placing this general rule within Section 34-2.1.2.C, staff
recommends removing Section 34-2.10.10.A.3.a.i, as its narrow language becomes redundant
once a broader governing principle for split-zoned parcels is established.
Page 58 of 225
Proposed Amendment
Revisions to an Approved Development Plan or Final Site Plan
Sections 34-5.2.9.E.2.c
Page: 5-40
Amendment Log A.16
Existing Language:
c. Revisions to an Approved Development Plan or Final Site Plan
i. Minor revisions to an approved Development Plan or Final Site Plan may be
approved by the Administrator. The following revisions are considered minor:
a) Up to 10% increase in the gross floor area of a single building;
b) Any decrease in gross floor area of a single building;
c) Up to 10% reduction in the approved setbacks from street or common lot
lines; and
d) Relocation of parking areas, internal driveways or structures where
relocation occurs more than 100 feet from street or common lot lines.
ii. All other changes to an approved Development Plan or Final Site Plan must be
resubmitted as a new application.
Proposed Language:
c. Revisions to an Approved Development Plan or Final Site Plan
i. Minor revisions to an approved Development Plan or Final Site Plan during the
period of validity may be granted by the Administrator after completion of the
appropriate review. Minor revisions per this section do not constitute a waiver nor
extend the period of validity of the plan. The following revisions are considered
minor:
a) Up to 10% increase in the gross floor area of a single building;
b) Any decrease in gross floor area of a single building;
c) Up to 10% reduction in the approved setbacks from street or common lot
lines;
d) Relocation of parking areas, internal driveways or structures where
relocation occurs more than 100 feet from street or common lot lines; and
e) additional unlisted minor revisions that do not substantially alter the
vested plans as determined by the Administrator.
ii. All other changes to an approved Development Plan or Final Site Plan must be
resubmitted as a new application.
Analysis:
This amendment is intended to align the City’s Development Code with Virginia Code
§ 15.2-2261(D), which governs the validity of approved plats and site plans and clarifies
that minor modifications made during that validity period do not extend or waive any rights
associated with the approved plan. Updating our local language to mirror these
Page 59 of 225
Proposed Amendment
Revisions to an Approved Development Plan or Final Site Plan
requirements ensures legal consistency, reduces ambiguity for applicants, and
strengthens our administrative practices.
The amendment also addresses a practical limitation in the current Code. While several
specific thresholds define “minor revisions, ” they do not encompass the broader range of
small, non-material adjustments routinely needed as projects move from approval toward
construction. Without a clear mechanism for approving these unlisted but truly minor
changes, applicants can be forced into unnecessary resubmittals, creating delays and
administrative inefficiencies. Granting the Administrator limited discretion to approve
additional minor revisions—when they do not materially alter the approved plan—provides
the flexibility needed to keep projects on track while maintaining appropriate safeguards.
This update is also forward-looking. The Development Code is still new, and staff are only
beginning to see how applicants will navigate revisions once projects receive initial
approvals. At this moment, we are receiving very few revision requests simply because
most plans are still early in the development pipeline. However, as projects advance over
the next one to two years, we anticipate a growing need for a predictable and streamlined
path for minor adjustments prior to or during construction. Establishing this framework
now positions the City to manage those future revisions efficiently and consistently.
Overall, the amendment strengthens legal compliance, improves administrative clarity,
and prepares the City for the expected increase in minor modifications as newly approved
projects progress toward construction.
Page 60 of 225
Proposed Amendment
Sign Permits & Certificate of Appropriateness (CoA) Applications
Section 34-4.11.3.a.2
Page 4-82
Amendment Log ADC.3
Section 34-4.11.3.a.2
Existing Language:
For signs within an ADC District, HC District, Entrance Corridor, or an IPP, a Certificate of
Appropriateness will be issued in lieu of a Sign Permit according to 5.2.6 Minor Historic
Review, 5.2.7 Major Historic Review, and 5.2.8 Corridor Review.
Proposed Language:
For signs located within an ADC District, HC District, Entrance Corridor, or an IPP, required
design review shall be conducted as part of the sign permit process. In these overlay
districts, the approved sign permit serves in lieu of a Certificate of Appropriateness for
sign-related work.
Analysis:
The current code language incorrectly states that a Certificate of Appropriateness (CoA)
will be issued in lieu of a sign permit for signs within the ADC, HC, Entrance Corridor, or IPP
overlay districts. In practice, this does not reflect how sign applications are reviewed or
approved. Several problems arise from this mismatch between code language and real-
world procedures, making revision necessary.
First, design review for signs is conducted within the sign permit workflow, not as a
separate CoA process. Zoning staff determines whether a proposed sign meets the
applicable sign regulations before design review staff evaluate its design. Only after zoning
confirms compliance does design review occur, and its approval allows the sign permit to
be issued. The existing language reverses this order by implying the CoA is the primary
approval mechanism.
Second, issuing a CoA for a sign creates the false impression that the CoA itself confers
zoning compliance, even though it does not. In all other contexts, a CoA addresses only
Page 61 of 225
Proposed Amendment
Sign Permits & Certificate of Appropriateness (CoA) Applications
design considerations and never substitutes for zoning approval. Maintaining an exception
for signs inadvertently elevates the CoA beyond its intended purpose and could mislead
applicants or reviewers into believing that historic or corridor approval overrides the
underlying zoning rules.
Third, the current code language does not acknowledge how integrated and
interdependent zoning and design review are for sign approvals. Signs must meet both
zoning regulations and design standards, and the existing wording disrupts that
relationship by suggesting an alternate approval path that does not align with actual
regulatory requirements or workflow sequencing.
Finally, revising the language restores consistency with both staff practice and regulatory
intent. By clarifying that design review approval must occur before issuance of a sign
permit, and that the sign permit serves in lieu of a CoA, the code better reflects established
procedures. This helps eliminate confusion for applicants, ensures internal alignment
between zoning and design review staff, and prevents misinterpretation that could lead to
procedural errors or improper approvals.
In short, the revision is necessary to ensure the ordinance accurately describes the real
approval pathway, maintains clear distinctions between zoning and design authority, and
supports a coherent and predictable permitting process.
Page 62 of 225
Proposed Amendment
Review and Approval Authority Table
Section 34-5.1.1
Page 5-3; 5-4
Amendment Log ADC.7
Section 34-5.1.1
Existing Language:
The following table summarizes the review and approval authority of various review bodies
and officials that implement and administer this Development Code.
Page 63 of 225
Proposed Amendment
Review and Approval Authority Table
Proposed Language:
The following table summarizes the review and approval authority of various review bodies
and officials that implement and administer this Development Code.
Page 64 of 225
Proposed Amendment
Review and Approval Authority Table
Analysis:
These corrections to the Review and Approval Authority table accurately reflect authorities of
the Board of Architectural Review as provided within the text of the Development Code.
Included below are the corresponding code sections for each proposed revision to the table.
Zoning Text Amendment and Zoning Map Amendment review authority, see 34-5.2.5.C.1.b:
When the property is within an ADC District, HC District, or an Individually Protected Property,
the Administrator will refer the application to the BAR for review as to whether the proposed
application will have an adverse impact on the district, and for recommendation as to
reasonable conditions which, if imposed, would mitigate any such impacts. The BAR may submit
a written report of its findings in support of its recommendation to the Planning Commission
and City Council.
Sign Permit review authority, see 34-5.2.10.A.3.a:
Signs in an Architectural Design Control District, Historic Conservation District, or an Individual
Protected Property are required to apply for a Certificate of Appropriateness according to 5.2.7.
Major Historic Review or 5.2.7. Major Historic Review instead of review under this Section.
Special Use Permit review authority, see 34-5.2.14.C.1.b:
When the property is within an ADC District, HC District, or an Individually Protected Property,
the Administrator will refer the application to the BAR for review as to whether the proposed
application will have an adverse impact on the district, and for recommendation as to
reasonable conditions which, if imposed, would mitigate any such impacts. The BAR must
submit a written report of its findings in support of its recommendation City Council.
Special Exception Permit review authority, see 34-5.2.15.C.1.c:
When the property is within an ADC district, HC district, or an IPP, the Administrator will refer
the application to the BAR for review as to whether the proposed exception will have an adverse
impact on the district, and for recommendation as the (sic.) to reasonable conditions which, if
imposed, would mitigate any such impacts. The BAR must submit a written report of its findings
in support of its recommendation to City Council.
Page 65 of 225
Proposed Amendment
Established Individually Protected Properties
Section 34-2.9.3.B
Page 2-85
Amendment Log ADC.14
Section 34-2.9.3.B
Existing Language:
Following is a list of landmarks, buildings and structures outside the City’s ADC Districts,
which are deemed by City Council to be of special historic, cultural, or architectural value.
Page 66 of 225
Proposed Amendment
Established Individually Protected Properties
Proposed Language: (Revisions to the list of established Individually Protected Properties are
shown in red.)
Street Number Street Name Tax Map Number Parcel Number
901 Emmet Street N. Tax Map 1 Parcel 1 (portion)
Street Number Street Name Tax Map Number Parcel Number
209 and 211 Sprigg Lane Tax Map 8 Parcel 28
Page 67 of 225
Proposed Amendment
Established Individually Protected Properties
Street Number Street Name Tax Map Number Parcel Number
1328 Riverdale Drive Tax Map 50 Parcel 5
Street Number Street Name Tax Map Number Parcel Number
104 Stadium Road Tax Map 16 Parcel 2
Street Number Street Name Tax Map Number Parcel Number
801 West Street Tax Map 31 Parcel 42
Analysis:
The proposed corrections to the list of established Individually Protected Properties (IPPs) are
necessary to improve address clarity, to remove demolished IPPs which were left on the list by
error during adoption in December 2023, and to amend the table by adding the most recently
designated property.
Page 68 of 225
Proposed Amendment
B.08 Bicycle Parking and Lodging
Section 34-4.5.2.C.1
Page: 4-27
Amendment Log B.08
Section 34-4.5.2.C.1
Existing Language:
Required Bicycle Parking
Bicycle parking must be provided in accordance with the following table:
Proposed Language:
Update Commercial by adding a subcategory for “Lodging”
Spaces Required (min)
Uses Short-Term Spaces Long-Term Spaces
Commercial
All uses 1 / 2,500 SF of gross floor
area, 2 min
1 / 5,500 SF of gross floor
area, 2 min
Lodging 1 / 2,500 SF of gross floor area not
intended for lodging, 2 min
1 Space per 40 rooms,
2 min
Analysis:
The current Development Code requires all Commercial uses to provide bicycle parking
according to a gross-floor-area formula. While this approach works for most commercial
activity, lodging uses (such as hotels) are unique: they typically have very large building
footprints but generate bicycle parking demand based on guests, employees, and the size
of publicly accessible non-lodging spaces rather than the overall square footage. Applying
the generic Commercial GFA ratios to lodging has resulted in bicycle parking requirements
Page 69 of 225
Proposed Amendment
B.08 Bicycle Parking and Lodging
far exceeding real-world demand, creating outcomes that are disproportionate and
inconsistent with multimodal best practices.
The proposed amendment uses two simple ratios: short-term spaces tied to non-lodging
areas of the building, and long-term spaces tied to the number of guest rooms. This
approach follows national guidance from the Association of Pedestrian and Bicycle
Professionals (APBP), which emphasizes that bicycle parking should be assigned based on
the nature of the users rather than total building size. APBP also distinguishes short-term
and long-term demand, noting that visitor trips tend to cluster around publicly accessible
spaces, while employees and overnight guests generate predictable long-term storage
needs. Similarly, the NACTO Urban Bikeway Design Guide encourages cities to adopt
context-sensitive ratios that respond to expected bicycle activity rather than applying
uniform formulas across all uses.
Peer practice further reinforces this direction. Cities with modern multimodal standards,
including Raleigh, use room-based ratios for hotel bicycle parking because room count
strongly correlates with employee and guest demand, while short-term visitor demand
aligns with the building’s active public spaces. Industry-specific guidance for hotel design
also supports this distinction, noting that secure long-term storage has become an
essential amenity for employees and cycling travelers, but that demand remains modest
and consistent across room counts rather than varying with building square footage.
The specific numbers selected for this amendment reflect these established patterns. The
short-term standard applies the existing Commercial ratio only to the portion of the
building that generates visitor trips, while the long-term standard uses a room-based ratio
common in other cities and consistent with national guidance on lodging-use behavior. The
minimum of two spaces for each type ensures that even small lodging uses provide basic
bicycle access and maintains consistency with the minimums applied across other
Commercial uses.
Page 70 of 225
Proposed Amendment
Food Trucks
Section 34-3.6.1 and 34-3.6.2.D
Page: 3-40 to 3-43
Amendment Log B.9
Section 34-3.6.1.B.7
Existing Language:
7. Only One Temporary use permit will be active on any lot or parcel at any time.
Proposed Language:
Remove line 7.
7. Only one temporary use permit will be active on any lot or parcel at any time.
8 7. All temporary uses and any appurtenant structures, signs, goods and other features
must be set back from an adjacent right-of-way by at least 20 feet.
9 8. All activities to be conducted pursuant to a temporary use permit must be in
compliance with:
a. The standards set forth in this Division, as applicable; and
b. All applicable city ordinances, permits and approvals, including, without
limitation: Occupancy permits, peddler’s licenses, sign permits, BAR certificates of
appropriateness, etc.
10 9. Use of all buildings and structures must be in compliance with all applicable building
code regulations.
11 10. A temporary use permit may be revoked by the Administrator at any time, due to the
failure of the permit holder to comply with all requirements of this Chapter. Notice of
revocation must be made in writing to the permit holder. Any person aggrieved by such
notice may appeal the revocation to the Board of Zoning Appeals.
Section 34-3.6.2.D
Existing Language:
Mobile Food Unit
A mobile food unit located on private property authorized by a temporary use permit is
subject to the following regulations:
1. No mobile food unit may be operated on private property without the mobile food unit
owner or their designee having first been issued a temporary use permit pursuant to this
section.
2. A temporary use permit allows the permittee to operate at up to 10 different properties.
An applicant may apply for more than one temporary use permit.
3. Applicants for a temporary use permit authorizing a mobile food unit to operate on
private property must provide:
Page 71 of 225
Proposed Amendment
Food Trucks
a. A City business license (or a statement from the commissioner of revenue that no
City business license is required).
b. A valid health permit from the Virginia Health Department stating that the mobile
food unit meets all applicable standards. A valid health permit must be maintained
for the duration of the temporary use permit.
c. Written permission from the owner of the private properties upon which the
permittee will operate.
d. A site diagram to be approved by the Administrator for each property, illustrating
access to the site, all parking areas, routes for ingress and egress, placement of the
mobile food unit, distance from property lines, garbage receptacles and any other
feature associated with the mobile food unit.
4. A mobile food unit temporary use permit is valid for one year from the date of issuance.
5. A mobile food unit operator cannot:
a. Sell anything other than food and non-alcoholic beverages and items incidental to
the product and its consumption;
b. Set up more than one covered 10 × 10 table to provide condiments to patrons;
c. Play any music that is audible outside of the vehicle;
d. Place or utilize any sign that is not permanently affixed to the mobile food unit;
e. Fail to provide receptacles and properly dispose of all trash, refuse, compost and
garbage that is generated by the use; and
f. Cause any liquid wastes to be discharged from the mobile food unit.
Proposed Language:
Mobile Food Unit
A mobile food unit located on private property authorized by a temporary use permit is
subject to the following regulations:
1. No mobile food unit may be operated on private property without the mobile food unit
owner or their designee having first been issued a temporary use permit pursuant to this
section.
2. A temporary use permit allows the permittee to operate at up to 10 different properties.
An applicant may apply for more than one temporary use permit.
3. Applicants for a temporary use permit authorizing a mobile food unit to operate on
private property must provide:
a. A City business license (or a statement from the commissioner of revenue that no
City business license is required).
b. A valid health permit from the Virginia Health Department stating that the mobile
food unit meets all applicable standards. A valid health permit must be maintained
for the duration of the temporary use permit.
Page 72 of 225
Proposed Amendment
Food Trucks
c. Written permission from the owner of the private properties upon which the
permittee will operate.
d. A site diagram to be approved by the Administrator for each property, illustrating
access to the site, all parking areas, routes for ingress and egress, placement of the
mobile food unit, distance from property lines, garbage receptacles and any other
feature associated with the mobile food unit.
e. Location of Mobile Food Unit when not in use
4. A mobile food unit temporary use permit is valid for one year from the date of issuance.
5. A mobile food unit operator cannot:
a. Sell anything other than food and non-alcoholic beverages and items incidental
to the product and its consumption;
b. Set up more than one covered 10 × 10 table to provide condiments to patrons;
c. b. Play any music that is audible outside of the vehicle;
d. c. Place or utilize any sign that is not permanently affixed to the mobile food unit;
e. d. Fail to provide receptacles and properly dispose of all trash, refuse, compost
and garbage that is generated by the use; and
f. e. Cause any liquid wastes to be discharged from the mobile food unit.
Analysis:
Mobile food units were previously regulated through a provisional use permit process that
allowed operators to obtain annual authorization to operate from multiple private
properties throughout the City. When the Development Code was adopted, mobile food
units were incorporated into the Temporary Uses section with many of the same
operational requirements. In doing so, a conflict was created between Section 34-
3.6.1.B.6, which allows multiple temporary use permits to be issued for the same lot, and
Section 34-3.6.1.B.7, which limits a property to only one active temporary use permit at a
time. As a result, multiple food truck operators may obtain permits to operate from the
same property, but only one may legally operate at any given time. This provision has
created administrative challenges for staff, confusion for applicants, and limitations on
commercial properties seeking to accommodate multiple food vendors as a temporary
use.
During discussions regarding food truck regulations, staff, Planning Commissioners, and
other City departments identified several provisions that warrant clarification or
modification. The proposed amendment removes the restriction allowing only one active
temporary use permit on a property at a time and eliminates the provision authorizing a
covered 10-by-10-foot table for condiment service. Removal of the table provision
reinforces the temporary nature of mobile food unit operations by eliminating an accessory
feature that is not necessary for food truck operations and is inconsistent with the intent of
Page 73 of 225
Proposed Amendment
Food Trucks
a temporary use. These changes provide additional flexibility for food truck operators while
maintaining existing requirements related to licensing, health permits, site plans, signage,
waste management, and other operational standards. The amendment does not establish
regulations for food truck courts or permanent food truck facilities and does not alter the
requirement that mobile food units operate pursuant to a temporary use permit.
The amendment also adds a requirement for applicants to identify the location of a mobile
food unit when it is not in operation. This information will assist staff in administering
permits and monitoring compliance with temporary use regulations by providing a clearer
understanding of where mobile food units are stored between operating periods. Together,
these revisions remove unnecessary regulatory conflicts, improve permit administration,
and preserve the distinction between temporary mobile food unit operations and more
permanent food service establishments while maintaining the City's ability to regulate
these uses as temporary activities.
Page 74 of 225
Proposed Amendment
Nonresidential Height in the R-A and R-B Districts
Sections 34-2.2.2.A.B.1 and 2.2.4.B.1
Page: 2-9 and 2-13
Amendment Log B.12
Sections 34-2.2.2.A.B.1 and 2.2.4.B.1
Existing Language:
No existing language for maximum height for nonresidential structures in the R-A and R-B,
Zoning Districts.
Proposed Language:
34-2.2.2.A.B.1 and 2.2.4.B.1
A. Building height (feet)
1 unit and nonresidential 35’
B. Side wall height (max)
1 unit and nonresidential 28’
Analysis:
In the R-A and R-B Zoning Districts, the maximum allowable height is currently specified only for
residential structures. However, these districts permit several nonresidential uses, such as
religious assembly and day care facilities. While Section 34-2.8 (Alternate Forms) provides
additional height and form options, it does not presently apply to the nonresidential uses allowed
under Section 34-3.1. Should the Alternate Forms provisions be expanded in the future, further
analysis will be needed to determine appropriate height and form standards for those uses.
To address the current gap in the code, staff recommends establishing maximum height and side
wall height standards for nonresidential uses that match those of one-unit residential structures.
This approach provides clarity, maintains consistency within the districts, and ensures reasonable
development standards until a more comprehensive review can be conducted.
Page 75 of 225
Proposed Amendment
Special Exception Permits
Sections 34-5.2.15.A
Page: 5-54
Amendment Log B.14
Sections 34-5.2.15.A
Existing Language:
1. The City Council may grant a modification of any physical dimensional standard of this
Development Code by Special Exception Permit.
2. A Special Exception Permits may be granted for physical dimensional standards
described in the following Divisions:
Proposed Language:
34-2.2.2.A.B.1 and 2.2.4.B.1
1. The City Council may grant a modification of any physical dimensional or numerical
standard of this Development Code by Special Exception Permit.
2. A Special Exception Permits may be granted for physical dimensional or numerical
standards described in the following Divisions:
Analysis:
The current language in Section 34-5.2.15.A limits Special Exception Permits (SEPs) to
modifications of physical dimensional standards. While this is appropriate for many provisions
within the Development Code, it creates a gap for circumstances where relief from numerical
standards is warranted to support feasibility, innovation, or site-specific constraints. For example,
under the existing language, City Council could modify the physical dimensional requirements for
short- or long-term bicycle storage but would not have the ability to adjust the number of required
bicycle parking spaces.
Expanding SEP eligibility to include numerical standards provides a more complete and functional
tool for addressing practical challenges encountered in development proposals. Allowing City
Council to consider modifications to both physical dimensional and numerical standards ensure a
more flexible, context-sensitive approach to evaluating unique project conditions, while still
maintaining alignment with the broader objectives of the Development Code and the
Comprehensive Plan. This change enhances the City’s ability to support well-designed projects that
meet community needs without imposing unnecessary barriers when strict application of
numerical requirements may not be appropriate.
Page 76 of 225
Proposed Amendment
Sublot Access Clarification
Section 34-7.1.2.E.3.b
Page: 7-10
Amendment Log B.15
Section 34-7.1.2.E.3.b
Existing Language:
b. A sublot is not required to abut a primary street, side street, or alley but must abut a
permanent access easement that meets the requirements of Article 6. Subdivision.
Proposed Language:
b. A sublot is not required to abut a primary street, side street, or alley but must abut a
permanent access easement that meets the requirements of Article 6. Subdivision. A
permanent access easement through abutting zoning lots is permitted when the easement
meets the requirements of Article 6. Subdivision.
Analysis:
The current wording of this section does not clearly articulate access easements for
sublots may be provided on adjacent zoning lots. The proposed amendment provides
clarity for property owners and developers regarding the allowances for sublot creation.
Page 77 of 225
Proposed Amendment
Active Depth
Section 34-2.10.10.B.2.b, 34-2.10.10.B.2.d, and 34-7.2
Page: 2-133 and 7-11
Amendment Log B.16
Section 34-2.10.10.B.2.b
Existing Language:
On primary streets, the active depth applies to all stories.
Proposed Language:
On primary streets, the active depth applies to the first two stories.
Section 34-2.10.10.B.2.d
Existing Language:
A Primary Building on a lot or sublot consisting of a maximum of only 1 dwelling unit and no
additional primary/principal uses does not have to meet the active depth requirements.
Proposed Language:
Remove existing language.
A Primary Building on a lot or sublot consisting of a maximum of only 1 dwelling unit and no
additional primary/principal uses does not have to meet the active depth requirements.
Section 34-7.2
Existing Language:
Active space. Any occupiable space designed and intended for human activity such as
living, working, commerce, sleeping, eating, or cooking as determined by the Administrator.
Restrooms, toilet rooms, closets, halls, storage or utility spaces, and similar areas are not
considered active space.
Proposed Language:
Active space. Any occupiable space designed and intended for human activity such as,
working, commerce, sleeping, eating, or cooking as determined by the Administrator.
Examples of active space include Residential Uses including Householding Living and
Group Living. Vehicle uses related to Residential Uses are not considered active space
Other examples of nonactive space include nonresidential restrooms, closets, storage
spaces, utility spaces, and similar spaces not intended for human activity.
Analysis:
These amendments refine how the Development Code regulates active depth and active space by
addressing implementation challenges repeatedly encountered during site plan review, applicant
consultations, and Planning Commission work sessions. The updates bring greater clarity and
Page 78 of 225
Proposed Amendment
Active Depth
flexibility while aligning Code language with the Planning Commission’s stated priorities for the
2026 amendment cycle.
First, the revision to Section 34-2.10.10.B.2.b, limiting active depth applicability on Primary Streets
to the first two stories, responds to concerns raised by both applicants and commissioners that
requiring active depth on every story creates upper-story floorplates that are difficult or impractical
to design—particularly in DX districts where the active depth requirement can reach 30 feet. During
the July 9th Code Clean-up Subcommittee meeting and July 28th Work Session, commissioners
emphasized that upper-story active depth does little to contribute to street activation and often
results in unusable or excessively constrained interior spaces. This amendment preserves the
pedestrian-oriented purpose of active depth at the street level while reducing unnecessary
constraints on higher floors.
Second, with the update to the Active Space definition to clearly include residential units, section
34-2.10.10.B.2.d is redundant and can be removed. By removing this code section, the code will
remain consistent and less prone to future consistence issues.
Finally, the amendment to Section 34-7.2 (Active Space definition) makes the most substantive
change in this set by:
1. Removing “halls” from the list of excluded non-active spaces, consistent with PC feedback
that hallways can serve important transitional or human-use functions and should not be
categorically excluded.
2. Adding explicit examples of active space, including “Residential Uses including
Householding Living and Group Living, ” which clarifies that standard residential interior
living areas meet the definition of active space.
3. Clarifying that vehicle-related areas associated with Residential Uses are not active space,
ensuring garages and similar areas remain outside the definition without relying on a
separate exception section.
These refinements directly respond to concerns raised in multiple subcommittee meetings that the
previous phrasing of “hall” and other excluded spaces was creating confusion when applying active
depth to multifamily layouts, especially where circulation spaces could qualify as active space
depending on context. Incorporating examples strengthens administrative clarity and helps
applicants more easily understand how their interior programming interacts with active depth
requirements.
Together, these amendments improve predictability for applicants, clarify ambiguities uncovered
during real-world code application, and refine the active depth and active space standards to
better match the Planning Commission’s policy direction. By focusing active depth on the building’s
street-facing lower stories, refining the single-unit exemption, and updating the definition of active
space, these changes produce a more functional and context-appropriate regulatory framework—
one that supports the city’s goals for activated streetscapes while ensuring practical feasibility for
residential and mixed-use development.
Page 79 of 225
Proposed Amendment
Nonconforming Buildings and Structures
Section 34-5.3.3.
Page: 5-62 to 5-66
Amendment Log B.17
Section 34-5.3.3.C.1
Existing Language:
New Primary Buildings on an Interior Lot
All new primary buildings must occupy the build-to zone until the build-to width
requirement has been met. Until all build-to width standards have been met, all new
primary buildings must occupy the build-to zone for their entire building width.
Proposed Language:
New Primary Buildings on an Interior Lot
New primary buildings and structures on interior lots are permitted as follows:
a. Rear Yard: New primary buildings and structures are permitted in the rear yard of the
existing nonconforming primary building. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
b. Side Yard: New primary buildings and structures are permitted in the side yard of the
existing nonconforming primary building. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
c. Side Street Yard: See New Primary Building on a Corner Lot.
d. Front Yard: All new front yard primary buildings must occupy the build-to zone until
the build-to width requirement has been met. Once the build-to requirements have
been met, a new front yard will be established based on the additional buildings.
Prior to the build-to width requirements being satisfied, the front yard will remain all
portions of the lot between the primary street lot line and the initial existing
nonconforming building. Transition setbacks may apply, see Div. 4.7 Transitions and
Screening.
Page 80 of 225
Proposed Amendment
Nonconforming Buildings and Structures
Graphics to be removed.
Section 34-5.3.3.C.2.b
Additions on an Interior Lot
Existing Language:
b. Side additions having a floor area less than 20% of the existing building footprint are
allowed. Once the build-to width standard has been met, side additions of any size
are allowed.
Proposed Language:
b. Side additions of any size allowed. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
Graphics to be removed.
Section 34-5.3.3.C.3
New Primary Buildings on a Corner Lot
Existing Language:
a. All new primary buildings must occupy the build-to zone until the build-to width
requirement for both streets have been met.
b. Once the build-to width requirement has been met for both streets, new primary
buildings may be placed behind the build-to zone.
Proposed Language:
New Primary Buildings on a Corner Lot
New primary buildings and structures on a corner lots are permitted as follows:
Page 81 of 225
Proposed Amendment
Nonconforming Buildings and Structures
a. Rear Yard: New primary buildings and structures are permitted in the rear yard of the
existing nonconforming primary building. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
b. Side Yard: New primary buildings and structures are permitted in the side yard of the
existing nonconforming primary building. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
c. Side Street Yard: All new side street yard primary buildings must occupy the build-to
zone until the build-to width requirement has been met. Once the build-to
requirements have been met, a new side street yard will be established based on
the additional buildings. Prior to the build-to width requirements being satisfied, the
side street yard will remain all portions of the lot between the side street lot line and
the initial existing nonconforming building. Transition setbacks may apply, see Div.
4.7 Transitions and Screening.
d. Front Yard: All new front yard primary buildings must occupy the build-to zone until
the build-to width requirement has been met. Once the build-to requirements have
been met, a new front yard will be established based on the additional buildings.
Prior to the build-to width requirements being satisfied, the front yard will remain all
portions of the lot between the primary street lot line and the initial existing
nonconforming building. Transition setbacks may apply, see Div. 4.7 Transitions and
Screening.
Graphics to be removed.
Section 34-5.3.3.C.4.b
Additions to Primary Buildings on a Corner Lot
Existing Language:
b. Side additions with floor area no greater than 20% of the existing primary building
footprint are allowed. Once the build-to width standard has been met for both
streets, side additions of any size are allowed.
Proposed Language:
b. Side additions of any size allowed. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
Graphics to be removed.
Section 34-5.3.3.C.4.c
Additions to Primary Buildings on a Corner Lot
Existing Language:
c. Rear additions of any size, located behind the build-to zone, are allowed provided:
Page 82 of 225
Proposed Amendment
Nonconforming Buildings and Structures
i. A landscape area at least 6 feet wide adjacent to the side street lot line is
installed across the entire length of the side street frontage. Breaks for
pedestrian, bicycle, and vehicular access of the minimum practical width are
allowed.
ii. The landscape area must include medium or large trees planted an
average of 30 feet on-center along the entire landscape area.
iii. Trees should be planted offset from street trees to maximize space for
canopy growth.
iv. All landscaping must meet the applicable standards of Div. 4.9.
Landscaping.
Proposed Language:
c. Rear additions of any size allowed. Transition setbacks may apply, see Div. 4.7
Transitions and Screening.
Graphics to be removed.
Analysis:
The proposed amendments to Section 34-5.3.3 of the Development Code respond to
specific concerns raised by the Planning Commission regarding how the existing build-to
requirements affect infill development, density goals, and the clarity of the nonconforming
building provisions. Under current language, new primary buildings on interior and corner
lots must first satisfy build-to width requirements before they may be constructed outside
the build-to zone. While this requirement is intended to reinforce street-related urban form,
the Planning Commission views it as unintentionally restrictive—particularly on lots
containing nonconforming primary buildings where the City seeks to encourage additional
units and site efficiency.
A significant source of confusion has been the distinction between rear additions to an
existing nonconforming primary building—which are allowed without meeting build-to
width—and new primary buildings placed behind the existing structure, which are treated
Page 83 of 225
Proposed Amendment
Nonconforming Buildings and Structures
differently. Several Commissioners have expressed that the Code creates a
counterproductive incentive: an applicant may construct a large rear addition by-right, but
if they instead choose a more flexible site layout that separates that volume into an
additional building, the Code forces them to meet build-to requirements before doing so.
This distinction, while technically consistent with the structure of the Code, is not intuitive
and has been interpreted as contradictory to overall density and housing production
objectives.
These amendments clarify and expand where new primary buildings and structures may be
located on both interior and corner lots. By explicitly permitting new buildings in rear, side,
and (for corner lots) side-street yards of an existing nonconforming building—subject only
to transition setback requirements—the revisions provide a more intuitive and permissive
framework for infill development. This supports the City’s goals by allowing additional units
or structures without forcing every project to front-load density at the street edge before
any other development can occur.
A key improvement in the proposed language is the clarification of yard establishment.
Under the amendments, the front yard and street-facing yard remain unchanged until the
build-to width requirement is fully met. No new front or side-street yard is established until
compliance occurs. This prevents partial build-to situations—such as only half the frontage
being built out—from inadvertently creating a new yard condition that could enable
undesirable site layouts, including the possibility of placing parking or vehicular areas in
locations the City intends to reserve for building frontage and pedestrian-oriented form.
Maintaining the original yard definitions until full build-to compliance ensures consistency
and protects the integrity of the street environment.
The amendments also remove percentage-based limits on side additions and eliminate
graphics that attempted to illustrate placement and build-to rules. With clearer, more
direct text, these graphics are no longer necessary and often caused interpretive
confusion. Their removal streamlines the code and improves usability for applicants, staff,
and the Planning Commission.
Overall, these revisions make Section 5.3.3 more permissive, clearer, and better aligned
with the City’s density, housing production, and urban design objectives. By resolving
ambiguities, supporting more flexible infill options, and ensuring yard conditions remain
appropriately regulated until build-to requirements are met, the amendments strengthen
the Development Code and reflect the Planning Commission’s policy direction.
Page 84 of 225
Tier 2 Amendment
Section 34-4.12.3.D
Page: 4-105
Working Document reference: B.19
Existing language:
D. Flood Lights and Flood Lamps
All flood lighting must be activated only by motion-sensors, and must be on a timer limiting
the illumination to a maximum of 15 minutes at a time.
Proposed language:
All flood lighting, except athletic field lighting in the Civic (CV) and Campus (CM) districts,
must be activated only by motion-sensors, and must be on a timer limiting the illumination
to a maximum of 15 minutes at a time.
Analysis:
Current timer provisions for flood lights do not in practice allow for athletic field lighting.
Adding an exemption to field lighting in the CV and CM districts would permit athletic field
lights within City parks, school grounds and the University of Virginia. These lights would
still have to comply with mounting and shielding requirements, as well as color
temperature and light trespass requirements which apply to all outdoor light fixtures.
Page 85 of 225
Proposed Amendment
Average Grade Clarification
Section 34-2.10.1.G
Page: 2-102
Amendment Log B.20
Section 34-2.10.1.G
Existing Language:
2. Full Building Method
For the full building method, a average grade is calculated by averaging the highest and
lowest elevation of existing grade within 5 feet of the building perimeter.
3. Building Module Method
For the building module method, average grade is calculated independent for each building
module by averaging the highest and lowest elevation of existing grade within 5 feet of the
perimeter of each building module.
Proposed Language:
2. Full Building Method
For the full building method, a average grade is calculated by averaging the highest and
lowest elevation of existing finished grade within 5 feet of the building perimeter.
3. Building Module Method
For the building module method, average grade is calculated independent for each building
module by averaging the highest and lowest elevation of existing finished grade within 5
feet of the perimeter of each building module.
Analysis:
Per Section 34-7.2, the existing grade is the grade prior to any site modification.
Requirements such as building height per Section 34-2.10.9.A.4.b are measured from the
average grade. Basing the average grade on existing grade requires a building’s height to be
measured from a grade which no longer exists due to site modification as a part of the
project and creates an inconsistent pattern of development.
Page 86 of 225
City Council Meeting Minutes – July 20, 2026
CHARLOTTESVILLE CITY COUNCIL MEETING MINUTES
July 20, 2026 at 4:00 PM
Council Chamber
The Charlottesville City Council met on Monday, July 20, 2026. Mayor Juandiego Wade called the
meeting to order, and Clerk of Council Kyna Thomas called the roll, noting the following councilors
present: Mayor Juandiego Wade, Vice Mayor Natalie Oschrin and Councilors Jen Fleisher and Michael
Payne.
*Councilor Snook requested approval to participate electronically, and there were technical difficulties
while trying to establish an audible connection.
On motion by Payne, seconded by Fleisher, Council by a 4-0 vote approved the meeting agenda
as amended to approve Item #17 by motion instead of resolution (Ayes: Fleisher, Oschrin, Payne, Wade;
Absent: Snook).
REPORTS
1. REPORT: Transportation Planning Annual Update
Ben Chambers, Transportation Planning Manager, presented the annual Transportation Planning Update
to highlight the accomplishments of the previous year and look ahead to upcoming work, including the
Citywide Mobility Plan.
Zoe Macomber, Senior Transportation Planner, described the process for planning, prioritizing and
implementing traffic-calming design elements on Rose Hill Drive with goals to:
• reduce the design speed to 25 mph,
• improve bicycle safety with protected facilities,
• improve pedestrian crossing safety,
• reduce conflicts between transit vehicles and bicycles at bus stops,
• provide space for bus stop amenities and bike parking, and
• provide safe pick-up/drop-off patterns in front of Burley Middle School.
Mr. Chambers provided an overview of Citywide Mobility Plan scope, and key findings from the review
of existing plans. The purposes of the Citywide Mobility Plan are to:
• Create a consistent approach to identifying and designing projects
• Ensure approach promotes equity and is consistent with the City’s adopted plans and policies,
and
• Develop a long-term vision and an implementation strategy with a program of projects, policies,
and actions that will achieve that vision.
City Council engaged in discussion.
*A voice connection was confirmed at 5:24 p.m. for Councilor Lloyd Snook and he confirmed that he was
participating from Basye, Virginia, because of personal travel. On motion by Fleisher, seconded by
Oschrin Council voted 4-0 to approve electronic participation by Councilor Snook (Ayes: Fleisher,
Oschrin, Payne, Wade; Noes: none).
Page 87 of 225
City Council Meeting Minutes – July 20, 2026
CLOSED MEETING
On motion by Oschrin, seconded by Fleisher, Council voted 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook,
Wade; Noes: none) to meet in closed session as authorized by the Virginia Freedom of Information Act,
specifically:
1. Pursuant to Virginia Code Section 2.2-3711(A)(1) for:
a. discussion and consideration of the performance of a City Council appointee,
specifically, to conduct the City Manager’s annual performance evaluation, and
b. discussion and consideration of prospective candidates to be appointed to the Retirement
Commission
On motion by Oschrin, seconded by Fleisher, Council certified by the following vote: 5-0 (Ayes: Fleisher,
Oschrin, Payne, Snook, Wade; Noes: none.), that to the best of each Council member’s knowledge only
public business matters lawfully exempted from the open meeting requirements of the Virginia Freedom
of Information Act and identified in the Motion convening the closed session were heard, discussed or
considered in the closed session.
BUSINESS SESSION
City Council began the business meeting by observing a moment of silence.
ANNOUNCEMENTS
Councilor Payne acknowledged ICE raids in Greene County involving individuals in their work vehicles.
He also announced open seats on Council-appointed boards and commissions.
Vice Mayor Oschrin announced the open application process for eBike vouchers at
www.connect.charlottesville.gov, and she announced the MyCville public engagement platform.
COMMUNITY MATTERS
Mayor Wade had City Attorney Maddux make remarks to address requests for City Council to rescind or
take another vote regarding its decision to approve a Certificate of Appropriateness for The Mark project
on 7th Street, Mr. Maddux summarized legalities as outlined in the following statement released to the
public:
“CHARLOTTESVILLE, VA - The Charlottesville City Council recognizes that its decision regarding
the historic review Certificate of Appropriateness for The Mark has generated significant concern and
disagreement within the community. Council respects the right of residents to continue expressing
their views about the project and understands that some residents remain deeply disappointed by the
decision.
In recent days, members of the community have asked Council to rescind its prior action or vote again
on the Certificate of Appropriateness. Council is providing the following clarification regarding the
legal process applicable to that decision.
Council’s general procedural rules include a process for reconsidering certain votes. Those rules may
apply, for example, when Council adopts a resolution establishing or changing a City policy on a
matter that remains within its continuing authority.
Page 88 of 225
City Council Meeting Minutes – July 20, 2026
The decision regarding The Mark is different. It was made under the specific historic review process
established by Virginia law and the City’s Development Code. That process provides for a decision by
the Board of Architectural Review and an appeal to Council. Council’s decision on the appeal is the
final decision in this case.
Council’s general reconsideration procedures do not override or add to that specific process. Because
the historic-review process does not authorize Council to reopen, rescind, or re-vote on its decision,
another vote is not legally available."
Councilor Payne requested that Council initiate a Zoning Text Amendment process to expand the core
neighborhood overlay and allow student housing by Special Exception Permit versus by-right and amend the
0.5-mile radius framework so that student housing does not pay lower affordable housing fees than non-
student housing.
Mayor Wade opened the floor for comments from the public.
1. Mary Gulland, city resident, spoke in support of the City proposal to end the Rivanna encampment.
2. Claude Convisser, city resident, encouraged Council not to open the proposed homeless facility. He
spoke of a personal situation involving his stays at The Haven and PACEM.
3. Jeffrey Lisciandrello, city resident, spoke in support of clearing the Free Bridge encampment. He
also spoke in opposition to building a low-barrier shelter.
4. Donnas Chambers, Free Bridge encampment resident, spoke about the September 1st deadline to
clear the Free Bridge encampment, and expressed concerns and challenges with the available
shelters and programs perpetuating homelessness conditions.
5. Jennifer Grant, Free Bridge encampment resident, spoke about the September 1st deadline to clear
the Free Bridge encampment, and expressed concerns about pets being allowed at the homeless
shelter, and about various entities such as jail officials being sent to the encampment. She stated
that many people in the encampment need mental health resources and to be helped by Region Ten.
6. Rosia Parker, city resident, spoke about housing and the history of dismantling and displacing
Black and Brown residents. She suggested that funds for jail renovations should have been used
instead to help the homeless population.
7. Anna Malinowski ceded her time to Christopher Kenneth Scott Hall, who stated that he is a drifter
and has been homeless for some time. city resident, and that certain nonprofit organizations who
provide services to homeless individuals need to hear directly from the City. Ms. Malinowski used
the remaining time to speak against the September 1 deadline for disbanding the Rivanna
encampment.
8. Frank Bechter, city resident, spoke about the need to value, protect, respect, and celebrate
neighbors by receiving community input for development projects - particularly affordable housing
at 7th and Delevan Streets.
9. Rev. Dr. R. S. Long, Jr., spoke in defense of building public trust related to public housing decisions
by including community members in the decision-making process and creating stronger zoning
practices.
10. Laura Goldblatt, city resident, reviewed the effects of luxury student housing on surrounding
neighborhoods, and how student housing contributes to rising costs, displacement and
"studentification."
11. Brandon Tyson, First Baptist Church, spoke about the need for City Council to include Fifeville
Page 89 of 225
City Council Meeting Minutes – July 20, 2026
residents in student housing discussions that impact their neighborhood, and to build housing that
makes sense.
12. Roscoe, city resident, stated that he started "tent city" as a protest. He stated that he wants to start
another movement.
13. Don Gathers, city resident, referenced a statement from the June 24 meeting by developers about
renting to people who can afford the units. He requested that Council demand more from the
developers, and to know what the plans are for the $7M allotted by the State budget to address
homelessness...
14. Drew, city resident and public health worker, opposed the city's decision to disband the Free Bridge
encampment.
15. Zyanha Bryant, city resident, spoke in opposition to the luxury student housing development
approved for building in Fifeville.
16. Jessica Jackson, city resident, spoke about the need for more affordable housing in Charlottesville,
and she opposed the idea that the city needs more student housing in general. She spoke in
opposition to The Mark development approved by City Council.
Sam Roman, Assistant City Manager, gave an update on the proposed transition plan for relocating people
staying in the encampment(s) near Free Bridge, and to align needs with available resources and
connection to services.
CONSENT AGENDA
Clerk of Council Kyna Thomas read the following Consent Agenda items into the record, and on motion
by Fleisher, seconded by Oschrin, Council by the following vote adopted the Consent Agenda: 5-0 (Ayes:
Fleisher, Oschrin, Payne, Snook, Wade; Noes: none).
2. MINUTES: March 16 regular meeting, April 6 regular meeting, April 20 regular meeting, July 8 work
session
3. Resolution Allocating $575,000 in Housing Operations and Support FY27 Grant Funding (2nd
reading)
RESOLUTION
Allocating FY27 Housing Operations and Program Support Grant Program Funding
for Housing and Homelessness Prevention Programs in the Amount of $575,000
WHEREAS, City of Charlottesville, Virginia (“City”), having established the Housing Operations
and Program Support (“HOPS7.”) Grant Program to provide financial support for operational needs of
nonprofit organizations that provide essential housing-related services, hereby allocates $575,000 from
the Charlottesville Affordable Housing Fund (“CAHF”) under Fund 426 Project: CP-084, as per the
City’s FY27 Capital Improvement Program Budget.
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville, Virginia
(“City Council”), that upon consideration of the CAHF Committee’s recommendations for the HOPS
Grant Program, City Council hereby allocates funds to the following HOPS Applicants:
Page 90 of 225
City Council Meeting Minutes – July 20, 2026
Fund Project G/L
Account
Applicant Funded Project/Initiative Award
426 CP-084 530670
Albemarle Housing
Improvement Program AHIP System of Care $42,905.00
426 CP-084 530670
Community Services
Housing Community Services Housing $44,700.00
426 CP-084 530670 Georgia’s Friends
Georgia’s Friends Recovery
Residence & Support Program $1,900.00
426 CP-084 530670
Habitat For Humanity of
Greater Charlottesville
Habitat Homeownership
Program $33,525.00
426 CP-084 530670
International Rescue
Committee
IRC Housing Navigation
Support $20,115.00
426 CP-084 530670 Legal Aid Justice Center
Legal Services to Prevent
Evictions and Ensure Housing
Stability $22,350.00
426 CP-084 530670
Monticello Area
Community Action Agency Hope House $13,410.00
426 CP-084 530670
People and Congregations
Engaged in Ministry PACEM Case Management $53,640.00
426 CP-084 530670 Piedmont Housing Alliance
Charlottesville Affordable
Housing Program $89,400.00
426 CP-084 530670 SupportWorks Housing The Crossings PSH Program $29,055.00
426 CP-084 530670 The Haven at First & Market Day Shelter Program $77,000.00
426 CP-084 530670 The Haven at First & Market
Homeless Information Line at
The Haven $35,000.00
426 CP-084 530670 The Haven at First & Market Vital Housing Services $112,000.00
BE IT FURTHER RESOLVED that all funding awards within this Resolution shall be provided as
grants to the entities listed under the “Applicant” column above to be used solely for the purposes
outlined in their respective Grant Applications, and any subsequent Grant Agreement. The City
Manager is authorized to negotiate and execute Funding Grant Agreements with each recipient to
ensure proper utilization of funds.
4. Resolution for Approval of Addendum to Lease with Botanical Garden of the Piedmont (2nd reading)
RESOLUTION
Authorizing Approval of an Addendum to the City’s Ground Lease with the
Botanical Garden of the Piedmont, Inc.
WHEREAS, the City of Charlottesville, Virginia (the City) is the owner of certain land currently
leased to the Botanical Garden of the Piedmont, Inc. (the Botanical Garden) pursuant to a forty-year
ground lease dated November 8, 2021; and
Page 91 of 225
City Council Meeting Minutes – July 20, 2026
WHEREAS, the Botanical Garden is preparing its first phase of construction of a botanical garden that
will be open and free of charge to City residents; and
WHEREAS, the Botanical Garden has been awarded a federal grant from the National Fish and
Wildlife Foundation to assist with implementation of a nature-based stormwater management system
intended to improve water quality and protect native habitat; and
WHEREAS, the Botanical Garden has requested the City’s approval to enter into the grant agreement
and the City’s acknowledgment of a limited federal reversionary interest solely in certain grant-funded
improvements constructed with grant funds during their useful life, and only to the extent provided in
the grant agreement; and
WHEREAS, the proposed lease addendum clarifies that the City is not granting any interest in its fee
simple ownership of the land, is not creating any lien or encumbrance on City property, is not pledging
the City’s credit or assets, is not guaranteeing the obligations of the Botanical Garden and is not
assuming any repayment or performance obligations under the grant agreement; and
WHEREAS, the proposed lease addendum further provides that any default by the Botanical Garden
under the grant agreement during the lease term, including any extensions, shall constitute a default
under the lease; and
WHEREAS, City Council finds that approval of the proposed lease addendum is in the public interest.
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville:
1. The City Manager is hereby authorized to execute an addendum to the November 8, 2021 ground
lease with the Botanical Garden in substantially the form presented to City Council, together with
such minor or technical revisions as the City Manager and City Attorney deem necessary or
appropriate, provided that such revisions do not materially alter the substance of the addendum.
2. The City’s approval and acknowledgment shall be limited to the terms set forth in the lease
addendum and shall not be construed to grant any interest in the City’s fee simple ownership of
the land, create any lien or encumbrance on City property, pledge the City’s credit or assets, make
the City a guarantor of any obligation, or cause the City to assume any repayment or performance
obligation arising under the Botanical Garden’s grant agreement.
5. RESOLUTION appropriating funds for the Virginia Department of Education Special Nutrition
Program Summer Food Service Program - $40,000 (layover)
6. RESOLUTION Considering A Special Exception Permit for 1138 Rose Hill Drive
RESOLUTION
Approving a Request for a Special Exception Permit (“SEP”)
for Property Located at 1138 Rose Hill Drive
WHEREAS, the City of Charlottesville, Virginia (“Landowner”), is the current owner of a lot
identified on 2025 City Tax Map 44 as Parcel 302 (City Parcel Identification No. 440030200), having
an area of approximately 2.54 acres (110,642 square feet); (“Subject Property”); and
WHEREAS, Landowner wishes to expand a ground mechanical equipment area on the Subject
Property (“Project”); and
Page 92 of 225
City Council Meeting Minutes – July 20, 2026
WHEREAS, the Project is described in more detail within the Landowner’s Application materials
submitted in connection with Application PL-26-0063 (“Application”), as required by City
Development Code Section 34-5.2.15.B.2 (collectively, "Application Materials"); and
WHEREAS, the Planning Commission of the City of Charlottesville, Virginia (“PC”), made a
recommendation of approval of the SEP at its June 9, 2026, Public Meeting, per City Development
Code Section 34-5.2.15.C.2.
NOW THEREFORE, BE IT HEREBY RESOLVED, by the City Council of the City of
Charlottesville, Virginia (“City Council”), upon consideration of the PC's recommendation and the
City Staff Report discussing the Application, as well as the factors set forth within City Development
Code Section 34-5.2.15.D, that it finds and determines that granting the proposed SEP would serve the
public necessity, convenience, general welfare, or good zoning practice; and
BE IT FURTHER RESOLVED, by City Council, pursuant to City Development Code Section 34-
5.2.15, a SEP is hereby approved and granted to authorize the Project and permit ground mechanical
equipment consistent with the Application Materials for the Subject Property, with the following
condition:
1. Trex composite material shall be used for all required equipment screening.
7. ORDINANCE amending and reenacting Chapter 2, Article XV of the Code of the City of
Charlottesville, the Charlottesville Human Rights Ordinance (layover)
8. Adoption of Amending Ordinance Correcting Two (2) Scrivener’s Errors in the Original Ordinance
Vacating and Quitclaiming Clarke Court to the Jefferson Scholars Foundation
ORDINANCE AMENDING THE DECEMBER 15, 2025 ORDINANCE CLOSING,
VACATING, AND DISCONTINUING CLARKE COURT TO CORRECT SCRIVENER’S
ERRORS
9. RESOLUTION Allocating Charlottesville Affordable Housing Fund Grant Program Funding for
Charlottesville Redevelopment and Housing Authority South First Street Phase Two in the
Amount of $425,000 (layover)
CITY MANAGER REPORT
City Manager Sam Sanders thanked Assistant City Manager Roman for the report regarding the Free
Bridge encampment approach, and he said that compassion will be important moving forward. He
reinforced the drought declaration for the region and encouraged voluntary conservation.
ACTION ITEMS
10. PUBLIC HEARING and RESOLUTION to Authorize the Issuance and Sale of General
Obligation Public Improvement Bonds of The City of Charlottesville, Virginia, in an Aggregate
Principal Amount Not to Exceed $29,000,000, to Finance the Costs of Certain Public
Improvement Projects, Providing for the Issuance and Sale of General Obligation Refunding
Bonds Of The City Of Charlottesville, Virginia, in an Aggregate Principal Amount Not to
Exceed $25,000,000, Providing for the Form, Details and Payment of Such Bonds, and
Providing for the Refunding of Certain Outstanding General Obligation Bonds of the City
Page 93 of 225
City Council Meeting Minutes – July 20, 2026
Krisy Hammill, Director of Budget and Grants Management, presented the request for authorization,
followed by the public hearing where one person came forward:
- James Rogers asked for clarification of the city’s bond rating.
Mayor Wade closed the public hearing.
On motion by Snook, seconded by Payne, Council by a vote of 5-0 (Ayes: Fleisher, Oschrin,
Payne, Snook, Wade; Noes: None) approved the following resolution:
RESOLUTION AUTHORIZING THE ISSUANCE AND SALE OF GENERAL
OBLIGATION PUBLIC IMPROVEMENT BONDS OF THE CITY OF
CHARLOTTESVILLE, VIRGINIA, IN AN AGGREGATE PRINCIPAL AMOUNT NOT
TO EXCEED $29,000,000, TO FINANCE THE COSTS OF CERTAIN PUBLIC
IMPROVEMENT PROJECTS, PROVIDING FOR THE ISSUANCE AND SALE OF
GENERAL OBLIGATION REFUNDING BONDS OF THE CITY OF
CHARLOTTESVILLE, VIRGINIA, IN AN AGGREGATE PRINCIPAL AMOUNT NOT
TO EXCEED $25,000,000, PROVIDING FOR THE FORM, DETAILS AND
PAYMENT OF SUCH BONDS, AND PROVIDING FOR THE REFUNDING OF
CERTAIN OUTSTANDING GENERAL OBLIGATION BONDS OF THE CITY
11. PUBLIC HEARING and ORDINANCE Adoption: 801 West Street; Zoning Text Amendment
(Pl-26-0043), Designation of Individually Protected Property (layover)
Jeff Werner, Historic Preservation and Design Planner, provided an overview of the request to designate
the property at 801 West Street, as an Individually Protected Property (IPP).
On December 9, 2025, the Planning Commission (PC) recommended approval of a Zoning Text
Amendment (ZTA) to City Code Section 34-2.9.3.B. to designate the Subject Property as an IPP, and, per
City Code Section 34-5.2.5, amend the City Zoning Map to identify the Subject Property as having an IPP
overlay. On the Subject Property, the proposed contributing structure is a two (2)-story, framed dwelling,
clad in stucco. The dwelling is characterized by a hipped roof with pedimented gables, a wood-railed
widow's walk in the center, with an attached single-story, rear addition. In 1905, James Patterson
constructed the dwelling for his family. The Patterson family sold the property in 1944, during WWII, to
James Fleming, a fireman with the railroad, and his wife Maude Fleming, a prominent local teacher at the
Jefferson School for forty (40) years. The Subject Property remains in the family to this day. (The NE
corner of the 10th and Page neighborhood was initially segregated. Between 1930 and 1950, it
transitioned to predominantly Black residents, including the Flemings.) Richard Hunt, the current owner,
is the grandson of Maude and James Fleming, and a descendant of Henry Martin (1826-1915), the bell
ringer at the University of Virginia from c.1868 until 1909.
In June 2020, on behalf of the City, the 106 Group completed a Reconnaissance Architectural History
Survey of 438 properties within the 10th and Page neighborhood. As a result, the Virginia Department of
Historic Resources State Review Board recommended the approximately fifty (50)-acre Tenth and Page
Historic District be eligible for listing on the Virginia Landmarks Register and the National Register of
Historic Places (“NRHP”). Within that review, the Subject Property was assessed as retaining excellent
integrity of both location and setting. In the areas of design, materials, and workmanship, the dwelling
was assessed as retaining good integrity and therefore recommended as potentially individually eligible
for listing in the NRHP under criterion “A,” as one (1) of the oldest extent houses within the (also eligible)
10th and Page neighborhood. After consideration of the Standards of Review for IPP Designations (City
Code Section 34-2.9.3.C), the City's Board of Architectural Review (BAR) approved a Motion
recommending the ZTA to City Council on January 21, 2026. The PC held a Public Hearing on May 12,
Page 94 of 225
City Council Meeting Minutes – July 20, 2026
2026, during which the Subject Property owner provided context for seeking IPP designation status for
the Subject Property. Following discussion, the PC voted to recommend approval.
Mr. Richard Hunt, homeowner, provided some background on his request, and described the lineage of his
family and the way this designation honors the neighborhood and people who have been part of the fabric
of Charlottesville.
Following clarifying questions from Council, Mayor Wade opened the public hearing.
- Frank Bechter, city resident, stated that Mr. Hunt has kept up the property.
Mayor Wade closed the public hearing.
Council agreed to carry the item to the August 3, 2026, meeting for second reading and vote.
12. PUBLIC HEARING and ORDINANCE: 801 West Street: Zoning Map Amendment (Pl-26-
0042), Designation of Individually Protected Property (layover)
A Zoning Map Amendment (ZMA) was proposed for property located at 801 West Street, Charlottesville,
Virginia, TMP # 310042000 (Subject Property), pursuant to Charlottesville City Code Section 34-5.2.5.
On July 25, 2025, the Subject Property owner requested City Staff initiate the ZMA process to designate
the Subject Property (an existing house at 801 West Street) as an Individually Protected Property (“IPP”).
The proposed IPP designation will overlay an approximately 0.3-acre parcel, located at the NW corner of
West Street and 8th Street, NW, within the 10th and Page neighborhood.
Following clarifying questions from Council, Mayor Wade opened the public hearing, and with no
speakers coming forward the public hearing was closed.
Council agreed to carry the item to the August 3, 2026, meeting for second reading and vote.
13. PUBLIC HEARING and ORDINANCE to Update the Citizen Participation Plan, a Component
of the City’s Community Development Block (CDBG) Grants and HOME Investment Partnerships
Programs (HOME), and Associated Municipal Code
Anthony Warn, Grants Analyst, presented the request, which involves a resolution and ordinance.
Following clarifying questions from Council, Mayor Wade opened the public hearing on both the
resolution and ordinance. With no speakers coming forward, Mayor Wade closed the public hearing.
a. RESOLUTION Amending the Citizen Participation Plan, a Component of the City’s
Community Development Block Grants and HOME Investment Partnerships Programs
On motion by Payne, seconded by Oschrin, Council by a vote of 5-0 (Ayes: Fleisher, Oschrin,
Payne, Snook, Wade; Noes: None) approved the following resolution:
A Resolution to Approve Amending the Citizen Participation Plan, a Component of the City’s
Community Development Block Grants and HOME Investment Partnerships Programs
WHEREAS the City of Charlottesville engages as a ‘participating jurisdiction’ (“PJ”) in the
Community Development Block Grant (“CDBG”) & HOME Investment Partnerships (“HOME”)
programs offered by the U.S. Department of Housing and Urban Development ("HUD") and in that
Page 95 of 225
City Council Meeting Minutes – July 20, 2026
role is the periodic recipient of federal funds to support eligible community development, affordable
housing and planning activities; and
WHEREAS the city’s is called on by HUD to adopt a Citizen Participation Plan (“CPP”) that
sets forth the jurisdiction's policies and procedures that encourage broad and representative
citizen participation in certain aspects of the development of HUD-funded programs, including CDBG
and HOME; and
WHEREAS updates to the CPP and associated municipal code, at Chapter 2, Article XIII, can
strengthen the City’s work to address important community needs through meaningful citizen
engagement with the CDBG and HOME programs;
NOW, THEREFORE, BE IT RESOLVED that the City Council of the City of Charlottesville,
Virginia, hereby approves the amended Citizen Participation Plan as presented here before us today.
b. PUBLIC HEARING and ORDINANCE to Amend and Reordain Article XIII of Chapter 2
of the Charlottesville City Code, 1990, as Amended, Relating to Community Planning and
Development Grant Programs
On motion by Payne, seconded by Oschrin, Council by a vote of 5-0 (Ayes: Fleisher, Oschrin,
Payne, Snook, Wade; Noes: None) approved the following ordinance:
AN ORDINANCE TO AMEND AND REORDAIN ARTICLE XIII OF CHAPTER 2
(ADMINISTRATION) OF THE CHARLOTTESVILLE CITY CODE, 1990, AS AMENDED,
RELATING TO COMMUNITY PLANNING AND DEVELOPMENT GRANT PROGRAMS
14. PUBLIC HEARING and RESOLUTION for City Right-of-Way Agreement Execution
Dedicating an Easement to Dominion Energy
Glenn Lee Cooper, Transportation Project Manager, presented the request for City Council to approve the
execution of a Right-of-Way Agreement ("Agreement") resolution authorizing the dedication of an
easement on City-owned property to Virginia Electric and Power Company, doing business in Virginia as
Dominion Energy Virginia ("Dominion Energy") for the purpose of charging Battery Electric Buses
("BEB's") for City use in the Charlottesville Area Transit ("CAT") transit parking lot at 1545 Avon St Ext.
Mayor Wade opened the public hearing and with no speakers coming forward, the public hearing was
closed.
On motion by Oschrin, seconded by Payne, Council by a vote of 5-0 (Ayes: Fleisher, Oschrin,
Payne, Snook, Wade; Noes: None) approved the following resolution:
RESOLUTION
Granting an Easement to Dominion Power to Enable Electrical Power Service to
Electric Charging Infrastructure
WHEREAS, the City has the need to install Charlottesville Area Transit (CAT) transit bus chargers;
and
WHEREAS, CAT buses will require access to electric charging infrastructure; and
Page 96 of 225
City Council Meeting Minutes – July 20, 2026
WHEREAS, Dominion Energy offers a program to support the City’s fleet electrification initiatives
by delivering and operating utility-owned charging infrastructure; and
WHEREAS, the installation of electric charging infrastructure required the establishment of an
easement to enable the provision of electrical service to the charging system; and
WHEREAS, City staff has worked with Dominion Power to verify the location, effectiveness,
and practicality of the proposed easement and has concluded that these modifications are legitimate
and necessary additions to the easement to enable Dominion to provide electrical service to the
charging system; and
WHEREAS, the proposed easement is depicted in instrument 81-26-00300, which is enclosed for
reference; and
WHEREAS, the electrical charging system will support the climate action initiative of electrifying the
school bus fleet.
NOW, THEREFORE, BE IT RESOLVED, that the City of Charlottesville approves the existing
easement provided to Dominion Power for the provision of electrical power service to the
electrical charging system, located at 1545 Avon Street Ext.
15. RESOLUTION to Appropriate $320,000 in School Zone Photo Enforcement Revenue for
FY2027
Sam Roman, Assistant City Manager, presented the request. In February 2023, City Council passed a
resolution (#R-23-020) which approved the use of speed cameras on Monticello Avenue for the school
zone near Summit Elementary and on Cherry Avenue for the school zones near Charlottesville Middle
School and Tall Oaks Elementary. In August 2024, the City entered into a Photo Enforcement Services
Agreement with American Traffic Solutions, Inc, doing business as Verra Mobility. The agreement
provided several payment options for the services. It was the understanding of staff that the cost of the
services would be budget-neutral in the sense that the revenues generated from enforcement would be
equal to or exceed the cost of the equipment and service fees.
Krisy Hammill, Budget Director, provided financial information related to the appropriation request. Six
cameras (two at each approved school zone) were installed and placed in service in October 2025. In
November 2025, the City received an invoice for the month of October for $25,504. The fees break down
to $4,250 a month for each camera and include some miscellaneous fees for the mailing of the notices.
The original agreement provided multiple payment options but was silent as to which one had been
selected. Upon receiving the invoice, staff reached out to the vendor to discuss the different options and
requirements of each option. One of the options provided allows for the City to pay either the amount of
the monthly invoice or the amount of enforcement revenue received, whichever is less.
From October 2025 through April 2026, $177,125 in enforcement revenue was collected. After many
attempts to discuss and reach agreement on the payment options with the vendor, a payment in the amount
of $177,125 was wired to the vendor on May 22, 2026. The photo enforcement revenue was not
appropriated as part of the FY 2026 budget. Funds previously appropriated funds to the Citywide reserve
account were used to pay the invoices. This resolution seeks to appropriate the enforcement revenue
which will be used to pay the invoices anticipated for FY 2027.
The term of the Photo Enforcement Services Agreement with American Traffic Solutions, Inc, doing
business as Verra Mobility is for 5 (five) years. The enforcement fees should cover a majority of the
Page 97 of 225
City Council Meeting Minutes – July 20, 2026
equipment costs. However, as staff continues to work through the administrative requirements of the
program, it is likely that funds in excess of the enforcement revenue will be needed.
On motion by Payne, seconded by Oschrin, Council by a vote of 5-0 (Ayes: Fleisher, Oschrin,
Payne, Snook, Wade; Noes: None) approved the following resolution, waiving the second reading:
RESOLUTION
To Appropriate $320,000 of School Zone Photo Enforcement Revenue for FY 2027
WHEREAS, the City Council of the City of Charlottesville passed a resolution (#R-23-020) on
February 6, 2023 which approved the use of speed cameras on Monticello Avenue for the school zone
near Summit Elementary and on Cherry Avenue for the school zones near Charlottesville Middle
School and Tall Oaks Elementary; and
WHEREAS, the City of Charlottesville has entered into a Photo Enforcement Services Agreement
with American Traffic Solutions, Inc, doing business as Verra Mobility;
WHEREAS, the City Council intends to use the revenue received from the enforcement services to
help offset the cost of the equipment and other administrative costs;
NOW, THEREFORE BE IT RESOLVED by the Council of the City of Charlottesville, Virginia,
that the sum of $306,000 or the amount of revenue actually collected, whichever is more, during FY
2027 is hereby appropriated as follows:
Revenue
Fund
$320,000 105
Cost Center
TBD
G/L Account
440050
Expenditures
$320,000
Fund
105
Cost Center
TBD
G/L Account
530550
16. RESOLUTION Initiating a Referendum to Authorize Imposition of a Local General Retail
Sales Tax Not to Exceed One Percent, the Proceeds of Which Would Be Used Solely for Capital
Projects for the Construction or Renovation of Public Schools Serving the City of
Charlottesville
City Attorney John Maddux summarized the resolution for consideration of whether City Council should
adopt a resolution initiating a referendum on the question of whether the City should be authorized to
impose a local general retail sales tax of up to one percent, with the revenues used solely for capital projects
involving the construction or renovation of public schools serving the City.
On motion by Payne, seconded by Fleisher, Council by a vote of 5-0 (Ayes: Fleisher, Oschrin,
Payne, Snook, Wade; Noes: none) approved the following resolution:
RESOLUTION INITIATING A REFERENDUM PURSUANT TO SECTION 58.1-605.1 OF
THE CODE OF VIRGINIA TO AUTHORIZE IMPOSITION OF A LOCAL GENERAL
RETAIL SALES TAX NOT TO EXCEED ONE PERCENT, THE PROCEEDS OF WHICH
WOULD BE USED SOLELY FOR CAPITAL PROJECTS FOR THE CONSTRUCTION OR
RENOVATION OF PUBLIC SCHOOLS SERVING THE CITY OF CHARLOTTESVILLE
Page 98 of 225
City Council Meeting Minutes – July 20, 2026
WHEREAS, Section 58.1-605.1 of the Code of Virginia authorizes qualifying localities to levy a
general retail sales tax at a rate not to exceed one percent to provide revenue solely for capital projects
for the construction or renovation of schools; and
WHEREAS, revenues from any such tax may be used solely for capital projects for new construction
or major renovation of schools, including bond and loan financing costs related to such construction or
renovation; and
WHEREAS, such tax may be levied only if approved by referendum within the City, held in
accordance with Virginia Code § 24.2-684 and initiated by resolution of the Charlottesville City
Council; and
WHEREAS, the Charlottesville City Council desires to initiate such a referendum for the purposes set
forth herein; and
WHEREAS, if approved by referendum and subsequently imposed by ordinance, any such tax shall
expire on June 30, 2046; and
WHEREAS, the City Council desires to preserve the City's ability to use revenues from such tax to
pay directly for eligible school construction or
renovation projects, to pay bond or loan financing costs related to such projects, or to use any lawful
combination of financing methods, provided that the tax shall expire on June 30, 2046.
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville, Virginia:
1. The Charlottesville City Council hereby requests that the Circuit Court of the City of
Charlottesville order and fix a referendum to be held in the City of Charlottesville on November
3, 2026, the date of the November 2026 general election, pursuant to Virginia Code §§ 24.2-684
and 58.1-605.1 on the issue of whether the City may levy a local general retail sales tax at a rate
not to exceed one percent, the revenues of which shall be used solely for capital projects for the
construction or renovation of public schools serving the City of Charlottesville.
2. Any tax approved by referendum and subsequently imposed by ordinance pursuant to Virginia
Code § 58.1-605.1 shall expire on June 30, 2046.
3. Revenues from any such tax may be used solely for capital projects for the construction or
renovation of schools serving the City of Charlottesville, including bond or loan financing costs
related to such construction or renovation. To the extent revenues from such tax are used for
bond or loan financing costs, the date by which such bonds or loans are to be repaid from
revenues of the tax shall be June 30, 2046.
4. Nothing in this Resolution shall prohibit the City from using other legally available revenues or
financing sources for school capital projects, provided that revenues from any tax approved by
referendum and imposed pursuant to Virginia Code § 58.1-605.1 shall be used only as
authorized by that section and shall not be collected after June 30, 2046.
5. The language to appear on the ballot on the referendum is proposed by the Charlottesville City
Council to be as follows:
Shall the City of Charlottesville, Virginia be authorized to levy a local general retail sales tax at a
rate not to exceed one percent (1%), the revenues of which shall be used solely for capital
projects for the construction or renovation of public schools serving the City of Charlottesville,
and which shall expire on June 30, 2046?
6. The City Attorney, City Manager, Clerk of Council, and such other appropriate officers and staff
Page 99 of 225
City Council Meeting Minutes – July 20, 2026
of the City are authorized and directed to execute, deliver, and file all documents, pleadings,
petitions, certificates, and instruments, and to take all further actions as may be necessary or
appropriate to carry out the purposes of this Resolution. The City Attorney, City Manager, and
Clerk of Council are further authorized to make non-substantive, conforming modifications to
the proposed ballot question and related court filings as may be necessary to conform to the
requirements of the Circuit Court, the State Board of Elections, the City Electoral Board, or the
General Registrar, provided that the ballot question shall continue to state that the revenues
from the tax shall be used solely for capital projects for the construction or renovation of
schools and that the tax shall expire on June 30, 2046.
7. A copy of this Resolution shall be forwarded by the Clerk of Council to the Clerk of the Circuit
Court for consideration and approval by the Court, if deemed to be in order, and for processing
and publication in accordance with state law.
8. An attested copy of this Resolution shall be forwarded by the Clerk of Council to the Registrar
and the Electoral Board of the City of Charlottesville.
9. The recitals to this Resolution are incorporated by reference and are declared to be findings of
the Council in connection with its adoption of this Resolution.
10. This Resolution shall take effect immediately.
17. BY MOTION: Appointment of Director of the Office of Police Civilian Oversight
Steve King, Assistant to the City Manager, requested appointment of James Walker as Director of the
Office of Police Civilian Oversight. Mr. Sanders spoke in support of the work that Mr. Walker has
achieved and helped to administer since the departure of the previous director. Mr. Walker made a few
remarks.
On motion by Payne, seconded by Fleisher, Council by the following vote Appointed James
Walker as Director of the Office of Police Civilian Oversight: 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook,
Wade; Noes: none).
GENERAL BUSINESS
18. WRITTEN REPORT: Rivanna Authorities Quarterly Update
Mayor Wade acknowledged receipt of the quarterly update from the Rivanna Authorities (Rivanna Solid
Waste Authority and Rivanna Water and Sewer Authority).
COMMUNITY MATTERS (2)
Mayor Wade opened the floor for comments from the public.
• Gloria Beard, resident of the 10th & Page neighborhood, spoke about her experience living in
Charlottesville. She expressed concerns about historically Black neighborhoods being negatively
impacted by encroaching housing developments. She asked about respect for First Baptist
Church and the neighborhood, with the recent decision to allow the building of a 7-story luxury
student housing building.
• Carmelita Wood, city resident, spoke on behalf of the Fifeville Neighborhood Association about the
approved high-rise luxury student housing building on 7th Street, and the negative impacts of
student-focused and UVA-focused developments on existing neighborhoods.
• Amber Guskin, city resident, spoke in opposition to luxury student housing approved for the
Fifeville neighborhood. She expressed concern that First Baptist Church and a broader spectrum
of community members were not consulted for input about The Mark project.
Page 100 of 225
City Council Meeting Minutes – July 20, 2026
• Deanna McDonald, city resident, spoke about an announcement today that the proposed food co-
op cannot operate at 501 Cherry Avenue because of financial reasons related to the building
design. She related the issue to systemic racism and the lack of programs and policies in place to
dismantle systemic racism and hold developers accountable for helping.
• James Rogers, city resident, expressed concern about stories in local media, and he asked about
the intended use of the emergency shelter at 2000 Holiday Drive and what a low or no barrier
shelter means for the community, including whether such shelter would permit access to
convicted sex offenders. He asked Council to keep in mind educating the broader community
beyond those who attend public meetings.
City Manager Sanders provided additional context for the definition of an emergency shelter, and the
scope of the capacity needed to address issues and provide resources to those in need.
• Sam Gulland, city resident, spoke in support of the city's decision to transition the Rivanna
encampment, to help provide resources to people in need, and to restore the riverfront. He
encouraged the city to protect public spaces and to reconsider passing an anti-camping
ordinance.
• Lizzie suggested using $24 Million to give housing to the unhoused community, using the police
budget. She stated that the encampment residents have already been surveyed and need action.
• Io Long, city resident, asked Council not to remove the Free Bridge encampment until all
individuals have a home to go to.
• Kagle McDonald, city resident, spoke about her observations of the impacts of the Rivanna
encampment, and she spoke in support of the city's plans to relocate individuals in the
encampment and provide services. She suggested the city provide guidance or a list of ways other
residents can help.
• Wren Walker, city resident, spoke about people she knows who have become homeless. She
requested the city take care of its residents, including individuals at the Free Bridge encampment,
many of whom have fallen on hard times living in Charlottesville.
• Sarah Tansey, city resident, expressed concerns about Council's leadership and decisions that
push people out of sight and traumatize Black and Brown neighborhoods.
• Jenny Ragsdale, city resident, spoke about the proposed Mark luxury student housing
development and the lack of appropriate infrastructure to address the traffic. She expressed other
concerns about the need to stop the project, including the church, the neighborhood and the
history of Vinegar Hill, hoping Council would reconsider its decision to approve the project.
• Jim Snyder, city resident, spoke about the Virginia Liberty Bell at the Ridge Street Fire Station.
He provided a handout of a letter that he sent to the Fire Marshal regarding access across 5th
Street and 7th Street, particularly when blocked by a train. He expressed concerns about
infrastructure needed to serve Fifeville and the Mark project and stated that the new zoning will
limit the ability to enhance service at the train station.
ADJOURNMENT
On motion by Fleisher, seconded by Oschrin, Council by acclamation adjourned the meeting at 9:41 p.m.
BY Order of City Council BY Kyna Thomas, Clerk of Council
Page 101 of 225
City Council – CRHA Joint Meeting – September 9, 2026; approved _________________
CHARLOTTESVILLE CITY COUNCIL
SPECIAL MEETING MINUTES
City Council / Charlottesville Redevelopment and Housing Authority Board
Joint Work Session
September 9, 2026, at 4:00 p.m.
CitySpace, 100 Fifth St NE, Charlottesville, VA
The Charlottesville City Council and Charlottesville Redevelopment and Housing Authority (CRHA)
Board convened for a joint work session to discuss updates on CRHA projects and existing collaborative
projects between the City of Charlottesville and CRHA.
CALL TO ORDER
The Charlottesville City Council special meeting was called to order at 4:03 p.m., with all members
present: Mayor Juandiego Wade, Vice Mayor Natalie Oschrin, and Councilors Jen Fleisher, Michael
Payne and Lloyd Snook.
The Charlottesville Redevelopment and Housing Authority Board special meeting was called to order.
The Charlottesville City Council approved the meeting agenda after which City Council acted on a
business item.
BY MOTION
On motion by Oschrin, seconded by Fleisher, Council voted 5-0 in favor of appointing Carl
Schwarz and Ross Harness to the Planning Commission.
JOINT MEETING
Update on CRHA projects and existing collaborative projects between the City of Charlottesville
and CRHA
The CRHA Board Chair, Brigid O’Rourke, began the report with a status update on the CRHA Executive
Director search. The current Director John Sales has resigned from the position, effective December 4,
2026.
Ms. O’Rourke presented the projected timeline for the executive director replacement process:
Week of August 31: Issue a request for proposals (RFP), allowing recruitment firms 30 days to
respond.
Week of September 30: Contract with a recruitment firm and post the executive director position.
November: Interview prospective candidates.
The CRHA Hiring Committee is engaging key stakeholders to develop a job description for the Executive
Director position. The committee is consulting with City leadership, the U.S. Department of Housing and
Urban Development (HUD), and local community groups to gather input. Although a compensation study
was not included in the RFP, Board representatives expressed the need for one. City Manager Sanders
indicated that the City’s Human Resources Office may be able to assist with the study.
Page 102 of 225
City Council – CRHA Joint Meeting – September 9, 2026; approved _________________
The committee continues to hold regular check-ins with Mr. Sales and key staff during the transition
period. It has also considered the possibility of appointing an interim executive director and is planning
for scenarios that may require a temporary appointment.
The CRHA Board presented three requests to City Council: (1) financial assistance with the cost of
contracting a recruitment firm to support the Executive Director search; (2) extending Board members’
terms in consideration of the current Board’s tenure; and (3) amending the Board’s membership
requirements to include at least one public housing resident commissioner and one Housing Choice
Voucher (HCV) recipient, as prescribed by Housing and Urban Development (HUD) code regulations.
The CRHA Board also reported ongoing efforts to establish a nonprofit entity to build internal fundraising
capacity, with establishment anticipated by the end of 2026.
City Council directed City Manager Sanders and City Attorney John Maddux to review the Board’s
requests and present recommendations for Council’s consideration.
The CRHA Deputy Executive Director, Kathleen Glenn-Matthews presented an update on Charlottesville
Redevelopment and Housing Authority (CRHA) redevelopment projects, housing renovations, and efforts
to preserve the city’s affordable housing through housing preservation initiatives.
CRHA, in partnership with the City of Charlottesville, has helped preserve approximately 80 Naturally
Occurring Affordable Housing (NOAH) units by acquiring and managing existing rental properties to
maintain affordability and prevent displacement. Preserving existing units is generally faster and less
costly than new construction. CRHA identifies potential properties through referrals and other sources or
when landlords contact the agency directly about selling their properties.
CRHA requested $3 million from the City to acquire 11 properties containing 13 deeply affordable units
as part of the Silk Purse acquisition. The initiative aims at affordability fortification opportunities. Public
investment is needed because current rental income cannot support conventional financing without
significant rent increases. Minor rehabilitation may be required. Vice Mayor Oschrin requested
clarification on how the properties were selected by the property owner from the larger portfolio of
approximately 70 parcels.
CRHA presented Rivanna Terrace Apartments, a 48-unit complex, as an affordable housing preservation
opportunity. The property is listed for $9.6 million, and CRHA requested $5 million in City funding to
support the acquisition.
CRHA’s City Housing Portfolio includes approximately 80 units. CRHA plans to sell one property back
to Woodward under a first-right-to-purchase agreement and is engaged in the disposition of 801 Harris
Street which will be converted back to commercial usage. The two dispositions would reduce the
Dogwood portfolio by 4 units. Councilor Snook requested clarification about the amount of city funding
that could be repaid and potentially reinvested in other affordable housing initiatives.
The CRHA Board and staff offered recommendations for how City Council can continue supporting
CRHA’s work, including providing funding assistance, supporting the incoming executive director,
ensuring that public housing redevelopment projects proceed as planned through completion, and
maintaining meaningful resident participation throughout the redevelopment process.
Joy Johnson, community advocate and Chair of the Public Housing Association of Residents, requested
that City Council recognize the 12 women who contributed to the design of various phases of public
Page 103 of 225
City Council – CRHA Joint Meeting – September 9, 2026; approved _________________
housing redevelopment.
Ms. O’Rourke noted that staffing capacity and compensation remain ongoing challenges, especially as
additional housing units come online. She also recommended reviewing CRHA’s organizational structure
to better align with industry standards and improve operational efficiency.
Mayor Wade left the meeting at 5:30 p.m.
Councilor Snook requested a three- to five-year financial forecast to support long-term financial planning
in light of proposed funding requests, redevelopment projects, and opportunities to preserve affordable
housing. CRHA Director of Finance TC Nichols will follow up with additional information.
City and CRHA staff emphasized continued communication and coordination on redevelopment projects,
including monthly leadership meetings and collaboration throughout the executive director transition. The
CRHA Board recommended reconvening with City staff in December to coordinate planning with the
incoming executive director.
ADJOURNMENT
On motion by Fleisher, seconded by Snook, Council by acclamation adjourned the meeting at 5:49 p.m.
BY Order of City Council BY Maxicelia Robinson, Deputy Clerk of Council
Page 104 of 225
City Council Meeting Minutes – October 19, 2026
CHARLOTTESVILLE CITY COUNCIL MEETING MINUTES
October 19, 2026 at 4:00 PM
Council Chamber
The Charlottesville City Council met on Monday, October 19, 2026, Mayor Juandiego presiding. The
meeting was called to order and Clerk of Council Kyna Thomas called the roll, noting the following
councilors present: Mayor Juandiego Wade, Vice Mayor Natalie Oschrin and Councilors Jen Fleisher and
Lloyd Snook. Councilor Michael Payne arrived during agenda approval.
On motion by Snook, seconded by Oschrin, Council by acclamation adopted the meeting agenda.
REPORTS
1. REPORT: Charlottesville Albemarle Regional Transit Authority Update
Ben Chambers, Transportation Planning Coordinator, presented an update on the Charlottesville
Albemarle Regional Transit Authority.
In December 2024, the City of Charlottesville, Virginia ("City"), along with Albemarle County, Virginia
("County"), created the Charlottesville Albemarle Regional Transit Authority ("CARTA"). CARTA,
enabled by 2009 state legislation, is able to coordinate regional transit expansion priorities and determine
a future dedicated revenue source for regional transit services. Over the past year, CARTA, supported by
staff from the Thomas Jefferson Planning District Commission ("TJPDC"), the City, and the County, has
been reviewing existing transit services and plans to assess the scale of the region's transit needs and
determine which priorities would benefit from additional regional funding. As CARTA concludes this
study of potential future services, it is looking to clarify the role of CARTA in governing the
implementation of those services and recommend changes to its enabling legislation to create a regional
source of revenue.
CARTA's current Study of Regional Planning Priorities ("Study') reviewed plans from TJPDC, the former
Regional Transit Partnership, CAT, Jaunt, the City, and the County, and documented a comprehensive
range of options for transit service expansion. The Study identified opportunities for improvements in
frequency and span of service for high-ridership fixed service routes, investments in commuter routes,
stronger links to major regional destinations and employers like the University of Virginia, the
Charlottesville-Albemarle Airport, and the Downtown Mall, and better connectivity across our urban,
suburban, and rural communities. In addition to the existing plans for improvement to CAT services that
should come online prior to 2030, this Study has identified approximately $12 million worth of additional
annual transit services that would be feasible to implement starting in 2031. The Study also identified
additional aspirational investments beyond this initial set of transit expansions.
Before the City and the County can request changes to state legislation that could enable CARTA to serve
as the vehicle for the kinds of investments identified in the prioritization study, CARTA will be working
to answer what the role of CARTA will be in terms of governing regional transit decisions and identifying
what opportunities could be available to set dedicated revenue for implementing them. The Study
identified approximately $12 million in regional transit priorities that could potentially be implemented
beginning in 2031. The direct financial impact of these proposed transit service expansions on the City has
not been determined yet, as revenue sources and the roles and responsibilities of regional partners,
including CARTA itself, are still in the process of being identified.
CLOSED MEETING
On motion by Oschrin, seconded by Snook, Council voted 5-0 (Ayes: Fleisher, Oschrin, Payne,
Page 105 of 225
City Council Meeting Minutes – October 19, 2026
Snook, Wade; Noes: none) to meet in closed session as authorized by the Virginia Freedom of
Information Act:
1. Pursuant to Virginia Code Section 2.2-3711(A)(1) for discussion and consideration of the
performance of specific appointees and pursuant to Section 2.2-3711(A)(8) for consultation with legal
counsel employed by the City Council regarding specific legal matters requiring the provision of legal
advice by such counsel, specifically, CRHA governing board appointees and Council authority with
respect to same; and
2. Pursuant to Virginia Code Section 2.2-3711(A)(7) for consultation with legal counsel and
briefings by staff members pertaining to actual or probable litigation, where such consultation or
briefing in open meeting would adversely affect the negotiating or litigating posture of the public
body. The specific matter to be discussed is SCC Case PUR-2026-00112; and
3. Pursuant to Virginia Code Section 2.2-3711(A)(8) for consultation with legal counsel employed
or retained by a public body regarding specific legal matters requiring the provision of legal advice by
such counsel, specifically, procedural requirements for certain matters on the City Council’s agenda.
On motion by Oschrin, seconded by Fleisher, Council certified by the following vote: 5-0 (Ayes:
Fleisher, Oschrin, Payne, Snook, Wade; Noes: none.), that to the best of each Council member’s
knowledge only public business matters lawfully exempted from the open meeting requirements of the
Virginia Freedom of Information Act and identified in the Motion convening the closed session were
heard, discussed or considered in the closed session.
BUSINESS SESSION
City Council began the business meeting by observing a moment of silence.
ANNOUNCEMENTS
Councilor Fleisher announced a VDOT meeting on October 22 at Monticello High School to receive public
input on multimodal improvements to Avon Street, with a public comment period open until November 2.
She also announced an October 26 public meeting at Henley Middle School in Crozet, where Albemarle
County will be sharing the preferred route for the Three Notch'd Trail.
Vice Mayor Oschrin announced: 1) VDOT STARS Studies surveys for roadway solutions; 2) the October
eBike subsidy voucher application period open on the City’s ConnectCharlottesville website; and 3) early
voting options.
RECOGNITIONS/PROCLAMATIONS
• PROCLAMATION: Mayor Wade read the Support Your Local Chamber of Commerce Day
proclamation.
COMMUNITY MATTERS
Mayor Wade opened the floor for comments from the public.
1. Elizabeth Smiley, Sister Cities Commission, provided a Besançon Delegation Trip Report.
2. Tom Oakley, city resident and Vietnam veteran, spoke about city parks development, particularly
the difficulty of accessing the Dogwood Vietnam Memorial.
3. Mike Henrietta, city resident, requested that Council approve reinstallation of the Court Square
enslavement auction block memorial marker.
Page 106 of 225
City Council Meeting Minutes – October 19, 2026
4. Alicia Lenahan, Albemarle County resident, spoke about preserving core neighborhoods, and
about forced economic displacement of working class and poor people in the face of urban
renewal.
5. Heidi Dhivya Berthoud, city resident, spoke in favor of reinstallation of the Court Square
enslavement auction block memorial plaque.
6. Richard H. “Freeman” Allan, Albemarle County resident, spoke in favor of reinstallation of the
Court Square enslavement auction block memorial marker.
7. Bellamy Brown, city resident, asked Council to consider establishing a regular, predictable and
transparent process for reviewing changes to the Charlottesville Development Code.
8. Casey Joeli, city resident, thanked Council for listening to resident comments regarding Stanley
Martin Homes and issues with the development project at Azalea Springs. She expressed a need to
figure out a solution for paper streets to meet the needs of landowners and will meet city
environmental goals.
9. Frank Bechter, city resident, shared a story about two recent housing development meetings
concerning which were spontaneously taken over by residents, and sparked a sense of pride in a
long-time resident who expressed the importance of residents speaking up for change.
CONSENT AGENDA
Clerk of Council Kyna Thomas read the following Consent Agenda items into the record, and on motion
by Oschrin, seconded by Snook, Council by the following vote Adopted the Consent Agenda, waiving the
second reading for Item #6 resolutions: 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook, Wade; Noes: none).
2. ORDINANCE to renew Franchise Agreement for FiberLight, LLC
AN ORDINANCE GRANTING A FRANCHISE TO FIBERLIGHT, LLC, ITS SUCCESSORS
AND ASSIGNS TO USE THE STREETS AND OTHER PUBLIC PLACES OF THE CITY OF
CHARLOTTESVILLE, VIRGINIA FOR ITS POLE, WIRES, CONDUITS, CABLES AND
FIXTURES, FOR A PERIOD OF FIVE (5) YEARS
3. RESOLUTION to Appropriate the Victim Witness Grant - $313,698 (layover)
4. RESOLUTION for Blue Ridge Health District Carryover Request - $18,000 (layover)
5. RESOLUTION to appropriate funding from the Virginia Department of Housing and Community
Development FY2027 Continuum of Care Capacity Building Funds - $25,000 (layover)
6. Tonsler Fitness Court
a. RESOLUTION appropriating $40,000 from National Fitness Campaign for Installation of an
Outdoor Gym at Tonsler Park
RESOLUTION
Allocating Funds from National Fitness Campaign for Installation of an
Outdoor Gym at Tonsler Park
WHEREAS, pursuant to Va. Code § 15.2-1806, the City of Charlottesville (the “City”), through the
Department of Parks & Recreation, plans to build such a free outdoor gym at Tonsler Park with partial
funding help through a $40,000.00 grant awarded by National Fitness Campaign (“NFC”), a private-
Page 107 of 225
City Council Meeting Minutes – October 19, 2026
public wellness initiative that builds and funds its trademarked outdoor Fitness Court® in the United
States; and
WHEREAS, while the City has a fitness trail at Pen Park, it is not readily available to downtown
residents. An outdoor gym at Tonsler would have equipment similar to an indoor gym, such as
stationary bicycles and other workout apparatus; and
WHEREAS, NFC’s grant requires (1) a Resolution of Adoption endorsed by the local governing
body; (2) authorization to proceed documented by formal funding confirmation (commonly a purchase
order); and (3) confirmation of a scheduled shipping date for NFC’s outdoor gym and storage plans;
and
WHEREAS, NFC’s Grant Program Requirements (“GPR”) milestones must be met to maintain
funding eligibility, which includes confirmation of a remaining funding requirement of
$164,050.00. The City understands the scope of this project includes the installation of a concrete pad,
as well as the assembly of NFC’s outdoor gym, both to be completed by separate vendors external to
NFC.
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville that a total
of $40,000.00 be appropriated in the following manner:
Revenues $40,000.00
Fund: 209 Order: 1900742 G/L: 430110
Expenditures $40,000.00
Fund: 209 Order: 1900742 G/L: 530550
b. RESOLUTION Appropriating $149,500 Land and Water Conservation Grant from the Virginia
Department of Conservation Grant for Installation of Outdoor Gym at Tonsler Park
RESOLUTION
Allocating $149,500 from Land and Water Conservation Grant from the Virginia Department of
Conservation for Installation of Outdoor Gym at Tonsler Park
WHEREAS, pursuant to Va. Code § 15.2-1806, the City of Charlottesville (the “City”), through the
Department of Parks & Recreation, plans to build such a free outdoor gym at Tonsler Park with partial
funding help through a $149,500.00 Land and Water Conservation Fund (“LWCF”) grant through the
Virginia Department of Conservation and Recreation; and
WHEREAS, the LWCF grant requires placing a permanent deed restriction on Tonsler Park to ensure
the park remains open space for public recreation, and matching funds of
$149,500.00.
NOW, THEREFORE BE IT RESOLVED by the Council of the City of Charlottesville that a total
of $149,500.00 from the LWCF grant be appropriated in the following manner:
Revenues $149,500.00
Fund: 209 Order: 1900742 G/L: 430110
Page 108 of 225
City Council Meeting Minutes – October 19, 2026
Expenditures $149,500.00
Fund: 209 Order: 1900742 G/L: 530550
Transfer From
Grant Match Amount: $149,500
Fund: 426 WBS Element: P-00777 G/L: 599999
CITY MANAGER REPORT
Mayor Wade acknowledged the City Manager Report in the agenda packet.
ACTION ITEMS
7. PUBLIC HEARING and RESOLUTION to Adopt Amendments to City Charter
City Attorney John Maddox presented the requested City Charter amendments.
Following clarifying questions from Council, the public hearing was opened. There being no speakers, the
public hearing was closed and Council engaged in discussion.
On motion by Payne, seconded by Oschrin, Council by the following vote Approved the
Resolution to Adopt Amendments to the City Charter: 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook, Wade;
Noes: none).
RESOLUTION
Requesting General Assembly Enactment of Amendments to the City Charter
WHEREAS, the City Council wishes to update and clarify provisions of the Charter of the City of
Charlottesville, as set forth in the proposed amendments attached to this resolution as Attachment A;
and
WHEREAS, Virginia Code §§ 15.2-201 and 15.2-202 provide for a locality to request that the
General Assembly amend its charter following an advertised public hearing; and
WHEREAS, City Council held an advertised public hearing on October 19, 2026 to receive public
comment on the proposed amendments and has considered the comments received;
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville that:
• Council approves the proposed Charter amendments set forth in Attachment A, which is
incorporated into this resolution, and requests that the Virginia General Assembly enact the
amendments during its 2027 regular session.
• The Clerk of Council is directed to transmit this resolution and the proposed amendments, together
with the publisher’s affidavit documenting the public hearing advertisement and certified copies of
the minutes showing Council’s action at the hearing, to the City’s General Assembly delegation
for introduction of the necessary legislation.
• The City Attorney is authorized to coordinate with the City’s legislative delegation and the
Division of Legislative Services in preparing legislation consistent with this resolution.
Page 109 of 225
City Council Meeting Minutes – October 19, 2026
8. RESOLUTION to Initiate the Five (5)-Year Review to City's Comprehensive Plan and Report on
Project Scope
Per Virginia State Code § 15.2-2230, each locality must review its Comprehensive Plan (“Comp Plan”) at
least every five (5) years to determine whether it is advisable to amend the Comp Plan. While there have
been several amendments to the City’s Comp Plan to date, it is best practice to complete a review of the
Comp Plan every five (5) years and determine if additional changes are needed. Virginia Code § 15.2-2229
authorizes City Council to initiate Comp Plan Amendments by majority vote and to refer the same to the
Planning Commission (“PC”) for review/recommendation.
Victoria Kanellopoulos, City Planner, provided an overview of the City’s draft process and approach for
reviewing the City’s Comp Plan and Project objectives. The Comp Plan review is an opportunity to
evaluate and respond to challenges, opportunities, and emerging issues that have been identified since the
City adopted the updated Comp Plan in 2021. The Comp Plan review will be informed by feedback and
expertise from City Staff, community members, the PC, and City Council, along with qualitative and
quantitative data, State Code requirements, and best practices. This will include:
• Updating existing conditions data and trends;
• Incorporating any new State Code requirements;
• Alignment with City plans that have been completed since November 2021 and coordinating with
in-progress plans that are moving in parallel;
• Evaluating strategies and priorities and where changes are needed; and
• Opportunities for community input and information-sharing throughout the process.
The community, PC, and City Council will be informed throughout the Project, and will be engaged at
key points to ask for input and feedback. City Staff will provide regular Project status updates and share
upcoming opportunities for engagement, including through a future Connect Charlottesville webpage. City
Staff will also hold work sessions with both the PC and City Council and will share the PC's
recommendations and feedback with City Council.
Councilors expressed a desire to have a robust public engagement and input process.
On motion by Fleisher, seconded by Oschrin, Council by the following vote Approved the
Resolution to Initiate the Five (5)-Year Review to City's Comprehensive Plan and Report on Project
Scope: 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook, Wade; Noes: none).
RESOLUTION
Initiating the Five (5)-Year Review to City’s Comprehensive Plan
WHEREAS, Virginia Code § 15.2-2230 requires that each locality review its Comprehensive Plan
(“Comp Plan”) at least once every five (5) years to determine whether it is advisable to amend the
Comp Plan; and
WHEREAS, In November 2021, City Council formally adopted the City’s Comp Plan, and since
then, there have been several Amendments thereto, including adopting the Climate Action Plan and
the Parks & Recreation Master Plan; and
WHEREAS, it is best practice to periodically review the Comp Plan informed by qualitative and
quantitative data, Virginia Code requirements, best practices, City Staff expertise, community input,
City Planning Commission (“PC”) feedback, and City Council direction; and
Page 110 of 225
City Council Meeting Minutes – October 19, 2026
WHEREAS, it is desirable to have recommendations, goals, strategies, and policies that reflect the
City's current priorities, policies, plans, and values, and that reflect current conditions and projected
future growth and change; and
WHEREAS, Virginia Code § 15.2-2229 authorizes City Council to initiate Comp Plan Reviews and
Amendments by majority vote and to refer the same to the PC for review/recommendation.
NOW, THEREFORE, BE IT RESOLVED, by City Council as authorized by Virginia Code §§
15.2-2229 and 15.2-2230, that City Council hereby initiates a review of the City’s Comp Plan, and
refers the same to the City’s PC for review/recommendation.
9. RESOLUTION allowing the installation of a sign recognizing the sale of enslaved persons in
Court Square
Michael Goddard, Interim Director of Neighborhood Development Services, summarized the request. A
group of local residents identified as the Court Square Enslavement Memorial (CSEM) group requested
that Council place a marker on a light post near to the building known as "0 Court Square" and that this
marker should read, "Auction Block of Enslaved Persons; Early 1800s - 1865; Removed 1920s." The
Historic Resources Committee (“HRC”) submitted the following statement:
“Position On CSEM Plaque Proposal:
HRC concurs with the view that the brutal reality of sales of enslaved people in Charlottesville and
Albemarle County must be kept alive in the collective memory. HRC is committed to fully, accurately,
and formally disseminating the terrible legacy of Charlottesville’s slave trade. We note, however, that
the current CSEM proposal is not an historically accurate means to this end and may serve to limit the
broader story of enslavement at Court Square. While HRC commends the wider intentions advocated
by CSEM, we feel that the current proposal placed before Council would put forth inaccurate
historical information.
Position On Accuracy:
No credible evidence has been identified or provided to support the concept that a dedicated slave
auction block existed within the Courthouse Square vicinity. The apparent theory that an auction block
ever existed began with circumstantial second-hand accounts compiled by Mary Rawlings in her 1942
book. No first-hand primary resource accounts have been identified that mention the presence of a
slave auction block. Refer to Appendix B. Extensive research shows that enslaved individuals were
sold in several locations including the Courthouse door and steps, neighborhood taverns, and private
homes. No contemporaneous firsthand accounts have been found of enslaved individuals being sold on
a platform or block of any kind specifically dedicated to this purpose. This finding led to the 2025
installation of a State historical marker noting that auctions occurred in several locations throughout
Court Square.
Basis for Position:
This position is based on research undertaken by several professional and volunteer historians
over the last quarter of a century. Prior to creating this statement, the HRC reviewed auction block
commemoration efforts dating from the 1940s to the present day. HRC also reviewed original
source material including newspaper articles and advertisements, oral histories, books, reports,
and other primary and secondary source materials.”
Staff concurred with findings and recommendations from the HRC.
Council engaged in discussion, and Vice Mayor Oschrin read the wording from existing historic marker
Page 111 of 225
City Council Meeting Minutes – October 19, 2026
#Q-49, located in Court Square. In response to a question from Ms. Oschrin, Deputy City Manager James
Freas stated that the process to stand up the Arts and Memorials Commission is expected to take until early
2027.
On motion by Snook, seconded by Oschrin, Council by the following vote Approved a substitute
to the published eesolution allowing the installation of a sign recognizing the sale of enslaved persons in
Court Square: 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook, Wade; Noes: none). The substitute motion
became the main motion.
On motion by Snook, seconded by Fleisher, Council by the following vote Approved the
following resolution to DENY the request for installation of a sign recognizing the sale of enslaved
persons in Court Square: 5-0 (Ayes: Fleisher, Oschrin, Payne, Snook, Wade; Noes: none).
RESOLUTION
Denying Sign Request and Providing Direction Regarding Court Square
Historical Markers and Memorials
WHEREAS the Court Square Enslavement Memorial group (CSEM) has requested that the
Charlottesville City Council authorize the installation of a sign near the building known as
Number Nothing Court Square that would state “Auction Block of Enslaved Persons; Early
1800s – 1865; Removed 1920's”; and
WHEREAS City Council has reviewed a report by the Historic Resources Committee, with its
Appendices, materials submitted by the CSEM group, and the public comments made on the
subject; and
WHEREAS City Council agrees with the conclusion of the Historic Resources Committee that
the available historical evidence does not substantiate the claim that a dedicated auction block for
the sale of enslaved people existed at the proposed marker location;
NOW THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville:
1. CSEM’s request that the City Council authorize the installation of the above-described marker is
denied.
2. Consideration of any further historical markers or memorials in the Court Square area should be
undertaken as part of a plan that will accurately reflect the square’s complete history, including
the sale of enslaved people in and around the same.
10. ORDINANCE to Approve Construction Management at Risk Procedures (CMAR)
Bruce White, Capital Development Manager in Public Works, presented a recommendation for City
Council to approve the City of Charlottesville, Virginia, Construction Management at Risk (CMAR)
Procedures. CMAR is a construction delivery model alternative to the traditional public procurement
model known as Design, Bid, and Build (“DBB”). When utilized on appropriate projects, CMAR provides
better cost control, reduces the risk of change orders, and reduces unanticipated impacts during
construction when compared to traditional DBB projects. CMAR is particularly well-suited to complex
projects, because it integrates the experience and construction perspective of a contractor into the design
development process.
The Virginia Public Procurement Act (“VPPA”) permits the use of CMAR by a public body in certain
Page 112 of 225
City Council Meeting Minutes – October 19, 2026
instances and with certain prerequisites, including the adoption of written procedures for the selection,
evaluation, and award of CMAR contracts. CMAR contracts have several features which increase the
potential for project success. First, is the utilization of a rigorous competitive negotiation process for
selection of the contractor. This allows the City of Charlottesville to select a contractor based upon a
measured evaluation of the contractor’s qualifications, in addition to anticipated cost. The second key
factor is that the contractor is integrated into the project team during the schematic design phase of the
project.
The contractor imparts a crucial constructability perspective during the development phase and becomes a
critical partner in the project team - fostering accountability and ownership of the resultant project.
Through contractor engagement at an early stage in the design process, ambiguities, errors, or omissions
in the plans and specifications are resolved before the price for construction is established. Potential
impact on timely completion and project cost is thereby minimized. The contractor can negotiate
subcontracts during the pre-construction phase, thus allowing the contractor to present a Guaranteed
Maximum Price based in part on agreed subcontract pricing, rather than estimated costs. Moreover, a
more cooperative spirit is developed for the construction phase as the contractor gains a sense of
ownership in the design by having actively contributed to it and by sharing responsibility for any errors or
omissions. Achieving timely completion with reduced potential for change orders is therefore much more
likely than under the traditional Competitive Sealed Bidding approach.
On motion by Natalie Oschrin, seconded by Jen Fleisher, Council by the following vote
Approved the Resolution to Approve Construction Management at Risk Procedures (CMAR): 5-0 (Ayes:
Fleisher, Oschrin, Payne, Snook, Wade; Noes: none). Following consultation with the City Attorney’s
Office, Clerk Thomas confirmed a scrivener’s error, wherein the item should have been labeled as an
Ordinance. The corrected ordinance title is:
ORDINANCE APPROVING CONSTRUCTION MANAGEMENT AT RISK PROCEDURES
11. RESOLUTION to Appropriate Revenue from Participation in Energy Load Reduction Program
in the Amount of $12,375.53 (layover)
Kirk Vizzier, Energy Management Coordinator, presented the appropriation request. In March 2025, the
City of Charlottesville enrolled in the Emergency Load Response Program (ELRP) with PJM
Interconnection, LLC (electric grid operator) as part of their demand response offerings. Through this
program, the City of Charlottesville can earn revenue by temporarily reducing energy usage at
participating sites/facilities to reduce the energy load on the PJM electric grid.
Krisy Hammill, Director of Budget and Grants Management, explained the financial procedures for
accepting additional revenue funds from this program.
Council agreed to carry the item to the November 2, 2026, meeting for a second reading and vote.
12. RESOLUTION to Adopt the City Council 2027 Legislative Agenda
Steve King, Assistant to the City Manager, presented the City Council Legislative Priorities for 2027.
Councilor Snook stated that he was not in favor of Single Transferable Voting which will come with
Ranked Choice voting listed in Tier 1.
Councilor Payne asked Council to consider attaching the Human Rights Commission recommendations
regarding renter rights in Tier 2. Vice Mayor Oschrin explained why the recommendations were not
included.
Page 113 of 225
City Council Meeting Minutes – October 19, 2026
On motion by Oschrin, seconded by Fleisher, Council by the following vote Approved the
Resolution to Adopt the City Council 2027 Legislative Agenda: 5-0 (Ayes: Fleisher, Oschrin, Payne,
Snook, Wade; Noes: none).
RESOLUTION
Adopting the City of Charlottesville’s 2027 Legislative Agenda
WHEREAS, City Council wishes to establish legislative priorities to guide the City’s advocacy
during the 2027 session of the Virginia General Assembly; and
WHEREAS, City Council’s Legislative Committee has developed a tiered legislative agenda
informed by recommendations from City departments, boards and commissions, and community
partners;
NOW, THEREFORE, BE IT RESOLVED by the City Council of the City of Charlottesville,
Virginia, that:
1. City Council adopts the six-page document entitled “Proposed Legislative Priorities,” attached as
Exhibit A and incorporated into this resolution, including its Tier 1, Tier 2, and Tier 3
designations, as the City’s 2027 Legislative Agenda.
2. The City Manager, or designee, in consultation with the City Attorney and in coordination with
the Thomas Jefferson Planning District Commission’s legislative liaison, is authorized to
communicate and advocate for positions consistent with the adopted agenda, including through
testimony, correspondence, and coordination with legislators, state agencies, and regional partners.
3. The City Manager shall transmit this resolution and the adopted agenda to the City’s General
Assembly delegation and the Thomas Jefferson Planning District Commission and provide City
Council with updates on significant legislative developments.
Proposed Legislative Priorities
TIER 1
• Planning & Zoning
o Delegate Special Exceptions Approval by amending § 15.2-2286 to allow governing
bodies to delegate the authority to grant special exceptions to their Planning
Commissions, rather than reserving that function exclusively to themselves.
o Clarify Local Hardship Standards by modifying § 15.2-2286 to permit local jurisdictions
to define through ordinance the conditions under which a “hardship” exists for zoning
relief applications.
o Modifying state law by broadening and clarifying the definition of “blighted property”
for eminent domain purposes; Removing overly burdensome elements from the
definition of “derelict” in the code; Increasing the tax penalties a locality can place on a
blighted or derelict property; and expanding the penalties and fines authorized under the
finding of a nuisance by a citizen-initiated special grand jury.
• Transportation
o Advocate that the Virginia Department of Rail and Transportation's (DRPT)
'Commonwealth Corridor' plan to create an east-west passenger rail connection between
Page 114 of 225
City Council Meeting Minutes – October 19, 2026
Charlottesville, Richmond, and Hampton Roads is included DPRT's 2026 Statewide Rail
Plan. Advocate for state funding to implement DRPT's 'Commonwealth Corridor' plan.
• Development/ADA
o Enable ADA compliance by streamlining pole transfers and establishing a One Touch Make
Ready process by amending Title 56 of the Code of Virginia to:
• Require attaching entities to transfer facilities within 30 days after notice that a
replacement pole is ready.
• Establish expedited procedures when double poles affect ADA access, pedestrian
safety, traffic operations, emergency response, or active infrastructure projects.
• Direct the SCC to establish a coordinated One Touch Make Ready process
allowing qualified contractors to perform eligible transfers for multiple entities.
• Require pole owners to remove obsolete poles within 15 days after all
attachments have been transferred, unless documented safety or engineering
conditions prevent removal.
• Require pole owners and attaching entities to maintain current contact
information and use electronic notices for replacement-pole activity and
outstanding transfers.
• Authorize SCC enforcement for repeated or unreasonable failures to meet
required timelines.
• Allow localities to formally identify double poles affecting public safety or
accessibility and request expedited resolution.
• Clarify the process for correcting ADA or pedestrian accessibility conflicts by
amending Title 56 of the Code of Virginia to:
• Allow localities, after engineering or accessibility review, to formally designate
utility facilities creating a documented ADA or pedestrian obstruction.
• Require utilities to evaluate the obstruction and develop relocation or mitigation
plans within defined timeframes.
• Establish clear timelines for completing relocation when feasible.
• Provide expedited procedures for priority locations such as intersections, curb
ramps, accessible routes, transit stops, schools, government buildings, and
documented pedestrian safety concerns.
• Create an SCC coordination and escalation process when a locality and utility
cannot agree on need, feasibility, schedule, or responsibility.
• Establish reasonable standards for assigning financial responsibility, accounting
for cases where facilities predate sidewalks and situations where utilities impede
ADA compliance.
• Allow relocation work to align with utility upgrades or capital projects when it
reduces cost or disruption.
• Require consideration of alternative relocation, consolidation, undergrounding
where appropriate, or 2 facility modification before concluding a conflict cannot
be resolved.
Page 115 of 225
City Council Meeting Minutes – October 19, 2026
• Taxes
o Amend § 58.1-3703.1(A)(4)(b) to clearly distinguish good-faith jurisdictional errors from
fraud or failure to obtain a license. Under this amendment, when a taxpayer shows that they
in good faith obtained a business license and paid the business license tax to the wrong
Virginia locality, that mistake will not be treated as fraud or non-licensure. In such cases,
the correct locality may assess and collect only:
• The tax due for the current license year, and
• The tax for the three preceding license years.
• Elections
o Amend the Virginia State Code to specify that ranked‑choice voting applies to all local
offices, including school board elections
TIER 2
• Planning & Zoning
o Enable “Housing Near Jobs” Zoning Reform by adding § 15.2-2286.2 to permit by-right
multi-unit development in commercial zones statewide (as proposed in HB 816/SB 454).
o Direct DHCD to study potential regulatory modifications to allow cost-effective elevators in
residential midrise buildings that meet safety standards but are less costly than full
commercial elevators, improving affordability in multi-unit construction.
o Commission a General Assembly study on how state-level daycare licensure standards
affect the viability of urban childcare centers, with the aim of identifying scalable, cost-
effective licensing for facilities under 12 children in dense neighborhoods.
• Transportation
o Extend the delegation of building-code enforcement for state-funded bus shelters by local
officials until 2032.
• Emergency Management
o Any legislation establishing a state grant fund for local emergency management planning,
preparedness, and mitigation, consistent with VEMA’s 2027 platform.
o Any measure that shifts VDEM core programmatic functions to the general fund or
otherwise increases the agency’s pass-through of federal grant funding to cities and
counties.
o The funding mechanism recommended by the Emergency Management Needs Evaluation
once it reaches the General Assembly.
• Human Rights/Economic Security
o Increase and sustain funding for the State Rental Assistance Program, providing adults with
intellectual and developmental disabilities the financial means to lease private market rental
housing and the opportunity to choose where and with whom they live.
Page 116 of 225
City Council Meeting Minutes – October 19, 2026
o Renew legislation protecting access to courthouses, schools, health care facilities, polling
places, and other essential public institutions from civil immigration enforcement absent a
valid judicial warrant.
o Increase and sustain state funding for deeply affordable housing, with particular attention to
households with incomes below 30% of Area Median Income and those at greatest risk of
housing instability and homelessness.
o Increase and sustain investment in the Virginia Housing Trust Fund, providing predictable
and sustained resources for the creation, preservation, rehabilitation, and support of
affordable housing.
• Tax
o Preserving local administration of the Transient Occupancy Tax (TOT) and oppose any
legislation that would transfer authority over TOT collection, enforcement, or revenue
distribution from local governments to the Virginia Department of Taxation.
• Health
o Request that the Virginia Department of Medical Assistance Services (DMAS) pursue an
1115 waiver amendment under the federal Health-Related Social Needs (HRSN) authority
to add medical respite care as a reimbursable Medicaid service
o Request that the Virginia Department of Housing and Community Development (DHCD)
explicitly include “medical respite” as an eligible use under both the Virginia Homeless
Solutions Program (VHSP) and the Housing Trust Fund’s Homeless Reduction Grant
(HTF-HRG).
• Sustainability
o Allocate $600,000 to support the operations of the Energy Resource Hub initiative for 3
years. This Charlottesville/Albemarle partnership aims to help community members
improve the energy and water performance of their homes and businesses by assisting them
in navigating and accessing local, state, federal, and utility program incentives.
TIER 3
• Planning & Zoning
o Authorize a one-time appropriation for planning and initial construction of the World
Heritage Trail connecting UVA and Monticello. This cultural infrastructure project would
enhance pedestrian and heritage tourism, aligning with regional goals.
o Clarify that if a demolition permit for a historic property is not granted and the owner elects
to offer the property for sale for 12 months, after which they can proceed with the
demolition, they must publicly advertise that the property is for sale.
o Adjust Notice Requirements in Areas Without Daily Newspapers by amending § 15.2-2204
to allow alternate notice methods (e.g., digital publication or public posting) for
jurisdictions where no daily-print newspaper exists.
• Emergency Management
o Support for VEMA’s 2027 legislative platform, and for any legislation establishing a state
grant fund for local emergency management planning, preparedness, and mitigation.
Page 117 of 225
City Council Meeting Minutes – October 19, 2026
o Support for the funding mechanism recommended by the Emergency Management Needs
Evaluation once that report is delivered to the General Assembly.
• Human Rights/Economic Security
o Strengthen state support for preservation of existing affordable housing. State housing
policy should prioritize preservation and rehabilitation of existing affordable properties,
including subsidized properties at risk of conversion to market-rate housing, alongside the
production of new affordable housing.
o Amend and reenact Code of Virginia §§ 55.1-1258 and 55.1-1314 to prohibit retaliatory
nonrenewal against all tenants who engage in legally protected activity.
o Improve language accessibility to state agencies and public-facing state information.
Establish and adequately fund consistent statewide standards for interpretation, translation
of vital documents, and meaningful language access in state agencies, courts, schools, and
other public programs and services.
• Health
o Fund a full-time Tick Surveillance Coordinator position within the Virginia Department of
Health, ensuring dedicated leadership and oversight of vector surveillance efforts statewide.
• Allocate resources to modernize tick surveillance data systems
• Provide recurring research funding
• Sustainability
o Support data center reform legislation to minimize environmental impacts and reduce
financial burden on ratepayers (e.g., building data disclosure, cost-share reform,
transmission cost allocation).
o Maintain the intent of the Virginia Clean Economy Act (VCEA), in particular in light of the
Dominion/Next Era acquisition negotiations.
o Support review of the methodology for allocating funding from the Regional Greenhouse
Gas Initiative (RGGI) to expand access beyond current eligible recipients.
GENERAL BUSINESS
13. PRESENTATION of the Social Services Advisory Board Annual Report
Cherry Stewart, Chair, presented the Social Services Advisory Board Annual Report. With changes at the
Federal and State levels, the Board recommended additional personnel to support the work of Social
Services. Councilors highlighted the negative local impacts from Federal changes.
Leon Henry, Director of Social Services, outlined the specific request for appropriate staffing and
technology to implement the work requirements of the Department of Social Services.
14. WRITTEN REPORT: Land Use and Environmental Planning Committee Semi-Annual Report
The Land Use and Environmental Planning Committee Semi-Annual Report was received as a written-
only report.
Page 118 of 225
City Council Meeting Minutes – October 19, 2026
15. WRITTEN REPORT: Rivanna Authorities Quarterly Update
The Rivanna Authorities quarterly report was received as written-only.
COMMUNITY MATTERS (2)
Mayor Wade opened the floor for comments from the public. There were no speakers.
ADJOURNMENT
On motion by Fleisher, seconded by Oschrin, Council by acclamation adjourned the meeting at 9:24 p.m.
BY Order of City Council BY Kyna Thomas, Clerk of Council
Page 119 of 225
Policy Briefing Summary
City Council
Regarding: Resolution to Appropriate the Victim Witness Grant - $313,698 (2nd
reading)
Staff Contact(s): Taylor Harvey-Ryan, Grants Program Manager
Presenter: Pat O'Donnell, Director Victim and Witness Assistance Program
Date of Proposed
Action:
November 2, 2026
Issue
The City of Charlottesville, through the Commonwealth’s Attorney’s Office, has received the Victim
Witness Program Grant from the Virginia Department of Criminal Justice Services in the amount of
$188,916.00 in Federal Funds; $47,230.00 in State General Funds; and a supplemental $77,552.00
from the Commonwealth Attorney’s operating budget for a total award of $313,698.00.
Background / Rule
The victim’s rights movement began in the 1970’s as a result of victims being re-victimized by the
criminal justice process. Victims had difficulty navigating the complexities of the criminal justice system
and no voice or recourse when their cases were continued or pled out without their knowledge or
consent. Prosecutors did not have the time or skills to respond to victims traumatized by this process.
To proceed with their case, prosecutors recognized that many victims would need more services than
the prosecutor’s office could provide. In response to this need, the federal Victims of Crime Act was
passed in 1984, and funds became available through the Virginia Department of Criminal Justice to
respond to the needs of victims.
Analysis
The Charlottesville Victim/Witness Assistance Program was established in 1989 to meet the needs of
victims of crimes in Charlottesville. This program is one of more than 115 such programs in the state
that provides crisis intervention and advocacy; information and support during and after criminal justice
proceedings; access to compensation and restitution; referrals to local community agencies; and
ensures victims are afforded their rights as outlined in Virginia’s Crime Victim and Witness Rights Act.
The program also provides training to law enforcement and allied agencies on victim issues. It regularly
serves more than 1,100 victims and witnesses each year.
Financial Impact
The grant requires a City match of $77,552.00 and will be covered using funds previously appropriated
as part of the Commonwealth Attorney’s Office Fiscal Year 2027 Adopted Budget. The Victim Witness
Assistance Program Grant is renewed annually, and the funds will be received and expensed in the
grants fund.
Recommendation
Staff recommend approval and appropriation of grant funds.
Recommended Motion (if Applicable)
Attachments
Page 120 of 225
1. RES_Victim Witness - 2026
Page 121 of 225
RESOLUTION #R-__-___
RESOLUTION APPROPRIATING FUNDS FOR
THE CHARLOTTESVILLE VICTIM WITNESS ASSISTANCE PROGRAM IN THE
AMOUNT OF $313,698.00
WHEREAS, the City of Charlottesville (“City”), through the Commonwealth
Attorney’s Office, has received the Victim Witness Program Grant from the Virginia
Department of Criminal Justice Services in the amount of $188,916.00 in federal funds
and $47,230.00 in state general funds for a combined $236,146.00; and
WHEREAS the City is providing a supplement in the amount of $77,552.00, the
source of which is the Commonwealth’s Attorney’s operating budget.
NOW, THEREFORE BE IT RESOLVED by the Council of the City of
Charlottesville, Virginia, that a total of $313,698.00 is hereby appropriated in the
following manner:
Revenues $313,698
$ 47,230 Fund: 209 Cost Center: 1414001000 G/L Account: 430110
$188,916 Fund: 209 Cost Center: 1414001000 G/L Account: 430120
$ 77,552 Fund: 209 Cost Center: 1414001000 G/L Account: 498105
Expenditures $313,698
$295,507 Fund: 209 Cost Center: 1414001000 G/L Account: 519999
$ 18,191 Fund: 209 Cost Center: 1414001000 G/L Account: 599999
Transfer
$77,552 Fund: 105 Cost Center: 1401001000 G/L Account: 561209
BE IT FURTHER RESOLVED, that this appropriation is conditioned upon the
receipt of $236,146.00 from the Virginia Department of Criminal Justice Services.
Date Adopted:
Certified: _________________________
Clerk of Council
Page 122 of 225
Policy Briefing Summary
City Council
Regarding: Resolution for Blue Ridge Health District Carryover Request - $18,000
(2nd reading)
Staff Contact(s): Krisy Hammill, Director of Budget, Taylor Harvey-Ryan, Grants Program
Manager
Presenter: Ryan McKay, Health Director
Date of Proposed
Action:
November 2, 2026
Issue
The FY 2026 year-end settlement process for the Blue Ridge Health Department resulted in a
$36,553.20 surplus to be potentially returned to the City. This resulted from higher than projected
revenue and vacancy savings. Ryan McKay, Health Department Director, is requesting the City’s
permission to carry over $18,000 of those surplus funds into the current year’s Health Department
budget.
Background / Rule
In accordance with the funding agreement, any excess funds at the end of the fiscal year are to be
returned to agencies funding partners. If the health department wishes to keep any of the excess,
approval from City Council is required.
Analysis
Carryover funds in the amount of $18,000 are being requested to purchase rapid HIV/STI and syphilis
test kits ($3,000) and to remove and install two new sheds - one for storage and the other for the rabies
prevention program ($15,000).
Financial Impact
No new funds are being requested in the current fiscal year. This request is to allow the health
department to keep excess funds appropriated to them in a prior fiscal year (FY 26). The total excess
fund balance was $36,553.20 of which $18,000 is being requested and the remaining $18,553.20 will
be returned to the City.
Recommendation
Staff recommends approval of the resolution.
Recommended Motion (if Applicable)
Attachments
1. BRHD FY 2026 Carryover
Page 123 of 225
RESOLUTION #R-__-___
Authorization of Carryover for Blue Ridge Health Department
$18,000
WHEREAS, the Charlottesville-Albemarle Health Department ended the 2026
fiscal year with a surplus of $36,553.20; and that this surplus is due to vacancy savings
and higher than projected revenue; and
WHEREAS, the Health Department intends to use these surplus funds to cover
the costs of Sexually Transmitted Infection (“STI”) testing kits; and
WHEREAS, the Health Department also seeks to use a portion of the surplus
funds to remove and replace two storage sheds;
NOW, THEREFORE BE IT RESOLVED by the Council of the City of
Charlottesville, Virginia, that the Charlottesville-Albemarle Health Department is
authorized to carry over the sum of $18,000 from Fiscal Year 2026 for the above-stated
purposes.
.
Date Adopted:
Certified: _________________________
Clerk of Council
Page 124 of 225
Policy Briefing Summary
City Council
Regarding: Resolution to appropriate funding from the Virginia Department of
Housing and Community Development FY2027 Continuum of Care
Capacity Building Funds - $25,000 (2nd reading)
Staff Contact(s): Taylor Harvey-Ryan, Grants Program Manager
Presenter: Taylor Harvey-Ryan, Grants Program Manager
Date of Proposed
Action:
November 2, 2026
Issue
City of Charlottesville has received a grant in the amount of $25,000 from the Virginia Department of
Housing and Community Development for capacity building for the Continuum of Care.
Background / Rule
The Office of Budget and Grants Management in coordination with the Blue Ridge Area Coalition for
the Homeless (B.R.A.C.H.) received a grant from the Virginia Department of Housing and Community
Development. The Virginia Housing Solutions Program (V.H.S.P.) Continuum of Care Balance of State
Local Planning Group Capacity Building (C.B.) Program award is $25,000 and funds to be expended
between July 1, 2026 and June 30, 2027.
Analysis
The City of Charlottesville has staff from the Office of Budget and Grants Management and the
Department of Human Services serving on the B.R.A.C.H. Board of Directors. Virginia Homeless
Solutions Program (V.H.S.P.) Continuum of Care Balance of State Local Planning Group Capacity
Building Program has been granted by DHCD to lead agencies or their designees of the Continuum of
Care to support the organizational capacity and administrative needs of the Continuum of Care lead
agencies in Virginia. Funds may be used for the following:
1. The development and management of homeless crisis response systems
2. Grant administration and reporting of DHCD administered homeless services programs
3. Staff training
4. Essential operational tasks
Financial Impact
There is no budgetary impact to the City of Charlottesville as this grant is entirely state funds and no
local match is required. All funds will be distributed to sub-recipients.
Recommendation
Staff recommends te acceptance and appropriation of the FY26 VHSP CB grant funds and the
approval for the City Manager to execute the grant agreement and any subsequent amendments as
applicable.
Recommended Motion (if Applicable)
I move to approve the resolution as presented to appropriate the FY27 VHSP CB grant funds in the
amount of $25,000.
I move to approve the City Manager to execute the FY27 VHSP CB grant agreement and any
subsequent amendments as applicable for the administration of the FY26 VHSP CB grant award.
Page 125 of 225
Attachments
1. FY27 VHSP CB Resolution
2. FY27 VHSP CB Grant Agreemenent
Page 126 of 225
RESOLUTION
Appropriating Funding in the Amount of $25,000 To Be Received from the Virginia
Department of Housing and Community Development’s Virginia Homeless Solutions
Program, Continuum of Care Capacity Building Fund Program Year 2026- 2027
WHEREAS, The City of Charlottesville, through the Office of Budget and Grants Management
has been notified that it will be awarded a grant from the Virginia Homeless Solutions Program
(V.H.S.P.) Continuum of Care and Virginia balance of State Local Planning Group Capacity
Building (C.B.) Funds of the Virginia Department of Housing and Community Development in
the amount of $25,000.
NOW, THEREFORE BE IT RESOLVED by the Council of the City of Charlottesville,
Virginia, that upon receipt of the V.H.S.P. C.B. funding the Commonwealth of Virginia, said
funding, anticipated in the sum of $25,000, is hereby appropriated in the following manner:
Revenues
$25,000 Fund 209 Order 1900758 G/L 430110 State Grant
Expenditures
$25,000 Fund 209 Order 1900758 G/L 530550 Contractual Services
BE IT FUTHER RESOLVED that this appropriation is conditioned upon receipt of $25,000 in
funds from the Virginia Department of Housing and Community Development.
Page 127 of 225
1 of 7
VIRGINIA HOMELESS SOLUTIONS PROGRAM
Grant Agreement
Continuum of Care and Virginia Balance of State Local Planning
Group Capacity Building Funds
Program Y ear 2026–2027
Grant Number: 27-VHSP CB-025
AGREEMENT
This Agreement, entered into on September 21, 2026, by and between the Virginia Department
of Housing and Community Development (hereinafter referred to as “DHCD”) and City of
Charlottesville (hereinafter referred to as “Grantee”), establishes the terms and conditions
governing the Virginia Homeless Solutions Program (VHSP) grant for the 2026–2027
program year.
Grant Period: July 1, 2026 – June 30, 2027
Total Award Amount: $25,000
Funds may be used for the development and management of homeless crisis response systems,
grant administration and reporting of DHCD-administered homeless services programs, staff
training, and essential operational tasks.
I. Scope of Services
The VHSP goals are to assist households experiencing homelessness to quickly regain stability in
permanent housing and to prevent households from becoming homeless. This funding will
support coordinated community-based activities that are designed to reduce the overall length of
homelessness in the community, the number of households becoming homeless, and the overall
rate of formerly homeless households returning to homelessness.
Page 128 of 225
2 of 7
VHSP funds may be used for one or more of the following activities as detailed in the HSNH
guidelines and must coincide with the year one request submitted by the CoC/LPG lead agency
and approved by DHCD:
• The development and management of homeless crisis response systems
• Grant administration and reporting of DHCD-administered homeless services programs
• Staff training
• Essential operational tasks
II. Conditions
A. Reimbursement
Funds are disbursed on a reimbursement basis. Grantees must submit remittances in DHCD’s
CAMS and be able to provide documentation that the work, services, or costs occurred within
the grant period and the expenses were paid appropriately by the Grantee.
Grantees may elect to submit remittances on a monthly or bi-monthly basis. The option selected
should be adhered to throughout the year. Supporting documentation must clearly indicate the
period for which the reimbursement is requested.
Remittance Submission Schedule
Payment Period Remittance Submission Timeframe
July 1-31, 2026 August 1-31, 2026
August 1-31, 2026 September 1-30, 2026
September 1-30, 2026 October 1-31, 2026
October 1-31, 2026 November 1-30, 2026
November 1-30, 2026 December 1-31, 2026
December 1-31, 2026 January 1-31, 2027
January 1-31, 2027 February 1-28, 2027
February 1-28, 2027 March 1-31, 2027
March 1-31, 2027 April 1-30, 2027
April 1-30, 2027 May 1-31, 2027
May 1-31, 2027 By June 5, 2027
June 1-30, 2027 (projection) By June 5, 2027
B. Reporting
Grantees must submit reports as required by DHCD. Such reports may include, but are not
limited to, outcomes and performance reports. Any required reports and their due dates will be
announced by DHCD along with any relevant instructions. Submission of reports implies
approval from the executive director and is considered final. DHCD reserves the right to
withhold reimbursement payments if the Grantee fails to submit the reports.
Page 129 of 225
3 of 7
C. Continuum of Care Participation
Grantees must actively participate in the Homeless Management Information System (HMIS)
and regional Continuum of Care or Balance of State Local Planning Groups. In addition,
Grantees must ensure full participation in annual point-in-time and housing inventory counts.
D. Accounting Requirements
The Grantee must adhere to Generally Accepted Accounting Principles (GAAP). The Grantee
shall establish and maintain separate accounts within its existing accounting system or set up
accounts independently. The Grantee shall record in its accounting system all grant payments
received pursuant to the grant and all other match funds provided for, accruing to, or otherwise
received on account of the grant.
All costs charged to the grant shall be supported by properly executed payrolls, timesheets,
contracts, or vouchers evidencing in proper detail the nature and propriety of the charges. All
checks, payrolls, contracts, vouchers, or other accounting documents pertaining in whole or in
part to the grant shall be clearly identified, readily accessible, and separate and distinct from all
other such documents. Such documents shall reside at the offices of the grantee.
E. DHCD Notification
Grantee must notify DHCD of any potentially illegal act, such as misuse of grant funds or fair
housing violations, immediately upon knowledge of such act. In addition, Grantee must notify
DHCD should any other local, federal, or state agency uncover evidence of any potentially
illegal act.
Grantee must notify DHCD if there is a change in agency management and/or fiscal personnel.
Failure to do so will constitute a finding and may result in repayment of funds by the Grantee,
the de-obligation of current funding and the preclusion of future funding.
F. Audit Requirements
All grantees, sub-grantees, CHDOs, localities, developers, or any other organizations that receive
funding during a program year and/or have projects in progress are required to submit financial
statements to DHCD. For further detail, please refer to DHCD Audit Policy, available through
the following web address: https://www.dhcd.virginia.gov/sites/default/files/Docx/audit-
policy/dhcd-audit-policy.pdf.
G. Suspension and Debarment
Grantees must comply with 2 CFR Part 180 regarding debarment and suspension.
H. Compliance
Grantees with outstanding audit findings, IRS findings, DHCD monitoring findings or other
compliance issues are not eligible to receive allocations. DHCD will work with all interested
parties toward the resolution of unresolved matters, where appropriate.
Page 130 of 225
4 of 7
I. Record Maintenance
Records shall be readily accessible to DHCD, appropriate state and federal agencies, and the
general public during the course of the grant agreement and shall remain intact and accessible for
five years thereafter. The exception is that, in the event that any litigation claim or audit is
started before expiration of the five year period, the records shall be retained until such action is
resolved.
J. Costs Incurred Prior To Grant Agreement Execution
No costs incurred prior to the start of the contract period shall be eligible for reimbursement with
grant funds, unless incurred costs are authorized in writing by DHCD
K. Expenditure Review
DHCD will monitor expenditure rates to ensure state resources are maximized. Failure to
expend funds proportionately throughout the contract period may result in the de-obligation of
funds. DHCD reserves the right to de-obligate funds at any time during the contract period and
reallocate as deemed appropriate within the CoC/LPG or statewide based on compliance,
performance, need, and available funding.
L. Termination or Suspension
If, through any cause, the Grantee fails to comply with the terms, conditions, or requirements of
the contract documents, DHCD may terminate or suspend this Agreement by giving written
notice of the same and specifying the effective date of termination or suspension at least five (5)
days prior to such action.
In the case of contract violation by the Grantee, DHCD may request that all or some of the grant
funds be returned, even if the Grantee has already expended the funds. The Grantee agrees to
return such funds as requested by DHCD within 30 days of the written request.
M. Subsequent Contracts
The Grantee shall remain fully obligated under the provisions of the Grant Agreement
notwithstanding its designation of any subsequent or third parties for the undertaking of all or
part of the activities for which the Grant assistance is being provided to the Grantee.
The Grantee agrees to ensure that any contractor or subcontractor who is not the Grantee shall
comply with all the lawful requirements of the Grantee necessary to ensure that the project for
which this assistance is being provided under this Agreement is carried out in accordance with
the Grantee’s Assurances and Certifications
N. Default
A default is any unapproved use of grant funds. Upon due notice to the Grantee of the
occurrence of any such default and the provision of a reasonable opportunity to respond, DHCD
may take one or more of the following actions:
Page 131 of 225
5 of 7
(1) direct the Grantee to submit progress schedules for completing approved
activities;
(2) issue a letter of warning advising the Grantee of the default, establishing a date by
which corrective actions must be completed and putting the Grantee on notice that
more serious actions will be taken if the default is not corrected or is repeated;
(3) direct the Grantee to suspend, discontinue or not incur costs for the affected
activity;
(4) require the Grantee to reimburse DHCD for costs inappropriately charged to the
program;
(5) other appropriate action including, but not limited to, any remedial action legally
available, such as affirmative litigation seeking declaratory judgment, specific
performance, damages, temporary or permanent injunctions and any other
available remedies.
No delay or omissions by DHCD in exercising any right or remedy available to it under the
Agreement shall impair any such right to remedy or constitute a waiver or acquiescence in any
Grantee default.
O. Conflict of Interest
Grantees and partners must maintain written conflict of interest policies that clearly prohibit
personal gain or benefit and must comply with 2 CFR 200.112 regarding conflicts of interest.
Grantees shall ensure that the provision of any type or amount of assistance may not be
conditional on an individual’s or family’s acceptance or occupancy of housing owned by the
grantee, the sub-grantee, a parent organization, or subsidiary. Grantees/sub-grantees, parent
organizations, or subsidiaries may not administer rapid re-housing or prevention assistance and
use the assistance for households residing in units owned by the grantee/sub-grantee, parent
organization, or subsidiary.
Individuals (employees, agents, consultants, officers, or elected or appointed officials of the
grantee or sub-grantee) may not both participate in decision-making related to determining
eligibility and receive any financial benefit. This financial benefit may not be received by the
specific individual, any member of his/her immediate family, or a business interest. The
restriction applies throughout tenure in the position and for a one-year period following tenure.
P. Religious Influence
The Grantee may not engage in inherently religious activities, such as worship, religious
instruction, or proselytization as part of the programs or services funded under VHSP. If an
organization conducts these activities, then they must be offered separately, in time or location,
from the programs or services funded under VHSP, and participation must be voluntary for
program participants.
Page 132 of 225
6 of 7
III. Additional Assurances
A. Grantee will give the DHCD, the Virginia State Comptroller, HUD, and any other
authorized state or federal representatives access to and the right to examine all records,
books, papers, or documents related to the Grant.
B. In accordance with federal law, the Grantee will provide that no person shall be
discriminated against on the basis of race, color, religion, sex, or national origin, in any
phase of employment or in any phase of service delivery.
IV . Additional Certifications
The Grantee certifies compliance with:
i. Freedom of Information Act (5 U.S.C 552) and Virginia Freedom of Information Act;
ii. Virginia Fair Employment Contracting Act;
iii. Virginia Fair Housing Law (Va. Code Ann. § 36-96.1) to provide fair housing throughout
the Commonwealth, to all its citizens, regardless of race, color, religion, national origin,
sex, elderliness, familial status, source of funds, sexual orientation, gender identity,
military status, or disability.
iv. Fair Housing Act (42 U.S.C. 3601-20), and implementing measures under:
a. 24 CFR 100 (discriminatory conduct under Fair Housing Act);
b. Executive Order 11063 and regulations at 24 CFR 107 (preventing discrimination
on the basis of race, color, creed, or national origin);
c. 24 CFR Part 8 (prohibiting discrimination against handicapped individuals);
d. Title VIII of the Civil Rights Act of 1968, as amended, also known as the Fair
Housing Act, prohibits discrimination in housing based on race, color, religion,
sex, disability, familial status, or national origin.
v. The Violence Against Women Act (V AWA), Title IV of the Violent Crime Control and
Law Enforcement Act of 1994, and implementing regulations at:
a. 28 CFR 90 Violence Against Women
vi. Age Discrimination Act of 1975 (42 U.S.C. 6101-07) and implementing regulations at:
a. 24 CFR 146 (nondiscrimination on the basis of age in HUD programs);
b. Section 504 of the Rehabilitation Act of 1973 (29 U.S.C. 794);
vii. 24 CFR 574.320 (Federal rent standards for rental assistance, requiring rents to be
charged no greater than appropriate Fair Market Rent levels);
viii. 24 CFR Part 35 (Federal lead-based paint provisions, requiring visual inspections and
stabilization of paint before commencement of occupancy);
ix. Encourage participation of locally-owned enterprises in connection with funded
activities;
a. McKinney-Vento Homeless Assistance Program Regulations;
b. Anti-lobbying Certification;
c. Drug-Free Workplace
Page 133 of 225
7 of 7
If requested:
• A Grantee that is a unit of local government agrees to assume the status of a responsible
Federal official under the National Environmental Policy Act (NEPA) of 1969 and other
provisions of Federal law as specified at 24 CFR 58 and 58.5 and agrees to comply with
these NEPA regulations.
All Grantees that are not units of local government agree to assist DHCD in carrying out 24 CFR
58 and 58.5.
Signatures and Date
The Agreement is hereby executed by the parties on the date set forth below their respective
signatures as follows:
Virginia Department of Housing and
Community Development
Signature:__________________________
Printed Name/Title:
Sandra Powell, Sr. Deputy Director
Date: _____________________________
City of Charlottesville
Signature: __________________________
Printed Name/Title:
__________________________________
Date: ______________________________
Page 134 of 225
Policy Briefing Summary
City Council
Regarding: Resolution to Appropriate Revenue from Participation in Energy Load
Reduction Program in the Amount of $12,375.53 (2nd reading)
Staff Contact(s): Kirk Vizzier, Kristel Riddervold, Director of the Office of Sustainability
Presenter: Kirk Vizzier, City Energy Management Coordinator
Date of Proposed
Action:
November 2, 2026
Issue
In March 2025, the City of Charlottesville enrolled in the Emergency Load Response Program (ELRP)
with PJM Interconnection, LLC (electric grid operator) as part of their demand response offerings.
Through this program, the City of Charlottesville can earn revenue by temporarily reducing energy
usage at participating sites/facilities to reduce the energy load on the PJM electric grid.
Background / Rule
An Energy and Water Management Program (EWMP) was created in June 2020 for the appropriation
of revenue generated from energy management and water management projects/programs. The City
participates in other PJM energy management programs including the Energy Efficiency Program
where past revenue earned has been appropriated to the EWMP Fund. The Emergency Load
Response Program offers another source of revenue from energy management practices that is to be
paid out on an annual (sometimes quarterly) basis.
• From October 2019 – November 2025, the City earned $3,770 from the PJM Energy
Efficiency Program, which was appropriated to the Energy and Water Management Fund.
• In August 2026, the City received payment in the amount of $12,375.53 in the PJM
Emergency Load Response Program for reducing energy usage at participating sites
during the May 2025 – April 2026 year.
It is recommended that revenue generated from the PJM Emergency Load Response Program and all
other PJM energy management programs be appropriated to the EWMP Fund.
Analysis
Participation in PJM energy management programs supports the goals of Climate Action, which is a
strategic outcome area of the City’s Strategic Plan and the Climate Action Plan is part of the City’s
Comprehensive Plan. Climate Action includes efforts related to climate adaptation and resilience
planning. PJM programs provide a mechanism for the City to support the stability of the electricity grid,
improving electricity resilience throughout the Charlottesville area. In addition, reduced energy usage at
City facilities will achieve greenhouse gas reductions bringing the City closer to meeting its Climate
Action goals.
Financial Impact
These funds, received through the City's participation in the PJM energy management programs, will
support energy and water efficiency measures.
Recommendation
Staff recommends City Council adoption of the attached Resolution.
Page 135 of 225
Recommended Motion (if Applicable)
“I move to adopt the attached Resolution appropriating PJM Energy Management Programs Revenue
to the Energy and Water Management Program Fund.”
Attachments
1. RESOLUTION ELRP Revenue Appropriation
Page 136 of 225
RESOLUTION #R-__-___
APPROPRIATING PJM ENERGY MANAGEMENT PROGRAM REVENUE TO THE
ENERGY AND WATER MANAGEMENT PROGRAM FUND
WHEREAS, PJM is the regional transmission organization that coordinates the movement of
wholesale electricity; and
WHEREAS, the City of Charlottesville has been participating in PJM energy management
programs, including the Emergency Load Response Program and the Energy Efficiency
Program, that provide a mechanism for the City to support the stability of the electricity grid,
improving electricity resilience throughout the Charlottesville area.
WHEREAS, participation in these PJM energy management programs results in payment to the
City by PJM; and
WHEREAS, the City of Charlottesville has recently received a payment of $12,375.53 from
PJM Interconnection, LLC from participation in PJM energy management programs; and
WHEREAS, this revenue is intended to be used for further energy and water management
projects that support City Climate Action goals;
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville that
the recently earned revenue from PJM Interconnection, LLC., in the sum of $12,375.53, and any
additional revenue received from PJM energy management programs during the fiscal year is
hereby automatically appropriated as follows:
Revenues:
$12,375.53 Fund: 105 Internal Order: 2000157 G/L Account: 451020
Expense:
$12,375.53 Fund: 105 Internal Order: 2000157 G/L Account: 599999
Date Adopted:
Certified: _________________________
Clerk of Council
Page 137 of 225
Policy Briefing Summary
City Council
Regarding: Resolution to Appropriate funds from the Sentara Foundation to the
Department of Human Services for the Westhaven CARES Center -
$7,000 (1 of 2 readings)
Staff Contact(s): Reginald Allen, Human Services Planner, Taylor Harvey-Ryan, Grants
Program Manager
Presenter: Reginald Allen, Human Services Planner
Date of Proposed
Action:
November 2, 2026
Issue
The City of Charlottesville’s Department of Human Services has been awarded a $7,000 Sentara
Cares grant to support the Westhaven Food Pantry that needs to be appropriated.
Background / Rule
The City of Charlottesville’s Department of Human Services has been awarded a $7,000 Sentara
Cares grant to support the Westhaven Food Pantry. Sentara Cares provides competitive grant
funding to eligible organizations for programs that advance community health and well-being.
The award aligns with Sentara’s food access funding priority, which promotes equitable access to
nutritious and culturally relevant food through food pantries, community partnerships, and
initiatives that reduce barriers to food access. Grant funds will support the Westhaven Food
Pantry in addressing food insecurity and improving food access for residents.
Analysis
Demand for services at the Westhaven CARES Center continues to grow. Based on anticipated
operating expenses and community needs, the Center identified a projected funding shortfall of
approximately $7,000. This shortfall was the primary basis for seeking Sentara Cares funding. The
$7,000 grant will help sustain pantry operations, maintain food inventory, and ensure consistent
food assistance for residents.
The Center’s monthly food pantry provides nutritious food and household essentials to at least 20
households, reaching an estimated 40 residents, including children. The Center also administers
the monthly First Wednesday Gift Card Program with assistance from the Emergency Food
Network, distributing approximately 30 gift cards valued at $50 each to households experiencing
financial hardship.
Over the past year, the Center has expanded its capacity through the acquisition of a deep freezer
and the creation of a walk-in pantry space. These improvements have increased food storage
capacity, expanded the variety of available foods, and improved distribution efficiency.
Page 138 of 225
The program supports priorities identified in the regional MAP to Health Community Health
Assessment by addressing food access and the social drivers of health. Grant funding will help
ensure the continued availability of these services and strengthen the Center’s role as a
community resource supporting families and improving quality of life in Westhaven and
surrounding neighborhoods.
Financial Impact
The $7,000 Sentara Cares grant will address the projected funding shortfall for the Westhaven
Food Pantry, support pantry operations, and maintain food inventory.
The funding will support community health by maintaining access to nutritious food for residents
experiencing food insecurity. Food and household assistance will also help reduce household
expenses, allowing residents to allocate limited financial resources toward housing, utilities,
transportation, medication, and other essential needs.
Recommendation
Staff recommends that City Council approve the appropriation of $7,000 in Sentara Cares grant
funds to support the Westhaven Food Pantry’s operations and continued provision of food
assistance to residents.
Recommended Motion (if Applicable)
Motion to approve the resolution to appropriate $7,000 in Sentara Cares grant funds to support
the Westhaven Food Pantry.
Attachments
1. West Haven Memo12
Page 139 of 225
RESOLUTION
TO APPROPRIATE $7000.00 IN GRANT FUNDING FROM SENTARA HEALTH FOR
WESTHAVEN’S FOOD PANTRY
WHEREAS, the City of Charlottesville, through the Department of Human Services,
has received funding to support Westhaven’s food pantry from Sentara Health
NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Charlottesville
that the sum of $7000.00 is hereby appropriated in the following manner:
Revenue - $7000.00
$7000.00 Fund: 210 Order: 1900757 G/L Account: 451022
Expenditures - $7000.00
$7000.00 Fund: 210 Order: 1900757 G/L Account: 599999
Be it further resolved that this appropriation is subject to the receipt of $7000.00
from Sentara Health. All funds hereby appropriated shall be accounted for and expended
in accordance with the requirements of the Sentara Health Grant.
Page 140 of 225
Policy Briefing Summary
City Council
Regarding: Resolution Considering a Special Exception Permit Application for 835
West Main Street, 843 West Main Street, and 847 West Main Street (PL-
26-0126)
Staff Contact(s): Carrie Rainey, Urban Designer/City Planner
Presenter: Carrie Rainey, Urban Designer/City Planner
Date of Proposed
Action:
November 2, 2026
Issue
Consideration of an Application for a Special Exception Permit
Background / Rule
Andree Sahakian of LV Collective ("Applicant") has requested a Special Exception Permit ("SEP") to
modify Active Depth, Ground Story Height, Finished Floor Elevation, and Street-Facing Entry Spacing,
and Bicycle Parking at 835 West Main Street, 843 West Main Street, and 847 West Main Street
("Subject Properties"), pursuant to City Development Code ("CDC") Sections 34-2.10.10.B, 34-
2.10.11.A, 34-2.10.11.B, 34-2.10.13, 34-4.5.2, and 34-5.2.15. Applicant proposes to redevelop the
Subject Properties with 182 multifamily residential units and a café. A public plaza is proposed
between the building and West Main Street and public pedestrian access to the adjacent Westhaven
property owned by the Charlottesville Redevelopment and Housing Authority.
The Applicant requests to reduce the Ground Story Height within a portion of the proposed building due
to existing site grades and access to upper level amenity space, to reduce the Active Depth
requirement within a portion of the proposed building where stair access is proposed, to modify the
Finished Floor Elevation for a portion of the proposed building to accommodate site grading and
accessible space, to modify the Street-Facing Entry Spacing requirement due to site grading and
accessible entrance requirements, and to modify the Bicycle Parking Space dimensional requirements
to permit the use of a two-tiered space-saving rack system.
Analysis
The Board of Architectural Review ("BAR") considered this SEP application at its September 15, 2026,
Meeting and found no adverse impact to the West Main Street Architectural Design Control District
("ADC") by the proposed modifications which impact the exterior building design germane to BAR's
review. The full Application for this Project can be found at the following link. Materials start on page 3.
Link to Staff Report and Application Materials
The Planning Commission ("PC") considered this SEP application at its October 13, 2026,
meeting. The PC discussed aspects of the Application, including the interaction between the public
plaza and interior building spaces and the usability of the proposed space-saving bicycle parking racks
before recommending approval of the Application with no recommended conditions.
A recording of the Meeting can be found at the following link. Discussion starts at the 1:00:07 mark.
Link to Recording of Regular Meeting
Page 141 of 225
The full Application for this Project can be found at the following link. Materials start on page 25.
Link to Staff Report and Application Materials
Financial Impact
None.
Recommendation
BAR found no adverse impact on the West Main Street ADC by the proposed modifications, which
impact the exterior building design germane to BAR review via a 8-0 affirmative vote. The PC
recommended approval of the SEP with no recommended conditions via a 7-0 affirmative
vote. Accordingly, NDS Staff recommends City Council adopt the attached Resolution approving the
SEP Application for the Subject Properties as presented.
Recommended Motion (if Applicable)
"I move to adopt the attached Resolution approving the SEP Application for the Subject Properties as
presented."
Attachments
1. RESOLUTION - Special Exception - 835 843 847 W Main Street
Page 142 of 225
#R-26-________
RESOLUTION APPROVING A REQUEST FOR A SPECIAL EXCEPTION PERMIT
(“SEP”) FOR PROPERTY LOCATED AT 835 W MAIN STREET, 843 W MAIN
STREET, AND 847 W MAIN STREET
WHEREAS, Fluvanna Holdings, LLC, Kim Tran Dabney, Kim T., and Chris T. Dabney
(“Landowners”) are the current owners of lots identified on 2026 City Tax Map 31 as Parcels
183, 175, and 174 (City Parcel Identification Numbers 310183000, 310175000, and 310174000),
having an area of approximately 1.61 acres (70,100 square feet); (“Subject Properties”); and
WHEREAS, the Landowners wish to develop residential units with modified active
depth, ground story height, finished floor elevation, street-facing entry spacing, and bicycle
parking space dimensions on the Subject Properties (“Project”); and
WHEREAS, the Project is described in more detail within the Landowners’ application
materials submitted in connection with Application PL-26-0126 (“Application”), as required by
City Development Code (“CDC”) § 34-5.2.15.B.2 (collectively, "Application Materials"); and
WHEREAS, the City of Charlottesville Board of Architectural Review (“BAR”)
recommended that the proposed exceptions will not have an adverse impact on the West Main
Street Architectural Design Control District at its September 15, 2026, Public Meeting, per CDC
§ 34-5.2.15.C.1.c; and
WHEREAS, the City of Charlottesville Planning Commission (“PC”) made a
recommendation of approval at its October 13, 2026, Public Meeting, per CDC § 34-5.2.15.C.2.
NOW THEREFORE, BE IT HEREBY RESOLVED, by the Council of the City of
Charlottesville, Virginia (“City Council”), upon consideration of BAR’s and PC's
recommendations and the City Staff Report discussing the Application, as well as the factors set
forth within CDC § 34-5.2.15.D, that it finds and determines that granting the proposed SEP
would serve the public necessity, convenience, general welfare, or good zoning practice; and
BE IT FURTHER RESOLVED, by City Council, pursuant to CDC § 34-5.2.15, a SEP
is hereby approved and granted to authorize the Project and permit modified active depth, ground
story height, finished floor elevation, street-facing entry spacing, and bicycle parking space
dimensions consistent with the Application Materials for the Subject Properties.
Approved by Council
__________, 2026
______________________
Kyna Thomas
Clerk of Council
Page 143 of 225
Policy Briefing Summary
City Council
Regarding: Marijuana Marketplace Local Ordinance Zoning Text Amendment
Initiation Resolution Adoption
Staff Contact(s): April Wimberley, Assistant City Attorney, Todd Divers, Commissioner of the
Revenue, Missy Creasy, Deputy Director of NDS, Elaine McCafferty, Deputy
City Attorney
Presenter: John Maddux, City Attorney, Missy Creasy, Deputy Director of NDS
Date of Proposed
Action:
November 2, 2026
Issue
Zoning Text Initiation
Background / Rule
In 2026, the Virginia General Assembly enacted legislation establishing a regulated adult-use cannabis
marketplace in the Commonwealth. Said legislation amends Title 4.1 of the Virginia Code and
establishes a comprehensive regulatory framework administered by the Virginia Cannabis Control
Authority (“VCCA”). This new framework has significant implications for localities, including impacts on
zoning, business licensing, taxation, and other local powers.
The VCCA’s Board of Directors must promulgate regulations by February 1, 2027, and the first
licensing period will commence on that date. Retail sales commence July 1, 2027. Localities must
address any necessary local Ordinance amendments, establish internal processes for responding to
license application notifications, and adopt a local marijuana tax Ordinance. Local zoning and other
ordinances concerning the marijuana marketplace should be effective by February 1, 2027, so that the
locality can review VCCA preliminary approval of applications based on noncompliance with local
ordinances.
As there are zoning-related regulations to be considered, initiation of the review of this Ordinance
needs to occur. Whenever and wherever the public necessity, convenience, general welfare, or good
zoning practice requires, the Council of the City of Charlottesville, Virginia (“City Council”), may, by
Ordinance, amend, supplement, or change the City of Charlottesville, Virginia’s (“City”), Zoning District
regulations, District boundaries, or Zoning District classifications of property.
A Zoning Text Amendment (“ZTA”) may be initiated by: (1) City Council Resolution; or (2) Planning
Commission (“PC”) Motion (See City Development Code (“CDC”) Section 34-5.2.5.B.1.a, which is
based on Virginia Code § 15.2-2286(A)(7)).
Analysis
City Staff has been researching this issue and working towards a local regulation proposal for
consideration by City Council. As the State regulations are in draft form and the City needs to have its
regulations in place by the same time as the State’s regulations become final, City Staff is planning to
provide a recommendation based on what information is available to meet all the statutory
requirements to have local regulations in place at the appropriate time. It is anticipated, once this
system is in place, that additional review of regulations will take place to refine the same.
Page 144 of 225
City Staff anticipates the creation of a standalone CDC/City Code Chapter to house the local
regulations related to the marijuana marketplace to meet the prescribed timeframes and ease of review
for all regulations pertaining to the topic.
Financial Impact
None
Recommendation
City Staff recommends City Council adopt the attached Resolution initiating PC review, consideration,
and recommendation relating to the proposed ZTA for local marijuana marketplace regulations to City
Council.
Recommended Motion (if Applicable)
"I move to adopt the attached Resolution initiating PC review, consideration, and recommendation
relating to the proposed ZTA for local marijuana marketplace regulations to City Council.”
Attachments
1. RESOLUTION - ZTA Initiation Marijuana Marketplace
2. LGA - 7.15.26 Model Ordinance
Page 145 of 225
RESOLUTION #R-26-___
RESOLUTION INITIATING PLANNING COMMISSION (“PC”) REVIEW,
CONSIDERATION, AND RECOMMENDATION OF CITY CODE ZONING TEXT
AMENDMENT (“ZTA”) REGARDING LOCAL REGULATION OF THE MARIJUANA
MARKETPLACE
WHEREAS, upon consideration of matters set forth within a report received from the
Director of Neighborhood Development Services, initiation of a ZTA is desirable to commence
debate and consideration within the context of a Public Hearing process of an amendment of the
Code of the City of Charlottesville, Virginia (“City Code”), to provide for local marijuana
marketplace regulations; and
WHEREAS, the Council of the City of Charlottesville, Virginia (“City Council”), finds
that consideration of a proposed ZTA is required by the public necessity, convenience, general
welfare; or good zoning practice.
NOW THEREFORE, BE IT RESOLVED by City Council that a ZTA process is hereby
initiated pursuant to and in accordance with Virginia Code § 15.2-2285(A) and City Code Section
34-5.2.5.B.1.a, to provide for regulation of the local marijuana marketplace; and
BE IT FURTHER RESOLVED THAT the proposed ZTA is hereby referred to the
Charlottesville PC for its recommendations, and to be scheduled for a Joint Public Hearing with
City Council. Based on the PC’s deliberations and input received during the Public Hearing
process the PC shall report its findings and recommendations back to City Council within one
hundred (100) days after its first regular Meeting following the adoption of this initiation
Resolution.
Date Adopted:
Certified: _________________________
Clerk of Council
Page 146 of 225
1
LGA MODEL MARIJUANA ORDINANCE
Welcome to the LGA Model Marijuana Ordinance. This document is inspired by the Virginia
General Assembly 2026 Special Session I’s marijuana legislation available here:
https://budget.lis.virginia.gov/item/2026/2/HB30/Chapter/4/4-14.00/. The codified version of the
Cannabis Control Act (Virginia Code Title 4.1, Subtitle II) is available here:
https://law.lis.virginia.gov/vacodefull/title4.1/subtitleII/.
This document:
(a) Is intended to (1) introduce localities to their regulatory options and requirements under
relevant marijuana legislation and (2) provide template language.
(b) Was written as if a locality were to adopt a chapter dedicated to marijuana regulation,
regardless of the type of regulation. For example, this document contains language
related to personal conduct, taxation, and zoning in the same model ordinance. The
drafters understand that localities are not likely to include zoning regulations outside of
their dedicated zoning ordinance. Nevertheless, zoning regulations are included alongside
other items herein to avoid multiplying documents. LGA members may consider
inserting provisions of this document in appropriate areas of their locality’s code or
noncodified ordinances.
(c) Includes explanatory footnotes and comments directing the reader to relevant authorities.
(d) Was written as if the adopting locality applied zoning regulations by marijuana
establishment type. LGA member localities may organize their zoning ordinances
differently. However, the zoning section includes a footnote about zoning authority over
marijuana establishments that may be useful.
This document may be updated from time to time. If you have any questions regarding this
document, please feel free to contact Marijuana Committee Chair Donnie Autry at
dautry@arlingtonva.us. The model ordinance begins on the following page.
Page 147 of 225
2
ORDINANCE TO AMEND THE [INSERT LOCALITY NAME HERE] CODE TO ADD
A NEW CHAPTER [ ] TO REGULATE CERTAIN LOCAL ASPECTS OF ADULT-USE
CANNABIS BUSINESSES
BE IT ORDAINED by the [INSERT NAME OF THE LOCALITY’S GOVERNING BODY
HERE] of [INSERT NAME OF LOCALITY HERE], Virginia:
1. That the [INSERT LOCALITY NAME HERE] Code is amended by adding a new
Chapter [ ] as follows:
[INSERT LOCALITY NAME HERE] Code
Chapter [ ]
CANNABIS
Sec. 1 – Title.
This chapter shall be known as the “Cannabis Ordinance of [INSERT LOCALITY NAME
HERE].”
Sec. 2 – Definitions (Effective until August 15, 2026).
This section is effective upon adoption and expires at 12:00 am on August 15, 2026. As used in
this chapter, unless the context requires a different meaning:
“Cannabis dispensing facility” means the same as that term is defined in Virginia Code § 4.1-
1600.
“Cultivation” means the planting, propagation, growing, harvesting, drying, curing, grading,
trimming, packaging, or other similar manufacturing of marijuana for use or sale. “Cultivation”
does not include processing or testing.
“Hemp product” means a product, including any raw materials from industrial hemp that are
used for or added to a food or beverage, that (i) contains industrial hemp and has completed all
stages of processing needed for the product and (ii) when offered for retail sale (a) contains a
total tetrahydrocannabinol concentration of no greater than 0.3 percent and (b) contains no more
than two milligrams of total tetrahydrocannabinol per package or an amount of cannabidiol that
is no less than 25 times greater than the amount of total tetrahydrocannabinol per package.
“Industrial hemp” means the same as that term is defined in Virginia Code § 3.2-4112.
“Industrial hemp extract” means the same as that term is defined in Virginia Code § 3.2-5145.1.
“Licensed” means the holding of a valid license or permit granted by the Virginia Cannabis
Control Authority.
Commented [A1]: If your locality’s zoning
ordinance is not codified, this obviously will not
change.
Commented [A2]: Consider how your locality
would like to frame the object of this ordinance in
its caption. See Virginia Code § 15.2-1426.
Commented [A3]: Authority: Virginia Code
section 4.1-600. Please note that this Virginia Code
section has two different versions with differing
effective dates. The seventh and ninth enactments
of the 2026 Special Session I language clarify that a
new version of Virginia Code section 4.1-600 takes
effect on August 15, 2026. Link. Consequently, this
Model Ordinance has two definition sections
reflecting the variable dates.
It is not likely that localities will be in a position to
update their codes with this language before
August 15, 2026. Thus, the pre-August 15, 2026,
language is presented here mostly for informational
purposes. Takeaway: Your locality will most likely
need to use the definitions found in section 2.1 of
this model ordinance and not in section 2.
Additionally, pleas note that the defined terms
listed in sections 2 and 2.1 in this model ordinance
are only those that appear elsewhere in the model
ordinance. Your locality’s ordinance may use more
than the terms listed here.
Furthermore, the terms “cannabis dispensing
facility” and “pharmaceutical processor” are not
defined by either version of Virginia Code section
4.1-600. However, both are considered “marijuana
establishments” and discussed in section 7 of this
model ordinance. Their definitions in this model
ordinance are derived from Virginia Code 4.1-1600.
Page 148 of 225
3
“Marijuana” means any part of a plant of the genus Cannabis, whether growing or not, its seeds
or resin; and every compound, manufacture, salt, derivative, mixture, or preparation of such
plant, its seeds, its resin, or any extract containing one or more cannabinoids. “Marijuana” does
not include (i) the mature stalks of such plant, fiber produced from such stalk, or oil or cake
made from the seed of such plant, unless such stalks, fiber, oil, or cake is combined with other
parts of plants of the genus Cannabis; (ii) industrial hemp that is possessed by a person registered
pursuant to subsection A of Virginia Code § 3.2-4115 or his agent; (iii) industrial hemp that is
possessed by a person who holds a hemp producer license issued by the U.S. Department of
Agriculture pursuant to 7 C.F.R. Part 990; (iv) a hemp product; (v) an industrial hemp extract; or
(vi) any substance containing a tetrahydrocannabinol isomer, ester, ether, salt, or salts of such
isomer, ester, or ether that has been placed by the Virginia Board of Pharmacy into one of the
schedules set forth in the Drug Control Act (Virginia Code § 54.1-3400 et seq.) pursuant to
Virginia Code § 54.1-3443.
“Marijuana concentrate” means marijuana that has undergone a process to concentrate one or
more active cannabinoids, thereby increasing the product's potency. Resin from granular
trichomes from a marijuana plant is a concentrate for purposes of this subtitle.
“Marijuana cultivation facility” means a facility licensed under Virginia Code § 4.1-800.
“Marijuana delivery operator” means an entity licensed under Virginia Code § 4.1-805.
“Marijuana establishment” means a marijuana cultivation facility, marijuana microbusiness,
marijuana deliver operator, marijuana testing facility, marijuana processing facility, marijuana
transporter, retail marijuana store, or pharmaceutical processor or cannabis dispensing facility
authorized to exercise dual-use privileges pursuant to Virginia Code § 4.1-1602.1.
“Marijuana processing facility” means a facility licensed under Virginia Code § 4.1-801.
“Marijuana products” means (i) products that are composed of marijuana and other ingredients
and are intended for use or consumption, ointments, and tinctures or (ii) marijuana concentrate.
“Marijuana testing facility” means a facility licensed under Virginia Code § 4.1-806.
“Marijuana transporter” means a facility licensed under Virginia Code § 4.1-804.
“Microbusiness” means a facility licensed under Virginia Code § 4.1-803.
“Pharmaceutical processor” means the same as that term is defined in Virginia Code § 4.1-1600.
“Processing” or “process” means that production of marijuana products or the blending, infusing,
compounding, or other preparation of marijuana or marijuana products, including marijuana
extraction or preparation by means of chemical synthesis. “Processing” or “process” does not
include cultivation or testing.
Page 149 of 225
4
“Retail marijuana store” means a facility licensed under Virginia Code § 4.1-802.
“Sale” includes soliciting or receiving an order; keeping, offering, or exposing for sale; peddling,
exchanging, or bartering; or delivering other than gratuitously, by any means.
“Testing” means the research and analysis of marijuana, marijuana products, or other substances
for contaminants, safety, or potency. “Testing” does not include cultivation or processing.
“Tetrahydrocannabinol” means any naturally occurring or synthetic tetrahydrocannabinol,
including its salts, isomers, and salts of isomers whenever the existence of such salts, isomers,
and salts of isomers is possible within the specific chemical designation and any preparation,
mixture, or substance containing, or mixed or infused with, any detectable amount of
tetrahydrocannabinol. For the purposes of this definition, “isomer” means the optical, position,
and geometric isomers.
“Total tetrahydrocannabinol” means the sum, after the application of any necessary conversion
factor, of the percentage by weight of tetrahydrocannabinol and the percentage by weight of
tetrahydrocannabinolic acid.
Sec 2.1 – Definitions (Effective August 15, 2026).
This section is effective at 12:00 am on August 15, 2026. As used in this chapter, unless the
context requires a different meaning:
“Cultivation” or “cultivate” means the planting, propagation, growing, harvesting, drying,
curing, grading, trimming, packaging, or other similar manufacturing of marijuana for use or
sale. “Cultivation” or “cultivate” does not include processing or testing.
“Hemp product” means a product, including any raw materials from industrial hemp that are
used for or added to a food or beverage, that (i) contains industrial hemp and has completed all
stages of processing needed for the product and (ii) when offered for retail sale (a) contains a
total tetrahydrocannabinol concentration of no greater than 0.3 percent and (b) contains no more
than two milligrams of total tetrahydrocannabinol per package.
“Immature plant” means a nonflowering marijuana plant that is no taller than eight inches and no
wider than eight inches, is produced from a cutting, clipping, or seedling, and is growing in a
container.
“Industrial hemp” means the same as that term is defined in Virginia Code § 3.2-4112.
“Industrial hemp extract” means the same as that term is defined in Virginia Code § 3.2-5145.1.
“Licensed” means the holding of a valid license or permit granted by the Virginia Cannabis
Control Authority.
Commented [A4]: See comment regarding
section 2 above. Takeaway: This language is likely
to be more helpful for your locality than the
language in section 2.
Page 150 of 225
5
“Marijuana” means any part of a plant of the genus Cannabis, whether growing or not, its seeds
or resin; and every compound, manufacture, salt, derivative, mixture, or preparation of such
plant, its seeds, its resin, or any extract containing one or more cannabinoids. “Marijuana” does
not include (i) the mature stalks of such plant, fiber produced from such stalk, or oil or cake
made from the seed of such plant, unless such stalks, fiber, oil, or cake is combined with other
parts of plants of the genus Cannabis; (ii) industrial hemp that is possessed by a person registered
pursuant to subsection A of Virginia Code § 3.2-4115 or his agent; (iii) industrial hemp that is
possessed by a person who holds a hemp producer license issued by the U.S. Department of
Agriculture pursuant to 7 C.F.R. Part 990; (iv) a hemp product; (v) an industrial hemp extract; or
(vi) any substance containing a tetrahydrocannabinol isomer, ester, ether, salt, or salts of such
isomer, ester, or ether that has been placed by the Virginia Board of Pharmacy into one of the
schedules set forth in the Drug Control Act (Virginia Code § 54.1-3400 et seq.) pursuant to
Virginia Code § 54.1-3443.
“Marijuana concentrate” means marijuana that has undergone a process to concentrate one or
more active cannabinoids, thereby increasing the product's potency. Resin from granular
trichomes from a marijuana plant is a concentrate for purposes of this subtitle.
“Marijuana cultivation facility” means a facility licensed by the Board of Directors of the
Virginia Cannabis Control Authority to cultivate, label, and package marijuana; to purchase or
take possession of marijuana plants and seeds from other marijuana cultivation facilities; to
transfer possession of and sell marijuana, immature marijuana plants, and marijuana seeds to
retail marijuana stores; to transfer possession of marijuana, immature marijuana plants, and
marijuana seeds to marijuana transporters; to transfer possession of and sell marijuana, marijuana
plants, and marijuana seeds to other marijuana cultivation facilities; to transfer possession of and
sell marijuana to marijuana processing facilities; and to transport marijuana, immature marijuana
plants, and marijuana seeds from the marijuana cultivation facility's licensed premises to another
licensed marijuana establishment.
“Marijuana delivery operator” means an entity licensed by the Board of Directors of the Virginia
Cannabis Control Authority to take possession of marijuana or marijuana products from a retail
marijuana store, microbusiness, pharmaceutical processor, or cannabis dispensing facility and
deliver such marijuana or marijuana products only in person to patients or consumers at their
residence or business.
“Marijuana establishment” means a marijuana cultivation facility, marijuana microbusiness,
marijuana delivery operator, marijuana testing facility, marijuana processing facility, marijuana
transporter, retail marijuana store, or pharmaceutical processor or cannabis dispensing facility
authorized to exercise dual-use privileges.
“Marijuana paraphernalia” means all equipment, products, and materials of any kind that are
either designed for use or are intended for use in planting, propagating, cultivating, growing,
harvesting, manufacturing, compounding, converting, producing, processing, preparing, strength
testing, analyzing, packaging, repackaging, storing, containing, concealing, ingesting, inhaling,
or otherwise introducing into the human body marijuana.
Page 151 of 225
6
“Marijuana processing facility” means a facility licensed by the Board of Directors of the
Virginia Cannabis Control Authority to process, label, and package marijuana and marijuana
products; to purchase or take possession of marijuana from a marijuana cultivation facility or
another marijuana processing facility; to transfer possession of and sell marijuana and marijuana
products to retail marijuana stores or other marijuana processing facilities; to transfer possession
of marijuana and marijuana products to marijuana transporters; and to transport marijuana and
marijuana products from the marijuana processing facility's licensed premises to another licensed
marijuana establishment.
“Marijuana products” means (i) products that are composed of marijuana and other ingredients
and are intended for use or consumption, ointments, and tinctures or (ii) marijuana concentrate.
“Marijuana testing facility” means a facility licensed by the Board of Directors of the Virginia
Cannabis Control Authority to develop, research, transport, or test marijuana, marijuana
products, or other substances.
“Marijuana transporter” means a facility licensed by the Board of Directors of the Virginia
Cannabis Control Authority to take possession of marijuana, marijuana products, immature
marijuana plants, and marijuana seeds from a marijuana cultivation facility, a marijuana
processing facility, a retail marijuana store, a microbusiness, or another marijuana transporter; to
transfer possession of marijuana, marijuana products, immature marijuana plants, and marijuana
seeds to a marijuana cultivation facility, marijuana processing facility, retail marijuana store,
microbusiness, or another marijuana transporter; and to transport marijuana, marijuana products,
immature marijuana plants, and marijuana seeds from one licensed establishment to another.
“Microbusiness” means a facility licensed by the Board of Directors of the Virginia Cannabis
Control Authority to conduct any activities authorized for marijuana cultivation facilities,
marijuana processing facilities, and retail marijuana stores, as determined by the Board of
Directors of the Virginia Cannabis Control Authority.
“Processing” or “process” means the production of marijuana products or the blending, infusing,
compounding, or other preparation of marijuana or marijuana products, including marijuana
extraction or preparation by means of chemical synthesis. “Processing” or “process” does not
include cultivation or testing.
“Residence” means any building or part of a building or structure where a person resides, but
does not include any part of a building that is not actually and exclusively used as a private
residence, nor any part of a hotel or club other than a private guest room thereof.
“Retail marijuana store” means a facility licensed by the Board of Directors of the Virginia
Cannabis Control Authority to purchase or take possession of marijuana, marijuana products,
immature marijuana plants, or marijuana seeds from a marijuana cultivation facility or marijuana
processing facility; to take possession of marijuana, marijuana products, immature marijuana
plants, or marijuana seeds from a marijuana transporter; to sell marijuana, marijuana products,
marijuana paraphernalia, immature marijuana plants, or marijuana seeds to consumers on
premises approved by the Board of Directors of the Virginia Cannabis Control Authority; to
Page 152 of 225
7
deliver marijuana, marijuana products, marijuana paraphernalia, immature marijuana plants, or
marijuana seeds only in person to consumers; to transfer possession of marijuana, marijuana
products, marijuana paraphernalia, immature marijuana plants, or marijuana seeds to marijuana
delivery operators; and to transport marijuana, marijuana products, marijuana paraphernalia,
immature marijuana plants, and marijuana seeds from the retail marijuana store's licensed
premises to another retail marijuana store.
“Sale” and “sell” includes soliciting or receiving an order; keeping, offering, or exposing for
sale; peddling, exchanging, or bartering; or delivering other than gratuitously, by any means.
“Testing” or “test” means the research and analysis of marijuana, marijuana products, or other
substances for contaminants, safety, or potency. “Testing” or “test” does not include cultivation
or processing.
“Tetrahydrocannabinol” means any naturally occurring or synthetic tetrahydrocannabinol,
including its salts, isomers, and salts of isomers whenever the existence of such salts, isomers,
and salts of isomers is possible within the specific chemical designation and any preparation,
mixture, or substance containing, or mixed or infused with, any detectable amount of
tetrahydrocannabinol. For the purpose of this definition, “isomer” means the optical, position,
and geometric isomers.
“Total tetrahydrocannabinol” means the sum, after the application of any necessary conversion
factor, of the percentage by weight of tetrahydrocannabinol and the percentage by weight of
tetrahydrocannabinolic acid.
Sec. 3 – Prohibited acts in certain areas; penalties.
(a) Prohibited acts. The following acts are prohibited:
(1) In local public parks, playgrounds, public streets, or any sidewalk adjoining any
public street:
(i) Consuming marijuana or a marijuana product.
(ii) Offering marijuana or a marijuana product to another, whether accepted or
not.
(2) Possessing, consuming, or serving any marijuana or marijuana products in or
upon the grounds of any public elementary or secondary school during school
hours or student activities.
(b) Penalties.
(1) Effective upon adoption and expiring at 12:00 am on July 1, 2027:
Commented [A5]: Authority: Virginia Code § 4.1-
629(B)(1). Virginia Code section 4.1-629(B)(1)
allows localities to prohibit the acts described in
Virginia Code sections 4.1-1108 or 4.1-1109 in local
public parks, playgrounds, public streets, or any
sidewalk adjoining any public street. Please note
the awkward wording of Virginia Code 4.1-629(B)(1)
with respect to Virginia Code section 4.1-1109,
which concerns marijuana activities at schools.
The language presented here presumes that it was
not the General Assembly’s intent to disallow
localities from ordaining the school-related
language here.
Page 153 of 225
8
Any person who violates section 3(a)(1) is subject to a civil penalty of no more
than $25 for a first offense. A person who is convicted under section 3(a)(1) of a
second offense is subject to a $25 civil penalty and shall be ordered to enter a
substance abuse treatment or education program or both, if available, that in the
opinion of the court best suits the needs of the accused. A person convicted under
section 3(a)(1) of a third or subsequent offense is guilty of a Class 4
misdemeanor.
(2) Effective at 12:00 am on July 1, 2027:
Any person who violates section 3(a)(1) is subject to a civil penalty of no more
than $250 for a first offense. A person who is convicted under section 3(a)(1) of a
second offense is subject to a $250 civil penalty and shall be ordered to enter a
substance abuse treatment or education program or both, if available, that in the
opinion of the court best suits the needs of the accused. A person convicted under
section 3(a)(1) of a third or subsequent offense is guilty of a Class 4
misdemeanor.
(3) Effective upon adoption:
Any person convicted of a violation of section 3(a)(2) is guilty of a Class 2
misdemeanor.
Sec. 4 – Time of sale of marijuana and marijuana products.
(a) Prohibited times. No marijuana or marijuana products shall be sold between [INSERT
START TIME HERE] and [INSERT END TIME HERE] on [INSERT ANY DAYS OF THE
WEEK HERE].
(b) Enforcement. Any violation of this section shall be enforced as if the violation were a Class 1
misdemeanor with a right of appeal pursuant to Virginia Code section 16.1-106.
Sec. 5 – Taxation.1
1 Virginia Code section 4.1-1004 is the authority for this section, which has a few notable points. First,
Virginia Code section 4.1-1004(A) states that taxes levied thereunder “shall be in addition to any tax
imposed under the Virginia Retail Sales and Use Tax Act (§ 58.1-600 et seq.) or any other provision of . .
. local law.” Contrastingly, as is stated in this model ordinance section, Virginia Code section 4.1-
1004(B)(2) states “Other than the tax authorized and identified in this subsection, a locality shall not
impose any other tax on a sale taxable under subsection A.” Virginia Code section 4.1-1004(B)(2) further
contrasts the language in subsections A and (B)(1) by expressly stating that Virginia Code section 4.1-
1004(B)(2) does not (a) prohibit localities from imposing taxes “authorized by law on a person or
property regulated under [Virginia Code Title 4.1, Subtitle II]” and (b) limit local authority to impose
certain license or privilege taxes or fees. Given this information, the scope of the quoted language from
Virginia Code section 4.1-1004(A) is uncertain. Localities should use discretion before imposing taxes
beyond what is expressly authorized in Virginia Code section 4.1-1004.
Commented [A6]: Explanation regarding the
differences between subdivisions (1) and (2) herein:
The authority for this subsection and subsection (a)
is Virginia Code section 4.1-629(B)(1). This Virginia
Code section allows localities to “may adopt an
ordinance that prohibits the acts described in § 4.1-
1108 or the acts described in § 4.1-1109 in its local
public parks, playgrounds, public streets, or any
sidewalk adjoining any public street. A penalty may
be prescribed by the locality for a violation of such
ordinance.” (emphasis added) Virginia Code
section 4.1-629(B)(1) never specifies the amount
for the “penalty” allowed therein. However, Virginia
Code section 15.2-1429 allows “[a]ny locality [to]
prescribe fines and other punishments for
violations of ordinances, which shall be enforced
by proceedings as if such violations were
misdemeanors. However, no fine or term of
confinement for the violation of ordinances shall
exceed the penalties provided by general law for
the violation of a Class 1 misdemeanor, and such
penalties shall not exceed those penalties
prescribed by general law for like offenses.”
(emphasis added)
Commented [A7]: Authority: Virginia Code
section 4.1-630. Regulating time of sale is not
required. For counties and towns, note that this
section would only be “effective in that portion of
such county not embraced within the corporate
limits of any incorporated town . . . .” Id.
Commented [A8]: Please note that the authority
for this language, Virginia Code section 4.1-630,
states that a “right of appeal pursuant to [Virginia
Code section] 16.1-106” is applicable here.
The General Assembly’s inclusion of the above in
the underlying bill requires discernment from the
local ordinance drafter. Virginia Code section 16.1-
106 already provides for what happens when cases
are heard in district court. Interestingly, this section
(unlike section 4.1-629 that prohibits
possession/sale in certain areas which does not
define the level of penalty) requires that this be
enforced as if it were a Class 1 misdemeanor. So,
jail time must be an option for violating the hours of
operation, but localities have an option for a lower
level (say Class 3 or 4, that have a fine but no jail
time) for possession in public parks, etc.
Commented [A9]: Note: Virginia Code section
4.1-1004(B) requires that “Each locality shall,
within 30 days, notify the Authority and any retail
marijuana store and microbusiness in such locality
of the ordinance enacted pursuant to this
subsection.”
Commented [A10]: Authority: Virginia Code § 4.1-
1004.
Page 154 of 225
9
There shall be a local sales tax at a rate of of [CHOOSE NOT LESS THAN ONE BUT NOT
GREATER THAN THREE AND ONE-HALF] percent on any sale taxable under subsection A
of Virginia Code § 4.1-1004. Other than the tax authorized and identified in this section, the
[COUNTY, CITY, OR TOWN] shall not impose any other tax on a sale taxable under subsection
A of Virginia Code § 4.1-1004. Such tax shall be collected, remitted, and disposed of in the
manner provided by Virginia Code Title 4.1 Chapter 10.
Nothing in this section shall be construed to (i) prohibit the [COUNTY, CITY, OR TOWN] from
imposing any tax authorized by law on a person or property regulated under Virginia Code Title
4.1, Subtitle II or (ii) limit the authority of the [COUNTY, CITY, OR TOWN] to impose a
license or privilege tax or fee on a business engaged in whole or in part in sales taxable under
subsection A of Virginia Code § 4.1-1004 if such tax or fee is (a) based on an annual or per-
event flat fee authorized by law or (b) an annual license or privilege tax authorized by law and
such tax includes sales or receipts taxable under subsection A of Virginia Code § 4.1-1004 in its
taxable measure.
* * *
Commented [A11]: For towns and counties with
towns: Please note that Virginia Code 4.1-
1004(B)(1) states “The tax imposed by a
surrounding county under this subsection shall not
apply within the limits of any town.”
For towns: Please note that Virginia Code section
1427(G) requires that “no tax shall be imposed
except by a two-thirds vote of the council
members.”
Commented [A12]: Please note the following
language from Virginia Code section 58.1-3007,
which means that your notice must include the
“proposed increase:"
Before any local tax levy shall be increased in any
county, city, town, or district, such proposed
increase shall be published in a newspaper having
general circulation in the locality affected at least
seven days before the increased levy is made and
the citizens of the locality shall be given an
opportunity to appear before, and be heard by, the
local governing body on the subject of such
increase.
Page 155 of 225
10
Sec. 6 – Zoning.2
(a) Legislative findings. The [GOVERNING BODY] hereby finds and declares that:
(1) General findings.
The public necessity, convenience, general welfare, and good zoning practice
require that the [COUNTY, CITY, OR TOWN] amend, supplement, or change its
regulations, district boundaries, or classifications of property with respect to
marijuana establishments. Location and siting standards for marijuana
2 Virginia Code section 4.1-629 (“Local Section”) is the authority for this section except as otherwise
specified in comments. The relationship between subsections A and C of the Local Section is a matter of
ongoing debate. Some reconcile the tension between subsections A and C by arguing as follows: (1) A
locality can only exercise its zoning or business licensing authority through its implementation of
subsection B of the Local Section or other express authority grants like section 4.1-630; and (2) With
respect to any regulatory powers other than zoning or business licensing, the locality can only use its
powers insofar as it does not do something forbidden by subsection A (which expansively includes
regulating the “sale” of marijuana or marijuana products). Essentially, this interpretation narrowly
construes subsection C of the Local Section. Those adopting this interpretation would either not enact this
section of the Model Ordinance or would exercise significant caution in doing so.
Others reconcile the tension between subsections A and C of the Local Section as follows: (1) Subsection
C broadly preserves localities’ zoning, business licensing, or other regulatory powers insofar as localities
do not completely prohibit the actions described in subsect
Text truncated. Open the original for the full document.
Source: City of Charlottesville website. First collected Nov 3, 2026.