Low Voltage Systems Commissioning Record

This template is built for low voltage systems such as data cabling, access control, signaling, and related control devices. It fits projects where you need to confirm installation quality, power and backup performance, network readiness, and end-to-end function before acceptance. If your scope includes fire alarm or life-safety work, use it only where your project team and AHJ have confirmed it is appropriate alongside the required fire alarm documentation.

Use it after rough-in and installation are complete, then again during functional testing and final acceptance. It is especially useful before owner turnover, before AHJ review, and after any corrective work that needs re-verification. If the system is still being actively installed, this template can be used as a working punch list, but it should not replace final commissioning sign-off.

The record is typically completed by the commissioning agent, low voltage contractor, or qualified inspector, with input from the installer and owner representative. For systems with security, network, or life-safety implications, the person signing should be able to verify the actual test results and not just review paperwork. A contractor representative should be present to confirm corrections and retests.

No. It is a commissioning and acceptance record, not a substitute for any code-mandated test report, manufacturer checklist, or AHJ-required form. It can support compliance with OSHA-related installation practices, NFPA-related firestopping or interface requirements, and industry commissioning workflows, but the project team still needs to follow the governing standard for each system. Use it as the project record that ties those results together.

Common issues include mislabeled cables, loose terminations, missing firestopping at penetrations, incorrect device addressing, failed battery backup, and access control doors that do not release as intended. It also helps catch network problems such as no link status, bad patching, or time sync failures that can break event logging. Another frequent miss is documenting a device as installed without proving it responds correctly to its input or command.

Commissioning is usually performed at project closeout, but rechecks are needed after corrective actions, device changes, firmware updates, or network reconfiguration. For systems that support ongoing operations, owners often reuse the same structure for periodic verification after maintenance or expansion work. The cadence should match the project scope and any manufacturer or owner requirements.

Yes. You can tailor the system identification, device list, test points, acceptance criteria, and deficiency workflow to the exact project. For example, a data room buildout may emphasize patching and link status, while an access control project may focus on reader, lock, and fail-safe behavior. The structure is flexible enough to add site-specific cause-and-effect logic or owner acceptance fields.

This record can capture whether IP-based devices are addressed correctly, whether time synchronization is working, and whether event logs are being generated as expected. That makes it useful when low voltage devices integrate with a network, security platform, or building control system. If your project uses software exports, you can add fields for controller names, IP ranges, panel IDs, or integration test results.

Document the deficiency with the exact location, device, symptom, and test condition that failed. Assign corrective action to the responsible party, set a due date, and retest after the fix is complete. Do not mark the system accepted until the deficiency is closed or formally deferred by the owner and AHJ, if applicable.