A department finds a useful tool, procurement moves faster than policy, and by the time residents ask questions, the contract is already signed. I've been pushing to get rules in place before the next one locks us in.
That's the normal pattern with new technology in local government, and Pflugerville isn't an exception. Surveillance systems already run on algorithmic features. Vendor software in records, code enforcement, permitting, dispatch support, and customer-service workflows increasingly ships with AI functions built in, whether a city asks for them or not.
The governance framework I've pushed for closes that gap before it gets worse. The core pieces are basic: city ownership of city data, contract terms that guarantee audit rights and deletion requirements, a tiered approval path for higher-risk technologies, and regular public reporting on what systems are in use.
This is normal governance, not a break from how the city already operates. Pflugerville shouldn't wait for a controversy around a specific contract to decide what the rules are supposed to be.
A staff lunch and learn might be useful. It isn't a substitute for policy. That's not governance. That's a lunch.
Related: see the priority on transparent government, read about Flock camera data rules, or send a question about AI governance.
I drafted and advanced a city-level governance concept built around a few practical guardrails: city ownership of city data, contract terms that guarantee audit rights and deletion requirements, a tiered approval path for higher-risk technologies, and regular public reporting on what systems are in use. I tied it to real local examples, including surveillance technology and vendor systems that increasingly add AI features without disclosure. The work session discussion didn't go as far as it should have. I'm keeping the issue alive because the gap didn't go away when the meeting ended.
Reach out directly or keep reading the council updates for the bigger picture.