Flock Safety Convoy Search Can Turn Co-Travel Into Suspicion
Two coworkers leave the same office every night. One later becomes a police target, and Flock Safety's Convoy Search finds the other car repeatedly nearby. The interface introduces the idea of a "potential accomplice and getaway car" even though the observation itself establishes only co-travel. Families, rideshare drivers, delivery workers, commuters, and strangers leaving the same event can all enter an investigation through proximity rather than conduct.
The captured FlockSafety interface describes Convoy Search in unusually consequential language. It says the feature can "Identify vehicles that have been seen together so you can verify a potential accomplice and getaway car." The accompanying code sends an initiating plate, selected cameras or networks, time ranges, a reason, a case-number field, and vehicle attributes to a dedicated /api/v1/caravan-search endpoint.
Convoy Search links a target plate to vehicles seen nearby.
For the family member, coworker, rideshare driver, commuter, neighbor, delivery worker, or unrelated motorist who repeatedly shares a route with a target vehicle, this mechanism can turn proximity into a candidate relationship. The word potential matters, but so does accomplice. Product language can shape the investigative meaning assigned to a correlation before the operator has independently established shared intent.
The product frames co-occurrence as an accomplice lead
The interface presents a heading, Convoy Search, followed by an example that asks for vehicles seen near a specific car multiple times. Its first sentence tells the operator that vehicles seen together can help verify a potential accomplice and getaway car in a series of vehicle thefts
This is product copy from the captured client, and it hands the operator a frame for reading vehicles that appear together repeatedly. The interface presents the result as a way to investigate a possible criminal association rather than shared traffic. It invites confirmation bias when repeated proximity is treated as proof instead of a lead that still needs independent corroboration.
The request begins with a vehicle and searches outward
The request helper posts to /api/v1/caravan-search. Its body can include cameraExternalIds, networkExternalIds, a licensePlate, reason, caseNumber, multiple date ranges combined with an or operator, class names, vehicle makes, vehicle types, colors, identifiers, page size, and sort order
A known plate becomes the anchor. The operator narrows where and when to look, adds vehicle attributes, and submits the criteria to a dedicated backend service whose implementation is not in the corpus.
The search then moves outward from one vehicle to discover other vehicles that satisfy an unseen co-occurrence rule.
The request includes purpose context in reason and a caseNumber field. Episode 02 covers the captured client's separate configurable case-number validation.
A vehicle relationship is not a human relationship
Convoy Search begins with observations of vehicles. A camera event does not identify who was driving or whether the people involved knew one another. Moving from co-observed vehicles to a claim about human association adds an inference the interface cannot verify on its own.
Common travel has many ordinary explanations:
- Members of a household leaving from the same address.
- Coworkers arriving for the same shift.
- Rideshare and delivery drivers repeating popular routes.
- Neighbors using the same arterial road.
- Commuters passing the same cameras at similar times.
- Motorists leaving a stadium, protest, school, house of worship, clinic, or public meeting.
Each downstream step strips the result of its caveats.
The privacy issue is association by inference. One vehicle's presence can become the basis for searching outward and scrutinizing other vehicles whose owners, drivers, or passengers were not initially under investigation. The risk grows if a tentative result is exported, hotlisted, placed into a report, or repeated without its uncertainty.
An accomplice label is only as strong as its corroboration
A convoy result is an investigative lead, not legal authority and not proof of a human relationship.
The interface has already supplied the criminal frame. Its instruction to verify becomes meaningful only if the candidate stays tied to the observations, settings, and human corroboration that support it, rather than traveling downstream as an unqualified association.
The captured product turns repeated vehicle proximity into a candidate investigative association and introduces that association with accomplice language. It is an invitation to investigate, not proof that an accomplice was found.