Skip to content

Check-call windows and escalation

A check call is a scheduled moment when the person on shift confirms they are safe. Each one has a window that opens a set number of minutes before it is due and lasts a set number of minutes. A call not logged before that window closes is missed, and a missed call raises an alarm that repeats until somebody acknowledges it — nothing on the shift itself changes.

When is a check call due?

By default, calls are spaced by interval and land on the clock: on multiples of the interval counted from midnight, in your organisation's time zone. On the hourly default every guard calls on the hour, whatever time their shift began, so the control room has one moment when everyone should be accounted for.

Two limits come from the shift itself. No call comes sooner than First Call After minutes into the shift — the first call is the first clock point at or after that — and none in the last No calls in last minutes. All three settings default to 60 minutes, so a 07:00–19:00 shift carries eleven calls, 08:00 to 18:00 on the hour, and a 06:30 start has its first call at 08:00 too.

If the first call would land after the last, the shift gets no check calls at all. On the defaults that is any shift of two hours or less.

Fixed times are the alternative, and they come only from a check-call pattern set to At fixed times, with its Check Times (HH:MM, comma-separated) filled in.

What is the window?

Each due time carries a window that opens Opens Before (min) early and stays open for Duration (min) from then. On the defaults of 15 and 30, a call due at 22:00 can be logged from 21:45 until 22:15.

Outside it, the platform refuses the call rather than logging it late: No active check-call window right now. The window has either passed or has not yet opened.

Book-on has a window of its own, set by Earliest Book-On (min before shift start) — 60 minutes by default — and running to the shift's end time. Earlier than that and book-on is refused with Book-on is not allowed yet. Separately, Require Previous Shift Booked Off is on by default, so somebody still booked on to an earlier shift sees Cannot Book On Yet until they close it.

What does missed mean?

The Check Calls screen labels every book-on, check call and book-off with where it currently stands:

State Meaning
Scheduled Due later. The window has not opened.
Window open Can be logged right now.
Completed Logged, by the worker or by an administrator.
Missed The window closed with nothing recorded against it.
Blocked Book-on is being held back by the previous shift.
Not required The window would have opened after the person booked off early, or closed before they booked on, so the call was never due. In the second case the shift's timeline reads Not yet on site, and it is never escalated.
Skipped A book-off on a shift nobody ever booked on to — there is nothing to book off from.

Missed is therefore about the window, not about the shift: a call logged 20 minutes after a 30-minute window closed does not retrospectively count.

An administrator can still close the slot afterwards. Log this event on the row records a manual book-on, check call or book-off against that specific due time, marked as manually completed and attributed to whoever did it, and the slot reads Completed even though the time recorded is now.

What happens when one is missed?

A sweep runs every five minutes. For each shift it finds that has been booked on and not yet booked off, it works out which due times are now overdue and raises one alarm each.

  • When the alarm is due. Escalation Delay (min) after the window shuts. A call due at 22:00 on the defaults has its window shut at 22:15 and its alarm due at 22:30.
  • What counts as having been made. Any check call or emergency call logged within Duration minutes either side of the due time.
  • Who is told. In the app and by push: every active Super Admin, Admin and Control user in the organisation, plus the managers assigned to the site. The alert is titled Missed check call and names the person, the site and how many minutes overdue they are. For an agency officer it is Missed officer check call, and the agency's Agency Admin and Agency Coordinator users are told too. The organisation's contact address also gets an email on the first alert, if one is set; if it is not, the in-app and push alerts still go out.
  • How often. One alarm per due time, ever. It is recorded before it is sent, so a repeat sweep cannot raise it twice. The alarm then repeats in the app and by push every 10 minutes until someone acknowledges it, saying Not yet acknowledged. After two repeats the organisation's Managers are told as well. A failed email is retried on the next ticks, three attempts in all. A repeat stops when someone acknowledges the alarm, or when it clears: the slot is answered, or the guard books off.
  • How it is acknowledged. On the Check Calls board, each alarm has an Acknowledge button naming the guard. Once taken it reads Acknowledged by NAME at TIME. Any user who can open the board can acknowledge. An alarm nobody acknowledges stops repeating 24 hours after it was raised, and stays open on the board.

Two other alarms work the same way. Not booked on is raised when a guard has not booked on a set number of minutes after the shift started — Alarm if not booked on after (min) in Settings → Check calls or on a site, 0 to 240, 15 by default — wherever missed-call escalation is on. It clears when the guard books on, or is taken off the shift. An Emergency from a guard, employee or officer, raises EMERGENCY raised at once, needs no PIN or location, and is e-mailed to the organisation and, for an officer, the agency.

Nothing else changes. The shift keeps its status, the person is not marked absent, no call is placed to them, and no cover is arranged. On the board the row shows how many minutes overdue it is, and a missed row carries an Escalate button that raises the same alarm by hand, sooner.

Where do the settings live, and which level wins?

The first one set wins, in this order: a pattern chosen for the service (the shift pattern), the site — its pattern and its adjustments — the organisation's default pattern, then the organisation-wide settings under Settings → Check Calls, then built-in defaults. How to set each is on Configure check-call patterns.

It goes field by field, with one twist: a site's own adjustments beat the pattern the site runs and the default pattern, but a pattern chosen for a service beats the site.

Setting Where it can be set Default
Check calls on or off Organisation only On
Interval, First Call After, No calls in last Pattern, then organisation 60 minutes each
Fixed check times Pattern only None
Window opens before, window duration Service pattern, site, site's pattern or default pattern, organisation 15 and 30 minutes
PIN, Site ID, GPS As for the window PIN and Site ID on, GPS off
Escalation delay Site, then organisation 15 minutes
Not-booked-on alarm delay Site, then organisation 15 minutes
Auto-escalate missed calls Site, then organisation On
Earliest book-on, Require previous shift booked off Organisation only 60 minutes, on
Geofencing Site only Off
Alert settings Pattern only Off

A site set to Don't escalate at this site is not escalated, even when the organisation escalates; a site set to escalate is, even when the organisation does not.

What else does the platform send?

Two layers sit beside the mandatory missed-call escalation, and both are off until somebody turns them on.

A check-call pattern can carry Alert Settings, covering book-on, check calls and book-off at either of two thresholds. Org admins get an in-app alert and a push; the Site manager address and any custom addresses get an email. Late fires at the halfway point of the window, while it is still open. Very late fires Very late after (min) past the window's close, 15 by default. There is also a Before-shift heads-up email, sent Heads-up before shift (min) ahead of the start — 60 by default — and an option to send the worker themselves an overdue push.

Separately, the worker on shift gets a Check call due notification while a window is open and the call has not been made.

All of this runs in a background worker on the same five-minute tick as the escalation sweep, so a deployment that runs its workers in a separate process needs that process up for any of it to fire.

How is an agency officer treated?

The same sweep covers agency officers working an organisation's sites, using the settings resolved from that site. The difference is who hears about it: a missed officer check call alerts the organisation's admins and site managers and the agency's Agency Admin and Agency Coordinator users, and emails both the organisation's and the agency's contact addresses.

Officers on accepted shifts also get the reminders employees get — Time to book on, Check call due and Book off your shift — in the app and by push, and a booked-on officer's book-on and book-off reach the organisation's roster. A control-room book-on or book-off of an officer stops the not-booked-on alarm, but a cancelled or no-show roster shift cannot be booked on.

Last updated 2026-11-17