Committee reviews pursuit policy and the administrative burden of CALEA compliance

At its quarterly meeting, the Police Accountability Committee examined the department’s vehicle‑pursuit policy and the time required to document pursuits for CALEA compliance.

Chief Patrick Foley walked the committee through the department’s written pursuit directive (identified in the meeting as chapter 4122), noting the policy’s detailed bullets on when a pursuit is authorized, responsibilities of secondary units and dispatch, and termination criteria. He said the department generally records five to eight pursuits a year and that each pursuit generates a vehicle pursuit report, body‑ and dash‑camera review, and an administrative compliance review.

Foley emphasized that CALEA standards require thorough documentation and an annual analysis to identify trends and training needs. He described the reporting as labor‑intensive for officers and supervisors but necessary to reduce liability and improve training. Committee members asked about real‑world examples and cross‑jurisdiction coordination; Foley and others referenced a high‑speed stolen‑vehicle pursuit in Ocean City that ended with spike strips and on‑foot apprehensions as an example of risk‑based decision‑making.

The committee did not change pursuit policy at the meeting but discussed the department’s processes for review, training and use of technological aids (license‑plate readers, aviation assets) to limit risky vehicle chases.

The chief said he will continue administrative analysis of pursuits and incorporate findings into training and accreditation proofs ahead of the upcoming CALEA compliance inspection.