Use this CCTV commissioning checklist to agree test conditions, record image and recording results, and close handover exceptions. Complete it with the appointed site team; it is a project record, not a product certificate or a guarantee of future performance.
Section 01
Agree What the System Must Demonstrate
Use the project's required viewing tasks, recording behavior, operator functions and supported service objectives. Define observable outcomes for each test. A generic list of online devices cannot establish that the system performs the job the client requested.
Turn the answer into a working record using Requirement, Test, Conditions, Expected outcome.
| Test area | Conditions to record | Acceptance basis to agree | Result and evidence | Owner and retest |
|---|---|---|---|---|
| Image task | Camera/view; day/night and movement conditions | Agreed target/framing/focus are checked in the relevant recorded view. | Record result and controlled evidence reference. | Name owner; record retest/open exception. |
| Recording and retrieval | Channel, recorder, storage, schedule and selected interval | The selected interval can be found, played and exported in the agreed workflow. | Record interval, playback/export result and exception. | Name owner; record retest/open exception. |
| Time information | Device timezone/time source and relevant exported time display | Time information is understandable and meets the project-agreed tolerance. | Record the observed comparison; do not invent a universal tolerance. | Name owner; record retest/open exception. |
| Access and events | Authorized role, supported interface/event and approved test condition | The agreed permitted action and exception behavior are demonstrated. | Record result, permission condition and unresolved interface. | Name owner; record retest/open exception. |
| Safe power/recovery | Approved plan, protected dependencies, actual load and conditions | Observed camera/network/recording recovery is compared with the agreed objective. | Record outcome; no uncontrolled outage or runtime inference. | Name site test owner; record retest/open exception. |
| Handover baseline | Installed models/versions/settings and drawing revision | Evidence, changes and unresolved items are traceable to the agreed scope. | Record baseline reference and remaining exceptions. | Name approval/maintenance owner. |
Section 02
Verify Images at Relevant Conditions
Check framing, focus, target detail and important day or night conditions with the recorded stream where relevant. A clear installation snapshot does not cover movement or difficult lighting. Identify any view that remains obstructed or unsuitable for its defined task.
Use Camera, Task, Lighting, Movement, Result to compare options on the same basis. Keep product capability, project assumption and operating responsibility in separate columns.
Section 03
Test Recording, Time and Retrieval
Confirm that selected events are stored on the intended platform and can be found, played and exported with understandable time information. Check representative earlier footage and configured schedules. A live image is not proof of sustained recording or the required retention.
The project output should make Event, Recorder, Timestamp, Playback, Export traceable from input to acceptance.
- Confirm the answer to: How should recording be verified?
- Record the project fields: Event / Recorder / Timestamp / Playback / Export.
- Keep product capability, project assumptions and site responsibility in separate records.
Section 04
Test Access and Required Integrations
Demonstrate the specific supported event and operator action under the agreed conditions, including permissions and exception behavior. Test remote access separately from local operation. Do not replace a door-event or alarm-layout test with a statement that both devices support networking.
Record Event, Interface, Expected action, Authorized role, Exception before selecting a product family. That makes later substitutions possible without silently changing the operational requirement.
Section 05
Exercise Power and Recovery Safely
Use an approved safe test plan coordinated with the site team to observe the required camera, network and recording service through the power event. Record load and conditions. Do not perform uncontrolled outages or infer system continuity solely from the UPS remaining powered.
Review Test condition, Protected path, Recording, Duration, Recovery with the party that will operate or maintain the system.
Section 06
Close Defects and Establish the Baseline
Each issue should identify the affected requirement, responsible action and observable retest result. Keep the final installed settings and unresolved exceptions clear. The output should help the client operate the system, not provide an unqualified certification of every possible future condition.
Use Issue, Asset, Action, Owner, Retest, Remaining exception as the handoff between design and procurement.
Engineering references
These sources support the general planning principles. Always use the selected product's current datasheet and applicable project standards for final design.
