TCOLE advisory panel narrows motor‑vehicle‑stop data definitions and directs staff to draft vendor guidance

The advisory committee to the Texas Commission on Law Enforcement spent its session revising the state'level motor‑vehicle‑stop data dictionary and agreed to send a draft of tightened definitions to vendors and agencies ahead of the next meeting.

Committee members focused on which detentions should count as a "traffic stop," how to record reasons for stops and searches, and how to classify contraband and outcomes so analysts can reliably measure potential racial profiling. Assistant Chief Putin, the subcommittee lead, said the group "kinda landed on, obviously, you know, it's a motor vehicle stop, so we want to exclude, collisions, where citation will more could or more likely will be issued, but we don't necessarily include that into racial profiling data because the officer did not initiate that contact with those drivers." The remark framed a central debate over whether collisions and dispatched calls should be recorded as stops or flagged separately for analysis.

Why it matters: The data dictionary will define the variables that law enforcement agencies must report and the labels vendors must implement. Those definitions determine whether agencies report every contact, or whether some detentions (for example dispatched calls or collision responses) can be set aside so analysts can focus on discretionary stops where profiling risk is highest.

Key outcomes and proposals

- Driver‑centric reporting: The committee favored making the dataset focus on the driver and vehicle for key analytic fields (search conducted, contraband discovered, race/ethnicity and outcome). Members argued that passenger entries and other ancillary records can inflate counts and complicate racial‑profiling analysis.

- Discretionary vs. preexisting/dispatch: Members debated excluding collisions and certain dispatch‑directed detentions from the operational definition of a discretionary stop. Several members proposed retaining those events in the submission but flagging them so researchers can exclude them when appropriate; one member warned narrowing the definition could reduce transparency by allowing agencies to omit stops.

- Contraband and categorization: The panel recommended grouping paraphernalia and chemical precursors under a "drug‑related items" label and broadening the currency category to include other financial instruments (forgery tools, stolen financial documents) so the large "other" bucket shrinks and analysts get clearer categories.

- Searches, hits and outcomes: The group proposed limiting the "search conducted" field to searches of the driver or the vehicle (not passengers) for the profiling dataset, and to record the initial reason for a search (probable cause, consent, incident‑to‑arrest) so vendors and analysts have a single primary reason for each search.

- Use of force and injury fields: Committee members recommended removing officer/suspect injury counts from the profiling submission because those data are collected in separate use‑of‑force systems and lack a consistent cross‑vendor definition; they retained a rephrased field for "force used on driver."

Implementation steps

Members asked staff to translate the revised definitions into an implementable collection form and a short guidance document vendors can use. The committee discussed technical constraints across e‑citation, CAD and RMS vendors and urged TCOLE to publish a standards document to make vendor changes consistent and enforceable; vendors were given December as a typical calendar target for implementation in past rollouts. Melissa (staff) agreed to draft the group''s edits and circulate them ahead of the next meeting.

Selected quotes

"Because the purpose is we're just trying to make sure that nobody's racial profiling," a committee member said, summarizing the group's analytic aim. "If we eliminate that category, if we get the definition of this traffic stop to include self‑initiated stop, that becomes more clear," Assistant Chief Putin added during the discussion of dispatched calls.

What happens next

Staff will produce a draft of the revised data dictionary and example scenarios for ambiguous cases; the committee scheduled a follow‑up meeting for April 8 at 1:30 p.m. to review the draft. The panel also recommended that TCOLE publish vendor guidance and suggested permissive language for multi‑select fields where agency systems can support it.