What happens when the site contact does not answer?
Prepared 22 October 2026 by NightMarshal

Agree the no-answer path before monitoring starts: permitted retries, backup roles, alternate channels and the point at which responsibility escalates. Sending a message should not automatically close the incident.

Instructions
1. Define an acknowledgement that counts.
2. Approve retries, backups and permitted fallback actions.
3. Test the full path and correct unreachable roles.

Open the blank CSV in a spreadsheet app; add one row per item. Use Pending for unknowns and N/A only where a field truly does not apply. Review the separate example CSV; all example values are fictional. Keep completed sheets private. Do not include passwords, access codes, personal contacts, footage links or camera stream URLs. No input is collected by these downloads.

Fields
Incident category
First role
Retry rule
Backup
Final owner
Exercise result

Fictional example
Fictional exercise: the duty manager is deliberately unavailable. The deputy receives the test incident but does not acknowledge; the test remains failed until the ownership step works.

Limits
This article supplies no universal retry interval or emergency policy. These must be agreed for the location and service.