Policy Recommendation Tracker
Pursuant to City Charter § 18-5(K), the Police Accountability Board shall review and assess RPD policies, procedures, patterns and practices and recommend changes with input from the community. Additionally, PAB shall publish on its website whether or not the Rochester Police Department has implemented its policy recommendations.
The recommendations below have been approved by the Board and sent to RPD’s Chief of Police. Within 30 days of receiving the recommendations, the Chief of Police must explain whether they agree or disagree with each recommendation.
Status Definitions
Pending: The PAB sent the recommendations to the Chief of Police, and it is still within the 30-day period for response.
Delayed or no response: The PAB sent the recommendations to the Chief of Police, and the Chief of Police has not responded within the 30-day period for response.
Implemented: The PAB has verified that the RPD has implemented the recommendation.
Partially implemented: The PAB has verified that the RPD has implemented some aspects of the recommendation.
Not implemented: The PAB was unable to verify that the RPD has implemented the recommendation.
Declined: The RPD rejected the PAB’s recommendation.
In progress: The RPD indicated that it is working to implement the recommendation.
Policy Category
| Policy Subject | Policy Number | Policy Recommendation | Date RPD Notified | RPD Response | Implement Status |
|---|---|---|---|---|---|
| Cost of Misconduct | 2024-02-01 | Implement a quality assurance plan to ensure that all civil claims data in IAPro, the Professional Standards Section database, match the data in the City Law Department's database. | 2024-12-06 | Delayed or no response | |
| Cost of Misconduct | 2024-02-02 | Collect data on the outcomes of civil claims in IAPro. | 2024-12-06 | Delayed or no response | |
| Cost of Misconduct | 2024-02-03 | Commence a PSS investigation when a claim is paid out or converted to litigation within 18 months of the alleged incident. | 2024-12-06 | Delayed or no response | |
| Cost of Misconduct | 2024-02-04 | Publish an annual review of patterns of civil claims against the RPD and/or its officers from IAPro data, and include recommendations for change to relevant policies and/or training. | 2024-12-06 | Delayed or no response | |
| Cost of Misconduct | 2024-02-05 | Incorporate the outcomes of civil claims into its early intervention system. . | 2024-12-06 | Delayed or no response | |
| Protest and Mass Gathering | 2024-01-01 | Prioritize better and more robust data collection and analysis. | 2024-10-09 | 2024-11-27 | Not implemented |
| Protest and Mass Gathering | 2024-01-02 | Improve intelligence gathering and maintain clear channels of communication. | 2024-10-09 | 2024-11-27 | Not implemented |
| Protest and Mass Gathering | 2024-01-03 | Plan for and implement better inter- and intra-agency training and coordination. | 2024-10-09 | 2024-11-27 | Not implemented |
| Protest and Mass Gathering | 2024-01-04 | Maintain and implement a clear command structure that outlines responsibilities, including documentation of decisions, operational actions, and results. | 2024-10-09 | 2024-11-27 | Not implemented |
| Protest and Mass Gathering | 2024-01-05 | Update policies and general orders to make sure those existing documents comply and agree with GO 680. | 2024-10-09 | 2024-11-27 | Not implemented |
| Protest and Mass Gathering | 2024-01-05 | Work to establish clear lines of communication with community members and organizations to better facilitate understanding of policies that dictate restrictions and enforcement actions, specifically dispersal orders | 2024-10-09 | 2024-11-27 | Not implemented |
| Protest and Mass Gathering | 2024-01-06 | Stronger support for officer safety and wellness efforts through equipment, supplies, support, mental-health services, and rest. | 2024-10-09 | 2024-11-27 | Not implemented |
| Right to Know | 2023-02-01 | The PAB recommends the City of Rochester adopt a local “Right to Know” law to provide the same level of accountability as our neighboring cities. | 2023-11-27 | 2024-01-12 | Not implemented |
| Right to Know | 2023-02-02 | The PAB further recommends the City of Rochester codify the mandate to collect, as well as require the public reporting of, specific data to improve how Rochesterians measure police activity and provide them with another means of ensuring police accountability. | 2023-11-27 | 2024-01-12 | Not implemented |
| Data Transparency | 2023-01-01 | Ensure that all public datasets are current and machine readable by providing data in a format accessible with commercially available software, such as .csv. | 2023-05-19 | 2023-06-16 | Implemented |
| Data Transparency | 2023-01-02 | Include datasets on the open data portal on complaints about police misconduct, instances of officers shooting firearms, use of force, arrests, calls for service, traffic and pedestrian stops, and crime reports. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-03 | Report incident-level information for all datasets, including: location, time, demographic information, and dataset-specific elements as listed in this report. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-04 | Code all incident data and officer-related data with unique identifiers to allow users to link datasets. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-05 | Continually evaluate datasets to adhere to best practices, using the Police Data Transparency Index and examples from other agencies as guidance. | 2023-05-19 | 2023-06-16 | Not implemented |
| Data Transparency | 2023-01-06 | Maintain an up-to-date, downloadable dataset of complaints with incident-level information, including: complaint source (internal or external), location (RPD section, beat, ZIP code), time (occurrence, complaint, investigation), officer and civilian demographics, allegation category, specific allegation, investigation finding, discipline, final disposition, appeal status. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-07 | Create an up-to-date, downloadable dataset of officer firearm discharge with incident-level information, including: fatalities, justification, accidental discharge, body-worn camera footage, location (ZIP code), time, officer and civilian demographics. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-08 | Create an up-to-date, downloadable use of force dataset with incident-level information, including: data elements in the FBI’s use of force data collection program and information about an internal review of the incident. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-09 | Create an up-to-date, downloadable arrest dataset with incident-level information, including: arrest charge, use of force, use of Mental Hygiene Detention, location (ZIP code), time, officer and civilian demographics. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-10 | Create an up-to-date, downloadable call for service dataset with incident-level information, including: location (ZIP code), time (origin, dispatch, closing), officer or civilian initiated, call type, dispatch result, outcome, priority level, City of Rochester Person in Crisis Team (PIC) dispatch, Monroe County Forensic Intervention Team (FIT) dispatch. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-11 | Create an up-to-date, downloadable dataset on traffic, bicyclist, and pedestrian stops with incident-level information similar to California’s RIPA data collection program. | 2023-05-19 | 2023-06-16 | Declined |
| Data Transparency | 2023-01-12 | Publish schedules and materials for live or online trainings. | 2023-05-19 | 2023-06-16 | Not implemented |
| Data Transparency | 2023-01-13 | Maintain the existing up-to-date, downloadable crime dataset with additional incident-level information, including: location, time, demographics (officer, victim, accused), charge. | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-14 | Add a contact email for section offices on the RPD Contact Information webpage. | 2023-05-19 | 2023-06-16 | Implemented |
| Data Transparency | 2023-01-15 | Implement a version control system that tracks specific changes to rules, regulations, and orders. | 2023-05-19 | 2023-06-16 | Declined |
| Data Transparency | 2023-01-16 | Maintain historical versions of rules, regulations, and orders to allow analysis of changes over time. | 2023-05-19 | 2023-06-16 | Declined |
| Data Transparency | 2023-01-17 | Create up-to-date, downloadable budget datasets with information for each division or unit, including: personnel and associated costs, the number and associated costs of equipment (i.e., guns, TASERs, ShotSpotter, KIPs, electronic surveillance tools, drones, cars, tanks, helicopters), full contracts with external vendors. | 2023-05-19 | 2023-06-16 | Declined |
| Data Transparency | 2023-01-18 | Create an up-to-date, downloadable chase dataset with incident-level information, including: date, time, location (ZIP code), reason for pursuit, pursuit vehicle speed (police and pursued vehicle), accidents, cost of repairs, injuries (officer, bystander, subject). | 2023-05-19 | 2023-06-16 | In progress |
| Data Transparency | 2023-01-19 | Engage an outside agency to carry out regular data integrity audits, comparing a random sample of publicly available data with body-worn camera footage. | 2023-05-19 | 2023-06-16 | Not implemented |
