68,471 docs · 699,671 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 48 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 47 Discussion: OPD has developed several policies that, in concert, incorporate the requirements of this Task. These include: Manual of Rules (MOR) Section 314.48, Reporting Violations of Laws, Ordinances, Rules or Orders; MOR Section 314.49, Confidential Reporting of Police Misconduct; Departmental General Order D-16, Check-In and Orientation; MOR Section 370.18, Arrests; and MOR Section 370.27, Use of Physical Force. The Department has trained at least 95% of relevant personnel on these policies, and remains in Phase 1 compliance with this Task. We found OPD in Phase 2 compliance with Task 33 during the last four reporting periods. Reporting Misconduct Task 33.1 requires that in all sustained internal investigations, OPD conduct an assessment to determine whether members/employees/supervisors knew or should have known that misconduct occurred (compliance standard: 95%); and Task 33.2 requires that where OPD determines that members/employees/supervisors knew or should have known that misconduct occurred but did not report it as required, OPD is required to take appropriate action (compliance standard: 95%). To assess OPD’s Phase 2 compliance with these subtasks during this reporting period, we discussed management of reporting misconduct by officers and employees of the Department with the Commander of IAD. We queried the IAD database to identify any cases with sustained findings that were approved between October 1, and December 31, 2014, that were applicable to Task 33. We identified and reviewed 27 cases with a total of 35 sustained findings involving 28 different officers and employees that were approved during this reporting period. We added four cases with eight sustained findings pertaining to four officers that had been brought to our attention during the previous reporting period but which were not disciplined until the third quarter of 2014. Our review, therefore, encompassed 31 cases with 43 findings pertaining to 32 officers. We found no instances where OPD disregarded indications that its employees or officers failed to report misconduct. Management Action to Address Reluctance to Report Misconduct We have noted consistently that the activation of PDRDs can be key in resolving allegations of use of force that arise from citizen contacts – particularly during demonstrations. Accordingly, it is a serious violation for an officer dealing with such circumstances to fail to activate his/her PDRD. In our review of the 31 cases in which there were sustained findings, we found six in which an officer was equipped with an operational PDRD should have activated it. In five of these cases the officers activated their PDRDs as required. In the one remaining case, the officer failed to activate his/her PDRD during his first contact with the citizen, and IAD sustained this violation. A three-day suspension was imposed as discipline in this case.