Alert Routing: The Right Alert to the Right Officer
When RTIS identifies a match, the alert does not broadcast to everyone in the building. It routes to a specific, designated recipient based on the alert type, the source database, and the operational plan for that event. LE alerts go to LE. Venue alerts go to venue security. Neither sees the other's data.
How Alert Routing Works
Every RTIS match goes through the Rapid Action Center (RAC) for human verification. Once confirmed, the alert is routed based on its source and type. The routing is configured before event day and enforced by the platform. Venue security staff cannot access LE alert data. LE contacts cannot access venue X-list data.
UMbRA Matches Route to Law Enforcement Only
When RTIS matches a person against UMbRA (active warrants, booking records, LE-flagged individuals), the RAC-verified alert is delivered exclusively to the designated LE contact for that event. Venue security management does not receive UMbRA alerts. Venue security staff do not see the matched person's name, charge information, or warrant status from UMbRA.
LE agencies will not share intelligence data with private sector entities. Compartmentalized routing ensures that participation in the RTIS program does not require LE to expose operational data to venue staff.
X-LST Matches Route to Venue Security Only
When RTIS matches a person against the venue's operator-controlled X-lists (banned patrons, VIPs, credentialed personnel, executive protection principals), the RAC-verified alert is delivered to the designated venue security contact. LE contacts do not receive X-list alerts unless the venue has explicitly configured cross-routing for specific list categories.
The venue controls its own lists. Safience has no visibility into X-list contents during normal operations. The venue's banned patron list, VIP list, and credential list remain private to the venue.
RVIS Matches Route Through RAC to Appropriate Agency
If RVIS identifies a potential missing person or trafficking victim, the Rapid Action Center coordinates directly with the appropriate law enforcement agency designated for that case. RVIS alerts follow their own routing path, separate from both UMbRA and X-LST alerts. The venue is notified as appropriate based on the operational protocol.
Missing person and victim identification alerts require careful handling. The RAC ensures that the alert reaches the correct agency and that response is coordinated.
All Routing Is Configurable Per Event
Alert routing is configured before each event based on the operational plan. Different events at the same venue may have different routing configurations. A football game may route alerts to the local PD detail commander. A concert may route to a different contact at the same agency or a different agency entirely. Routing configurations are reviewed and confirmed before each event.
Event-day operations vary. The system adapts to the operational plan, not the other way around.
Multi-Agency Event-Day Operations
A major venue event may involve four or more agencies operating in the same space: local PD, county sheriff, state police, and federal agencies. Each agency has its own watch lists, warrant databases, and operational priorities. RTIS provides a unified identity intelligence layer that serves all of them simultaneously without requiring any agency to share data with another.
One Venue, Multiple Agencies
Local PD assigns officers to the interior. County sheriff covers the parking lots and perimeter. State police provide support at designated events. Each agency may have persons of interest that the others do not know about. RTIS scans against UMbRA (which contains records from all contributing agencies) and routes alerts to the designated contact for each jurisdiction based on the source of the matching record.
League and Federal Coordination
For high-profile events (championship games, events with dignitary attendance), federal agencies may be involved. RTIS alert routing can be configured to include federal liaisons for specific alert categories. Routing rules are established during pre-event coordination, not improvised on game day.
Mutual Aid and Regional Partnerships
Large-scale events often require mutual aid from neighboring jurisdictions. Officers from assisting agencies may not be familiar with the venue or its specific threat landscape. RTIS provides identity intelligence to the detail command regardless of which agency the individual officers represent. The system does not require each participating officer to have separate access; alerts route to the designated command structure.
Every Alert Is Auditable
Every RTIS alert generates a complete audit record. The record documents: the sensor that captured the image, the time of capture, the database that produced the match (UMbRA or X-LST), the RAC analyst who verified the match, the time of verification, the recipient who received the alert, and the time of delivery. This audit trail serves two purposes. For law enforcement, it provides a documented chain of events that supports prosecution. For the venue and its counsel, it provides evidence of the system's operation for liability defense. No alert data is available retroactively for non-matches. If a person was not matched, no record of their presence exists. The audit trail applies only to confirmed, RAC-verified matches.
Configure Routing for Your Jurisdiction
We walk through the routing configuration during the LE briefing. You define which alert types reach your team, which contacts receive them, and how RTIS integrates into your event-day operational plan. All briefings are conducted under NDA.