Low-Voltage Project Documentation Checklist

Project and site information

Basic project details make every other record traceable. Without a consistent project name, address, customer contact, and internal job number, photos and test sheets quickly become difficult to match to the right location or phase. Capture this information once, then repeat the key identifiers on every field form and exported file.

• Customer, project name, complete service address, and internal job number
• Primary site contact, after-hours contact, and approved communication method
• General contractor, electrical contractor, consultant, and other relevant trades
• Building, floor, area, room, and phase identifiers used by the project
• Contract date, mobilization date, substantial completion target, and closeout date
• Permit, inspection, monitoring, and authority-having-jurisdiction references when applicable

Scope and system overview

A short, plain-language overview establishes what the project includes—and what it does not. This protects the closeout package from becoming a collection of disconnected forms and gives future service technicians the context needed to interpret individual device and cable records.

• Systems included, such as CCTV, access control, structured cabling, or fire alarm
• New work, reused equipment, owner-furnished equipment, and existing systems affected
• Interfaces with IT, elevators, HVAC, intrusion, monitoring, or other third-party systems
• Approved alternates, change orders, phased work, exclusions, and deferred items
• Expected operating result and the customer acceptance criteria

For multi-discipline projects, keep one project-level summary and separate system-specific records. The Complete System Documentation Bundle is organized for that kind of combined closeout workflow.

Equipment and device records

A useful device inventory does more than count equipment. It connects a unique field label and physical location to the manufacturer, model, serial number, controller or panel association, configuration notes, and warranty information. That makes replacements, licensing, expansion, and troubleshooting faster.

• Device ID and label exactly as installed in the field and shown on drawings
• Manufacturer, model, serial number, firmware version, and license information where relevant
• Physical location, mounting height, room, door, rack, panel, loop, or controller association
• Power source, backup power, network connection, and connected peripherals
• Configuration purpose, coverage area, programmed function, and approved exceptions
• Warranty start date and any customer-owned spare equipment

Camera identifiers, views, recorder assignments, and retention settings fit naturally in a CCTV Documentation Pack. Door hardware, readers, locks, request-to-exit devices, and controller points belong in an Access Control Documentation Pack. For a deeper system-specific review, use the CCTV Project Documentation Checklist and Access Control Project Documentation Checklist.

Cable runs, pathways, and labeling

Cable documentation is the map between endpoints. Record where each run begins and ends, how it is labeled, which pathway it follows, and how it tested. Clear run records reduce tracing time, help prevent accidental disconnects, and make future moves or additions safer.

• Cable ID, cable type, conductor or fiber count, rating, color, and approximate length
• Origin and destination, including rack, panel, port, device, room, and outlet identifiers
• Pathway type and route through trays, conduit, sleeves, risers, or underground sections
• Patch-panel, switch-port, splice, strand, pair, and termination information
• Test result reference and the filename or report page containing detailed measurements
• Abandoned, damaged, rerouted, spare, or future-use cable status

Keep naming consistent from the cable jacket to the patch panel, drawing, test report, and device record. The Structured Cabling Documentation Pack provides focused records for runs, labeling, racks, panels, and testing. The Structured Cabling Project Documentation Checklist expands that workflow into run schedules, pathways, port assignments, copper certification, and fiber test records.

Network and IP information where applicable

Networked low-voltage devices depend on addressing, switch configuration, time services, name resolution, and remote-access decisions that may not be visible at the device. Document the operational information needed for support without putting live passwords or reusable secrets into a general closeout package.

• Device hostname, IP address, subnet, gateway, DNS, VLAN, and switch-port assignment
• Static, reserved, or dynamic addressing method and the party responsible for it
• Relevant NTP, SMTP, directory, monitoring, or management-system connections
• Recorder, server, controller, workstation, or cloud-tenant relationship
• Required ports, firewall rules, certificates, and remote-support method
• Secure credential handoff method and the person or team responsible for future access

Installation documentation

Installation records show that the work was performed in the intended location and identify field conditions that drawings alone cannot explain. Capture the installed condition while ceilings are open and before access becomes difficult.

• Actual device mounting locations, heights, orientations, and coverage areas
• Power supplies, circuit sources, disconnects, grounding, bonding, and backup power
• Penetrations, sleeves, firestopping, weatherproofing, and environmental protection
• Cabinet, rack, enclosure, panel, and pathway installation details
• Deviations from plans, approved field changes, hidden conditions, and coordination issues
• Technician name, work date, area completed, and items left for return visits

Note the reason for any field deviation and the person who approved it. “Moved camera” is not enough; “Camera C-214 moved 6 feet east to clear the new duct, approved by the owner representative on the coordination walk” is actionable.

Testing and commissioning records

Testing proves performance at a specific point in time. A complete record states what was tested, which procedure or standard was used, the expected result, the actual result, who performed the test, and what equipment was used.

• Pre-test readiness checks and confirmation that prerequisites were complete
• Device-by-device functional results, including alarms, supervision, fail-safe behavior, and interfaces
• Cable certification, continuity, insulation, optical, signal, battery, or load results as applicable
• Test instrument make, model, serial number, and calibration status when required
• Software, firmware, database, and final configuration versions
• Witness names, inspection results, retest dates, and customer acceptance criteria

Fire alarm test records should match the applicable contract, adopted code, approved sequence, and authority requirements. A focused Fire Alarm Documentation Pack helps keep device testing, deficiencies, service work, and closeout records connected. The Fire Alarm Project Documentation Checklist provides a documentation-focused review of panel, device, circuit, programming, testing, and turnover records.

Deficiencies and corrective actions

A deficiency log prevents incomplete work from disappearing into emails, text messages, or memory. Give every issue a unique number, clear ownership, target date, current status, and evidence of resolution. Keep open items visible through closeout instead of deleting them when work is corrected.

• Unique issue number, discovery date, exact location, system, and affected device
• Plain description of the condition, operational impact, and supporting photo or test reference
• Responsible party, required action, priority, target date, and dependencies
• Temporary measure or impairment procedure used while the issue remains open
• Correction performed, completion date, technician, and retest result
• Customer, inspector, or project-manager verification when formal acceptance is required

Field and completion photos

Photos preserve conditions that may be concealed or difficult to access later. They are most valuable when a filename, caption, and related device or cable ID explain what the image shows. A folder of timestamped phone images without context is not a reliable installation record.

• Before-work conditions and existing damage that could affect scope or responsibility
• Above-ceiling routes, sleeves, penetrations, firestopping, and concealed junctions
• Rack, cabinet, panel, power-supply, grounding, and termination details
• Device overview and close-up showing the label or unique identifier
• Camera field of view or other visual confirmation of final aim and coverage
• Completed work area, corrected deficiency, and any remaining exception

Use a repeatable filename such as JOB-2417_B2-L2_C-214_FINAL_2026-09-18.jpg, and maintain an index when the project includes a large photo set.

As-built documentation

As-builts should show the system that was actually installed, not the original design with a few handwritten notes. Reconcile device IDs, cable paths, panels, addresses, interfaces, and approved changes against the final field condition.

• Final floor plans, risers, one-lines, rack elevations, details, and schedules
• Installed device locations, identifiers, addressing, and controller or panel relationships
• Actual cable and pathway routes, termination points, spare capacity, and concealed conditions
• Added, removed, relocated, reused, or owner-furnished equipment
• Revision date, revision description, preparer, reviewer, and approval status
• Native drawing files and a stable PDF export when required by the contract

The As-Built Documentation Pack provides a dedicated structure for recording installed systems, field changes, test references, and the information needed for final turnover.

Customer and technician sign-off

Sign-off establishes who completed, reviewed, demonstrated, and accepted the work. It should identify the scope being accepted and list any exceptions. A signature alone does not replace inspection or required test records, but it closes the communication loop.

• Installing and testing technician names, companies, dates, and signatures
• Project-manager review and confirmation that required records are present
• Customer representative name, title, date, and accepted scope
• Training topics covered, attendees, handouts, and demonstration date
• Keys, badges, spare parts, licenses, drawings, manuals, and credentials transferred
• Open exceptions, responsible party, target resolution date, and conditional acceptance language

Final project closeout

Final closeout is the quality-control pass that turns field records into a usable customer package. Confirm that filenames, device IDs, revisions, and references agree across the documents. Remove duplicates and temporary drafts, but retain required test history and deficiency resolution evidence.

• Approved as-built drawings and current system, device, cable, and network records
• Final testing, commissioning, inspection, and deficiency-resolution documents
• Manufacturer data, warranties, licenses, configuration backups, and service contacts
• Training and turnover records, signed acceptance, and a documented list of open exceptions
• Organized photo index with original-resolution files where required
• Consistent folder structure, readable filenames, final revision dates, and secure delivery confirmation