> 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-list.md).

# Incident List

The Incident List displays incidents that are currently affecting area roadways. Incidents are organized into three tabs: Need Action, In Progress, and Completed. The number on the Need Action tab shows how many incidents are waiting for review.

Each incident card shows its priority level, incident ID, incident type, location with road type, and the time it was reported. Priority applies to incidents in the Need Action tab, which you can confirm or reject directly from the card. Click any incident to open the card and enter more details.

<figure><img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FyPLTnqP5Uxou81voHPBW%2Fimage.png?alt=media&amp;token=2e13879f-739a-4bfd-8a19-10d74e1b0d25" alt=""><figcaption></figcaption></figure>

<p align="center"><em>The Incident List sorted by Highest priority.</em></p>

1\.    Need Action tab with the count of incidents awaiting review.

2\.    Sort by menu, set to Highest priority.

3\.    Review now: the highest ranked incident awaiting action.

4\.    Priority label for the incident.

5\.    Review next: the remaining incidents in rank order.

6\.    Confirm or Reject the incident directly from the card.

## &#x20;Priority Ranking

### &#x20;Why We Built This

During peak periods, operators can face dozens of incoming incidents from multiple data sources at once. Reviewing them in the order they arrive means a high impact incident can sit behind lower impact ones. Priority Ranking puts the incidents that matter most at the top of the list so operators can verify and respond to them first.

### &#x20;How Priority Ranking Works

Command assesses every unconfirmed incident in your account against six factors and assigns it a priority level of High, Medium, or Low. Some factors count more than others, and incident type counts the most.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Priority</strong></td><td valign="top"><strong>What it means</strong></td></tr><tr><td valign="top">High</td><td valign="top">Act on these first. The most important factors, such as a serious incident type on a major road, point to a significant incident.</td></tr><tr><td valign="top">Medium</td><td valign="top">Review after High priority incidents. The incident shows a mix of more and less serious factors.</td></tr><tr><td valign="top">Low</td><td valign="top">Review when time allows. Most factors point to a lower impact incident.</td></tr></tbody></table>

&#x20;

Priority Ranking considers six factors, listed here from most to least important:

<table data-header-hidden data-search="false"><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Factor</strong></td><td valign="top"><strong>What it captures</strong></td></tr><tr><td valign="top">Incident type</td><td valign="top">The kind of incident. By default, wrong way driving ranks highest, followed by vehicle on fire, crash, debris or hazard, abandoned or stalled vehicle, police activity, and traffic stop. Your account admin can change this order.</td></tr><tr><td valign="top">Persistence score</td><td valign="top">The likelihood that the incident is still active.</td></tr><tr><td valign="top">Road type</td><td valign="top">The class of roadway. Freeways rank highest, followed by highways, ramps, intersections, and bridges, down to streets and trails.</td></tr><tr><td valign="top">Traffic impact</td><td valign="top">The estimated time delay the incident is causing across its full extent.</td></tr><tr><td valign="top">Severity</td><td valign="top">The severity recorded for the incident: Minor, Intermediate, Major, or Critical.</td></tr><tr><td valign="top">Crash risk</td><td valign="top">Whether Command has flagged a crash risk at the incident location.</td></tr></tbody></table>

&#x20;&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>NOTE</strong>: If a factor is not available for an incident, Command sets priority using the factors that are available. A new incident that does not have a priority level yet appears at the bottom of the list.</td></tr></tbody></table>

### &#x20;Working the List By Priority

1. **Check that the list is sorted by Highest priority.** Highest priority is the default sort for the Need Action tab. If you have changed it, open the Sort by menu and select Highest priority. Command remembers your choice for future sessions.
2. **Start with Review now.** The incident at the top is the highest ranked incident awaiting action. Select Confirm to accept it, or Reject if it does not hold up on review.
3. **Work down Review next.** The incidents below are listed in rank order. Work through them from top to bottom.
4. **Check why an incident ranked where it did.** Hover over the priority label to see the incident’s priority level, then open **Incident Insight**. The Priority insight lists up to two factors that most influenced the ranking under **Heavily influenced by**.

<figure><img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2Fr5T3qOAC6D2bg2AL9yRm%2Fimage.png?alt=media&amp;token=c9413d72-7ead-41db-973d-8242ccfbb02e" alt=""><figcaption></figcaption></figure>

<p align="center"><em>Hovering over the priority label.</em></p>

1\.    **Priority label:** hover to see the tooltip.

2\.   **Tooltip** confirming the priority level, with a pointer to Incident Insight.

### &#x20;Rankings Update as Conditions Change

Command updates an incident’s priority whenever new information about it arrives, such as a change to its details, persistence score, or traffic impact. For active incidents this can happen every few minutes, and the list reorders each time, so the order can change while you work. In the example below, a stalled vehicle on US-290, reported at 9:51 AM, was ranked above the stalled vehicle on I-35 reported at 9:48 AM and replaced it in Review next.

<figure><img src="https://1152281022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffn8fmgXWpQ7tn1wzOQYI%2Fuploads%2FFO4QiXRybHhRthLopBqf%2Fimage.png?alt=media&amp;token=b8ca53fa-65b2-4314-9614-f92af1da8942" alt=""><figcaption></figcaption></figure>

<p align="center"><em>The Review next incident before and after a newly reported incident was ranked.</em></p>

### &#x20;Helpful Tips

* **Priority Ranking supports your judgment rather than replacing it.** Always verify an incident before confirming it.
* **Check the incident ID before you act.** Because the list updates in real time, confirm that the card you are about to confirm or reject is the one you reviewed.
* **Use Reject freely.** Rejecting incidents that do not hold up keeps the Need Action list focused on what is real.
* **Looking for the persistence score?** It is still one of the factors behind priority, and you can see it in [Insight Panel](https://docs.rekor.ai/rekor-command-r/live-map/editor/incident-card/insights-panel).
* **Admins can set incident type priority.** Users with account update permission can reorder incident types under **Configurations › Incidents › Type priority**. Because incident type carries the most weight, this has the biggest effect on how your li


---

# 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-list.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.
