NEW FEATURE
Missed tour detection and the Missed status
Available in: Security & Patrol > Tour Routes (site and zone level)
What it does
A scheduled tour that has not been started by its missed cutoff is now marked Missed. The two timing values that drive this are set per tour and shown on the Create a Tour form:
Missed cutoff = scheduled start + estimated tour duration
Late alert = scheduled start + grace period
A value of 0 in either field falls back to the effective regional value rather than being treated as "no limit". The form shows the resolved values inline and works through a live example against a start time you choose, so the behaviour is visible before the tour is saved.
Why it matters
Teams operating to a contractual patrol cadence can evidence coverage tour by tour. Previously a missed tour produced no record at all, which meant compliance reporting depended on comparing expected counts against actual counts by hand — an approach that breaks down as soon as a tour is scheduled more than once a day.
How to access it
Go to Security & Patrol > Tour Routes at the site or zone level, then create or edit a tour route.
NEW FEATURE
Missed Tour Alert
Available in: Security & Patrol > Tour Routes and Checkpoints · Notifications
What it does
The alert picker at site and zone level now offers Late Tour Alert and Missed Tour Alert alongside the existing Tour Finish Alert and Tour Incomplete Alert. The Missed Checkpoint Tour Alert is also available under Notifications, where it can use the default notification settings, no notifications, or a custom rule. Recipients can be added individually and notified by email or SMS.
Why it matters
A missed tour is escalated while there is still time to act on it, rather than surfacing days later in a report. Configuration follows the same pattern as the existing tour alerts, so there is nothing new for supervisors to learn.
NEW FEATURE
Regional defaults for tour duration and grace period
Available in: Settings > View All > General > Patrol & Security
What it does
Two settings have been added:
- Default Tour Route Estimated Duration (minutes)
- Default Tour Route Grace Period for Late Notification (minutes)
Set them once at a parent region and every region below inherits the value. To vary the value for a branch of the tree, open that region and replace the inherited value. Each field shows the value it is currently inheriting and from where.
Resolution walks up the region tree: the platform looks for a value set on the region itself, then the parent, and continues upward until it finds one. If no region in the chain has a value, the platform default applies.
Existing tours are not affected. Values already entered on a tour route are left exactly as they are. Regional defaults apply only where nothing has been set.
Why it matters
Timing rules were previously set tour by tour, with a grace period of 0 quietly resolving to 15 minutes — behaviour that was neither visible in the interface nor adjustable. Large portfolios can now establish a standard once and vary it deliberately where operations differ, instead of relying on an undocumented fallback.
NEW FEATURE
Redesigned Create a Tour form
Available in: Security & Patrol > Tour Routes
What changed
Description, Assigned to and Special Instructions are unchanged. Everything below them has been reorganised.
- Timing is grouped under a Timing for every scheduled start panel, with estimated duration and grace period split into two labelled fields.
- Each field explains what a value of 0 resolves to and states the resulting cutoff in plain language.
- An example row lets you pick a start time and shows exactly when that tour would be considered Missed and Late.
- Recurrence and schedule are grouped into their own panel.
Validation
Two warnings prevent configurations that would not behave as expected:
| CONDITION | WARNING SHOWN |
| Missed cutoff falls on or before the late alert | The missed cutoff lands on or before the late alert. Raise duration or lower grace. |
| Grace period exceeds 24 hours | Grace Period for Late Notification exceeds 24 hours. Late and missed tour notifications may not work as expected. |
Keep both values under 24 hours for notifications to fire reliably.
NEW FEATURE
Interval-based recurrence scheduling
Available in: Security & Patrol > Tour Routes
What it does
Weekly and monthly schedules can now be generated by interval instead of selecting every start time by hand. Choose By interval, set the frequency and the window it runs between, then pick the days — the full set of start times is generated for you and the total count is shown as you build it.
- Fine-tune individual days where one day runs longer or shorter than the rest.
- Switch to Specific times to add individual start times instead of a fixed interval.
- Schedule overview displays the generated schedule before you save.
- Monthly schedules note that days 29 to 31 do not occur in every month; where selected, they are used in the months that have them.
Why it matters
Building a high-frequency schedule previously meant clicking every slot for every day, then repeating it for each day of the week. A tour running every 30 minutes across a 12-hour window is now a few clicks rather than dozens.
NEW FEATURE
Missed status available in DataLab
Available in: DataLab
What it does
Checkpoint tour schedule occurrence status now includes a Missed value. Missed tours can be queried directly alongside the scheduled time, the time the tour was marked missed, the late notification time, the grace period and the estimated duration.
Why it matters
This is the reporting half of the feature. A single query now returns scheduled tours that were never performed, which previously was not expressible — missed tours generated no session record, so reporting on them required a cross-table comparison the query language could not perform.
ENHANCEMENT
Scheduling intervals down to 15 minutes
Available in: Security & Patrol > Tour Routes
What changed
Tour schedules could previously only be built on 30-minute intervals. A 15-minute interval is now available, so tours running on a quarter-hour cadence can be scheduled directly rather than approximated.