Question 1: who triggers the alarm
SOS is triggered by the employee, by a deliberate gesture on the watch: a triple press or a hold of the button, followed by a 3-second countdown during which it can be cancelled. It is an active and unconditional signal, so it does not depend on any settings on the system side.
Inactivity is triggered by the server, which infers the lack of movement from the watch pulses. The employee presses nothing. In the procedure, record this distinction as two rows of a table: SOS has a human initiator, inactivity has an automatic initiator.
Question 2: who closes the alarm
A person closes SOS. Movement by the employee does not clear it, and there is no automatic closure. The inactivity alarm closes by itself when movement returns to the system. For the procedure this is the most important difference, because it sets the duties of the dispatcher: SOS requires a deliberate decision to close, while inactivity usually expires on its own.
In a live production deployment, 7 out of 10 stops are cancelled by the employee, and the median time to close the alarm on site is 52 s. The reference covers over 3,400 hours of watch. These are data from inactivity, so do not carry them over to SOS: for SOS the closure time depends on the arrival of help and on the decision of the person closing it.
Who cancels an inactivity alarm in the production reference
Question 3: what the dispatcher does
For SOS the dispatcher receives a notification and sees the event on the online map. The system has opened its own SOS permit, so the dispatcher has a place to record the course of the event. Their tasks are to confirm receipt, send help and close after confirmation.
For inactivity the course is staged. In the production example, a warning appears after 20 s without movement, and after a further 30 s without a response the alarm is raised. An automatic dialler calls the assigned people and repeats the calls until there is an answer. The time from detecting inactivity to notifying the response team is under 2 minutes, and the process has 5 stages.
Recording it in the procedure
For each scenario record: the source of the alarm, who is notified first, within what time the dispatcher responds, who closes it and on what basis. Keep both scenarios on one page, so that the differences are visible side by side.
Question 4: which reports remain
After an inactivity event the system generates a report with the time, the location and the course of the escalation. For SOS the event is recorded in a separate permit, which documents who called for help and who closed the alarm. Both records serve as evidence for an audit and for analysis after the event.
The duty to ensure safe working conditions arises from art. 207 of the Polish Labour Code (Kodeks pracy). The system provides evidence for an audit, not a guarantee of compliance, so in the procedure the report is described as material for review, not as proof of meeting the duty in itself.
How to rehearse both scenarios
The rehearsal should cover both alarms on one day: one SOS triggered deliberately and one inactivity simulated in agreement with the dispatcher. After the rehearsal the team checks whether the dispatcher knows that SOS must be closed by a person, and that inactivity expires once movement returns.
Enter the results of the rehearsal into the procedure as an example: the time from pressing to notification, the time from warning to inactivity alarm, and the closure time. The site's own figures will replace the reference figures after the first months of operation.
Checklist
Video
Frequently asked questions
Does SOS have an automatic closure like inactivity?
No. SOS has no automatic closure and no link to inactivity settings. A person closes it.
Can inactivity data be carried over to SOS?
No. The 52 s median closure time and the cancellation by the employee in 7 out of 10 stops refer to inactivity. For SOS, the values depend on the arrival of help.
How quickly does the response team get a notification about inactivity?
The time from detecting inactivity to notifying the response team is under 2 minutes, and the process has 5 stages.
We will write the SOS and inactivity procedure with you
Book a call with the safety manager. We will help you set out two scenarios, the dispatcher roles and the post-event reports.
Let's talk