Configure check-call patterns
Check-call timing is decided in four places, and the first one set wins: a pattern chosen for a service, then the site's pattern and adjustments, then the organisation's default pattern, then the organisation-wide settings. Patterns are reusable schedules made on Settings → Check Calls; sites and services pick one. Admins and Managers set them.
How is a shift's check-call schedule decided?
The settings screen opens by saying so — How a shift's check calls are decided — and the first one set wins:
| Order | Where it is set |
|---|---|
| 1. Service | A pattern chosen for one shift pattern, on the site's pattern builder |
| 2. Site | The site's pattern, and its adjustments, in the site's settings |
| 3. Default pattern | The pattern marked ★ Default on Settings → Check Calls |
| 4. Organisation settings | The schedule for sites with no pattern, at the bottom of that screen |
So one site can mix: one service on 30-minute patrol calls, the rest on the site's hourly calls. A site's adjustments beat the default pattern, but a pattern chosen for a service still beats the site.
What a missed call then does is on Check-call windows and escalation.
Who can change them?
Admins and Managers, from Settings → Check Calls. Only they can create, change or delete a pattern, and a site or service can only use a pattern from its own organisation.
What is on the settings screen?

Book on, check calls and book off has the switch that turns all of it on or off for every site. Off, guards are not asked to book on, call in or book off, and no lateness alerts are sent. To keep book on and book off without check calls, leave it on and choose No check calls.
Under it, Schedule for sites with no pattern is a choice of Check calls every so many minutes or No check calls (book on and book off only), with Call every (min), First call after start (min) and Stop calls before end (min). When a call is accepted sets Early by up to (min) and Stays open for (min). While a default pattern exists, the schedule and the window are not used; the screen says so and greys them out. Verification, Escalation and Book-On Gating still apply wherever a pattern or site does not set its own.
Escalation holds Auto-Escalate Missed Calls with Escalation Delay (min), and Alarm if not booked on after (min): how long after a shift starts, with nobody booked on, before the control room is alarmed. It is 15 unless you change it, from 0 to 240.
Officer Form Access is not a check-call setting: it is how many days before and after a shift an officer can open its forms.
How do I create a pattern?
On Settings → Check Calls, press New Pattern.
Fill Pattern name * and, if you like, a Description.
Under How often should guards check in during the shift? *, choose:
- Every so many minutes — set Call every (minutes), First call, minutes after the shift starts and Stop calls, minutes before the shift ends. Calls land on the clock: every hour means on the hour.
- At set times of day — type Times to call in (24-hour, separated by commas), for example
10:00,13:00,16:00. - No check calls — Guards only book on and book off. There is no window to set.
A line beneath reads Guards will: book on → … → book off, as you fill it in.
Set Guards can call in early by (minutes) and Call stays open for (minutes) — how long before each call the window opens, and how long it stays open.
Under What guards must provide when they book on, call in and book off, for PIN, Site ID and GPS location, choose Required, Not required, or Site / organisation setting to leave it to them.
Tick Organisation default (replaces the current one) to make it the ★ default. Only one pattern can be the default.
Leave Active ticked — when off, sites and services using it fall back to the next place in the order.
Press Create Pattern.
Edit or delete a pattern from its card. A pattern with no check calls reads No check calls · guards book on and book off only on its card. Deleting asks first — Delete this pattern? Sites and services using it go back to the organisation default.
What are the limits?
| Field | Accepted |
|---|---|
| Interval | 15 to 480 minutes |
| First call after start, Stop calls before the end | 0 to 720 minutes |
| Check times | At least one, as 24-hour HH:MM |
| Window opens before | 0 to 60 minutes |
| Window duration | 5 to 120 minutes |
What are the Alert Settings?
An optional extra, off until you tick Alert Settings — email/push on late events. Choose the recipients — Site manager, Org admins, and any custom emails — and which events to alert on: book on, check call and book off (not check call, on a pattern with no check calls), each Late (halfway through the window) and Very late (Very late after (min), 15 by default). Two more options: a Before-shift heads-up email (Heads-up before shift (min), 60 by default), and Send the officer an overdue push when an event is late.
These are as well as, not instead of, the escalation of a missed call.
How do I set a site's check calls?
- Go to Sites, open the site, and choose Settings.
- Go to Check-call. The fields are editable straight away.
- Choose its Check-call pattern. Organisation default — name means the site follows the default; or pick any pattern.
- Under Adjust for this site, change only what this site needs: Window opens before the call, Window stays open for, PIN, Site ID, GPS location, Escalate missed calls, Escalate after and Alarm if not booked on after. Each shows the value it inherits — Inherited (Required) — and Use inherited puts a changed one back.
- Press Save, at the bottom beside Unsaved changes.
The box at the top, What guards at this site will do, shows the result as you edit: the schedule, the window and verification, when a missed call escalates, and when a guard not booked on alarms the control room, with badges for the pattern, the number of site adjustments, and any services running their own pattern.

How do I give one service its own pattern?
- On the site, open its shift patterns — Change per service from the site's Check-call section takes you there.
- On the service's pattern, set Check calls to one of your patterns. The default, Same as site — …, follows the site.
- Save. The service shows its pattern as a chip on its card, and the site's Services on this site lists it.
If it goes wrong
| What you see | What it means |
|---|---|
| A pattern with this name already exists | Names are unique in your organisation. |
| Interval must be between 15 and 480 minutes | Or one of the other limits above. |
| Pattern type must be interval, fixed times or no check calls | Choose one of the three schedule types. |
| Invalid time "9:00" — use HH:MM, e.g. 07:05 | Fixed times need two-digit hours. |
| Add at least one check time | A fixed-times pattern needs times. |
| Changing Schedule for sites with no pattern does nothing | A default pattern is set, and it wins. Edit the pattern instead. |
| A site's change has no effect on one service | That service has its own pattern. |
| A site set to Don't escalate at this site still escalates | The escalation sweep follows the organisation's setting only — see Check-call windows and escalation. |
Related
Last updated 2026-11-17