seventeenth-quarterly-report.pdf
Figures extracted from this document
Extracted text
Seventeenth Quarterly Report of the Independent Monitor
for the Oakland Police Department
April 28, 2014
Page 54
Task 34.1 requires that officers complete Stop Data Forms for every vehicle stop, field
investigation, and detention (compliance standard: 90%). To assess Task 34.1 compliance
during this reporting period, we reviewed a random sample of 375 stops to match them with
corresponding completed Stop Data Forms. This sample included 125 Computer Aided Dispatch
(CAD) entries, 125 Field Contact Cards, and 125 traffic citations. Using the Department’s
Forensic Logic Quicksearch program, we located corresponding Stop Data Forms for 99% of the
stops in our sample. OPD is in compliance with Task 34.1.
Task 34.2 requires that completed Stop Data Forms contain the following information: 1) time;
2) date; 3) location; 4) identification of member making stop; 5) reason for stop; 6) apparent
race/ethnicity of individual(s) stopped; 7) gender of individual(s) stopped; 8) outcome of stop
(arrest or no arrest); 9) whether a search was conducted; 10) outcome of any search; and 11)
offense category (felony, misdemeanor, or infraction) (compliance standard: 85%). The entry of
stop data into the Field Based Reporting (FBR) system requires officers to make a selection in
each form field. If an officer fails to fill in the information in any field, the system does not
allow the form to be completed.
During this reporting period, OIG conducted internal audits of its stop data forms. We
encourage OPD to continue to conduct these audits in future reporting periods. We saw an
improvement with OPD documenting the reason for the stop – and as such, OPD is in
compliance with Task 34.2.
Task 34.3.1 requires that OPD have a stop data database that can be summarized, searched,
queried, and reported by personnel authorized by OPD (compliance standard: Yes/No). Special
Order 9042 requires that officers “complete an electronic FBR [Field Based Reporting] Stop
Data Collection Form (SDF) for certain arrests, every detention not resulting in an arrest
(vehicle, walking, and bicycle stops), every consent search of a person conducted and any other
investigative encounter. A SDF shall also be completed for consensual encounters (contacts)
where the member talks with a person to confirm or dispel a suspicion that the person may be
involved in criminal activity, although the person is free to leave.” Data from the electronic
Field Based Reporting system is automatically sent to the Department’s Forensic Logic
Quicksearch program. Quicksearch allows Department personnel to search for and query
officers’ stop data. During this reporting period, we continued to experiment with the
Quicksearch program, and found that the stop data is summarized and easy to review. As noted
above, in May 2011, OPD merged the Stop Data Form with the Field Contact Card, intending to
provide one document for officers to enter stop data; and providing them with a narrative portion
for which they can articulate the factual support for the stop.
During our most recent site visit, we again met with OPD personnel responsible for data
collection and analysis. We found that the Department’s revisions to policies and additional
training have resulted in the collection of what appears to be accurate data since April 2013. The
data is being organized into tables and graphs depicting – both globally and by district – the
breakdown of stops, reasons for the stops and resulting action taken, including searches, the
results of searches and arrests and other actions. Although the data is sufficient to conduct
Case3:00-cv-04599-TEH Document979 Filed04/28/14 Page55 of 88