Alert Criteria
Define which monitored observations should move into the alert and escalation procedure instead of leaving the trigger unclear.
Define who should be contacted, what information should be communicated and how the escalation path should progress when a monitored event meets the agreed incident criteria.
When a relevant incident occurs, the monitoring team should not have to guess who to contact or what the next step should be. The communication path should already be defined for the site.
Define which monitored observations should move into the alert and escalation procedure instead of leaving the trigger unclear.
Identify the people authorized to receive monitoring alerts and keep their contact information accurate and current.
Establish the practical incident information that should be communicated so the recipient can understand why the alert was raised.
Define what should happen when the primary contact cannot be reached, including any secondary contact or next authorized step.
Consider who is expected to be available during the monitoring period and how changes to contact availability should be handled.
Review escalation instructions when personnel, operating hours, site conditions or business requirements change.
An effective escalation process is not only about contacting someone. The communication should provide useful context about the monitored observation so the authorized recipient can understand why the alert was generated.
The exact information available will depend on the monitoring arrangement and what can reasonably be established from the authorized CCTV view.
A clear contact hierarchy can reduce uncertainty when an applicable monitoring incident needs to be communicated.
The first authorized person or role identified for the relevant type of monitoring alert.
A defined alternative when the primary contact cannot be reached under the agreed procedure.
Any additional action or communication follows only the responsibilities explicitly defined for the monitoring arrangement.
The exact workflow should reflect the site-specific instructions agreed before monitoring begins.
A monitored observation has met the relevant incident criteria and enters the defined escalation workflow.
Confirm the authorized contact path and communication instructions associated with the applicable event.
Provide the relevant available incident information through the communication method defined for the site.
If additional escalation applies, continue only through the contacts and responsibilities included in the agreed procedure.
A contact list is more useful when it includes a clear fallback path. If the first authorized contact is unavailable, the monitoring team should know whether another contact should be attempted and what the next permitted step is.
The business should keep contact details, availability expectations and any temporary changes current so the escalation procedure reflects the people who can actually respond.
Incident detection and escalation serve different purposes within the monitoring workflow. Detection considers whether observable activity meets the agreed criteria. Escalation determines how an applicable observation should then be communicated.
Explore Incident Detection →Update names, roles and contact details when authorized personnel change.
Review the contact path when business hours, shifts or monitoring periods change.
Adjust instructions when monitored areas, access arrangements or site operations materially change.
Periodically confirm that the escalation path still reflects the business requirement and authorized responsibilities.
Rapid Linker follows the alert and escalation responsibilities included in the agreed monitoring arrangement. Unspecified actions, contacts or emergency responsibilities should not be assumed to form part of the service.
The customer remains responsible for providing accurate contact details, maintaining appropriate site procedures and defining any authorized escalation instructions required for the monitoring service.
Remote monitoring and alert communication do not replace emergency services, physical security measures or other professional response arrangements that may be appropriate for a location.
Practical information about contact procedures, fallback paths, incident communication and service responsibilities.
It is the agreed communication path used when a monitored observation meets the applicable incident criteria. It can define who should be contacted, what information should be communicated and what fallback step applies.
The customer should identify the appropriate authorized contacts for the site and provide accurate contact details and escalation instructions as part of the monitoring arrangement.
The next step depends on the agreed procedure. A secondary contact or another authorized action can be included in advance so the monitoring team has a defined fallback path.
Depending on the monitoring scope and available information, communication may include the relevant site or camera area, the observable activity and the reason the event entered the escalation procedure.
Yes, where appropriate and agreed in advance. Different event categories can require different authorized contacts or communication instructions depending on the site requirement.
Yes. Contact information and procedures should be updated when personnel, operating hours, responsibilities or site conditions change.
No unspecified emergency responsibility should be assumed. Any permitted communication or escalation action must be clearly defined within the agreed monitoring arrangement and applicable service scope.
Incident detection determines whether observable activity meets the relevant monitoring criteria. Alerts and escalation then define how an applicable observation should be communicated through the authorized contact path.
Tell us about your site, monitoring priorities, authorized contacts and the communication path you want defined for relevant CCTV incidents.