Emergency Communications Accountability & Justice Panel: How We Document, Verify, and Publish Failures That Harm Public Safety

Emergency Communications Accountability & Justice Panel: How We Document, Verify, and Publish Failures That Harm Public Safety

Emergency Communications Accountability & Justice Panel: How We Document, Verify, and Publish Failures That Harm Public Safety

Emergency moments are supposed to be met with urgency, care, and clarity. Yet in communities across the country, people report patterns of emergency call failures—crimes in progress not properly documented, dismissive or blaming call handling, delays or misrouting that cost time, and after-the-fact shifting of responsibility that leaves victims without answers and investigators without records.

The Emergency Communications Accountability & Justice Panel is a community inquiry and reporting project designed to document those failures and push for changes that improve public safety. This work is focused on what happens during emergency communication—and what gets recorded, or doesn’t get recorded—when people need help most.

What the Panel is

The Panel is a community-driven reporting initiative operated through Rochester Sun Times News (our newsroom). It documents and publishes failures in emergency communications, especially:

  • refused or inadequate documentation of a crime in progress
  • dismissive or blaming statements during call handling
  • delays, misrouting, or communication breakdowns that impact safety
  • after-the-fact responses that shift blame (“you should have called differently”)
  • repeated failures and systemic issues that appear across multiple incidents

We also may pursue related reporting that helps explain how these failures affect victims and investigations.

What we review

We focus on emergency call handling and communication documentation. That includes allegations such as:

  • crimes in progress not documented (or documented incompletely)
  • call handlers using dismissive, blaming, or minimizing language
  • failures in routing, transfers, or response coordination that increase risk
  • later statements claiming the caller did the wrong thing, rather than addressing the communication failure
  • patterns of repeated problems involving particular offices, units, or processes

The goal isn’t to speculate. The goal is to identify verifiable breakdowns, describe what happened in plain language, and recommend changes that reduce harm going forward.

Complaints and tips: how submissions work

We invite the community to submit two types of information: complaints and tips. Each serves a different role in our review process.

Complaints (for review and potential publication)

If you’re submitting a complaint, include the incident details as accurately as possible. Where you can, please share:

  • date and time (as accurately as you can)
  • location
  • who you spoke with (if known)
  • what was said (include exact phrases if possible)
  • what documentation or evidence exists, such as:
    • call logs
    • incident numbers
    • recordings
    • screenshots
    • emails/texts
    • photos you’re able to share

The more specific you can be, the easier it is for our team to verify and evaluate what to publish.

Tips (for investigative reporting)

Tips help us see patterns. If you’ve observed recurring issues, share information about what you’ve noticed, including:

  • patterns across multiple calls or incidents
  • names of offices/units involved (if known)
  • proof you can provide, or an explanation of how the pattern shows up

We may follow up for additional details when possible.

Anonymous submissions

You may submit anonymously.

However, there’s an important practical limitation: if we can’t verify key details or cannot follow up, anonymous submissions may limit what we can publish. Even so, we still may use information from anonymous submissions in ways that support broader reporting and redacted findings.

What happens after you submit

Once you send a submission, it goes through a structured workflow:

  1. Receipt & triage
    We review your submission for completeness and scope.

  2. Verification
    We check supporting details using available records and reporting methods when possible.

  3. Publication decisions
    If we can verify key facts, we may publish a story, or publish redacted findings that reflect what we can support.

  4. Redaction & privacy
    We remove identifying details when needed to protect privacy and reduce harm. Even when we can’t identify individuals, we may publish redacted summaries based on what we can verify.

Independence and editorial accountability

This community inquiry and reporting is operated independently by Rochester Sun Times News. It is not a government agency and is not operating under any city, county, or state contract or appointment.

Any review, verification, and investigation we conduct is part of our own investigative work. Our files and research remain private unless otherwise stated.

Clear boundaries: no legal advice, not an official complaint process

This project is focused on documentation and investigative reporting—not legal representation.

  • Nothing on this site or in any submission process is legal advice.
    We do not provide legal representation or legal counsel.

  • Submitting information to us does not create an official complaint process.
    It also does not replace contacting emergency services or filing complaints through official channels.

Submissions may be used—and materials may not be returned

By submitting, you understand that your information may be used for verification and reporting purposes.

We do not promise to return original materials or provide copies of internal notes, evidence files, drafts, or research.

How to contact us

If you’d like to submit a complaint or tip, use the contact form on our page and include the incident details (or the pattern you’ve observed) in the comment field.

Your information can help reveal where emergency communication systems fail—and where accountability and improvements are most urgently needed.

Back to blog