68,465 docs · 699,670 pages · 89,501 facts · as of 2026-07-31

Record D-4114 · nsa_report

21st-quarterly-report.pdf

oaklandca · 1.1 MB · 89 pages extracted · 65 facts cite this document · retrieved 2026-07-15 · original location · open the PDF

Figures extracted from this document

Figures extracted from this document
MetricValueUnitPeriodPage
NSA Task 1 compliance status0compliance_status2015-05-04p.86
NSA Task 13 compliance status1compliance_status2015-05-04p.88
NSA Task 16 compliance status1compliance_status2015-05-04p.29
NSA Task 18 compliance status1compliance_status2015-05-04p.31
NSA Task 2 compliance status1compliance_status2015-05-04p.11
NSA Task 2.1 compliance status1compliance_status2015-05-04p.10
NSA Task 2.2 compliance status1compliance_status2015-05-04p.10
NSA Task 2.3 compliance status1compliance_status2015-05-04p.11
NSA Task 20 compliance status1compliance_status2015-05-04p.34
NSA Task 20.1 compliance status1compliance_status2015-05-04p.32
NSA Task 20.2 compliance status1compliance_status2015-05-04p.33
NSA Task 20.3 compliance status1compliance_status2015-05-04p.33
NSA Task 20.5 compliance status1compliance_status2015-05-04p.34
NSA Task 20.6 compliance status1compliance_status2015-05-04p.34
NSA Task 24 compliance status1compliance_status2015-05-04p.38
NSA Task 24.1 compliance status1compliance_status2015-05-04p.36
NSA Task 24.2 compliance status1compliance_status2015-05-04p.37
NSA Task 24.3 compliance status1compliance_status2015-05-04p.37
NSA Task 24.4 compliance status1compliance_status2015-05-04p.37
NSA Task 24.9 compliance status1compliance_status2015-05-04p.37
NSA Task 25 compliance status1compliance_status2015-05-04p.42
NSA Task 25.1 compliance status1compliance_status2015-05-04p.40
NSA Task 25.2 compliance status1compliance_status2015-05-04p.41
NSA Task 25.3 compliance status1compliance_status2015-05-04p.41
NSA Task 25.4 compliance status1compliance_status2015-05-04p.41
NSA Task 25.5 compliance status1compliance_status2015-05-04p.42
NSA Task 25.6 compliance status1compliance_status2015-05-04p.42
NSA Task 26 compliance status1compliance_status2015-05-04p.45
NSA Task 26.2 compliance status1compliance_status2015-05-04p.44
NSA Task 3 compliance status1compliance_status2015-05-04p.13
NSA Task 30 compliance status1compliance_status2015-05-04p.46
NSA Task 33 compliance status1compliance_status2015-05-04p.49
NSA Task 34 compliance status0.5compliance_status2015-05-04p.56
NSA Task 34.1 compliance status1compliance_status2015-05-04p.50
NSA Task 34.2 compliance status1compliance_status2015-05-04p.51
NSA Task 34.3 compliance status0.5compliance_status2015-05-04p.55
NSA Task 35 compliance status1compliance_status2015-05-04p.57
NSA Task 35.3 compliance status1compliance_status2015-05-04p.57
NSA Task 35.4 compliance status1compliance_status2015-05-04p.57
NSA Task 37 compliance status1compliance_status2015-05-04p.59

…and 25 more in the API.

Extracted text

· page 56 of 89 · · see this page in the PDF

Twenty-First Quarterly Report of the Independent Monitor for the Oakland Police Department May 4, 2015 Page 55 Task 34.3.2 requires that the data captured on the Stop Data Forms be entered completely and accurately into the database (compliance standard: 85%). As noted above, the entering of stop data into the Field Based Reporting 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 will not allow the form to be completed. Task 34.3.2 was created to govern the submission of data from the written forms to the computerized system. Since this type of data entry is no longer necessary, the Department is in compliance with Task 34.3.2. OPD is in partial Phase 2 compliance with Task 34. Compliance Status: Phase 1: In compliance Phase 2: Partial compliance Next Steps: During our next site visit and upcoming technical assistance visits, we will again meet with relevant Department personnel to discuss the Department’s progress in this area. We will further discuss the Department’s various Task 34-related data systems to assess their operability, accuracy, and utility in storage, and ease of access to stop data. We will continue to work with OPD on ways to verify the legal basis for stops, searches, and other related activities expeditiously. We will also discuss how conducting internal audits of its stop data forms can help the Department to identify any disparities in its treatment of citizens. Task 35: Use of Force Reports - Witness Identification Requirements: 1. OPD shall require, by policy, that every use of force report, whether felonies were involved or not, include the names, telephone numbers, and addresses of witnesses to the incident, when such information is reasonably available to the members/employees on the scene. 2. In situations in which there are no known witnesses, the report shall specifically state this fact. Policy shall further require that in situations in which witnesses were present but circumstances prevented the author of the report from determining the identification or phone number or address of those witnesses, the 3. report shall state the reasons why the member/employee was unable to obtain that information. Reports shall also include the names of all other members/employees of OPD witnessing the use of force incident. (Negotiated Settlement Agreement VI. C.) Discussion: OPD published Special Order 8066, Use of Force—Witness Identification (April 12, 2004), which incorporates the requirements of Task 35. Additionally, OPD published Departmental