Delayed Access Models: Alternatives to Full Police Radio Encryption
Police departments often frame the choice as "encrypt everything or nothing." It isn't. Compare the real options and figure out what to push for in your community.
When police departments say they "must" encrypt, they usually mean it's the easiest path — not the only one. Communities in California, Colorado, and New York have already found workable middle ground that addresses legitimate safety concerns without cutting the public off entirely.
The goal isn't to broadcast sensitive tactical operations in real time. It's to keep routine dispatch open, maintain accountability for police actions, and preserve access for journalism. Several proven models do exactly that.
Access models compared
Real-world examples
NYC Local Law 46
Best PracticeModel: Real-time media access + public critical incident channel
How it works: Credentialed journalists receive real-time access to NYPD radio. Critical incidents are broadcast on an unencrypted public channel.
Key feature: First major U.S. city to mandate press access by law.
Read the full case studySeattle / Denver
Good ModelModel: Partial encryption (dispatch open, tactical encrypted)
How it works: Main dispatch channels remain publicly accessible. SWAT, undercover, and sensitive operations use encrypted tactical channels.
Key feature: Balances routine transparency with tactical security.
Learn about Seattle's approachSan Francisco Media Access
Good ModelModel: Voluntary media access program
How it works: SFPD provides credentialed journalists access to encrypted radio communications through a voluntary program.
Key feature: Preserves press ability to cover breaking news despite encryption.
Read about SF's programBerkeley Call Log
InadequateModel: 10-minute delayed call log (no radio access)
How it works: Web-based log shows call types, times, and block addresses with 10-minute delay. No officer communications included.
Key limitation: Provides fraction of information available from radio access.
Why this isn't enoughWhat to push for
When your community considers encryption, fight for these alternatives in order of priority:
Keep dispatch open
Main dispatch is the channel that matters most for accountability. Calls for service go there; that's where you can hear how police respond to the public. Push for partial encryption that leaves dispatch unencrypted.
Require media access
If full encryption goes forward, demand a media access program. NYC's Local Law 46 is the legislative model to cite. At minimum, credentialed journalists should get real-time access.
Push for a delayed public feed
If media access isn't on the table, advocate for a 15-30 minute delayed feed. It addresses officer safety concerns while keeping the historical record intact.
Don't accept call logs as adequate
Call logs are not a substitute for radio access. If that's what's offered, document what you're losing and keep pushing for real access.
Countering the common objections
"We need full encryption for officer safety"
Response: Partial encryption handles this. Keep dispatch open and encrypt tactical channels used for sensitive operations. Seattle and Denver have done it for years.
"Media access is too complicated"
Response: NYC made it mandatory. San Francisco runs a voluntary program. The technology works and other cities have already figured it out.
"Delayed feeds are too expensive"
Response: The same system that encrypts the radio can delay a feed. It's a configuration setting, not a budget line item.
"Our call log provides adequate information"
Response: Call logs don't include officer communications, scene updates, calls for backup, or any real-time developments. They contain a fraction of what radio access provides.
Implementation checklist
If your department agrees to an alternative model, make sure the agreement covers these:
Clear criteria
Define exactly which channels stay open and which get encrypted, or what delay applies and to what traffic.
Written policy
Get the agreement in writing. Local law or formal policy is better than a verbal promise from the current chief.
Public comment period
The public should be able to review and comment on implementation details before they're locked in.
Regular review
Build in periodic reviews so the program can't quietly expand encryption without anyone noticing.
Enforcement mechanism
What happens if the department violates the agreement? Accountability has to be built in, not assumed.
Full encryption is not the only option
Every community has alternatives. Use these models to push back and keep some level of transparency intact.