Test Mode vs. Drill Mode: Which Should I Use?

Audience: Portal administrators, security leaders, dispatch supervisors, implementation teams

Overview

911Cellular provides both Test Mode and Drill Mode so customers can validate different parts of an emergency workflow without treating every exercise like a live incident.

The most important difference is the amount of downstream activity each mode is designed to exercise.

Use Test Mode when you want a lower-impact check of panic activation, routing, labeling, and dashboard visibility.

Use Drill Mode when you want a more realistic exercise that can include configured responder notifications or other downstream actions.

Test Mode: best for controlled connection and routing checks

A test applies to the selected security zone and its descendant zones for the duration of the test. Matching panics are marked as test incidents.

In the current documented behavior, Test Mode is designed not to exercise Emergency Response Team notifications, zone phone calls, or asynchronous panic follow-up such as panic-triggered workflows and integrations.

Test Mode is a good choice when you want to verify:

- A panic button or application can successfully submit an activation.

- The activation is associated with the expected institution and security zone.

- The incident appears in the expected portal or dispatcher view.

- The displayed user, device, incident type, and location are correct.

- A newly installed or relocated device is communicating as expected.

Because Test Mode is intentionally lower-impact, it should not be used as proof that responder messages, zone phone calls, relays, integrations, or panic-triggered mass notifications are working.

Drill Mode: best for planned response exercises

Drill Mode is designed for more realistic exercises. A drill also applies to the selected security zone and its descendant zones.

Drill behavior is configurable. Depending on the drill settings and panic type, a drill can exercise selected downstream actions such as responder notifications, zone phone calls, relays, or integrations. Drill communications can use drill wording so participants know the event is an exercise.

Drill Mode is a better fit when you want to validate:

- Dispatcher and responder workflow.

- Configured responder notifications.

- Zone phone-call behavior.

- Selected relays or integrations.

- A planned exercise that needs to produce drill history or reporting.

Do not assume every downstream action runs automatically in Drill Mode. The exact behavior depends on the drill configuration and the workflows enabled for the customer.

Before starting either mode

1. Define the exact purpose of the exercise.

2. Choose the security zone that should be included.

3. Confirm whether descendant zones should also be in scope.

4. Identify which notification, integration, relay, or phone-call paths should be part of the exercise.

5. Notify anyone who could receive drill communications.

6. Confirm the exercise plan with the customer’s designated safety lead.

7. Record the expected device, location, incident type, recipients, and pass criteria.

Choosing the right mode

Choose Test Mode if your goal is primarily to confirm device/application communication, location, routing, or incident visibility.

Choose Drill Mode if your goal is to rehearse a broader response workflow and you have intentionally configured which downstream actions are appropriate for the exercise.

After the exercise

Review the drill/test history and compare the result with the pass criteria you defined before starting. Capture the activation time, device or computer identifier, security zone, incident type, expected result, actual result, and any visible error for follow-up.

Internal validation before publication: confirm final customer-facing UI labels, the production Drill Mode options, and whether all panic-origin types use the same Test Mode behavior.