Evacuation Roster

What you can build

• Muster from Kisi presence and Deputy rosters

  When the alarm fires, Kisi presences and today's Deputy roster become one muster list per floor in Microsoft Teams, and everyone still unaccounted gets a Twilio text asking where they are.

  With Kisi, Deputy, Microsoft Teams, Twilio

• Use Gallagher muster readers

  Reads at the Gallagher Command Centre readers you mark as muster points check people off as they arrive. The flagged list in Slack shrinks in place as reads come in.

  With Gallagher Command Centre, Slack

• Include today's guests

  Verkada Guest visits for the day are added to the list with their host, so the host is asked in Teams about a guest who has not been seen.

  With Verkada, Microsoft Teams

• File the roll call

  After the all-clear, the operator proposes the roll-call record, with each name, last Brivo read, and check-off time, as rows in Google Sheets for the emergency action plan file.

  With Brivo Access, Google Sheets

Requirements

• One access control connector with in and out reads or presence: Kisi, Brivo, Avigilon Alta, or Gallagher Command Centre
• One scheduling connector for who was expected: Deputy, When I Work, or Connecteam
• One messaging connector for wardens: Microsoft Teams or Slack, and Twilio for SMS to people
• A trigger for the alarm: an access platform alarm event, a building platform fire point, or a webhook from your panel

Authentication

Reads presence, shifts, and visits through the connectors you bind and their service accounts, and sends lists and messages through the messaging connectors' credentials; it holds none of its own.

Limits

• No visitor management connector is in the catalog. Fibric links yours on request; until then, visitors come from Verkada Guest or a sheet
• Presence is only as good as exit reads. A site without out-readers or anti-passback shows people who left hours ago as still inside
• It builds and updates the list. Wardens decide who is accounted for, and people call the fire service
• It never triggers or silences an alarm, and it never releases or locks a door

Questions and answers

What do wardens approve, and when?

The muster list before it is sent, then each update. Wardens check people off, correct the list, and approve the SMS to the unaccounted. The roll-call record is approved by the incident lead. Nothing goes out unreviewed.

What is filed after the all-clear?

One receipt per alarm: the trigger, who was on the list and from which source, each check-off with who made it and when, the messages sent, and the final roll call. It stays with the alarm, drill or real.

Can it run for a drill?

Yes. Trigger it from a drill event and it builds the same list, sends the same messages if you approve them, and files the same roll call, marked as a drill. Nothing in the access platform is changed.