Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Policy Language topic
No spam. Unsubscribe anytime.
Council members press for mandatory "reasonable articulable suspicion" in consent-search policy
Summary
Several council members argued the policy's language — which uses 'should' rather than 'must' for requiring reasonable articulable suspicion — weakens accountability; officials said the chief directs officers to seek such suspicion in most cases but kept 'should' to allow rare urgent exceptions.
Council members used the briefing to press a substantive policy question: should the policy require ("must") that officers have reasonable articulable suspicion (RAS) before seeking consent, or is the softer "should" adequate?
Council member May argued the word choice undermines enforceability: "The script as we have it now does not tell people that they have the freedom to leave," May said while pressing for clearer, mandatory language and public-facing script changes so people know they may refuse or withdraw consent. Several council members warned that without a mandatory standard it will be difficult for the public or the Administrative Charging Committee to determine whether the policy was followed.
Assistant Chief Frank acknowledged the concern but defended the drafting choice, saying the chief expects officers to have RAS in most instances while "should" leaves limited room for rare, urgent public-safety judgments. He urged use of the app's narrative fields and supervisory review to resolve borderline cases. The committee did not change the language during the session; members asked staff to return with options for clearer wording and with guidance for ACC review.
