> ## Documentation Index
> Fetch the complete documentation index at: https://help.breakpointcrm.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How to Onboard Your Team onto BreakPoint Successfully
> Follow this step-by-step onboarding guide to add workers, pair wearables, configure shifts and zones, and go live with BreakPoint in your facility.
Onboarding your team onto BreakPoint is most successful when you treat it as a four-phase process rather than a single deployment event. Rushing to hand out wearables before your zones, shifts, and alert rules are configured leads to noisy data, frustrated supervisors, and workers who don't trust the system. This guide walks you through every phase — Configure, Pair, Train, and Go Live — so your team is productive and confident from day one.
Before rolling out to your entire workforce, run a pilot with 10 workers across two or three roles for one full week. This lets you validate your zone boundaries, confirm alert thresholds make sense in your environment, and identify any workflow gaps before they affect everyone.
## The Four Phases of Onboarding
BreakPoint onboarding follows a deliberate sequence. Each phase builds on the last, and skipping ahead is the most common source of problems.
Create your organization, add facility locations, and invite your admin and supervisor users before anything else.
Step-by-step instructions for pairing each device to a worker profile and confirming sync status.
Draw hazard zones, entry/exit boundaries, and department areas on your facility map before pairing wearables.
Define alert rules, thresholds, escalation paths, and notification recipients for PulseGuard and TimeKeeper.
***
## Phase 1 — Configure
Complete your Console configuration before a single wearable leaves the box. Doing this first means every device you pair immediately inherits the correct zone boundaries, shift schedules, and alert rules.
**What to complete in Phase 1:**
* Add all facility locations and verify their addresses in the Console
* Draw zones on the facility map — include hazard zones, restricted areas, department zones, and break areas
* Create shift schedules for every team that will use BreakPoint (including overnight and rotating shifts)
* Define alert rules for PulseGuard (proximity and heart rate) and TimeKeeper (missed clock-ins, break violations, overtime thresholds)
* Set escalation contacts for Critical alerts — assign a primary and at least one backup supervisor per zone
* Invite all supervisors and safety managers to the Console and verify they can log in
You must define shifts before pairing wearables. If workers are paired without an assigned shift, TimeKeeper cannot calculate break compliance or flag overtime correctly, and you will need to retroactively correct records.
***
## Phase 2 — Pair
With your configuration in place, you can pair wearables to workers in batches. Working in groups of 10–20 at a time keeps the process manageable and lets you catch device issues before they multiply.
**What to complete in Phase 2:**
* Retrieve wearables from inventory and charge all devices to 100% before pairing sessions
* Pair each wearable to the correct worker profile in the Console — double-check names and employee IDs
* Assign each worker to their shift schedule and home zone
* After pairing, have each worker walk through at least one zone boundary to confirm entry and exit events register correctly
* Verify heart rate data appears in the Console within two minutes of the worker wearing the device
* Flag any devices that fail sync or show abnormal readings for replacement before go-live
Never assign one wearable to multiple workers, even temporarily. BreakPoint uses device-to-worker pairing for all TimeKeeper records and PulseGuard alerts. Sharing devices will corrupt attendance logs and produce inaccurate safety data that cannot be retroactively corrected.
***
## Phase 3 — Train
A 15-minute worker orientation is all it takes to set expectations and prevent the most common support questions. Workers who understand what the wearable does and what the alerts mean are far less likely to remove or ignore their device.
**What to cover in your worker orientation:**
* **Wearing the device** — show workers how to put the wearable on correctly, how snug it should fit for accurate heart rate readings, and how to charge it at the end of a shift
* **Tap gestures** — demonstrate the tap-to-confirm gesture workers use to acknowledge proximity alerts, and the double-tap for manual check-ins if your facility uses them
* **What alerts mean** — explain that a vibration alert means they should move away from a hazard zone or that a supervisor has been notified; workers should never panic but should act promptly
* **Privacy expectations** — be transparent that location data is used for safety and attendance, who can see it, and how long it is retained; workers who understand the "why" are more cooperative
* **What to do if the device malfunctions** — direct workers to their supervisor immediately rather than continuing their shift without it
Record your orientation session or create a one-page reference card workers can keep. This dramatically reduces repeat questions during the first week and helps you onboard new hires faster in the future.
***
## Phase 4 — Go Live
Go-live week is not the finish line — it is your most important observation window. Plan to check the Console at least twice daily during the first week and treat every unexpected alert as a signal worth investigating rather than dismissing.
**What to do during Go Live week:**
* Monitor the live workforce map each morning and afternoon for the first five days
* Review the alert log daily — look for clusters of alerts in the same zone or from the same worker, which often signal a threshold or zone boundary that needs adjustment
* Check Device Health in the Console to confirm all paired devices are syncing and battery levels are healthy
* Collect feedback from supervisors and workers after the first two days — small friction points are much easier to fix now than after a full rollout
* Make one configuration change at a time so you can clearly attribute any improvement or regression
Schedule a 30-minute debrief with your supervisors at the end of go-live week. Review what the data showed, which alerts fired correctly, and which thresholds may need tuning. This habit, carried into weekly operations, is what separates teams that get real value from BreakPoint from those that stop checking the Console after month one.
***
## Onboarding Checklist
Use this checklist to confirm you are ready before go-live. Every item should be checked before your first production shift.
**Console Configuration**
* [ ] All facility locations added and verified
* [ ] Zone map complete — hazard, department, and break zones defined
* [ ] All shifts created and assigned to the correct worker groups
* [ ] PulseGuard alert thresholds configured for each zone
* [ ] TimeKeeper rules set for clock-in grace periods, break durations, and overtime limits
* [ ] Escalation contacts set with at least one backup per Critical alert rule
* [ ] All supervisors and safety managers invited and able to log in
**Wearable Pairing**
* [ ] All wearables charged to 100%
* [ ] Every active worker paired to a unique device
* [ ] Each worker assigned to correct shift and home zone
* [ ] Zone boundary walk-through completed and events confirmed in Console
* [ ] Heart rate data visible in Console for all paired workers
* [ ] Faulty or unresponsive devices flagged and replaced
**Training**
* [ ] Worker orientation completed for all shifts
* [ ] Workers can demonstrate correct tap-to-acknowledge gesture
* [ ] Workers know what to do if their device malfunctions
* [ ] Supervisors have reviewed the Console alerts dashboard and understand escalation flow
**Go Live**
* [ ] Pilot results reviewed and configuration updated
* [ ] First-week monitoring schedule confirmed with supervisors
* [ ] End-of-week debrief meeting scheduled
***
## Common Onboarding Mistakes to Avoid
Even well-prepared teams run into the same pitfalls. Knowing these in advance helps you sidestep them entirely.
Zone boundaries that look correct on the map often have small gaps or overlaps that only show up when workers actually walk through them. Always complete a physical walk-through of every zone boundary with a paired device before going live. A five-minute walk prevents hours of data cleanup.
TimeKeeper requires a shift assignment to calculate break compliance and overtime. If you pair wearables and start collecting attendance data before shifts are defined, those records are incomplete and cannot be fully reconstructed. Configure all shifts first, even rough ones you plan to refine later.
Workers who don't understand what the wearable does will remove it, wear it incorrectly, or ignore alerts — all of which degrade your data quality and safety coverage. The 15-minute orientation is not optional. Even a brief verbal explanation with a demo is far better than handing out devices with no context.
When something isn't working as expected, the instinct is to fix everything at once. Resist this. Change one threshold, one zone boundary, or one alert rule at a time, and observe for at least one full shift before making another change. Otherwise you won't know which change made the difference.
***
## Quick Onboarding Steps
Add locations, draw zones, create shifts, define alert rules, and invite your supervisors. Do not skip any of these — each one is required for the next phase to work correctly.
Work through your device inventory in groups of 10–20. Pair each device to the correct worker profile, assign their shift, and confirm zone events and heart rate data appear in the Console.
Hold a 15-minute orientation for each shift group covering how to wear the device, tap gestures, what alerts mean, and who to contact if there is a problem.
Select 10 representative workers across roles and run a full week of live monitoring. Review alert patterns, gather feedback, and tune your configuration before expanding to the full team.
Launch across your full workforce. Check the Console twice daily during the first week, review the alert log daily, and hold a debrief at the end of the week to lock in any final configuration changes.
## Related topics
- [Set Up Your BreakPoint Account, Team, and Locations](/getting-started/setup-your-account.md)
- [How BreakPoint Works: Wearable, Cloud, and Console](/getting-started/overview.md)
- [BreakPoint: Real-Time Safety and Workforce Visibility](/introduction.md)