Valdosta council approves sanitation tracking software amid sharp resident complaints about rollout and billing
Get AI-powered insights, summaries, and transcripts
SubscribeSummary
The Valdosta City Council approved a cooperative‑purchase sanitation tracking software and cloud service to monitor routes and container collections, while residents urged the council to address communication gaps and unexpected fees tied to a recent sanitation policy change.
Valdosta City Council voted to approve a sanitation tracking software provider after a presentation by Public Works Director Larry Ogden detailing system capabilities, hardware costs and expected operational benefits.
Ogden told the council the project grew from an August audit that showed about 40% of households had additional 96‑gallon cans and that some accounts were keyed incorrectly into the billing system. He said the city had already installed cameras and tablets on trucks and that the software would allow dispatchers to verify stops, see route breadcrumbs and email photographic proof to residents who report a missed pickup. Ogden summarized costs: hardware budgeted at $10,366 with final hardware about $10,951; installation budgeted $23,000, actual installation $15,000; and an annual subscription that came in at about $67,156, slightly under the budgeted $67,200.
On the procurement process, Ogden said the vendor (referenced in the presentation by multiple spellings in the transcript) is a Sourcewell member, which allowed staff to use the cooperative contract rather than run a lengthier RFP; the purchasing officer verified the Sourcewell status and recommended proceeding.
During council questions, members asked whether the existing truck cameras would integrate with the new software (Ogden: "Yes"), whether the system had an SOS or automatic injury alert (Ogden: it can flag stopped vehicles or low speed but does not automatically detect an injured employee), and how long images would be retained in the cloud (Ogden: asked to follow up; answer not provided at the meeting).
An unidentified councilmember moved to approve the software as presented; a second was recorded and the motion passed by show of hands. The motion and vote were taken by voice/show‑of‑hands; no roll‑call tally was recorded in the transcript.
Residents who addressed the council during the public‑comment period raised sharp concerns tied to a separate sanitation policy change that now limits collection to city‑issued 96‑gallon rollout containers. Speakers described minimal advance notice, unexpected added monthly fees for multiple households, and missed pickups in neighborhoods. ‘‘A Facebook post is completely unacceptable,’’ a resident said, criticizing the city’s outreach. Several residents said they were on fixed incomes and that the timing—immediately after the holidays—created particular strain.
Council members acknowledged the communication breakdown and said staff is working on solutions. One councilmember announced an extension of the enforcement/transition window to March 1 to give residents more time to obtain or register additional containers. The council also discussed how to handle residents who purchased third‑party cans earlier per city guidance, and councilmembers asked staff to return with options.
The city did not provide, during the meeting, a final policy on image retention, an explicit privacy policy tied to the camera footage, or a detailed plan for reimbursing residents who purchased noncity cans; staff committed to follow up on those points.
The most immediate next step recorded in the meeting was implementation of the software under the cooperative contract and additional staff follow‑up on data‑retention and communication plans for residents.
