> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.anghello.com/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # 4. Using Anghello during an evacuation **For:** QHSE Managers, Safety Officers, Site Managers, evacuation responders **Application:** Admin (app.anghello.co) **Estimated time:** 5-minute read --- In this guide, "**triggering an evacuation**" means activating the roll call report in Anghello. This starts the digital head count, notifies authorized users, and displays a red banner on the check-in kiosk (Spot app). Triggering Anghello happens alongside your alarm system, which remains independent. ## Typical timeline Anghello automatically timestamps every action: | # | Step | Action in Anghello | Measured by Anghello | | ---- | | 1 | Alarm / evacuation signal | — | — | | 2 | Evacuation triggered | Scan the QR code or click **Trigger** | Trigger timestamp, notifications sent | | 3 | Roll call at the assembly point | Click **Safe** for each person | Timestamp of each check-off, identity of who did it | | 4 | Roll call complete + missing people identified | Full list, call the missing | Automatic counter: checked off / unaccounted for | | 5 | Evacuation closed | Click **End** | Total duration, archived report | The evacuation report provides all these timestamps automatically, directly comparable with the targets in your internal procedure. --- ## Triggering an evacuation ### Method 1: From a user account 1. Open app.anghello.co or use the shortcut on your home screen 2. Sign in if you aren't already (email/password or SSO) 3. Click the red **Trigger evacuation** button 4. Select the site, review the evacuation message (a default text is pre-filled — you can customize it), and click **Trigger now** ![Red "Trigger evacuation" button and trigger screen](https://storage.crisp.chat/users/helpdesk/website/-/2/0/a/6/20a671ba57d61a00/screenshot15xpostspark2026-03-_1qgalst.png) ### Method 2: From an Emergency Evacuation QR code 1. Scan the Emergency Evacuation QR code with the phone's camera 2. A confirmation screen appears. Click **Continue** 3. The behavior adapts automatically: * **If an evacuation is already in progress:** you're taken straight to the roll call page. * **If no evacuation is in progress:** a dialog offers to trigger one immediately. Click "Yes, trigger" or "No, view the on-site list". ![](https://storage.crisp.chat/users/helpdesk/website/-/2/0/a/6/20a671ba57d61a00/screenshot15xpostspark2026-03-_1lz0slv.png) **What happens automatically on trigger:** * The list of visitors on site is generated * Notifications go out to Anghello users (email) and secondary contacts (email and/or SMS) * A red banner appears on the check-in kiosk (Spot app) with the evacuation message Even if two people trigger at the same time, only one evacuation list is created. No risk of duplicates. --- ## Running the roll call at the assembly point Several responders can run the roll call at the same time — everything syncs in real time. 1. Open Anghello (via the app, the notification link, or the QR code) 2. Click the "Evacuation in progress" banner if you're not redirected automatically 3. Click **Safe** next to each evacuated person A green indicator appears with an automatic timestamp and the identity of the person who checked them off. ![Evacuation dashboard: real-time statistics, unaccounted-for visitors, progress](https://storage.crisp.chat/users/helpdesk/website/-/2/0/a/6/20a671ba57d61a00/screenshot15xpostspark2026-03-_vqqbok.png) Secondary contacts can view the list and follow progress in real time, but cannot check people off. ## Handling a missing person 1. Click the person's name in the list 2. Review their details: expected host (or point of contact), phone number if collected 3. Call the visitor directly, or contact their host on site 4. If there's no answer: start your internal procedure (alert the rescue team) --- ## Closing the evacuation 1. Once every visitor is checked off, a confirmation dialog appears automatically and offers to end the evacuation 2. Click **Yes, end the evacuation** 3. You can also click the **End** button at the top of the page at any time to close manually | **Important:** The **End** button is available at any time, even if some visitors are not yet checked off (for example, a visitor who left the site without checking out). **Data retained:** full on-site list, roll call statuses with timestamps, identity of whoever checked each person off, trigger message, and who triggered and closed the evacuation. Everything is archived automatically. --- ## The evacuation report Every evacuation generates a report that syncs in real time, then is archived on closure. | Information | Detail | | ---- | | **Header** | Site, date and time of the trigger, who triggered it | | **Message** | The evacuation message entered at trigger time | | **On-site list** | Every visitor checked in on site when the evacuation was triggered: first name, last name, company, expected host, phone | | **Roll call status** | For each person: status ("Safe" or "Unaccounted for"), check-off timestamp, identity of the person who checked them off | | **Timeline** | Trigger time, total evacuation duration, closing time | | **Metadata** | Who closed the evacuation, total number of people on site, number checked off | Reports are available from **Evacuations** > **History** (Administrators and Managers only). They can be used directly for your health & safety committee reports, post-evacuation reviews, and record-keeping for ISO 45001 and labor law requirements. --- ## Related articles * [Set up custom fields](https://help.anghello.com/en/article/add-custom-fields-1sm7vxm/) — Add an "evacuation assistance required" field or other information useful during roll call --- > Next page → [Typical scenarios and maintenance](https://help.anghello.com/en/article/5-typical-scenarios-and-maintenance-g8f1xd/)