Key takeaway
ShiftTracker runs check calls in its app on intervals you set per site or service. A missed call alerts your control room after the escalation delay and repeats every 10 minutes until acknowledged, officers have a press-and-hold Emergency button, and patrol forms add NFC or QR checkpoint scans. The response to an alert stays with your team.
A lone worker in the UK security industry faces risks that do not exist for officers deployed in pairs or teams. Whether a static guard on an empty commercial premises, a mobile patrol officer working overnight, or a key-holder responding to an alarm activation, the duty of care owed by the employer is the same as for any other worker — but the practical safeguards are different. Check-call systems are one of the primary tools British security managers use to meet that duty of care. This guide explains how they work in practice, what the relevant regulations say, and how ShiftTracker automates the process so that a missed check-call triggers an alert rather than a silent incident. The result is a timestamped, auditable record that satisfies both HSE guidance and BS 7858 compliance documentation requirements.
What is a check-call system?
A check-call system is a scheduled confirmation that a lone worker is safe and on post. The officer confirms their status at pre-agreed intervals using a phone app or a physical checkpoint reader. If the confirmation does not arrive, the system treats it as an alert and escalates to a supervisor.
The two main formats used by UK security managers are timed interval systems and patrol reader systems. Timed interval systems require the officer to check in via the ShiftTracker Employee App at agreed intervals. Patrol reader systems require officers to visit physical checkpoint markers during their shift, with each scan confirming location and status. ShiftTracker supports both: timed check calls in the app, and NFC or QR checkpoint scans in patrol forms. Both produce a timestamped audit trail that demonstrates a duty-of-care process was in place.
Why check-calls matter under UK law
The Health and Safety at Work etc. Act 1974 (HSWA 1974) requires employers to ensure, so far as is reasonably practicable, the health, safety, and welfare of their employees. For lone workers, this duty is heightened because the employee has no colleague immediately available to notice if something goes wrong.
The Management of Health and Safety at Work Regulations 1999 specifically requires employers to assess and document adequate arrangements for lone workers. The SIA holds licensed security officers to professional conduct standards that include welfare arrangements.
How ShiftTracker automates the check-call workflow
Manual check-call systems rely on a supervisor remembering to call the officer at each interval. ShiftTracker replaces this with a rules-based workflow that runs without human intervention. When the officer confirms each check-call via the Employee App, the system logs the time, and the location where GPS is required. A missed call raises an alarm after the escalation delay, 15 minutes by default, to your Admin and Control users and the site's managers, and repeats every 10 minutes until someone acknowledges it.
For multi-site operators, ShiftTracker lets you set intervals per site, per service or as an organisation default. A static guard on a high-risk site might require 30-minute intervals; a mobile patrol on a low-risk commercial park might have 90-minute intervals. Both run in the same system, with separate windows and escalation delays.
Who needs a check-call system?
Any UK security employer who deploys officers alone should have a check-call system. A static guard working alone on a commercial premises outside business hours is the most common case — a missed check-call after the agreed interval triggers an immediate supervisor alert.
A key-holder responding to an out-of-hours alarm activation is a higher-risk scenario. A mobile patrol officer working alone overnight across multiple sites requires geo-fenced check-calls at each site visit to provide both a safety confirmation and an attendance record. For BS 7858 accredited organisations, the timestamped check-call record is the evidence base that auditors expect to see.
Check-calls and SIA licence verification
SIA licence verification and check-calls are two separate obligations that interact in practice. If an officer is working in a lone worker capacity and their SIA licence has expired, the employer carries both a compliance risk and a duty-of-care risk.
ShiftTracker integrates SIA licence verification into the scheduling workflow: when an officer is assigned to a shift, a verified licence document that expires before the shift date blocks the assignment. The check-call record provides a contemporaneous log of who was on site, when, and under what licence conditions — useful evidence in the event of an SIA investigation.
Common mistakes when setting up check-call systems
The most common mistake is setting check-call intervals too wide to be meaningful. A two-hour interval on a high-risk lone worker deployment gives a potential attacker a long window before any missed check-call would trigger a response. Best practice for static lone worker deployments is 30 to 60 minutes, with shorter intervals for higher-risk environments.
A second mistake is not configuring escalation paths that work outside office hours. If the supervisor who receives the alert is not reachable at 3am, the alert needs a secondary escalation — a nominated on-call manager, a nominated response officer, or a remote monitoring service. A third mistake is treating check-call records as optional: sporadic use or use only when a supervisor remembers to check considerably weakens the legal defensibility of the arrangement.
What ShiftTracker does not cover
ShiftTracker's check-call module handles the confirmation workflow and alert escalation. It does not replace a physical safety response — when an alert fires, the supervisor or nominated responder must take actual action. The system provides the notification and the record; human judgement and physical response remain with the employer.
ShiftTracker does not supply lone worker hardware. Check calls and the press-and-hold Emergency button work in the ShiftTracker app on the officer's own or company phone. If you need hardware panic buttons or satellite communicators as an extra layer, those are a separate purchase.
Related ShiftTracker resources
BS 7858 vetting: complete guide for UK security employers — duty-of-care documentation requirements under BS 7858
SIA-compliant security scheduling — scheduling requirements for SIA-licensed officers
SIA licence verification for UK employers — automated licence checking workflow
Compliance-led workforce management for protected sites — check-calls in high-security environments
Frequently asked questions
- What are ShiftTracker's default check-call settings?
- A call every 60 minutes, landing on the clock, with a window that opens 15 minutes before the call is due and stays open for 30 minutes. A PIN and the site ID are required by default, and GPS is optional. Intervals can be set from 15 to 480 minutes.
- Who receives a missed check-call alert?
- Every Super Admin, Admin and Control user and the site's managers get it in the app and by push, and the organisation contact is emailed on the first alert. After two unacknowledged repeats, Managers are told too. For an agency officer, the agency's admins and coordinators are also alerted.
- Does ShiftTracker phone the officer when a call is missed?
- No. ShiftTracker raises and repeats the alarm, and your control room decides the response, such as phoning the officer or sending a supervisor. The shift keeps its status, and no cover is arranged automatically.
- Is there an emergency button for lone workers?
- Yes. Officers press and hold the Emergency button in the ShiftTracker app. It needs no PIN or location, works outside any check-call window, and raises an alarm straight away.
- Does ShiftTracker support patrol checkpoints?
- Yes. Patrol forms can include NFC tag, QR code or barcode, GPS and photo fields, so each checkpoint scan is saved with its time and location.



