My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Document of Interest Provided By Councilmember Hamann on Civilian Review Boards
sbend
>
Public
>
Common Council
>
Boards and Commissions
>
Community Police Review Board (CPRB)
>
Document of Interest Provided By Councilmember Hamann on Civilian Review Boards
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/23/2020 10:09:33 AM
Creation date
6/23/2020 10:08:26 AM
Metadata
Fields
Template:
City Council - City Clerk
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
181
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
• Affirm the police bureau’s finding. <br />• Refer the case to IA for further investigation. <br />• Recommend that PIIAC (i.e., the city council) inform <br />the chief in writing that the finding does not support <br />IA’s determination. <br />• Refer the finding for reconsideration to the police <br />bureau’s Review Level Committee (consisting of <br />branch managers, the accused officer’s manager, the <br />PIIAC auditor, one citizen adviser, and nonvoting rep- <br />resentatives from the police bureau and the city). <br />On the two or three occasions a year when the advisory <br />board asks the Review Level Committee to reconsider a <br />finding, the examiner and the adviser who reviewed the <br />case participate in the meeting. On occasion, the Review <br />Level Committee has agreed to change an exonerated <br />finding to one of insufficient facts. On one occasion, the <br />chief overruled the Review Level Committee’s recom- <br />mendation and sided with the PIIAC advisers to sustain <br />a complaint. <br />Advisory meetings last about 90 minutes, with 15–20 <br />minutes devoted to each appeal. After each monthly meet- <br />ing, the examiner drafts a report for PIIAC summarizing <br />the advisory board’s conclusions regarding each appeal. <br />Audits <br />Five citizen advisers volunteer to be on a PIIAC monitor- <br />ing subcommittee. Subcommittee members look at cases <br />chosen at random by the examiner to determine trends in <br />quality, timeliness, and accuracy of the police bureau’s <br />IA procedures and investigations. <br />Internal affairs sends the examiner all closed cases each <br />month—30–40 cases. The examiner assigns the cases to <br />monitoring subcommittee members with a worksheet to <br />guide their review, but she does most of the reviews her- <br />self, including all cases that involve the alleged use of <br />excessive force or discrimination and all cases IA sustains. <br />The examiner or the assigned subcommittee member goes <br />individually to the police bureau to review the entire file <br />for each case in a private room. One of them completes <br />the worksheet with pertinent information about the case. <br />Officers’and complainants’names are not included in the <br />reports. The examiner and adviser spend 2–4 hours <br />examining how thoroughly and fairly the investigation was <br />conducted and whether the finding is solidly supported. <br />At each monthly monitoring subcommittee meeting, <br />which is open to the public and the press, advisers and <br />the examiner discuss trends they may have spotted in <br />their investigations. (See “Troublesome Trends Revealed <br />by Monitoring Cases.”) Based on the audit results, the <br />examiner develops a draft quarterly report, with subcom- <br />mittee members’ help, highlighting shortcomings in the <br />investigations, abuse trends, and recommended policy or <br />training changes (see “Other activities” on page 45). At <br />the next monthly subcommittee meeting, subcommittee <br />members review the report—and pertinent statutes and <br />C ITIZEN R EVIEW OF P OLICE: APPROACHES AND I MPLEMENTATION <br />43 <br />TROUBLESOME TRENDS REVEALED <br />BY MONITORING CASES <br />In 1998, the examiner—Lisa Botsko (at that time)— <br />and citizen advisers noticed that several com- <br />plainants reported that, when they asked police offi- <br />cers for their badge numbers, the officers would <br />reply,“I don’t have a badge number.” Technically, this <br />was accurate. However, officers do have identifica- <br />tion numbers. After Botsko shared this concern <br />with the police bureau, the chief clarified the perti- <br />nent general order to require officers to interpret <br />requests for their badge number as a request for <br />their identification number. <br />Botsko and the advisers also noticed that a number <br />of incident reports referred to officers’ use of a “dis- <br />traction blow” without explaining its purpose. After <br />inquiring about the behavior, Botsko learned that the <br />police bureau training department taught the distrac- <br />tion principle (e.g., pushing the driver’s head while <br />prying his or her hands off the steering wheel)—but <br />not a blow—as a means of diverting someone’s atten- <br />tion. Indeed, the bureau considers a blow to be a use <br />of force that requires explanation in the incident <br />report. It turned out that some officers had learned <br />the distraction blow technique at the State training <br />academy. As a result, the bureau agreed to explain <br />during inservice training that officers always have to <br />explain in their reports why they struck someone <br />and refrain from using incorrect terminology.
The URL can be used to link to this page
Your browser does not support the video tag.