0060.60 Standard Operating Procedures

Directive 0060.60, Standard Operating Procedures

Refer: 
•    Northwest Accreditation Alliance Law Enforcement Standards Manual
•    ADM-300, Policy and Procedure
•    DIR 0010.00, Directives Review and Development Process
•    Directive/Standard Operating Procedures Form (Intranet)
 

Definitions: 
•    Directive: The Bureau's formal written standards, approved by the Chief of Police, establishing Bureau-wide Rules, policy, and Procedure for a specific topic. Bureau Directives fall under the following statuses:
o    Active: Enacted, currently enforceable Bureau Directives.
o    Draft: A new Directive or proposed changes to an Active Directive.
o    Archive: A previous version of a Directive, or rescinded Directive.

•    Procedure: Specific guidance on an operational practice that explains the steps members take to perform their duties and certain functions, including details such as timing, frequency, responsibilities, and Rules.

•    Rules: Specific direction members are required to follow when faced with certain situations.

•    Standard Operating Procedure: A branch, division, unit, or precinct order that provides detailed technical or process-oriented direction for managing specified matters or completing certain tasks.

Policy: 
1.    This Directive establishes the guidelines for creating, reviewing, and maintaining Bureau Standard Operating Procedures (SOPs).

2.    The Bureau may create SOPs for purposes such as contingency planning, relaying information, outlining specific procedures for routine matters or subjects related to Directives, or providing guidance relating to emergencies.

Procedure: 
1.    General Requirements.
1.1.    SOPs must be consistent with applicable Directives, though may be more detailed in content and application.

1.2.    Review and Approval.
1.2.1.    The Bureau will regularly review SOPs on a Responsibility Unit (RU)-determined schedule at least every two years to ensure direction remains consistent with applicable Directives and other Bureau standards, and reflects current practices. 
1.2.2.    RU Managers or designees shall review, approve and, as necessary, rescind or revise all division, unit, and precinct SOPs.
1.2.3.    The appropriate branch Chief, or a designee, shall review, approve and, as necessary, rescind all branch SOPs.

2.    SOP Development and Organization.  
2.1.    RU Managers and Branch Chiefs, or their designees, may direct a reporting member to develop SOPs that affect their area of command responsibil¬ity.

2.2.    All Bureau SOPs must include the following: 
2.2.1.    Responsible branch, division, unit, or precinct.
2.2.2.    SOP Number.
2.2.3.    SOP Name. 
2.2.4.    Purpose: A brief statement summarizing why the SOP exists. 
2.2.5.    Effective date and projected future review date.
2.2.6.    Procedure. 
2.2.7.    References and Definitions, if applicable. 
2.2.8.    Approval: Signature and date lines for the RU Manager, Branch Chief, or designee authorizing the SOP. 
2.2.9.    Development and Review History: Originating document and past review dates, when available, and a brief summary of the latest changes.

2.3.    Storage and Maintenance.
2.3.1.    RUs and Branches will electronically store all SOPs in a manner determined by the Chief or Bureau policy. 
2.3.2.    SOPs are subject to a permanent retention schedule; therefore, RUs and Branches must permanently maintain all historical SOPs.

Effective:          5/30/2026
Next Review:    5/30/2031