Low Voltage Closeout Documentation Checklist

What a complete low voltage closeout package contains#

Closeout is the last item on a construction schedule and the first to get compressed. The result on most projects is a binder of product data sheets, a one page test summary and drawings that were never revised after the second RFI. That package satisfies the contract requirement for closeout documents without giving anyone the information they need.

The test of a closeout package is simple. Hand it to a contractor who has never been in the building and ask them to find a specific outlet, trace it to a patch panel port, identify the switch it lands on, and say what the link tested at. If they can do that from the documents alone, the package works.

Telelink Business Services is a licensed C-7 Low Voltage Systems Contractor, CSLB License #472017. The list below is what a complete Division 27 and Division 28 package contains, item by item, with the reason each one exists and the person who needs it.

Deliverable	Who uses it	When
Record drawings showing every outlet, pathway, sleeve and room as installed	Facilities, IT, the next contractor	From day one and at every future project
Native test database, one record per copper link and fiber strand	The owner’s engineer, the next contractor, the warranty claim	When an application starts failing, and at warranty claim
Test summary exported to PDF from that database	General contractor, architect, project closeout file	At turnover, for acceptance
Labeling scheme document describing the identifier format	Anyone reading a label for the life of the building	Continuously
Firestop photographs with listed system number, rating and location	Inspector, owner, insurer, the next contractor to open the wall	At final inspection and at every future penetration
Approved product submittals as accepted, not as originally submitted	Owner, funding agency, warranty administrator	At audit, at claim, at replacement
Manufacturer warranty registration and certificate	Owner, at claim	Only if registered, which happens after installation
Rack elevations as installed, not as designed	IT, the next installer, anyone adding a switch	Every time equipment is added
Bonding diagram with trade responsibility marked	Electrician, low voltage contractor, troubleshooter	When a ground loop or noise problem appears
Patching schedule mapping outlet to panel port to switch port	IT operations	Daily
Switch, controller and platform configuration exports	IT, the replacement vendor	At failure, at upgrade, at migration
Camera schedule and coverage map by model, location and field of view	Security staff, investigators, the retention policy owner	At every incident review
Door schedule with device list, credential format and reader technology	Security, facilities, the next access control vendor	At every door change or credential migration
Device schedule by room for nurse call, emergency call and intercom	Nursing or building staff, the service contractor	At every service call and annual test
Administrator credentials for every commissioned platform	The owner	At turnover, permanently
Operation and maintenance manuals for installed equipment only	Facilities and the service contractor	At service
Training records with attendees, date and topics	Owner, agency, and the next staff turnover	When the trained person leaves

Drawings, test data and the labeling record#

Three documents carry most of the value, and they only work together.

Record drawings show what was installed, which is never quite what was drawn. Every outlet, pathway, sleeve, telecom room, device location and identifier belongs on them. Field redlines are the source; the deliverable is the corrected drawing set in the owner’s format, not a photograph of a marked-up print.

Test data proves the plant performs. Require one record per permanent link and per fiber strand in the tester manufacturer’s native format, plus a PDF exported from it. Each record should carry the link identifier, the standard and limit line, the tester model, serial number and calibration date, the test date, and the measured value and margin for every parameter. A pass with 8 dB of margin and a pass with 0.4 dB of margin are both a pass, and only one causes a problem when the building moves to a faster application. That distinction is invisible in a summary sheet. Our cabling testing and audits page covers what certification measures.

The labeling scheme is the index that ties the other two together. It should be submitted for approval before the first label is printed, follow the ANSI/TIA-606 administration standard scaled to the site, and state the format for every class of identifier: cable, outlet, patch panel port, rack, telecom room and pathway. It belongs in the package so a technician five years from now can read a label without guessing.

Firestop, submittals and warranty registration#

Firestop records. Communications cable crosses fire-resistance-rated walls and floors constantly. California Building Code Section 714 governs those penetrations, and the seal has to be a firestop system tested to ASTM E814 or UL 1479 and installed as listed, with an F rating matched to the assembly. The record is a photograph of each penetration before it is concealed, labeled with the location, the assembly rating and the listed system number. Take them as the work proceeds, because after the ceiling closes the only way to produce them is to open it again.

Approved submittals. Include the submittals as accepted, with the reviewer’s stamp and comments, not the version first sent. On federally funded work the camera and network equipment submittals naming the actual manufacturer are what a funding audit asks for. On any work, the accepted submittal is what the owner compares against when a device is replaced.

Warranty registration. A manufacturer system warranty on a cabling plant, commonly 20 to 25 years, is not automatic. An enrolled installer registers it after installation and the certificate comes back naming the building and the installed channel. If the specification required it, the certificate belongs in the package. If nobody registered it, the owner has an installation warranty only and usually finds out at claim.

Rack elevations and the bonding diagram. Elevations show what is mounted where, with rack unit positions, so the next person adding equipment knows what space and power exist. The bonding diagram shows the telecom busbar, the bonding conductor to the building ground, the backbone bonding conductor between rooms and the rack bonding jumpers, with the responsible trade marked on each segment. That last detail is the one that resolves arguments later. Our network room buildout guide covers how those elements get built in the first place.

System records: switches, cameras, doors and call systems#

Every commissioned platform produces its own record, and each one has a specific reader.

Configuration exports. Switch configurations, wireless controller settings, VLAN assignments, IP schemes and license keys, exported as files rather than described in prose. When a switch dies, the export is the difference between a short swap and a day of rebuilding.

Camera schedule and coverage map. Every camera by identifier, model, serial number, location, mounting height, lens or field of view, resolution, frame rate and the recorder or cloud tenant it writes to, plus a floor plan showing the covered area. Security staff use the coverage map at every incident, and it is also the document that shows an owner where the gaps are. Our security camera systems page describes what gets recorded at commissioning.

Door schedule and credential format. Every controlled opening with its reader, lock type, position switch, request-to-exit device, power supply, controller and port, plus the credential technology and card format in use. Card format is the item that gets omitted and the item that stops the next project cold, because a building whose format is unknown cannot have credentials reissued without a migration. See our access control systems page for how those doors get documented.

Device schedule by room for call systems. Nurse call, emergency call and intercom devices by room number with device type, address and zone, so the annual test has a list to work from and staff can report a fault by room.

Administrator credentials. Full administrator access to every platform, handed to a named owner representative, with the handover recorded. A contractor may retain a separate service account under a service agreement, which is normal and useful. Retaining the only administrator account is not.

The two failures that make a package worthless#

Everything above can be present and the package can still be useless. Two do it.

The identifiers do not match. The label on the jack says 2A-14. The record drawing calls the same outlet 214. The test result is filed under B2-014. Each document is internally consistent and no two agree, so nothing can be cross-referenced and the package becomes three unrelated documents. This is not a documentation problem, it is a sequencing problem: the labeling scheme was approved late, or changed mid-project, and the drawings and test files were produced from different versions. The fix is to approve the scheme before the first label is printed and to require the same identifier string in the label, the drawing and the test record, checked on a sample at turnover.

The PDF is a scan of a printout. A tester exports a database. Someone prints it, scans the stack, and delivers a 300 page image file. Every measured value is now a picture. It cannot be searched, sorted, filtered by margin, or reopened in the tester manufacturer’s software to compare against a retest. The data still exists somewhere on the tester or the contractor’s laptop, and in two years it will not. Require the native database file as a named deliverable alongside the PDF, and open one file at turnover to confirm it is what it claims to be.

What to write into the specification to get it#

Closeout deliverables arrive when they are specified as line items with a format and a due date, and when payment is tied to them. Asking for “complete closeout documentation” produces a binder.

Write this into the specification	Where it goes	What it prevents
Submit the labeling scheme for approval before printing any label	Identification section	Identifiers that disagree across documents
Deliver test results in the tester manufacturer’s native database format, one record per link, plus a PDF exported from that database	Testing paragraph of each cabling section	Scanned printouts and summary sheets
Test records shall include tester model, serial number and calibration date	Testing paragraph	Undefendable results from an uncalibrated tester
Identifiers in labels, record drawings and test records shall be identical strings	Identification and closeout sections	Three documents that cannot be cross-referenced
Photograph every rated penetration before concealment, labeled with location, assembly rating and listed system number	Firestopping paragraph	Firestop compliance that cannot be demonstrated
Deliver record drawings in the owner’s native CAD format and PDF	Closeout section	Redline photographs delivered as as-builts
Deliver configuration exports as files for every commissioned platform	Each system section	Configuration described in prose and lost at failure
Transfer full administrator credentials to the owner and record the transfer	Closeout section	Owner locked out of a system it paid for
Submit manufacturer warranty registration and certificate where an extended warranty is specified	Warranty paragraph	An unregistered warranty discovered at claim
Withhold a stated portion of retention until the closeout package is accepted	Division 01 or the subcontract	A package that arrives after the crew has demobilized

The last row is the one that changes behavior. The rows above describe deliverables; that row gives them a due date with consequences.

A closeout package is not paperwork for its own sake. It is what the next contractor prices from, what an auditor asks for, and what an engineer opens when something intermittent starts on the third floor. Against the cost of rediscovering all of it by opening ceilings, it is the cheapest insurance on the project. The Division 27 and 28 specification checklist covers the rest of those sections, and the pre-signature question list covers how to confirm a bidder priced it.

Next step#

If you are writing the closeout requirements for a California commercial or institutional project, take the specification table above and paste it into your Division 27 and 28 sections. If you are accepting a package that has already been delivered and want a second read on whether it is complete, send it through request a bid and note that it is a closeout review rather than a bid.