“We monitor the site” can sound reassuring until a camera fails or nobody answers a call. A scope of work earns its place at that moment: it tells each party which job they accepted and what evidence should exist afterward.
The idea in view · Planning diagram
A scope connects the requirement to accepted work
- Site purpose
- Named views
- Active hours
- Review duty
- Authorized action
- Closure evidence
Make the call
Turn broad promises into assigned work
| Situation | Decision to make | What to ask for |
|---|---|---|
| An installed camera is outside the agreed view list | Whether to add it to monitoring | An amended view register and acceptance result |
| A reviewer calls a response partner | Who owns the incident after the call | Acknowledgement and a separate attendance record |
| A camera becomes obstructed | Who repairs the view and who reports the gap | Named owners and an approved temporary arrangement |
Start with observable duties
Use one row per service duty. “Monitor the yard” leaves the boundary unclear; “review person detections from Y01 and Y02 between closing and reopening” identifies a testable activity. Specify whether review is event driven or continuous human viewing, and who handles video loss.
Define the handoff
Record which party owns cameras, connectivity, rule changes and local attendance. A provider contacting a responder is different from that responder arriving. Give each handoff an acknowledgement requirement and define what happens when the receiving party is unavailable.
Keep exclusions visible
List unsupported views and actions beside the included scope. Include downtime handling, scheduled maintenance and third party charges. Ask for written approval when the camera map or operating hours change; a verbal change should not silently become a contractual expectation.
Try the scope against an awkward evening
Imagine a trailer blocks the gate camera just before closing. The site has an installer, an internet supplier and a monitoring provider. Ask who notices the unusable view, who tells the duty manager and who is allowed to move or repair anything. Write those answers into the scope. If everyone points to someone else, the document has exposed a problem before a real incident does.
Keep the approved drawing and view list attached to the agreement rather than buried in an email chain. Use stable view aliases and a revision date. When one party changes a camera angle or adds a new duty, ask whether the fee, review workload or response permissions change too. The useful output is a document a new duty manager can follow without reconstructing the sales conversation.
What belongs in a monitoring scope of work?
A monitoring scope of work describes the service at the level where an operator, site manager and installer can each identify their own job. Begin with the premises and the operational purpose. A loading door used overnight needs a different instruction from an equipment cage that should remain empty. Name the camera views used for each purpose, the active hours, the activity that should trigger review and the actions that review can lead to. A camera count alone leaves most of that work undefined.
Separate the technical inventory from the operating instruction. The inventory can identify the recorder, camera aliases and accepted streams. The operating instruction should explain what the reviewer needs to recognize and who may decide that an exception is legitimate. Link the two records with stable aliases. That lets a technician replace a device without silently changing the duty attached to its view. The scope should also identify its version, approval owner and effective date so an old attachment cannot become the operating truth by accident.
Reference context: Surveillance Camera Commissioner: Buyers Toolkit (2018)
Make the boundary between review and response explicit
Detection, review, notification, acknowledged ownership and physical attendance are separate events. A service may provide some of these and depend on others for the rest. State which party performs each action and which evidence records completion. If a reviewer calls a duty manager, the call attempt is one record. The duty manager accepting responsibility is another. Neither establishes that anyone attended the site or resolved the event.
Ask what the provider does when the planned path cannot be completed. A camera can be unavailable, a contact can fail to answer, or the only visible detail can be too ambiguous to support a decision. The scope needs an authorized fallback and a person who owns the unresolved condition. Avoid writing a response instruction that assumes an operator can authorize entry, confirm identity or dispatch a local team when the contract does not actually give that authority.
Exclusions need an operating consequence
An exclusion becomes useful when the team understands what it changes. If an unmonitored side passage leads into a covered yard, record the gap and how the site plans to manage it. If audio warnings are unavailable, do not leave them in the escalation plan as a default response. If repair work belongs to an installer, identify who reports the defect and who decides whether temporary coverage is needed until repair is complete.
Do the same for holidays, maintenance periods, exceptional deliveries and changes in opening hours. A document that covers normal weekdays but leaves every exception to an informal message is difficult to operate consistently. Name the channel for approved changes, how the monitoring team acknowledges them and when they expire. A temporary exception should not quietly become a permanent reduction in coverage. Where a requirement cannot be accepted, keep it visible as pending rather than replacing it with optimistic wording.
A fictional scope review: the unlisted rear gate
Imagine a business asks for monitoring of twelve cameras. During a planning review, the team discovers that three views are inside a locked office, the rear gate is visible only in daylight and a late delivery uses a route outside the proposed area. The useful outcome is not simply a lower camera count. It is a revised map connecting each required task to a view, lighting condition, review instruction and authorized contact.
The team might accept the front gate for the agreed overnight hours, leave the rear gate pending a night test and exclude the office cameras because no monitoring task has been defined for them. The delivery route needs its own instruction or a documented gap. None of these decisions proves that an incident will be prevented. They make the service assessable before someone relies on it. Use the blank worksheet to record these decisions and keep the accepted version with the camera register and escalation plan.
Before you move on
- Create a numbered view register and attach operating hours with time zones.
- Describe the review and escalation duties using verbs that can be tested.
- Agree evidence records and acceptance criteria before activation.
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
- Duty
- Name a specific observable job, such as reviewing a defined approach, rather than an outcome the service cannot guarantee.
- Covered views
- Use stable aliases for the views accepted for this duty. Keep candidate or excluded cameras distinguishable from accepted ones.
- Hours and zone
- Record the active period and its time-zone basis, including the owner of holiday or temporary schedule changes.
- Owner
- Identify the role that accepts the duty. Use a controlled reference for personal contacts rather than copying private numbers.
- Acceptance evidence
- Link the relevant test or approval record and state what it establishes. A connection check alone may be insufficient.
- Exclusion
- Describe what is outside this duty and the resulting operating gap, including any separately accepted temporary arrangement.
A worked example
Fictional depot: Y01 covers the locked gate overnight. The monitoring team reviews qualifying alerts; the depot manager owns lighting repairs. An independent responder is contacted only under a separately agreed arrangement.
| Duty | Covered views | Hours and zone | Owner | Acceptance evidence | Exclusion |
|---|---|---|---|---|---|
| Gate alert review | Y01 | 20:00–06:00 Europe/London | Monitoring provider | Approved staged test | Physical attendance separate |
Questions readers bring to this task
What else should you know?
Can the scope be only one page?
Yes, if the site is simple and its attached registers make the duties clear. Length is less useful than a complete boundary: views, hours, actions, owners, exclusions and a way to accept the work. A short main scope with controlled attachments is often easier to maintain than repeated prose.
Link to this answer ↗Who should approve a monitoring scope?
The business owner of the security requirement should approve the operating duties, with technical access confirmed by the responsible IT or camera-system owner. The provider confirms what it accepts. Where local response or a landlord is involved, obtain their agreement to the duties attributed to them; a name in a document is not acceptance.
Link to this answer ↗Is a camera list enough to define coverage?
No. A camera list identifies devices or views. Coverage also depends on the task, lighting, obstructions, hours, event rules and response arrangements. Use the list as an index into those decisions, then test representative conditions before treating the views as accepted for monitoring.
Link to this answer ↗When should the scope be reviewed?
Review it when the site, equipment, hours, event rules or response responsibilities change, and at the review interval agreed in the service. A camera moved during building work can change the duty even when the number of devices and the monthly fee remain the same.
Link to this answer ↗Notes & sources
This is a procurement worksheet, not a legal contract. Have the final agreement reviewed for the relevant country and actual service capabilities.
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.
- MonitorCrew: service scope and pricing factors
Provider description of staffing, hours, handovers and scope. No comparative testing is claimed.
- Surveillance Camera Commissioner: Buyers Toolkit (2018)
Historical operational requirements, commissioning and handover context; not current legal advice or certification.