> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/evacuation/evacuation-statuses.md).

# Evacuation statuses

During an active evacuation, a person's safety status appears on two surfaces with two different label sets: the **self-report prompt** the recipient sees in their alert, and the **roll call** safety officers watch on the dashboard. The recipient's report flows through to the officer's view, and officers can also set a status by hand.

## The recipient self-report prompt

The link in each alert lets a recipient mark themselves as one of two options:

* **Safe**
* **In Danger**

That is the entire choice the recipient makes. What an officer sees, though, is the richer roll call below.

## The dashboard roll call

On the Visitor Log (and Employee Logs), each person shows one of these statuses, both as a summary tile at the top and in the **Evacuation Status** column per person:

| Status               | Means                                                                                     |
| -------------------- | ----------------------------------------------------------------------------------------- |
| **Safe**             | The person has been marked safe through one of the available channels. Shown in green.    |
| **Needs Assistance** | The person has responded that they are in danger or not safe. Shown in red.               |
| **No Response**      | A notification was sent but no response has been received. Shown in amber.                |
| **Signed Out**       | The person was onsite but had already signed out before the event started. Shown in grey. |
| **N/A**              | The evacuation status does not apply to this person's record. Shown in grey.              |

## How the two surfaces map

A recipient's **In Danger** self-report surfaces to officers as **Needs Assistance** on the roll call. The recipient never sees the words "Needs Assistance"; the officer never sees a separate "In Danger" label. They are the same event seen from two sides.

{% embed url="<https://app.arcade.software/share/wqtRKbOnnCJIIClsbaAO?embed=true>" %}
Walkthrough: reading each evacuation status on the dashboard.
{% endembed %}

## Setting a status manually

Officers do not have to wait for a self-report. Click a person's status in the **Evacuation Status** column to open the **Update Evacuation Status** dialog, then choose **Needs Assistance** or **Safe**. A note is required on every update, so each change carries a reason.

{% embed url="<https://app.arcade.software/share/udxjrKpenRgNPmZtiv47?embed=true>" %}
Walkthrough: manually updating a person's evacuation status.
{% endembed %}

A status can be changed from any state and as often as needed. Each change is recorded, giving a timestamped audit trail per person from the first notification through to the final status.

{% hint style="info" %}
**Note**: Muster-point sign-outs feed the same model. During an event, a kiosk sign-in or sign-out registers as a muster event and updates the roll call automatically.
{% endhint %}

For what the module is and the end-to-end flow, see [About Kenai Evacuation](/command-centre/visitor-management-powered-by-kenai/evacuation/evacuation-overview.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/evacuation/evacuation-statuses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.