An operator cannot read a delivery schedule that exists only in the site manager’s head. The rulebook puts ordinary activity, unusual activity and decision authority in the same place.
The idea in view · Planning diagram
Normal activity and authority need separate facts
- Approved window
- Permitted route
- Current booking
- Who may confirm
- What reviewer may do
- No-answer fallback
Describe normal before abnormal
List open hours, regular visitors and known movements by area. Reference authorized roles or schedules rather than collecting unnecessary personal information. Explain how a reviewer should resolve an unexpected but plausible delivery.
Define the action boundary
Separate “observe”, “contact the duty manager” and “issue an approved speaker message”. State what the reviewer must never authorize independently. Add a no-answer path and keep emergency procedures distinct from routine exceptions.
Keep versions aligned
Use a named owner, effective date and change log. Confirm that the monitoring team received the latest version. Remove expired temporary exceptions so yesterday’s contractor permission cannot become permanent access by accident.
Use language a new reviewer can act on
“Watch for suspicious activity” leaves too much interpretation. Describe the area, expected activity and observable exception, then state the permitted next action. “Person inside the locked equipment zone after closure: review and contact the duty manager” gives a clearer decision boundary. It still does not establish who the person is or why they entered.
Keep the rulebook short enough to consult during an event. Use separate controlled attachments for maps, restricted contacts and specialist procedures. The PSA training material describes site-specific assignment instructions and escalation context; your own record should name its effective version and who accepted it. Retire old copies when schedules change.
Describe normal activity so exceptions can be interpreted
A monitoring rulebook translates site operations into instructions a reviewer can act on. Begin with the schedule: opening and closing, deliveries, cleaners, maintenance and authorized out-of-hours activity. Then identify restricted routes and conditions that need clarification. A useful instruction explains what fact makes activity expected and where the reviewer can obtain that fact.
Avoid describing normality only by appearance. A familiar van, uniform or face may not establish current authorization for a particular area. Use approved booking or site-confirmation processes where the duty requires a decision. Keep the instruction practical: which role can confirm, what information to provide and what to do if confirmation is unavailable. The reviewer should not have to invent permission from an unclear scene.
Write instructions that distinguish observation and judgement
Use concrete locations, camera aliases and actions. Instead of suspicious activity, explain the observable condition that calls for review, such as a person entering a defined route outside its approved operating window. The instruction can then state the questions to resolve and the authorized next step. It should not encourage the reviewer to turn a visual impression into a claim about identity or intent.
Separate site policy from the reviewer's authority. A business may prohibit entry after closing, but that does not automatically authorize a remote reviewer to unlock a door, confront a person or issue an improvised warning. Link the rulebook to the accepted escalation plan. Where instructions conflict, name who can resolve the conflict and keep the uncertainty recorded rather than asking the operator to choose an unsupported action.
Keep temporary instructions from becoming permanent
Give each temporary note an owner, effective period and expiry. A contractor working late on one evening should not become an indefinite exception to the site schedule. Use a controlled channel for updates and acknowledgement so the monitoring team knows which version is active. Do not rely on messages scattered across individual inboxes.
At handover, make the important changes visible: an altered delivery route, a failed view or a contact substitution. The rulebook should remain concise enough to use during review while linking to detailed records where necessary. If every entry repeats the entire site history, important instructions become hard to find. Retain old versions separately so past incidents can be interpreted without cluttering the current operating document.
Reference context: Private Security Authority: monitoring centre training requirements (2018)
A fictional rulebook entry for a late contractor
A maintenance contractor is approved to use the front entrance between specified hours, while the equipment cage remains restricted. A weak note says contractor on site tonight. A useful instruction states the approved route, time window, site role that can confirm the booking and what to do if the person moves into the restricted area.
If the contractor arrives outside the window, the reviewer records the observation and asks for the permitted confirmation. A familiar vehicle does not extend the booking. If no contact answers, the no-answer plan applies. At expiry, the temporary note is removed from active instructions and retained with its approval reference. The example shows how a short instruction can carry the decision without collecting unnecessary personal information or giving the reviewer authority the business never granted.
Make the call
When should the reviewer ask?
| Situation | Decision to make | What to ask for |
|---|---|---|
| An expected vehicle arrives in the approved window | Whether the normal procedure applies | The current booking or approved schedule |
| A recognizable vehicle enters a restricted area | Whether permission covers that route | A duty-manager decision |
| A temporary contractor note has expired | Whether the exception still applies | Fresh authorization rather than an assumption |
Before you move on
- List areas, hours and expected activity.
- Write one permitted action for each exception type.
- Approve, distribute and version the rulebook.
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
- Area
- Use the site area and view aliases that a reviewer can recognize reliably during an event.
- Normal activity
- Describe the approved schedule or activity and how its current authorization is confirmed when that matters.
- Exception
- State the observable condition that needs clarification rather than relying on a vague instruction to spot suspicious behavior.
- Permitted action
- Keep the reviewer's approved action distinct from access control, physical intervention or decisions reserved for the site.
- Version owner
- Identify who approves updates, communicates them to the reviewing team and retires temporary instructions at expiry.
A worked example
Fictional rule: cleaners may use the east door until 23:00 on weekdays. An unidentified person at the locked storage cage still requires review regardless of the cleaner schedule.
| Area | Normal activity | Exception | Permitted action | Version owner |
|---|---|---|---|---|
| East door | Weekday cleaning to 23:00 | Unknown storage-cage access | Contact duty manager | Facilities lead |
Questions readers bring to this task
What else should you know?
How should temporary instructions be handled?
State the affected area, start, expiry, approver and confirmation route. Keep them distinguishable from the permanent rulebook. Once expired, the usual rule should resume unless a new authorized instruction replaces it.
Link to this answer ↗Should a rulebook list individual employees?
Use the minimum detail needed for the task and keep personal information in the approved controlled system. Role aliases, booking references and authorized confirmation routes may be sufficient. The rulebook should help the reviewer act without becoming an unrestricted directory of staff movements and contacts.
Link to this answer ↗How detailed should a monitoring instruction be?
Detailed enough to identify the condition, relevant view, permitted decision path and fallback. Keep it short enough to use during the task. Supporting plans can hold background detail, while the active instruction points to the current version and the person authorized to resolve uncertainty.
Link to this answer ↗What if the site gives conflicting instructions?
Record the conflict and seek clarification through the agreed owner rather than silently choosing one. If immediate action is needed, use only the authorized fallback. Update the controlled instruction after clarification so the same ambiguity does not recur on the next shift.
Link to this answer ↗Notes & sources
The rulebook supports human decisions; camera appearance alone may not establish identity or permission.
Reviewed October 27, 2026. The examples and worksheets are planning aids, not customer results or a statement of contracted service.
- ProtectUK: CCTV operational checklist (2022)
Operational prompts on purpose, coverage, lighting and review. Its historical legal references are not used as current law.
- Private Security Authority: monitoring centre training requirements (2018)
Historical operational handover context; local licensing requirements need separate review.