BadgeR+ Deployment: Large-Scale Testing Tips

Pre-Test Staging: Confirm all devices have passed the "4 green blinks" verification in a controlled environment before distributing them for the mass test.

Incident Routing Verification: Before the test, visit the configuration page to verify that the Incident Type (e.g., DRILL) is toggled ON and correctly routed to the intended recipients.
Support Admin: Establish a central Admin users can contact, or bring any device that displays an unconfigured RGB cycle or an error code (Red, Orange, Pink, Yellow) during the test.
The Portal Audit: After the exercise, use the 'Active Buttons' tab to verify that every intended device successfully registered an alert and check for any low-battery triggers (below 3.50V) caused by the high activity.
Verification of Reset State: Remind administrators that if a device was reset during the test, it must be re-paired via the portal before it can send alerts again.

Conducting Large-Scale Device Testing

Overview

When planning a large-scale system audit, the goal is twofold: ensuring your Safety Team has total confidence in the data being captured, and ensuring your End Users feel confident in the solution they carry.

To set your organization up for success, we have curated a set of operational best practices derived from successful deployments. A well-organized test is defined by who is testing, when they are testing, and how the data is verified.

Pre-Test Planning & Logistics

1. Define the Roles

The Test Administrator(s): The Safety Team members responsible for monitoring the Dashboard and verifying signals via the Active Buttons tab.
The Participants: The team members activating their BadgeR+ devices.

2. Establish Time Blocks & Cohorts Organize your participants into logical groups (e.g., by Department, Role, or Building Location) and assign specific calendar holds.

Example Schedule:
- 09:00 AM – 09:30 AM: XYZ Department
- 09:30 AM – 10:00 AM: XYZ Department

3. Resource Distribution & Training When sending the calendar invite, including links to End User Resources (videos/guides) is a great way to confirm confidence and understanding.

💡 Pro-tip!

Use this time block to confirm that users have viewed the materials and offer a brief Q&A window. This ensures every team member has visibility into the training materials before the BadgeR+ devices go live

Execution & Data Integrity

Organizing the test by time block is not just a scheduling preference; it is a data integrity strategy.

3. Controlled Verification Testing in smaller, scheduled blocks allows the Administrator to focus on a manageable list of incoming signals in the Active Buttons tab.

Documentation & Compliance

A successful test provides necessary documentation for Administration or future compliance requests.

Creating the Audit Trail By utilizing the Time Block method and a Device Audit Log, you generate a clear historical record of:

Which devices were tested.
Who verified the signal.
The exact date and time of verification.

This documentation is critical for internal safety audits and provides stakeholder assurance that the fleet is fully operational.

💡 Tool Tip:

Utilize your Onboarding Playbook to manually check off each BadgeR+ ID. This creates a physical paper trail confirming that the device was tested and verified by a Portal Admin.

Don't have this resource on hand? Contact your Account Manager to receive a copy of the testing template.

Sustainment Strategy

A successful launch is just the beginning.

To maintain system health, consider defining your long-term Portal Management: How often will the Admin team review the Active Devices tab to check for low batteries or offline devices outside of scheduled drills?

Recommendation: We suggest establishing a recurring "System Health Check" on the calendar to ensure your data remains pristine year-round.