The difficult part of an incident is often the handoff. A reviewer can notice something and place a call while the decision still belongs to nobody.
The idea in view · Planning diagram
Notification is not the end of the response
- Observation
- Review decision
- Contact attempt
- Acknowledged owner
- Authorized next action
- Outcome or open work
Start with decision categories
Separate routine exceptions, uncertain activity, confirmed unauthorized activity and technical faults. Use observable descriptions rather than assigning criminal intent from appearance. Ask the site owner to approve which actions are allowed for each category.
Define the handoff
Use role aliases in the planning sheet, then maintain real contact details in a restricted operational directory. State who can authorize a response partner and what the monitoring team does if the primary contact is unavailable. Emergency procedures need their own locally approved rules.
Exercise the fallback
Use a planned test contact and simulate an unanswered primary through an approved exercise. Confirm the backup receives enough context and records ownership. Review the matrix after role changes and after incidents expose an unclear decision.
Give each condition a clear decision boundary
Use descriptions the available evidence can support. “Person visible inside the closed gate” is more defensible than assigning criminal intent. State the next permitted action and who can approve anything beyond it. Keep routine exceptions, technical faults and emergency procedures distinguishable so an operator does not improvise from one general instruction.
Walk through the matrix with the people named by role. Ask whether they have the information and authority needed to accept the handoff. CFPA’s keyholder guidance provides role and response-planning context, but local requirements and safety arrangements still control the actual plan. Test with designated contacts and keep real dispatch outside an unapproved exercise.
Build the matrix around decisions, not phone numbers
An escalation matrix should tell a reviewer which condition requires action, who can accept the next decision and what happens if that person is unavailable. A list of contacts is only one input. The useful distinction is authority: who can confirm expected activity, authorize a local action, arrange repair or decide that the site needs a temporary change in coverage.
Use observable conditions and keep assumptions explicit. A person visible near a door, a lost camera and an unanswered call are different conditions. They may need different owners even at the same site. Avoid a single instruction to call security for everything unless that role has accepted the duties and the fallback is clear. The matrix should point to the current controlled contact record without becoming a broadly shared source of personal details.
Define the handoff that transfers ownership
A call attempt, voicemail and acknowledged instruction are different outcomes. State what counts as acceptance of the next action and how it is recorded. If the monitoring team contacts a duty manager, the manager's acknowledgement may transfer a decision duty; it does not necessarily confirm attendance or incident closure. Keep those stages distinct in the timeline.
The plan also needs a person who owns unresolved incidents. If no contact accepts the action, the reviewer should have an authorized fallback and a clear record of what remains open. Do not ask the reviewer to invent authority or treat exhaustion of a contact list as resolution. Where the business cannot provide a workable response path, that is a site-planning gap to address before relying on the service.
Keep urgent action within the agreed local procedure
The matrix is not a substitute for emergency instructions or local requirements. Any urgent contact or attendance request must follow the accepted site procedure and the conditions of the responding organization. Avoid promising a particular emergency response or assigning duties to a third party that has not agreed to them. A provider can describe its own action and evidence, not guarantee another organization's timing.
Review the matrix when hours, contacts, access rights or local response arrangements change. Test a representative incident and a no-answer case through an authorized exercise. Use aliases in general planning records and store real contact details securely. A correct phone number is insufficient if the person no longer has authority or cannot access the location for which they are listed.
A fictional escalation involving a camera and a delivery
During a late delivery, one camera becomes unavailable and another shows activity near a restricted route. The delivery question may need the duty manager's confirmation, while the lost camera needs the technical owner's attention. Sending both to a single undifferentiated contact can delay the right decision or leave one issue forgotten.
The matrix routes each condition to the accepted role and records acknowledgement separately. If the duty manager confirms the delivery but the technical owner has not accepted the outage, the incident record shows that distinction. The reviewer does not close the camera issue merely because the delivery was legitimate. A well-designed matrix makes parallel responsibilities visible without assuming that one conversation resolves every part of an event.
Make the call
Which action transfers responsibility?
| Situation | Decision to make | What to ask for |
|---|---|---|
| A message is sent | Whether it was received and accepted | An explicit acknowledgement rule |
| A response partner is contacted | Whether attendance was accepted or completed | Separate request, acceptance and arrival records |
| The first role is unavailable | Who may make the next decision | An approved backup and no-answer path |
Before you move on
- Define incident categories and allowed actions.
- Assign primary, backup and no-answer handling.
- Test acknowledgement without contacting emergency services.
A worksheet you can actually use
Start with the blank sheet. Add one row per item, assign an owner and mark anything unresolved as pending. The completed example shows the level of detail to aim for.
Keep completed security plans private. Use aliases; keep passwords, access codes, personal contacts and footage links in your approved systems.
How to fill the worksheet
- Condition
- Describe an observable situation that needs a decision, separating activity, technical faults and unresolved contacts where appropriate.
- Permitted action
- State the authorized action for this condition and do not assign physical or emergency-service commitments without acceptance.
- Primary role
- Identify the role that can accept the required decision, using the controlled contact source for private details.
- Backup role
- Choose an accepted fallback appropriate to the duty rather than adding an available person who lacks authority.
- No-answer path
- Record the approved branch when contact or acceptance fails, including who retains ownership of the unresolved condition.
- Acknowledgement evidence
- Specify the record that demonstrates the next role accepted its task, distinguishing it from a sent message or ringing call.
A worked example
Fictional depot: an uncertain gate event goes to the duty manager. If the test call is unanswered, the deputy acknowledges through the agreed channel and owns the next decision.
| Condition | Permitted action | Primary role | Backup role | No-answer path | Acknowledgement evidence |
|---|---|---|---|---|---|
| Uncertain gate event | Contact duty role | Duty manager | Deputy | Approved escalation procedure | Incident reference |
Questions readers bring to this task
What else should you know?
What if the same person holds several roles?
Make the duties explicit anyway and provide suitable cover. One person can be the manager and keyholder, but that does not create an independent backup when they are unavailable. Document which authority transfers and how the receiving person confirms it.
Link to this answer ↗How many escalation levels should a site have?
Enough to provide a realistic primary and fallback path for the relevant duties. More names do not help if their authority and availability are unclear. Use the actual operating arrangement and test it, including the case where the first person does not answer.
Link to this answer ↗Does a successful call mean the incident is closed?
No. Record what the recipient accepted and what remains to happen. Notification, ownership, attendance and resolution are separate stages. Closure should follow the agreed completion condition with any open work assigned to an owner.
Link to this answer ↗Who approves changes to the matrix?
The business owner of the response duty should approve the operating change, with affected contacts or response organizations accepting their assigned roles. The monitoring team needs the current version and effective time. An edited spreadsheet does not establish that the new duty has been accepted.
Link to this answer ↗Notes & sources
The matrix does not guarantee police dispatch, attendance or response time. Actual actions require a site-specific agreement.
Reviewed October 27, 2026. The examples and worksheets are planning aids, not customer results or a statement of contracted service.
- SCW: professional camera monitoring
Provider description of alert review and scoped response. Its offer is not a NightMarshal commitment.
- CFPA Europe: Keyholder selections and duties (2024)
Role selection and response planning context. Local requirements and safety arrangements take precedence.
- Private Security Authority: monitoring centre training requirements (2018)
Historical operational handover context; local licensing requirements need separate review.