Skip to content
emergency notification system
Juliet HulseDec 19, 2018 11:54:40 AM9 min read

Best Practices for Testing Your Emergency Notification System

When was the last time you exercised your emergency mass notification system? Six months ago? A year? Since no two organizations are exactly the same, it’s up to you to discover the best interval for testing your emergency notification system (ENS). Taking a look at how other organizations test their systems; however, can be quite helpful when making decisions regarding how your emergency reporting works.



Testing the ability of your systems and infrastructure to effectively handle the high volume of traffic that an emergency situation generates is important. Compare your emergency response strategy to a fire drill; you’re not just measuring how fast the word gets out, you are also making sure that the people recognize what the siren means and are prepared to take the appropriate action. Testing also allows you the opportunity to document and analyze the success of each emergency notification system endpoint to better understand the most effective methods for communicating with your population.


Having a scheduled and documented testing plan helps guarantee that, in the event of an actual emergency, your people will receive the message and respond to it appropriately. Testing your emergency plan will help prepare you for when a real emergency occurs and gives you the opportunity to troubleshoot any problems that may occur before a possible life or death situation arises. Exercising is also a chance to raise awareness of how an alert will appear to a recipient and potentially increase participation/enrollment.



We randomly polled emergency administrators across the country and compiled the results to look for some true “best practices.” The polling provided the results and some trends were very easy to spot.


  • The vast majority (82%) of organizations test their emergency notification system regularly. Of the 18% of organizations that do not test, half of them expressed an interest in a testing procedure, but simply do not have the time or resources to put a plan together at this time.


  • Forty-four percent (44%) of the total polled test their emergency notification system twice a year; with a smaller amount (14%) testing once per month. Some organizations polled (16%) have a testing plan in place, but test “as needed,” rather than on a schedule.


  • A full sixty-two percent (62%) perform a “full test” during the year, sending SMS and emails to all users, rather than a limited “test list.” Of those, 8% perform additional testing at other times during the year, but send messages to a limited testing group during this additional testing.



For the most part, the criteria for a successful test differed from organization to organization. Most also differ in how they respond to their testing results. Many of the administrators stated that they do not review the results in any way and simply leave it up to their population to verify that they received the message. Several also stated that the email and SMS tools “simply work,” so there is no need to review the results.

Other organizations simply look for a successful send as their testing “goal,” and if the message appears on all of their endpoints... posting to Twitter or Facebook, appearing on their website or digital signage, or setting off the sirens... then they consider the test a success.

Of those that do use delivery statistics to analyze the results, testing is usually followed by a questionnaire, or mass email requesting that the “failed” users modify their account settings or contact a support department for assistance.


Testing your emergency notification system will help keep your team’s skills sharp and allow you to troubleshoot any problems before an actual emergency occurs. Keep in mind, it’s not just about testing your emergency services, it’s also about testing your infrastructure and connected devices, your internal team and processes, as well as managing your population’s expectations of your emergency response plan.


Testing the functionality and the response that it elicits is important as well. If you push messaging to physical devices, such as PC desktops, loudspeakers, or digital signage, you’ll want to verify that those connections are still configured properly and that your community recognizes that emergency messaging may/will appear there. Testing is as much the ability to make communities prepare for an emergency and how they should recognize an emergency situation, as it is about testing your emergency notification system.

We advise that you perform a “full test” on all of your users regularly, but no more than 3-4 times per year. Sending a full test about twice a year seems to be the “sweet spot” for testing. More than a few tests a year to your full user-base could lead to people ignoring real threats or seeing your alert messages as SPAM and unsubscribing altogether. It’s important to balance the benefit of your system tests versus the possible backlash.


Now that you’ve completed your test, what’s next? After your tests have been performed, it’s important to review your results. You can use emergency reporting, send out post-test surveys, or simply review feedback left by email. But how do you gauge success or failure? How many of your text messages, emails, etc. are delivered? Why are there some failed deliveries?

Obviously, with any mass communication, some messages just won’t get through. People change their email address, go over their mail quota, etc. Some mobile phones will be out of range, have changed carriers, or canceled texting altogether. In a system test, you should expect to see some emails and texts rejected. That’s why your tests should include all of your endpoints in your alerts. The more communication channels you use, the more likely a user is to receive the message.

The key to interpreting your results is to look for trends. If the same mobile carrier always seems to reject texts, it may indicate a problem in your area that can be addressed. If a large number of emails on your organization’s domain show up as rejected, you may need to double-check your spam filter. If a large number of voice calls show up as “busy”, you may be overwhelming your local phone lines. Your delivery status and user feedback can help you troubleshoot all of these situations.

In a general sense, if delivery (text, email, or voice calls) is above 90% success (Accepted, Delivered, etc), your stats are in the normal range. In many of our case studies, we’ve seen texting success rates of 95% or higher, which is outstanding for any mass communication on any medium.


System tests are also a great time to review your emergency guidelines with your administrators before an emergency happens. They may know how to initiate a message, but do they know when to use it? Do they know what to type and which group(s) to select? Regular refresher training makes sure that your team knows what to do when a real emergency occurs.