The Rekor Command Persistence Score is designed to help operators easily prioritize and validate incidents.
The Rekor Command Persistence Score helps operators quickly validate and prioritize incidents. It estimates how likely an incident is still active, giving teams a simple way to decide what to handle first.
Incidents appear as event cards on the left panel. Each card includes a Persistence Score, visible when you open the Event Card and view the Incident Detail Panel.
Persistence Score Details
The Persistence Score reflects the likelihood that an incident is still active on the roadway. It uses a High / Medium / Low / Very Low scale and continues updating in real time from the opening to the closing of an incident.
The score is influenced by several factors, including:
- Incident type
- Time since first report
- Number and recency of updates
- Historical behavior patterns by state
- Estimated Time to Clear*
*Estimated Time to Clear is a new function that gives operators an early sense of whether an incident is likely to remain active for a short period or require longer monitoring. This additional signal helps operators:
- Better gauge incident urgency
- Allocate attention where it will have the most long-term impact
- Anticipate downstream effects on traffic operations
How Estimated Time to Clear Is Calculated:
Estimated Time to Clear is the best assessment for how long an incident will take to fully resolve. It’s generated by looking at how long similar incidents have taken to clear in the past.
To calculate it, Rekor Command:
- Finds similar historical incidents in the Rekor data.
- Matches the incidents by key conditions, such as incident type, road type, time of day, and whether the incident caused traffic disruptions.
- Calculates the typical duration by taking the median time it took for those past incidents to go from “open” to “closed.”