- Define triggers using visible activity and agreed site rules.
- Assign responsibility and a fallback for every contact route.
- Rehearse the written plan and update it whenever site arrangements change.
Write the plan around a decision
An escalation plan connects an observation to a person who has the authority to decide what happens next. A spreadsheet full of phone numbers cannot do that on its own. Start by identifying the situations you want reported and the decisions your team needs to make when those situations arise.
Keep the first version short enough to use during a busy shift. A good working structure is event, relevant camera, coverage period, primary contact, fallback contact, and reporting requirement. Add an owner and revision date so operators can tell which instructions are current.
Describe triggers through visible behavior
Write event rules using what someone can reasonably observe on the available views. A person entering a marked area after an agreed closing time is clearer than suspicious behavior. An open gate, vehicle movement, or a queue crossing a defined point can be described without guessing someone's intentions.
Include expected exceptions, such as scheduled cleaners or an authorized late collection. Illustrative rule: report vehicle entry through the north gate during the site's agreed closed period, unless an approved visit is listed in the current brief. Define how approval updates reach the monitoring team, and what to do if the visitor cannot be verified.
Assign one responsible contact for each situation
Choose the person who can act on the information, not simply the most senior person in the organization. A maintenance issue may belong to a facilities contact, while unexpected after-hours access may belong to the duty manager. Make responsibilities explicit when several people receive the same notification.
Record each contact's role, communication channel, availability, and time zone. For international sites, write dates and times unambiguously and account for the site's seasonal clock changes where applicable. Monitexa's operations are in Bangladesh, so a shared understanding of the site's local schedule matters more than informal references to tonight or tomorrow morning.
Agree the fallback before a call goes unanswered
Document the next authorized step if the first person cannot be reached. Specify which backup is appropriate, how attempts should be recorded, and when another attempt is expected. Agree these details with the people involved; do not borrow arbitrary response times from an unrelated site's procedure.
Distinguish message sent, call answered, responsibility accepted, and issue resolved. They are different states. A delivery receipt does not show that a person has taken action. Also state the limits of the monitoring assignment: remote observation and agreed notifications do not automatically include emergency dispatch or an on-site intervention. Maintain your own local emergency arrangements.
Give the recipient a usable event summary
A notification should provide enough context for the recipient to understand why they are being contacted. Include the site, named camera or area, observed time and time zone, visible activity, current visibility, and any relevant approved exception. State uncertainty directly when the available images do not support a firm conclusion.
Illustrative notification: North loading gate, 21:14 site local time. One vehicle entered during the closed period. No approved arrival appears in the current brief. The vehicle is visible beside bay two. Please confirm whether this visit is authorized. This example supplies a decision to make without labeling the driver or predicting an outcome.
Rehearse, then maintain the plan
Run a tabletop exercise with a routine event, an unclear image, and an unavailable primary contact. Ask each participant what they would do using only the written plan. Resolve ambiguity before the procedure becomes operational. Mark test communications clearly so a rehearsal is not mistaken for a genuine event.
Update the plan when contacts, hours, camera names, or responsibilities change. After an event, review whether the trigger was clear, the right person received the information, and the record showed the outcome. Agree revisions with Monitexa through the designated site owner so the next monitoring shift works from one consistent set of instructions.
