OpenPublica

Accountability starts with access.

© 2026 · Filed for the public record

Use casesAboutAPIPrivacyTermsLinkedIn
Home/Richmond, Virginia/City Council
OPENPUBLICA · PUBLIC MEETING RECORD
Record of Proceedings

Finance and Economic Development Standing Committee Meeting - September 16, 2026

City Council — Wednesday, September 16, 2026
BodyRichmond, Virginia
SessionCity Council
DateWednesday, September 16, 2026
StatusFILED
Video Record
0:00 / 54:43

Original source
Transcript — VerbatimClick a timed line to jump · ⧉ to share it
0:00

To call to order the finance and economic development standing committee meeting this time.

0:06

Um Adam Claire take care of chamber emergency evacuation.

0:16

Upon activation of the emergency alarm signal, all persons should immediately exit the building.

0:21

Please use the exits to the left or right front of the council chamber or the north or west stairwells outside of the rear doors of the chamber.

0:29

Do not use elevators or escalators.

0:31

At the exit in the building, security would direct everyone down Knife Street to the fenced area located between Clay and Lee Streets.

0:38

Able persons should assist visually and hearing a pair of visitors with exiting the building.

0:42

Persons wishing to speak during the public comment period andor public hearings are journey allowed three minutes to speak.

0:48

Persons appearing before the committee are not allowed to campaign for public office, promote private business ventures, use language of a personal nature which installs or demeans any person, including comments directed at public officials or staff members that are not related to the official duties or just the question staff members directly.

1:04

All questions are to be directed to the committee chair.

1:07

Fayette here to the gun lines may result in speakers forfeiting any remaining time and further disciplinary action as necessary, which can include bar from attendance at future meetings of the committee for a period of six months.

1:18

Madam Chair concludes announcements.

1:21

Thank you, Madam Clerk.

1:24

We will proceed with the public comment period for those that are here that would like to address the committee on items that are not on the docket.

1:35

Is anyone that would like to provide comment or anything not on today's agenda?

1:40

Seeing none, the public comment period is now closed.

1:43

Thank you, Madam Clerk.

1:45

Minutes for approval.

1:47

The minutes to be approved from the July 15th, 2026 finance economic development standing committee meeting.

1:54

If there are no amendments of corrections, then those meeting minutes stand approved as presented.

1:57

Those minutes have been approved.

1:59

Thank you, Madam Clerk.

2:00

We will proceed with the docket as it is presented.

2:06

Item one, ordinance 2026 081 to amend city code concerned publication of the city's payment register for the purpose of promoting transparency and accountability in the expenditure of public funds by providing public access to information regarding payments made by the city to vendors for goods and services and reimbursement to employees while protecting confidential and personal information as required by law that papers before the committee.

3:04

Today I'm here to reiterate the administration's commitment to provide maximum proactive transparency to the public, especially with our money, while honoring legitimate privacy concerns and following privacy laws better addressed through the FOIA process.

3:19

We learned a lot through the process of producing the fiscal year 25 payment register, as I've previously shared at the last committee meeting, which has informed our proposed amendments to our ordinance.

3:30

We also adjusted our proposal based on the committee's questions and guidance back in June.

3:36

So I have provided a new chart for your review since the comparative chart provided before the amendments were actually introduced, which was in your briefing, are actually no longer accurate.

3:47

So based off of the careful work we've done, we now have a better understanding of what it takes to prepare this payment register.

3:54

Um and it's based off of our own financial records, the actual realities of the systems that we have, which fields of data are standardized, which are not, and who within the organization has access to which pieces of data.

4:08

And really, we, as you can see from the amended chart, are only removing a few pieces of information based on that information.

4:16

So our proposed amendments to the current ordinance first change the scope to vendor payments and employee reimbursements based on the high volume of privacy laws governing the other payments to individuals.

4:28

We must protect personal information and ensure legal compliance, and we can do this based on a more automated, predictable process, not by relying on time-consuming manual redactions with the risk of human error.

4:42

Again, I want to note that the individual payment information still does remain available, but we strongly recommend against mandating proactive disclosure through city code because of the increased risk of sharing someone's protected private information.

5:00

We are proposing to remove invoice description and add account description.

5:03

Invoice description is a free form text field that staff write into on their own.

5:08

Through the process of producing the fiscal year 25 register, we learned that the invoice description field was actually mostly left blank.

5:16

The instances that were not blank many times required manual review and had to be redacted for the reasons already discussed.

5:24

So instead, cost center, which was already there, and account description, which we're adding in, are more helpful for understanding what was purchased because you can tie to the budget with cost center, and you read a description of a particular payment from the account description, things like office supplies and stationary uniforms and safety supplies, et cetera.

5:46

We are removing fund code and keeping fund description because the fund code does not match any other information that the general public has access to.

5:57

It's really just four digits that are used internally.

6:01

And so we don't think that it adds information and does actually or doesn't add meaningful information, but does add the risk of things like AI being able to mimic payments and so on and so forth.

6:15

Payment document used is a field that does not actually exist in the original data that we find in the ordinance, the original ordinance.

6:24

And so we believe it is intended to satisfy the same information we're disclosing in type of disbursement.

6:32

So the this was the one that previously at the committee we talked about payment document.

6:37

We actually don't know exactly what was intended in the original ordinance, but we believe the intent of payment document was just to know is it a check, is it a wire transfer, et cetera?

6:49

So we are keeping in that information in type of disbursement.

6:53

And then we also adjusted the timeline for publication to be more specific, addressing a maximum of 60 days after close of the month's payments.

7:02

So I'm gonna steal a line from Vice Chair Jones, and I'm gonna say it with my chest and say this is our best and final proposal, which from our perspective is only making a few adjustments to the information proactively shared with significant benefit of protecting individual privacy and deploying the city's resources proportionately for public benefit.

7:30

Thank you, Miss Lawson.

7:32

Any questions, Ms.

7:33

Jones, before we move to public?

7:35

I do have one.

7:36

Is there an imp is there a um have you all prepared an implementation plan for this?

7:45

So yes, our because we just went through this process based on the old one, we feel very equipped to know what we'll need to do.

7:54

Of course, the SOPs will need to be written if this these proposed changes are accepted.

8:00

So we have not pre-written those out because we need to know what what we will be doing, um, but we feel very prepared to do so within the timeline that has been laid out.

8:13

What is the timeline?

8:16

So the implementation timeline, do you have a start date?

8:23

So the yeah, so the ordinance calls for the implementation period being 90 days, and we think we'll be well inside of that.

Discussion Breakdown — Share of Meeting
Public Finance██████████████████████22%
Transparency and Oversight████████████████████20%
Procedural█████████████13%
Technology and Innovation█████████████13%
Youth Programs███████7%
Sustainability██████6%
Historic Preservation████4%
Social Services████4%
Homelessness████4%
Summary of Proceedings

Finance and Economic Development Standing Committee Meeting - September 16, 2026

The Finance and Economic Development Standing Committee met on September 16, 2026, to consider 13 legislative items and one discussion item related to the city's fiscal operations, transparency, and community investments. The committee approved most items, forwarded one to council without recommendation, and received updates on ARPA fund expenditure and future presentations.

Public Comments & Testimony

  • Alfonso Goncello (6th District) spoke in opposition to Item 1 (Ordinance 2026-081), arguing that before changing the payment register law, the council should investigate why the city failed to comply with the current law. He noted that 1,080 staff hours (including 433 hours of temporary staff) were spent producing the Fiscal Year 2025 register and contended that transparency saves taxpayer money in the long run, contrary to claims of high cost.

Discussion Items

  • Item 1 – Ordinance 2026-081 (Payment Register Amendments): Ms. Lawson (Administration) presented proposed amendments to the city code on the payment register, citing lessons from producing the Fiscal Year 2025 register. Changes include removing invoice descriptions (often left blank or requiring redaction), adding account descriptions, removing fund code (non-public codes), clarifying payment document as type of disbursement, and setting a 60-day publication timeline after month-end. She described this as the administration's "best and final proposal" to balance transparency with privacy and resource efficiency. Vice Chair Jones asked about an implementation plan; Ms. Lawson said standard operating procedures would be written after adoption, with a 90-day implementation period expected to be met. Councilmember Gibson expressed strong opposition, arguing that reducing public financial information harms public trust and the council's ability to oversee spending, especially given high community needs (schools, living wages, infrastructure). She urged the body not to approve the paper.
  • Item 2 – Ordinance 2026-192 (Pump House Roof Replacement): Chris Frelkey, Director of Parks, Recreation and Community Facilities, noted this $500,000 from Historic Richmond Foundation serves as a match for federal funds already received. With additional capital funds from the James River Park System infrastructure budget, the city believes it has sufficient funding for Phase 1 of the roof replacement.
  • Item 3 – Ordinance 2026-193 (Neighborhood Climate Resilience Grants): Laura Thomas, Director of Sustainability, explained this is the third annual cohort of the neighborhood resilience grant program, distributing $150,000 to eight organizations across every district. At Councilmember Jones's request, she agreed to provide a list of approved projects and district distributions after the meeting.
  • Item 4 – Ordinance 2026-194 (East End and Evergreen Cemetery License Agreement): Chris Frelkey highlighted this as a major milestone, fulfilling the community's third priority (after land transfer and cultural landscape study) by formalizing the partnership with Friends of East End Cemetery for maintenance and restoration.
  • Item 5 – Ordinance 2026-195 (Ernst & Young Donation): Kevin J. Vonk, Director of Planning and Development Review, stated that EY is donating services valued at $268,209.20 for a voice-of-customer survey and an AI proof-of-concept for certificate of occupancy processes. The donation was initiated by EY's approach to the mayor. Councilmember Jones asked about the high value; Vonk explained it includes senior-level principals and extensive data analysis, with a not-to-exceed ceiling.
  • Item 6 – Ordinance 2026-196 (Real Estate Tax Rate of $1.16 for 2028): Councilmember Jones moved to forward the ordinance to full council with no recommendation, noting it is a significant policy decision needing full council debate. Councilmember Gibson expressed concern about lack of data, questioning mixed signals from earlier statements about tax rate decreases and sales tax referendums. R.J. Warren, Council Chief of Staff, informed the committee that a budget work session for FY28 is planned for October, where the administration will present revenue projections and data.
  • Items 7 & 8 – Ordinances 2026-202 and 2026-205 (Youth Climate Action Fund): Laura Thomas reported that the city received a $50,000 Bloomberg Philanthropies Youth Climate Action Fund award to provide microgrants ($1,000–$5,000 each) to youth ages 15–24. Applications close November 6, with an estimated 8–45 projects funded. Next Up RVA, an out-of-school time nonprofit, will serve as fiscal agent. Councilmember Jones expressed hope for collaboration with schools and higher education.
  • Item 9 – Ordinance 2026-203 (Family Crisis Fund): Staff reported that $100,000 appropriated in the FY27 budget for the Family Crisis Fund will be transferred to ACT (Area Congregations Together in Service), selected through a competitive NOFA process. Transition from the current provider is targeted for the week of October 13.
  • Item 10 – Ordinance 2026-204 (CARITAS Surge Shelter and Warming Center): Staff provided detailed statistics: during FY2026, the surge shelter activated 87 of 121 possible nights (72% likelihood), a 290% increase over the originally contracted 30 nights; 4,877 service instances were delivered, serving 671 unique individuals. The FY27 contract expands to 70 beds for up to 90 days, plus overnight warming centers for up to 20 nights (max 60 individuals). Activation triggers are temperature below 40°F for 2+ hours and IWS at 85% capacity. Councilmember Jones questioned how the budget accounts for weather variability; staff explained the protocol and noted adjustments based on prior year demand.
  • Item 11 – Ordinance 2026-206 (IT Contracts): Staff explained the amendment allows the city to push back on vendor requests for governance under other states' laws, providing negotiating leverage.
  • Items 12 & 13 – Ordinances 2026-276 and 2026-277 (Medication-Assisted Treatment Pilot Program): Anna Jones, Opioid Response Strategist, noted the program has served 176 individuals to date, and that overdose risk increases 40 times upon release from incarceration. The third year of funding transfers $400,000 from the Opioid Settlement Special Fund to the Sheriff's Office for medications and discharge planning. Councilmember Jones asked about monitoring implementation; staff described monthly reports, quarterly meetings, and participation in the Richmond Opioid Task Force.
  • Discussion Item – ARPA Fund Update: Megan Quinn, Senior Manager of Grants, reported that the city was awarded $154 million in ARPA funds, with 94% expended as of the latest report. All funds must be expended by December 31, 2026. A final report on remaining balances will be provided to Treasury by October 31.

Key Outcomes

  • Item 1 (Ordinance 2026-081): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 2 (Ordinance 2026-192): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 3 (Ordinance 2026-193): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 4 (Ordinance 2026-194): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 5 (Ordinance 2026-195): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 6 (Ordinance 2026-196): Motion to forward to council with no recommendation passed (2-0).
  • Items 7 & 8 (Ordinances 2026-202 & 2026-205): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 9 (Ordinance 2026-203): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 10 (Ordinance 2026-204): Motion to forward to council with recommendation to approve passed (2-0).
  • Item 11 (Ordinance 2026-206): Motion to forward to council with recommendation to approve passed (2-0).
  • Items 12 & 13 (Ordinances 2026-276 & 2026-277): Motion to forward to council with recommendation to approve passed (2-0).
  • Future Presentations: The committee noted that a disparity study update from the Office of Minority Business Development is scheduled for the next committee meeting.

Meeting Transcript

To call to order the finance and economic development standing committee meeting this time. Um Adam Claire take care of chamber emergency evacuation. Upon activation of the emergency alarm signal, all persons should immediately exit the building. Please use the exits to the left or right front of the council chamber or the north or west stairwells outside of the rear doors of the chamber. Do not use elevators or escalators. At the exit in the building, security would direct everyone down Knife Street to the fenced area located between Clay and Lee Streets. Able persons should assist visually and hearing a pair of visitors with exiting the building. Persons wishing to speak during the public comment period andor public hearings are journey allowed three minutes to speak. Persons appearing before the committee are not allowed to campaign for public office, promote private business ventures, use language of a personal nature which installs or demeans any person, including comments directed at public officials or staff members that are not related to the official duties or just the question staff members directly. All questions are to be directed to the committee chair. Fayette here to the gun lines may result in speakers forfeiting any remaining time and further disciplinary action as necessary, which can include bar from attendance at future meetings of the committee for a period of six months. Madam Chair concludes announcements. Thank you, Madam Clerk. We will proceed with the public comment period for those that are here that would like to address the committee on items that are not on the docket. Is anyone that would like to provide comment or anything not on today's agenda? Seeing none, the public comment period is now closed. Thank you, Madam Clerk. Minutes for approval. The minutes to be approved from the July 15th, 2026 finance economic development standing committee meeting. If there are no amendments of corrections, then those meeting minutes stand approved as presented. Those minutes have been approved. Thank you, Madam Clerk. We will proceed with the docket as it is presented. Item one, ordinance 2026 081 to amend city code concerned publication of the city's payment register for the purpose of promoting transparency and accountability in the expenditure of public funds by providing public access to information regarding payments made by the city to vendors for goods and services and reimbursement to employees while protecting confidential and personal information as required by law that papers before the committee. Today I'm here to reiterate the administration's commitment to provide maximum proactive transparency to the public, especially with our money, while honoring legitimate privacy concerns and following privacy laws better addressed through the FOIA process. We learned a lot through the process of producing the fiscal year 25 payment register, as I've previously shared at the last committee meeting, which has informed our proposed amendments to our ordinance. We also adjusted our proposal based on the committee's questions and guidance back in June. So I have provided a new chart for your review since the comparative chart provided before the amendments were actually introduced, which was in your briefing, are actually no longer accurate. So based off of the careful work we've done, we now have a better understanding of what it takes to prepare this payment register. Um and it's based off of our own financial records, the actual realities of the systems that we have, which fields of data are standardized, which are not, and who within the organization has access to which pieces of data. And really, we, as you can see from the amended chart, are only removing a few pieces of information based on that information. So our proposed amendments to the current ordinance first change the scope to vendor payments and employee reimbursements based on the high volume of privacy laws governing the other payments to individuals. We must protect personal information and ensure legal compliance, and we can do this based on a more automated, predictable process, not by relying on time-consuming manual redactions with the risk of human error. Again, I want to note that the individual payment information still does remain available, but we strongly recommend against mandating proactive disclosure through city code because of the increased risk of sharing someone's protected private information. We are proposing to remove invoice description and add account description. Invoice description is a free form text field that staff write into on their own. Through the process of producing the fiscal year 25 register, we learned that the invoice description field was actually mostly left blank. The instances that were not blank many times required manual review and had to be redacted for the reasons already discussed. So instead, cost center, which was already there, and account description, which we're adding in, are more helpful for understanding what was purchased because you can tie to the budget with cost center, and you read a description of a particular payment from the account description, things like office supplies and stationary uniforms and safety supplies, et cetera. We are removing fund code and keeping fund description because the fund code does not match any other information that the general public has access to. It's really just four digits that are used internally. And so we don't think that it adds information and does actually or doesn't add meaningful information, but does add the risk of things like AI being able to mimic payments and so on and so forth. Payment document used is a field that does not actually exist in the original data that we find in the ordinance, the original ordinance. And so we believe it is intended to satisfy the same information we're disclosing in type of disbursement. So the this was the one that previously at the committee we talked about payment document. We actually don't know exactly what was intended in the original ordinance, but we believe the intent of payment document was just to know is it a check, is it a wire transfer, et cetera? So we are keeping in that information in type of disbursement. And then we also adjusted the timeline for publication to be more specific, addressing a maximum of 60 days after close of the month's payments. So I'm gonna steal a line from Vice Chair Jones, and I'm gonna say it with my chest and say this is our best and final proposal, which from our perspective is only making a few adjustments to the information proactively shared with significant benefit of protecting individual privacy and deploying the city's resources proportionately for public benefit. Thank you, Miss Lawson.

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com