68,471 docs · 699,671 pages · 90,616 facts · as of 2026-08-01

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 30 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 29 Task 18: Approval of Field-Arrest by Supervisor Requirements: Within 260 days from the effective date of this Agreement, the Chief of Police shall, based on contemporary police standards and best practices, develop and implement policies to address the following standards and provisions: Approval of Field-Arrest by Supervisor 1. OPD shall develop standards for field supervisors that encourage or mandate close and frequent supervisory contacts with subordinates on calls for service. The policies developed in this Section shall require supervisors to respond to the scene of (at least) the following categories of arrest, unless community unrest or other conditions at the scene make this impractical: a. All Felonies; b. All drug offenses (including narcotics, controlled substances and marijuana arrests if the subject is taken to jail). c. Where there is an investigated use of force; d. Penal Code §§69, 148 and 243(b)(c). The responding supervisor shall review the arrest documentation to determine whether probable cause for the arrest, or reasonable suspicion for the stop, is articulated, to ensure that available witnesses are identified, to approve or disapprove the arrest in the field, and to log the time of the contact.9 (Negotiated Settlement Agreement IV. A.) Discussion: Three Departmental policies incorporate the requirements of Task 18.2.2: DGO M-18, Arrest Approval and Review in the Field (published May 13, 2004 and updated October 1, 2005); Special Order 8536, Probable Cause Arrest Authorization and Report Review (published December 2006); and Training Bulletin I-O.4, Legal Aspects Of Searching Persons On Parole And Probation (published November 23, 2011). As the Department has trained at least 95% of relevant personnel on these policies, we find OPD in continued Phase 1 compliance with this Task. Only one provision of Task 18 (18.2.2) is being actively monitored under the MOU. During all of the previous reporting periods, we found the Department in compliance with this subtask. Task 18.2.2 requires that supervisors review arrest documentation to verify that available witnesses are identified (compliance standard: 90%). To assess Phase 2 compliance with this subtask, we reviewed arrest documentation for all of the applicable arrest categories, as well as documentation for arrests resulting in an investigated use of force. Specifically, we reviewed a random sample of 72 adult and three juvenile arrest reports documenting felony arrests; drug arrests; and arrests for Penal Code 69, 148, and 243(b)(c); as well as documentation for 12 9 The underlined requirement is the only provision of Task 18 that is being actively monitored under the MOU.