LONEALERT historically connected worker devices and check-in timers to the OWL portal. Its current official notice directs customers and new enquiries to Peoplesafe. Existing customers should review their actual Nexus configuration, transferred records and response contacts instead of assuming every former OWL function migrated unchanged.
Built from vendor sources checked ; AI-assisted drafting. Documentation review, not a hands-on test. How pages are made
Lone Worker Safety
Existing LONEALERT customers checking their Peoplesafe transition and support arrangements. Legacy OWL and device pages remain accessible, but they do not establish current standalone LONEALERT availability or unchanged Nexus functionality. Treat every current Peoplesafe app, device, ARC, tracking, report and roaming feature as conditional on the migrated contract, chosen product and account configuration. A working communications route is required for alarm delivery; GPS, Wi-Fi positioning and What3Words do not replace mobile/data connectivity. Device and app assignments must identify the worker, escalation plans and contacts must be current, and planned alarm tests must be agreed so they do not trigger an unintended emergency response. Location access should be role-restricted and explained to workers; app permissions, MDM settings, battery state, signal and OS compatibility can affect operation. Monitoring technology supports but does not replace the employer's lone-worker risk assessment, procedures, training or emergency planning.
Evaluate the current migration contract and replacement-device costs before extending a legacy arrangement.
Sources checked .
The official LONEALERT site says customers have migrated to Peoplesafe Nexus and LONEALERT will shortly cease to operate. This is therefore a legacy/migration profile, not a representation of OWL as a current standalone purchase. Current Peoplesafe app, device, portal and Alarm Receiving Centre capabilities are relevant replacement evidence, but a migrated customer's actual devices, subscriptions, settings, records and entitlements must be reconciled in writing.
| Capability | Evidence | Scope and source |
|---|---|---|
| Migration to Peoplesafe Nexus | Documented by vendor | The official LONEALERT notice says customers have migrated to Peoplesafe Nexus and LONEALERT will shortly cease operating. It does not enumerate account-level records, device compatibility or preserved feature settings. Official migration notice and current enquiry routes |
| Legacy OWL timers, check-ins and alerts | Depends on scope | Legacy OWL material documents timers, check-ins and alerts. Use it only as a migration checklist and demonstrate the corresponding current Nexus/product workflow rather than assuming identical behavior. Legacy OWL portal and timer documentation |
| Legacy device continuity | Not verified | The historical device catalogue does not identify which models remain supported, replaced, reconfigured or commercially covered after migration. Obtain a device-by-device support statement. |
| 24/7 monitored alarm response | Depends on scope | Peoplesafe documents a 24/7 Alarm Receiving Centre that assesses alarms and follows pre-agreed escalation instructions. Confirm that ARC monitoring is active for every migrated device/app, region and working schedule. Current Peoplesafe Alarm Receiving Centre processCurrent Peoplesafe service and portal scope |
| SOS alarm and two-way audio | Depends on scope | Current Peoplesafe app and device pages describe SOS activation and an audio channel to the ARC. Availability and audio behavior depend on the selected product, permissions, signal and account setup. Current Peoplesafe lone-worker app featuresCurrent Peoplesafe device scope and optional features |
| Timed activities, check-ins and welfare checks | Depends on scope | The current app documents timed alarms, check-in/out and scheduled welfare checks. Verify which functions are enabled for each migrated group and how expiry is escalated. Current Peoplesafe lone-worker app features |
| Fall or man-down detection | Depends on scope | Supported app and device configurations can include fall detection. It is not evidence that every legacy device, worker activity or fall pattern is covered; test product-specific sensitivity and cancellation behavior. Current Peoplesafe lone-worker app featuresCurrent Peoplesafe device scope and optional features |
| Emergency location context | Depends on scope | Supported products can use GPS, Wi-Fi, mobile-network data and What3Words to assist location. Accuracy and transmission depend on the product, permissions, environment and communications path and are not guaranteed by the marketing figures alone. Current Peoplesafe service and portal scopeCurrent Peoplesafe lone-worker app features |
| Nexus user and asset assignment | Depends on scope | Nexus supports assigning, swapping and unassigning devices for activated users. Reconcile serial numbers and profiles because correct assignment lets the ARC identify who raised an alarm. Nexus device assignment and reassignmentNexus onboarding, escalation and asset-assignment guidance |
| Escalation and response-plan configuration | Depends on scope | Nexus onboarding guidance documents escalation plans and alarm-response plans. These require customer configuration and maintenance; the platform does not supply accurate contacts or organization-specific emergency procedures automatically. Nexus onboarding, escalation and asset-assignment guidance |
| Role-based Nexus access | Depends on scope | Nexus documents restricted User access to the user's own profile/device while management functions depend on other roles. Validate administrator and manager permissions and separation of duties in the migrated tenant. Nexus user-role access boundaries |
| Location-access controls | Depends on scope | Nexus can restrict map access by role, and Peoplesafe recommends transparent policies. Confirm collection mode, role visibility, retention and lawful-use controls rather than assuming location is visible only during emergencies. Nexus location-access restrictionsPeoplesafe location privacy explanation |
2 additional areas. Status describes reviewed sources, not hands-on performance.
Also watch for: Procurement should confirm configuration, support, data handling and the complete commercial scope.
Custom quote
On 26 September 2026 the LONEALERT site offered "Get a quote" and trial routes and shows no amount; lonealert.co.uk/pricing/ returned page not found and the site search for "price" returned only the terms and conditions of sale. Contact Peoplesafe for a migration or replacement quote covering retained devices, replacement hardware, monitoring, training, historical records, contract term and renewal. Older OWL prices and trial buttons should not be treated as a current offer.
Pricing sources checked : Selected sources checked; no starting price recorded. The current migration notice supersedes legacy sales assumptions.
Legacy LONEALERT-to-Peoplesafe Nexus migration and continuity checks, with separately scoped current Peoplesafe app, device, portal and monitored-response services.
Ask the vendor to identify the product, region, modules, billing unit, contract term and included services in writing.
Historical devices used different cellular, Wi-Fi or satellite arrangements. None establishes alarm delivery without any functioning communication route. Ask Peoplesafe to confirm supported devices, connectivity, alerts and escalation in the migrated account.
The official notice says customers migrated to Peoplesafe Nexus and LONEALERT will shortly cease operating. Remaining legacy pages are not evidence of a current OWL offer; direct new procurement questions to Peoplesafe.
No public account-level mapping proves that. Reconcile users, devices, timers, response plans, contacts, reports and historical records against the live Nexus account and contract.
The legacy catalogue does not establish current support for each model. Obtain written confirmation for every serial number, network/SIM arrangement, configuration and replacement date.
Peoplesafe describes alarms going to a 24/7 Alarm Receiving Centre, where a Controller assesses the situation and follows agreed escalation instructions. Confirm monitoring entitlement, geography, contacts and product configuration for the migrated account.
Do not assume so. Location technologies and a communications path solve different problems. Ask for a role-specific signal assessment and demonstrate the proposed app, SIM, roaming or alternative device in real work locations.
It depends on the product and optional settings. Peoplesafe documents emergency/manual location and optional tracking, while Nexus can expose maps to configured roles. Establish collection, access, retention and worker-notice rules before rollout.
Do not assume a generic shared assignment is safe. ARC response depends on correct identity and risk context. Demonstrate the provider-approved sharing method, or assign devices individually, and document who is responsible at each handover.
At minimum reconcile activated profiles, device/app assignments, escalation contacts, alarm-response instructions, roles, app permissions, training and planned tests. Technology does not create correct response data automatically.
Nexus support describes usage, alarm, user-status, management and activity reports, with scheduling for most reports. Confirm which roles can access them, authorized email recipients and the retention needed for investigations.
Drawn from the profiles behind the Alternatives list above: most category tags shared with LONEALERT (Peoplesafe migration) first, then the closest overlap in documented capability names, then A to Z. Ratings, search demand and sponsorship are not used; rows are shown A to Z.
No shared category tag.
Differs: price amount published (this profile: no verified amount).
Same: scope, offline and trial.
No shared category tag.
Differs: trial free trial documented (this profile: not established).
Same: scope, offline and price.
No shared category tag.
Differs: price amount published (this profile: no verified amount); trial on request (this profile: not established).
Same: scope and offline.
Also recorded as LONEALERT, LoneAlert. Older entries under a previous name may describe a different release or owner.
Star ratings and review counts from the old catalog are not shown: no source for them was recorded.
