Clayton City Council — July 17: E-bike safety rules and Flock camera privacy dominate Friday discussion session

The council's informal session tackled electric bicycle regulation and the city's Flock license-plate-reader contract, with no votes taken and no public comment period.

audio-thumbnail
Listen: Clayton City Council — July 17: E-bike safety rules and Flock camera privacy dominate Friday discussion session
0:00
/305.35

What happened

The Clayton City Council held a Friday afternoon discussion session on July 17, 2026, taking up two topics: a police department briefing on electric bicycle safety and the city's existing ordinances, and a lengthy question-and-answer session with a representative from Flock Safety, the vendor that supplies Clayton's automated license-plate-reader cameras. Because the session was a discussion forum rather than a regular meeting, no votes were taken and no public comment period was held.

What the council decided

No formal votes were taken. The session produced two staff directions:

  • Council members asked staff and the police department to draft e-bike ordinance concepts — covering potential restrictions on sidewalk use, age limits, and helmet requirements — for the full council to consider at a future regular meeting.
  • On Flock cameras, council members indicated that continuing or ending the Flock relationship is a policy decision any member could bring to a regular meeting as a legislative matter.

Who was there

The mayor opened the session and multiple council members participated, including at least one joining online, as the transcript reflects. A Flock Safety vendor representative and the city's police chief also attended and presented. Because this was a discussion session rather than a regular meeting, no formal roll call appears in the available record.

This post is for paying subscribers only

Already have an account? Sign in.

Subscribe to Clayton Ledger

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe