Articles on: Evacuation Management

5. Typical scenarios and maintenance

For: QHSE Managers, Safety Officers, Site Managers
Application: Admin (app.anghello.co)
Estimated time: 4-minute read



Scenarios


The setups below illustrate common situations. Every site is different — adapt them to your organization and your constraints in the field.


Scenario 1: Daytime evacuation with staffed reception


Context: site with a reception desk, office hours, front desk staff present, QHSE manager on site.


Setup: 1 Manager account (QHSE), 1 Receptionist account (front desk staff), secondary contacts: first aiders, management.


How it plays out: the QHSE manager or reception triggers from their account. Several responders run the roll call at the same time.


Scenario 2: Evacuation after hours / on rotating shifts


Context: production site with shift work, no reception desk, rotating teams.


Setup: 1 Manager account (QHSE, overall supervision), 1 personal Evacuation account per shift leader (3 accounts for 3 shifts), 1 QR code Evacuation account in the evacuation pack (fallback), secondary contacts: on-call staff, management.


How it plays out: the shift leader triggers from their personal account. If they can't sign in, the QR code in the pack serves as backup. The QHSE manager gets the notification and can follow remotely.


Scenario 3: Multiple assembly points


Context: large site with several buildings and separate assembly points.


Setup: the usual Manager and Receptionist accounts + 1 QR code Evacuation account per assembly point, explicitly named: "Evac - North Point", "Evac - South Parking".


How it plays out: each responder scans the QR code at their assembly point. Everyone checks people off on the same list, synchronized in real time. The account names provide traceability (e.g. "Visitor ABC checked off by Evac - North Point").


If your site has a single assembly point, one QR code is enough.


Scenario 4: Planned evacuation drill


Anghello makes no technical distinction between a drill and a real evacuation. To tell them apart:


  • Customize the trigger message: "Planned drill - No real emergency"
  • Warn your secondary contacts beforehand to avoid confusion
  • After the drill, use the archived report for your post-exercise review


Use drills to test every access method: have different responders scan the QR code, sign in via the notification link, and run the roll call simultaneously.



Maintenance and continuous improvement


Quarterly checks


  • Check that notification email addresses and phone numbers are up to date
  • Check that the QR codes in the evacuation packs are still readable (wear, weather)
  • Test a QR code scan to confirm the account is still active
  • Check network coverage at the assembly point
  • Delete Evacuation accounts that are no longer used
  • Update the secondary contact list (departures, role changes)


After every drill or real evacuation


  • Review the archived report in Anghello
  • Assess the time to access the list, the time to complete the roll call, and the total duration
  • Check that all notifications arrived on time
  • Identify improvement points (untrained people, network issues, unreadable QR code)
  • Update your procedure if needed


Make it official


Update your internal evacuation procedure to include Anghello: document the access methods you chose, the associated roles, and where the QR codes are stored on site. The more people are trained, the less the system depends on a single person.


Make sure you receive Anghello's notification emails — they come from the same sender as visitor arrival notifications.


You're ready. Try it at your next drill, and contact us if you have any questions — we're here to help.


On the roadmap


We're working on several evacuation-related improvements. Contact us if one of these matters for your site — your feedback helps us prioritize:


  • Including internal staff in the evacuation report
  • Printing the evacuation list for a complementary physical copy
  • Post-closure status (error/cancellation, drill, real evacuation) with an after-the-fact comment






Next page → Evacuation QR code best practices

Updated on: 27/07/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!