Three minutes at a podium can feel impossibly short and strangely endless at the same time. Whether you’re addressing a city council, a police oversight board, or a county commission about automated license plate readers (ALPRs), the key to effective public comment isn’t eloquence — it’s preparation. Here’s how to make every second count.
Know the Format Before You Speak
Most public bodies follow a predictable pattern: you sign up in advance or on a sheet at the door, wait for the public comment period, and speak for a strictly enforced time limit, often signaled by a light, clock, or bell. Comments typically become part of the public record. Arrive early, read the meeting agenda, and confirm the exact rules — some bodies require written comments submitted in advance, others allow comment only on agenda items.
Do Your Homework First
Before writing a word, learn what’s actually being proposed or already installed in your community. DeFlock’s community-sourced map can help you confirm whether ALPR cameras already exist nearby. If a formal policy or contract is on the agenda, request a copy ahead of time — vendor names, data retention periods, and sharing agreements are usually public record. Speaking with specifics, not assumptions, gives your comment credibility.
Build a Simple Three-Part Structure
A tight structure keeps you on time and on message:
Opening (15–20 seconds): State your name, that you’re a resident, and why you’re speaking today.
Middle (2 minutes): Present your strongest argument, backed by one or two concrete points — cost, data retention, third-party sharing, or lack of evidence that the cameras reduce crime.
Close (20–30 seconds): Make a specific, actionable request — a moratorium, a public audit, a retention limit, or simply more time before a vote.
Pick One Argument, Not Ten
New speakers often try to cram every concern about surveillance into three minutes. Resist this. Choose the one or two points most relevant to the decision at hand and develop them clearly. A single well-explained concern lands harder than a list of ten rushed ones. If you want a refresher on the core issues, DeFlock’s learn section covers how ALPR systems work, who operates them, and what typically goes wrong with oversight.
Write It, Time It, Trim It
Most people speak at roughly 130–150 words per minute when reading prepared remarks, so three minutes is about 400–450 words. Write a full script, read it aloud with a timer, and cut anything that isn’t essential. Short sentences read better under pressure than long ones. Print your final version in large, easy-to-read type, and bring an extra copy to hand to the clerk for the record.
What to Leave Out
Avoid technical jargon your audience may not share, personal attacks on officials, or repeating points already made by earlier speakers — instead, say “I want to echo the previous speaker’s concern about data sharing” and move to your own point. Rambling or reading unprepared thoughts almost always eats your limited time without adding persuasive weight.
Deliver With Confidence
Practice out loud, ideally in front of another person, until the words feel natural rather than memorized. Speak slower than feels comfortable — nerves speed people up. Make eye contact with the board when possible, and don’t apologize for taking up their time; public comment exists precisely for this purpose.
After the Meeting
One comment rarely changes a vote by itself, but a pattern of informed public comment often does. Connect with neighbors who share your concerns, and consider organizing through a local DeFlock chapter to coordinate future turnout. If you’re ready to do more between meetings, DeFlock’s take action page offers concrete next steps, from public records requests to model policy language you can bring to your own officials.
Three minutes is short. Prepared, specific, and calm, it can still be enough.
Watch — on our site:
▶Watch on DeFlockLoudon Paused Flock. A Pause Is Not a BAN, GTFOHGTFOH Loudon County
Independent, ad-free, reader-funded
No ads, no paywalls, no selling your data. The costs are server bills, the data services behind the map, the Docket and the archives, and the computing power behind the tools being built on top of them. Every dollar readers chip in goes to exactly that.
Support us on PayPal or scan the code, or Venmo @deflocktheusa