Police response subcommittee proposes clearer GPS alert protocol, urges statutory fixes for jurisdictional confusion

A subcommittee of the Connecticut Domestic Violence Council on April 22 urged the council to adopt a revised, three‑page section for the model policy that explains how the domestic‑violence alert notification GPS program works and how police should respond when an alert is triggered.

Chief Alaric Fox of the Enfield Police Department, co‑chair of the police response subcommittee, walked members through the draft, saying it distinguishes GPS monitoring for protective orders from probation or parole systems and defines buffer, exclusionary and mobile zones, alert triggers, officer dispatch steps and how law‑enforcement liaisons obtain offender location points from GPS vendors. "This is three pages well spent," Fox said, arguing the detail will reduce confusion for patrol officers.

The draft also corrects an editorial issue that could change the duty of officers; Fox asked to remove a redundant "if" so verifying a victim's safety reads as a required step rather than optional language. Karen Foley‑O'Connor, CEO of the Network Against Domestic Abuse in Enfield, told the council the change will make the guidance consistent across departments and help officers who may carry a pocket ‘‘red book’’ of model policy language.

Members asked operational questions about welfare checks when a GPS point cannot be located. Nancy Turner, representing the Connecticut Board of Pardons and Paroles, asked whether a victim or the GPS vendor initiates a wellness check. A prosecutor's designee explained that vendors sometimes contact defendants (named in the meeting transcript) to obtain a point when an environmental factor prevents GPS reception; victims are notified and officers are dispatched only when victims request a welfare check or when there are direct safety concerns.

The subcommittee made clear the draft is intended to replace the existing GPS section of the model policy (currently around page 18) and said the language will be included in the July packet for a vote by the full council. Chief Fox warned the section's length could make it harder to read in the field but defended keeping the substantive detail to avoid operational ambiguity.

The report also recommended the council press for legislative clarification of jurisdictional rules. Fox reviewed Connecticut statutes including Conn. Gen. Stat. 54‑1f (general local jurisdiction) and 54‑1r (special jurisdiction for certain communications offenses), and said the legislature has carved out three communications statutes (53a‑223, 53a‑223a and 53a‑223b) that permit jurisdiction where the defendant resides, where the communication was received, or where it originated. But other related statutes for harassment and stalking contain narrower jurisdictional language, creating confusion for officers about which police department should take a complaint.

Fox said the subcommittee drafted a one‑page guidance to reconcile which agencies properly have jurisdiction in common domestic‑violence communications cases and suggested that, to eliminate lingering ambiguity, the council work with legislative liaisons to consider expanding 54‑1r or adding clarifying language to related statutes.

Next steps: the GPS replacement language and the jurisdiction one‑pager will be edited based on today's discussion and circulated; the GPS language is scheduled for a full‑council vote in July. The council did not take a final vote on the jurisdiction recommendations but asked legislative liaisons to explore statutory options.