Use these worksheets alongside the complete planning guide. Copy the tables into the organization’s project record and assign an owner to every unresolved item. Keep camera locations, network diagrams and credentials in an appropriately controlled repository; do not publish a detailed security layout.
Project brief
| Field | Decision to record |
|---|---|
| Property and scope | Buildings, outdoor areas, operating hours and excluded areas |
| Operational objectives | Events to document, required detail and review/response workflow |
| Responsibilities | Facilities, IT, security, privacy/legal and final acceptance owner |
| Constraints | Existing equipment, access windows, network capacity, procurement and growth |
Camera schedule
Create one row per camera and a separate row per sensor or stream when it performs a distinct task.
| Camera ID and scene | Required evidence | Design and test record |
|---|---|---|
| Location, view boundary and mounting point | Target, distance, movement and day/night detail | Model, lens, firmware, stream and representative export |
| Network and power | Port, cable, PoE demand and required continuity | Test result, UPS dependency and recovery behavior |
| Privacy and access | Excluded areas, approved features and authorized roles | Mask verification in live view, playback and export |
Recording and retention worksheet
Record each stream’s measured average bitrate, peak behavior, recording schedule, pre-event buffer and required retention. State where full-resolution recordings and incident exports are stored. Show usable storage after redundancy and reserve, then verify actual oldest available footage after the system has operated long enough. Record the person authorized to place and release an incident hold.
Role and disclosure matrix
| Role | Allowed activity | Control to verify |
|---|---|---|
| Viewer | Approved live views | Restricted cameras and no unintended export |
| Investigator | Playback and authorized incident preservation | Audit trail, export approval and disclosure record |
| Administrator | Configuration and account maintenance | Named account, MFA where available and change record |
Acceptance record
For each requirement record the test date, exact version, expected result, observed result, evidence filename, reviewer and outstanding exception. Include moving subjects in day/night conditions, multi-camera playback, time synchronization, export on another workstation, offline alerts, authorized outage recovery and account removal. Do not close an exception with a vague “system works” statement.
Handover checklist
Retain the final design, inventory, licenses, support periods, configuration backup procedure, patch responsibilities, maintenance schedule, operator training and recovery instructions. Transfer credentials securely and separately from the general documentation. Revisit the record when layouts, lighting, staffing or equipment change.
Related NERSA reference
See NERSA’s security system documentation standards for the corresponding applied reference.