Emergency Headcounts and Mustering

At any point, whether at a place of business, an event, or a school, a disaster may strike. When it comes to dealing with the unexpected, the most important thing is to be prepared. For workplaces, schools, and events large enough, these preparedness plans might be required by law. With that in mind, having a preparedness plan in place for these unexpected disasters will help everyone get to safety, and in some cases, save lives.

Captains and Drills

Whether it’s a supervisor, a CEO, or an administrator, someone will need to establish a clear chain of command. What that means is that someone will need to be appointed to be “in charge”. Usually, in regard to a preparedness plan, a “captain” will be placed in charge in the event of an emergency, with a “second” or sub-captain in place as well. Sometimes, with large scale evacuations, multiple captains should be in place. In the case of schools, this will almost always be a teacher, or multiple teachers.

This chain of command should be established and practiced during drills. Drilling will allow the emergency mustering process to go smoothly when a real emergency occurs. According to OSHA, workplace emergency drills should be conducted “as often as necessary to keep employees prepared.”

Where codeREADr comes in

codeREADr allows for mustering and roll call to be easily accomplished. We suggest importing the values of the IDs you will be scanning. This can be either all IDs, or who you expect to be there. For a more detailed approach, check this page.

Alternatively, the service can be configured to only read the ID number. No personal information has to be imported at all. This can be used to later compare scan records with offline databases or Excel sheets.

In addition, codeREADr can also integrate with third party attendance systems. We suggest either utilizing Zapier or connecting through our API. A web developer may be required for these options.

Then in the event of an emergency, everyone will be checked in again by a captain or sub-captain with a device.

codeREADr Mustering Basics

An emergency mustering service with codeREADr can be simple to set up. Here’s a quick rundown of how the platform could work:

upload database

Upload a Database

First, a validation database is imported and filled with values of those who will be scanned.

create a service

Create a Service

Second, create and associate an attendance service to the database to validate against.


Scan Attendees

Third, scan in the “attendees”, which could be employees, students, or guests.


Scan Attendees Again

Next, with the initial attendees accounted for, a master list will be composed. When the time calls for mustering, the attendees can be scanned again


Verify who is Present

Finally, the service compares against those who are present and those who were expected to be present. This will show who is present and who is “absent.”

Appointing a Mustering Ground

There should be designated areas to muster in and then conduct an emergency headcount. Different staff members might arrive at different points of evacuation. There needs to be at least one captain with a device at each location, or a sub-captain with a device. That way, everyone can be checked in when they arrive. Selecting a point, or multiple points, to muster in is central to being able to gather up everyone who should be present, and then figure out who might be missing.

Identification and Guests

Staff, attendees, or students will have to be scanned in and out in order to have the roll call function well. In order for the mustering application to be of use, you’ll need a list of which people are there on that given day, on site. Another hurdle is the presence of guests. Guests have to be registered or taken into account somehow, we suggest with guest-specific ID badges or cards. You can also use designated guest passes that aren’t linked to anyone specific, but are scanned in on a provisional basis.