> For the complete documentation index, see [llms.txt](https://docs.rekor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rekor.ai/rekor-command-r/live-map/editor/incident-card/insights-panel.md).

# Insights Panel

The Insights Panel is a panel in Rekor Command that serves up a range of real-time insights. These insights help operators understand the roadway more fully to help them better prioritize their roadway management approach, ensuring maximum effectiveness.&#x20;

## Incident Priority

Incident priority ranking provided by Rekor Command ensures operators can respond to the events disrupting roadways in a timely and efficient manner, improving traffic flow, minimizing the risk of secondary crashes, and enhancing safety for motorists and emergency responders.  By providing this new priority ranking, we support quick and decisive action on the highest priority incident and improving the overall effectiveness of traffic management operations.&#x20;

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FCom3x6IIgKJncBB9fiYs%2FIncidentsettings-1?alt=media&amp;token=44fa390a-1754-45be-bf0c-a6402bdd41d5" alt="Incident settings" height="293" width="624">

  To customize priorities:&#x20;

1. A manager-level user will mouse over the username in the upper right corner, then select the gear icon to go to Settings. &#x20;
2. Go to Incidents then Type Priority in the left navigation pane.&#x20;
3. Drag and drop the incident types into the preferred order of importance by clicking and hovering over each incident type to select it. Once the changes are made, click Save Changes in the upper right corner.&#x20;

When sorted by highest priority, unconfirmed incidents are identified then displayed on the Live Map and are automatically sorted based on priority on the Need Action tab. This priority ranking is based on several factors including the incident type, persistence score, and road type, among other factors.&#x20;

To view prioritized incidents, sort by Highest Priority.&#x20;

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2F8aUlFX3Lh8No4ri5F9uI%2FIncidentLiveMap?alt=media&amp;token=377f0cfb-c6ad-48e7-8ff5-5137a9ff8d02" alt="Incident Live Map" height="376" width="624">

To view more information on the incident, click on the incident in the left side panel.

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2Fg16ErARatbaKhForZf1J%2FIncidentInsightPanel?alt=media&amp;token=953490b5-415b-4659-a043-391cfbb52c69" alt="Incident Insight Panel" height="352" width="624">

The Insights section now displays the Priority level, as well as the Persistence score, and Traffic impact. Each section may be expanded to view more details, if available. &#x20;

Note: The Priority level is based on several metrics. The most impactful metrics are displayed when the details are expanded.&#x20;

## Persistence Score

The 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.&#x20;

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.&#x20;

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FcSMnygyZi6B9VVBTEyzu%2FPersistence%20Score?alt=media&amp;token=d41991d4-2101-4726-9f67-1163863348cd" alt="Persistence Score" height="452" width="467">

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.&#x20;

The score is influenced by several factors, including:&#x20;

* 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 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, allowcate attention where it will have the most long-term impact, and anticipate downstream effects on traffic operations.

How Estimated Time to Clear Is Calculated:&#x20;

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.&#x20;

To calculate it, Rekor Command:&#x20;

1. Finds similar historical incidents in the Rekor data.
2. Matches the incidents by key conditions, such as incident type, road type, time of day, and whether the incident caused traffic disruptions.&#x20;
3. Calculates the typical duration by taking the median time it took for those past incidents to go from “open” to “closed.”

## Traffic Impact

Traffic Impact helps operators quickly understand how incidents affect surrounding roads and how long those impacts are expected to last.

The Traffic Impact feature analyzes real-time telematics data alongside historical traffic patterns to assess the severity and reach of each incident. This provides immediate situational awareness—without additional hardware—so traffic operators can identify, prioritize, and manage the most disruptive events directly within Rekor Command.&#x20;

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FoKcJmD7CQfAvb2PrRT7F%2FInsight%20Panel?alt=media&amp;token=f6efccc7-dc9c-4aba-b94d-c77b499a0fb0" alt="Insight Panel" height="517" width="541">

When nearby roads are affected, each impacted corridor is listed with key performance indicators, including current speed, expected speed, and travel time index. Corridors are ordered by severity to help operators focus on the most impacted areas first.&#x20;

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2F7hw5yd30eZkrZQoBntVf%2FTraffic%20Impact%20Panel?alt=media&amp;token=1016fc02-cfff-4145-97d9-c63b685f3677" alt="Traffic Impact Panel" height="505" width="575">

Operators can select Show on Map to visualize affected corridors directly on the Live Map.&#x20;

<img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FIlLTAaZmKqKZSBudGrWb%2FTraffic%20Impact%20Map?alt=media&amp;token=873bdaa0-9477-4b18-b638-4ab0b9e2e99e" alt="Traffic Impact Map" height="451" width="435">

The Traffic Impact panel includes an Estimated Time to Return to Normal Traffic, which predicts how long it will take for traffic conditions to recover based on current conditions and historical trends.&#x20;

This estimate is presented as:&#x20;

* Duration (e.g., 20–30 minutes)&#x20;
* Time window showing when normal traffic is expected to resume&#x20;

This capability helps operators:&#x20;

* Set clearer expectations with stakeholders and the public&#x20;
* Make more informed decisions about incident response and mitigation&#x20;
* Reduce uncertainty during evolving events&#x20;

The estimate updates dynamically as traffic conditions change.&#x20;

Please note: Traffic Impact is an Add-On feature and is not enabled by default. Customers must request activation for this feature to be available in their environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rekor.ai/rekor-command-r/live-map/editor/incident-card/insights-panel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
