Security System Commissioning Checklist: What to Test Before Project Handover

A security system is ready for handover when the installed equipment, software and response procedures work together against the agreed project requirements. A camera picture, a green status light or an unlocking relay is useful evidence, but none proves the complete service. This security system commissioning checklist helps New Zealand installers test CCTV, access control, alarms, intercoms and backup power before the client takes responsibility.

For each test, record the device or door ID, expected result, actual result, date, technician and supporting evidence. Mark an untested requirement as outstanding rather than passed. Adapt the checklist to the approved design, manufacturer instructions and contract, with specialist contractors involved where required.

1. Agree the commissioning plan and acceptance criteria

Collect the final drawings, equipment schedule, network plan, cause-and-effect matrix and client operating requirements. Confirm what each camera must capture, who may enter each door, where alarms must report and who answers intercom calls. Assign an owner to every interface between contractors so an incomplete network or fire interface cannot disappear between scopes.

Arrange an authorised test window. Notify the monitoring centre, client representative and affected building teams before generating alarms or interrupting services. Agree how normal operation will be restored and who will confirm restoration. Emergency interfaces and egress tests must follow the approved procedure with the responsible specialists.

2. Inspect equipment, cabling and installation records

Match installed models and locations to the schedule. Record serial numbers, firmware, controller addresses, cable labels and switch ports as applicable. Inspect enclosure fixings, glands, cable support, accessible terminations and service access. Check for unsealed entries, strained connectors and equipment that cannot be maintained without disturbing other services.

Retain the specified cable test results. Basic continuity testing helps identify some wiring faults, but it does not certify a Cat6 channel or prove network throughput. Where certification forms part of the specification, use the required certification instrument and test limits. Record approved variations in the as-built drawings.

3. Check low-voltage supplies with a Digitech meter

The Digitech XC5078 combines a network cable tester and digital multimeter, making it a relevant tool candidate for cable integrity and supported electrical measurements. Use the XC5078 user manual to confirm its input ratings, permitted connections and test functions before use. It does not replace a camera display, Ethernet certification instrument or end-to-end system test.

For supported low-voltage measurements, record supply voltage at the source and at the remote equipment under representative operating load. Compare the readings with the connected device's permitted input range. A supply reading taken with the lock or camera disconnected can conceal voltage drop that appears when the equipment operates.

Use resistance or continuity modes only on appropriately isolated, de-energised circuits. Follow the cable tester's instructions concerning connected equipment and powered ports. Do not connect it to live PoE unless that specific connection is permitted. Mains testing and electrical certification belong with the appropriately authorised contractor and suitable instruments.

4. Prove CCTV recording, playback and export

Test every camera against its intended scene. Check field of view, focus, mounting stability, obstructions, backlighting and representative movement. Include night conditions where the operational requirement depends on darkness or infrared illumination. Assess recorded footage at the intended settings; a sharp live image alone does not establish usable recorded detail.

• Confirm camera names, addresses, production streams, frame rates and recording schedules.
• Create a known event and retrieve it by the correct camera and time.
• Check event triggers, pre-event and post-event recording where specified.
• Export the required footage and play it on the client's agreed device.
• Verify recording storage alerts and supported camera-offline notifications.

Check time zone, daylight-saving behaviour and time synchronisation across cameras, recorders and related systems. Estimate retention from the final recording load and verify actual retention once enough operating history exists. Do not claim a multi-week retention result from a short commissioning visit.

Confirm authorised viewing and export permissions, privacy masks and the client's approved audio settings. The Office of the Privacy Commissioner's CCTV guidance covers collection purpose, access, retention, security and notification. Record who owns the footage and handles requests. See our CCTV evidence export guide for the retrieval workflow.

5. Test each access-controlled door physically

For the featured controller, consult the RBH UNC500 hardware manual for supported inputs, outputs, reader connections and operating modes. Match the instructions to the installed hardware revision and optional modules before testing.

Test the complete opening, including the reader, controller, lock, door contact, closer and exit arrangement. Present an authorised credential, an invalid credential and a test credential outside its permitted schedule. Observe the actual latch or lock and confirm that the door closes and secures reliably. A granted-access event does not prove the door physically relocked.

Check request-to-exit, unlock duration, held-open and forced-door events where provided. Confirm event identity and timing in the software. Disable a designated credential, verify that the change reaches the relevant controller, then attempt access again. Test the agreed offline behaviour and reconcile controller events after communications return.

Verify approved power-loss and emergency release behaviour with the responsible specialists. Document the expected outcome for each opening; one fail-safe or fail-secure description does not explain every mechanical and electrical condition. Restore temporary permissions and overrides before moving to the next door.

6. Walk-test alarms and confirm monitoring receipt

Walk-test every detection zone using the manufacturer's procedure and realistic approach routes. Check zone descriptions, area assignments, entry and exit sequences, tamper indications and supported fault states. Review conditions that affect detection, such as obstructions, moving stock, heating outlets and animal access.

Send agreed test events through the installed reporting path and obtain confirmation from the monitoring destination. Record the received account, zone, event and restoration. For dual-path reporting, test the approved loss and recovery scenario for each path. A communicator showing connected does not prove the correct event reached the operator.

Before leaving, remove authorised test modes, restore bypassed zones and confirm the monitoring account has returned to its intended operating state. Keep evidence of this restoration with the test record.

7. Verify intercom calls and authorised door release

Call every intended answering destination. Check entrance identity, intelligible audio in both directions, usable video where included and the correct door-release action. Test busy, unanswered and offline destinations, plus any approved forwarding or escalation route. Repeat relevant checks against after-hours schedules.

Where smartphone answering is included, test the actual client account, application permissions and agreed network conditions. Record dependencies on internet connectivity and third-party services. Demonstrate who receives a call and what happens if nobody answers rather than promising uninterrupted availability.

8. Test standby power and recovery

The Powerbox PB256 manufacturer specifications distinguish load current from battery charging current. For PB256-1210CML, the standard allocation is 8A for the load and 2A for battery charging at 13.8Vdc; do not treat the combined 10A figure as available load current. Check the installed variant and specified battery arrangement.

Map the whole service dependency chain: cameras, recorders, access controllers, routers, network switches and alarm communicators. Backing up one panel does not establish backup for the complete system. Confirm the intended standby duration, load assumptions, battery provision and approved test method.

Record the outage duration and load actually observed. Check relevant supply-failure notifications, battery operation and low-battery indications using supported procedures. After restoration, verify recording resumes, controllers reconnect, permissions remain correct and fault messages clear. Distinguish measured runtime from a calculated estimate in the handover report.

9. Secure accounts and verify configuration backups

Replace default credentials and assign named accounts with appropriate permissions. Agree ownership of administrator access, software licences, cloud accounts and remote support. Remove temporary commissioning users and disable services that the approved design does not need. Transfer sensitive credentials through the client's agreed secure process.

Save final configuration backups and record their software or firmware versions. Confirm the files are readable and identify the supported restore procedure. Demonstrate restoration in an authorised test environment where practical. Keep backup files protected and separate from an unrestricted handover folder containing site drawings.

10. Complete the handover and defect register

Use a record that allows another technician to reproduce each test. A practical commissioning sheet can use the following fields:

Provide as-built drawings, the asset schedule, test reports, configuration records, operating instructions and maintenance responsibilities. Train the operator to handle a normal event, a fault and an escalation. Record unresolved defects openly and follow the agreed acceptance process. Critical failures must not be marked passed simply to close the project.

Review the security project planning checklist alongside the final results. For product selection or a trade quotation, contact Essential Security Supplies with the equipment schedule and intended testing requirements.

Frequently asked questions

What should a security system commissioning checklist include?

Include installation and cable checks, low-voltage supply measurements, CCTV recording and export, physical door operation, alarms, intercoms, standby power, fault recovery, account ownership, backups and operator training. Record expected and actual results against the approved project requirements.

Can a Digitech meter replace a CCTV field tester?

A digital multimeter and cable tester support their specified electrical and cable checks. They do not replace a camera video display, category certification instrument or tests of recording, playback and export. Select each tool for the test required.

Does a commissioning checklist certify compliance?

No. A checklist organises acceptance testing. Regulatory, contractual and manufacturer requirements still need the appropriate evidence, approved procedures and responsible specialists.

Can a security project be handed over with outstanding defects?

Follow the contract and client acceptance process. Identify each defect, its operational impact, owner and retest date. Do not mark unresolved critical requirements as passed or hide untested functions in a general sign-off.