Skip to main content
Whether you are evaluating BreakPoint for your facility, just completed your onboarding, or are troubleshooting a specific situation, this FAQ covers the questions our customers ask most often. Answers are organized by topic — jump to the section most relevant to what you need, or read through the full page to get a comprehensive picture of how BreakPoint works in practice.

​
Getting Started

Most facilities complete initial Console configuration — including locations, zones, shifts, and alert rules — in two to four hours. Pairing wearables to workers takes roughly three to five minutes per device, so a team of 50 workers typically requires a half-day pairing session. Add time for worker orientation (about 15 minutes per shift group) and a brief pilot run, and most teams are fully live within one to two weeks of receiving their hardware. Larger facilities with multiple locations or complex shift structures may benefit from spreading configuration across two or three sessions rather than doing it all in one day.
No. Workers do not need a smartphone or any app to use BreakPoint. The wearable device operates independently and communicates directly with the BreakPoint network. All monitoring, alerts, and data happen automatically once the device is paired and worn. Supervisors and managers access the BreakPoint Console through a web browser on any device — no desktop application installation is required on their end either.
Report the lost or damaged device to your Console administrator as soon as possible so it can be deactivated and removed from the active fleet — this prevents the device from generating spurious data if it ends up somewhere unexpected. Replacement devices are available through your BreakPoint account portal; once your replacement ships, pair it to the worker’s existing profile and their history and settings carry over automatically. Your BreakPoint plan includes a specified number of replacement devices per year; contact Support for details on coverage limits and out-of-warranty replacement pricing.
Yes. BreakPoint is designed for multi-location operations. Each facility gets its own location entry in the Console with independent zone maps, shift schedules, and alert rules, but all locations roll up into a single organizational account. Supervisors can be granted access to one location, multiple locations, or all locations depending on their role. Reporting can be run per location or aggregated across your entire organization, making it straightforward to compare safety and attendance performance across sites.

​
PulseGuard

PulseGuard is designed to operate in industrial environments where metal structures, heavy machinery, and radio frequency interference are common. The system uses a combination of signal technologies and is calibrated to compensate for typical industrial interference patterns. In extremely dense metal environments — such as enclosed steel tanks or very large server rooms — you may experience some reduction in proximity detection accuracy near the affected structure. BreakPoint’s onboarding team can advise on optimal device placement and zone configuration strategies for challenging RF environments during your setup.
The Console detects when a paired wearable has been removed or is no longer registering biometric data, and generates a Device Removed alert for the assigned supervisor. The alert includes the worker’s name, device ID, last known zone, and the time the removal was detected. Supervisors can configure the severity and routing of Device Removed alerts in the Console. BreakPoint does not enforce wearable use — that remains a workplace policy and supervisory responsibility — but the platform ensures you are notified promptly so you can address it.
BreakPoint wearables use optical heart rate sensors validated to within ±3 BPM under normal wearing conditions with good skin contact. Accuracy is highest when the device is worn snugly on the wrist or upper arm as directed — a loose fit reduces optical sensor contact and can introduce measurement variance. Intense physical movement, very cold temperatures, and certain skin conditions (such as heavy callusing or very dark tattoos over the sensor area) can affect accuracy in isolated cases. For workers in roles where heart rate monitoring is safety-critical, we recommend verifying the sensor reading against a manual pulse check during your initial pairing session.
No. PulseGuard is a real-time monitoring and alerting layer designed to complement your existing safety program — not replace it. Your facility’s safety procedures, PPE requirements, equipment operating rules, and emergency response protocols remain fully in effect. PulseGuard adds visibility that helps supervisors respond faster when something goes wrong and helps safety managers identify patterns that written procedures may not catch. Regulatory compliance (OSHA, local safety codes, industry standards) is determined by your procedures and training program, not by monitoring technology alone.

​
TimeKeeper

Yes. Supervisors with the appropriate Console permissions can create, edit, or void TimeKeeper records for workers under their supervision. To correct a missed clock-in, navigate to TimeKeeper → Attendance Records, locate the worker and date, and use the Edit Record option to add the correct clock-in time and a brief correction note. Manual corrections are logged with the supervisor’s name, timestamp, and note for audit purposes, so there is a clear record of what was changed and why. Only users with Supervisor or Administrator roles can make manual corrections — workers cannot edit their own records.
BreakPoint exports attendance and hours data in CSV format compatible with most major payroll platforms including ADP, Paychex, Gusto, and Workday. The CSV export combined with your payroll system’s import function handles the data transfer reliably for most teams processing payroll weekly or bi-weekly. If you need help mapping BreakPoint’s export columns to your payroll platform’s import format, contact BreakPoint Support — the team can provide field mapping guides for common platforms.
If a worker’s wearable registers a clock-in event but the device’s location is outside the configured clock-in zone, TimeKeeper flags the record as an Out-of-Zone Clock-In and notifies the assigned supervisor. The clock-in is recorded but marked for supervisor review — it does not automatically approve or reject the time. Supervisors can then approve the record (for legitimate cases like a worker who checked in from a nearby staging area) or void it and request the worker repeat the clock-in from the correct location. You can configure the notification sensitivity and review workflow for out-of-zone events in your TimeKeeper settings.
When a supervisor updates a worker’s shift assignment mid-week in the Console, TimeKeeper applies the new schedule from the effective date forward and retains the original shift assignment for all prior records in that pay period. This means historical attendance records are not retroactively altered — you can always see what shift the worker was scheduled for on any given day. If a mid-week change affects overtime calculations for hours already worked earlier in the week, TimeKeeper recalculates the full week’s totals using the applicable shift rules and flags any records affected by the change for supervisor review.

​
Account & Privacy

Worker location data is only accessible to users with an active BreakPoint Console account and the appropriate role permissions within your organization. By default, Supervisors can see location data for workers assigned to their zones and shifts; Administrators have organization-wide access. Workers do not have Console access and cannot view their own location history through BreakPoint. Your organization’s Administrator controls all role assignments and can audit which users have viewed location data through the Console’s Access Log under Account Settings → Security.
BreakPoint retains all worker data — including attendance records, safety alerts, location history, and biometric readings — for 12 months by default on Standard and Business plans. Enterprise plans include configurable retention periods of up to 7 years to support organizations with extended compliance or legal hold requirements. When a worker is removed from your account, their historical data is retained for the remainder of your active retention period and then permanently deleted. You can export a complete archive of any worker’s data at any time before deletion through Account Settings → Data Export.
Yes. You retain full ownership of all data your organization generates on BreakPoint. At any time — including during an account cancellation — you can request a full data export from Account Settings → Data Export, which packages all attendance records, safety incident logs, alert histories, and configuration data into downloadable CSV and JSON files. BreakPoint processes data export requests within 5 business days. After your account is closed, your data is retained for 90 days to allow for any final exports before being permanently deleted from BreakPoint’s systems.
Organization Administrators can manage all user accounts from Account Settings → Team Members. To add a supervisor, click Invite User, enter their email address, select the Supervisor role, and assign them to the appropriate locations and zones. They will receive an email invitation to set up their login. To remove a supervisor, locate their account in the Team Members list and click Deactivate Account — this immediately revokes their Console access and removes them from all alert escalation rules they were assigned to. Deactivated accounts are retained in your audit log but can no longer log in or receive alert notifications.