CSLB #472017, C-7 Low Voltage Systems

Guide · 10 min read

Low Voltage Closeout Documentation Checklist

At turnover, owners, IT directors, facility managers and general contractors accepting a Division 27 or Division 28 scope should get a complete documentation package. This checklist goes through every document it contains, why each one exists, and the specification language that gets you those documents instead of a binder of product brochures.

Published
September 12, 2026
By
Telelink Business Services
CSLB #472017 · Licensed C-7 contractor

The short answer

A complete low voltage closeout package contains record drawings, the native test database with one record per link, the labeling scheme document, firestop photographs with listed system numbers, approved product submittals, manufacturer warranty registration where a warranted system was specified, rack elevations as installed, a bonding diagram with trade responsibility marked, the patching schedule, configuration exports for every commissioned platform, camera, door and device schedules, administrator credentials turned over to the owner, operation and maintenance manuals, and training records. Two defects can undermine an otherwise thick package: identifiers that don't match across the labels, the drawings and the test results, and a PDF that's a scan of a printout instead of exported test data.

Key points
Core deliverableNative test database, one record per link
LabelingTIA-606 identifiers matching the drawings
Firestop recordPhotographs with the listed system number
CredentialsTurned over to the owner, not retained
Worst defectIdentifiers that disagree across documents
Second worstScanned printouts instead of exported data

What a complete low voltage closeout package contains

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

Here’s a simple test for a closeout package. 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 covers what a complete Division 27 and Division 28 package contains, item by item, with why each one exists and who needs it.

DeliverableWho uses itWhen
Record drawings showing every outlet, pathway, sleeve and room as installedFacilities, IT, the next contractorFrom day one and at every future project
Native test database, one record per copper link and fiber strandThe owner’s engineer, the next contractor, the warranty claimWhen an application starts failing, and at warranty claim
Test summary exported to PDF from that databaseGeneral contractor, architect, project closeout fileAt turnover, for acceptance
Labeling scheme document describing the identifier formatAnyone reading a label for the life of the buildingContinuously
Firestop photographs with listed system number, rating and locationInspector, owner, insurer, the next contractor to open the wallAt final inspection and at every future penetration
Approved product submittals as accepted, not as originally submittedOwner, funding agency, warranty administratorAt audit, at claim, at replacement
Manufacturer warranty registration and certificateOwner, at claimOnly if registered, which happens after installation
Rack elevations as installed, not as designedIT, the next installer, anyone adding a switchEvery time equipment is added
Bonding diagram with trade responsibility markedElectrician, low voltage contractor, troubleshooterWhen a ground loop or noise problem appears
Patching schedule mapping outlet to panel port to switch portIT operationsDaily
Switch, controller and platform configuration exportsIT, the replacement vendorAt failure, at upgrade, at migration
Camera schedule and coverage map by model, location and field of viewSecurity staff, investigators, the retention policy ownerAt every incident review
Door schedule with device list, credential format and reader technologySecurity, facilities, the next access control vendorAt every door change or credential migration
Device schedule by room for nurse call, emergency call and intercomNursing or building staff, the service contractorAt every service call and annual test
Administrator credentials for every commissioned platformThe ownerAt turnover, permanently
Operation and maintenance manuals for installed equipment onlyFacilities and the service contractorAt service
Training records with attendees, date and topicsOwner, agency, and the next staff turnoverWhen the trained person leaves

Drawings, test data and the labeling record

Three documents carry most of the value, and they only work as a set.

Record drawings show what was installed, which is rarely quite what was drawn. Every outlet, pathway, sleeve, telecom room, device location and identifier belongs on them. Field redlines are the source material. The deliverable is the corrected drawing set in the owner’s format, not a photo 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 include 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 link that passes with 8 dB of margin and one that passes with 0.4 dB are both a pass, but only one of them is likely to cause trouble when the building moves to a faster application. You can’t see that difference on 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. It should 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. Put it 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 all the time. California Building Code Section 714 governs those penetrations. 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 photo of each penetration before it’s concealed, labeled with the location, the assembly rating and the listed system number. Take the photos as the work goes along, because once the ceiling closes, the only way to get them is to open it back up.

Approved submittals. Include the submittals as accepted, with the reviewer’s stamp and comments, rather than the version first sent. On federally funded work, a funding audit may ask for the camera and network equipment submittals that name the actual manufacturer. On any job, the accepted submittal is what the owner checks against when a device gets replaced.

Warranty registration. A manufacturer system warranty on a cabling plant, commonly 20 to 25 years, isn’t 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 that out at claim time.

Rack elevations and the bonding diagram. Elevations show what’s mounted where, with rack unit positions, so the next person adding equipment knows what space and power are available. 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. Marking the trade is the detail that helps settle 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 has its own record, and each record has someone specific who relies on it.

Configuration exports. These are switch configurations, wireless controller settings, VLAN assignments, IP schemes and license keys, exported as files instead of described in prose. When a switch dies, the export can turn a day of rebuilding into a short swap.

Camera schedule and coverage map. List 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’s 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. List 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 tends to get left out, and it can stop the next project cold. If nobody knows a building’s card format, credentials can’t be reissued without a migration. See our access control systems page for how those doors get documented.

Device schedule by room for call systems. List nurse call, emergency call and intercom devices by room number, with device type, address and zone. That way 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 goes to a named owner representative, and the transfer gets recorded. A contractor may keep a separate service account under a service agreement, which is normal and useful. Keeping the only administrator account isn’t.

The two failures that undermine a closeout package

Everything above can be present and the package can still be useless. Two problems cause that.

The identifiers don’t 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 consistent with itself, but no two agree, so nothing can be cross-referenced and the package turns into three unrelated documents. What goes wrong here is sequencing. 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, require the same identifier string in the label, the drawing and the test record, and check a sample at turnover.

The PDF is a scan of a printout. The tester exports a database. Someone prints it, scans the stack and delivers a 300 page image file. Now every measured value is a picture. It can’t 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, but in two years it may not. Require the native database file as a named deliverable alongside the PDF, and open one file at turnover to confirm it’s what it claims to be.

What to write into the specification to get it

Closeout deliverables show up when they’re specified as line items with a format and a due date, and when payment is tied to them. If you just ask for “complete closeout documentation,” you’ll likely get a binder.

Write this into the specificationWhere it goesWhat it prevents
Submit the labeling scheme for approval before printing any labelIdentification sectionIdentifiers 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 databaseTesting paragraph of each cabling sectionScanned printouts and summary sheets
Test records shall include tester model, serial number and calibration dateTesting paragraphUndefendable results from an uncalibrated tester
Identifiers in labels, record drawings and test records shall be identical stringsIdentification and closeout sectionsThree documents that cannot be cross-referenced
Photograph every rated penetration before concealment, labeled with location, assembly rating and listed system numberFirestopping paragraphFirestop compliance that cannot be demonstrated
Deliver record drawings in the owner’s native CAD format and PDFCloseout sectionRedline photographs delivered as as-builts
Deliver configuration exports as files for every commissioned platformEach system sectionConfiguration described in prose and lost at failure
Transfer full administrator credentials to the owner and record the transferCloseout sectionOwner locked out of a system it paid for
Submit manufacturer warranty registration and certificate where an extended warranty is specifiedWarranty paragraphAn unregistered warranty discovered at claim
Withhold a stated portion of retention until the closeout package is acceptedDivision 01 or the subcontractA package that arrives after the crew has demobilized

The last row tends to change behavior the most. The rows above it describe deliverables, and that row gives them a due date with consequences.

A good closeout package is what the next contractor prices from, what an auditor asks for, and what an engineer opens when something intermittent starts happening on the third floor. Compared with the cost of rediscovering all of it by opening ceilings, it’s some of the cheapest insurance on the project. Our Division 27 and 28 specification checklist covers the rest of those sections, and the pre-signature question list shows how to confirm a bidder priced it.

Next step

If you’re writing the closeout requirements for a California commercial or institutional project, feel free to take the specification table above and paste it into your Division 27 and 28 sections. If you’re accepting a package that’s already been delivered and want a second read on whether it’s complete, send it through request a bid with a note that it’s a closeout review rather than a bid. We’re happy to take a look.

FAQ

Questions we hear about this

What's the difference between test results and a test summary?

A test summary is a sheet saying that some number of links were tested and passed. A test result is one record per link, with the identifier, the standard and limit line used, the tester model, its serial number and calibration date, the date of the test, and the measured value and margin for every parameter. Only the test result lets an engineer see that a link passed with 0.4 dB of margin, which makes it the first place to look when an application starts failing. We'd ask for the native tester database plus a PDF exported from it.

Link to this answer
Why do firestop photographs need a listed system number?

A penetration through a fire-resistance-rated wall or floor has to be sealed with a firestop system tested to ASTM E814 or UL 1479 and installed exactly as that system is listed. Once the ceiling is closed, the practical way to show compliance is a photograph tied to the system number, the assembly rating and the location. Without the number, a photo of red sealant only shows that something was applied, not that the right system was used.

Link to this answer
Should the contractor keep administrator credentials after the job?

No. The owner should receive full administrator credentials for every platform commissioned on the project: video management, access control, intercom, phone system, network switches and any cloud tenant created for the building. A contractor may hold a separate service account under a service agreement, and that's normal. What shouldn't happen is the owner getting an operator login while the only administrator account belongs to the contractor who installed the system.

Link to this answer
Who actually reads a low voltage closeout package?

Different people at different times. The general contractor and the architect check it against the specification at turnover. The owner's IT and facilities staff use the drawings, labeling and credentials from day one. A future contractor uses the record drawings, patching schedule and test data to price and perform the next project. And years later, an insurer, an auditor or a funding agency may ask for the submittals, warranty registration and firestop records.

Link to this answer
How long should we keep closeout documents?

As long as the cabling plant is in service, which on a commercial building is usually longer than any single owner's tenure. Structured cabling routinely outlives two or three generations of active equipment, so the record drawings and test data from the original installation are often the only record of what's in the walls. Keep the native files, not just the PDF binder, and store them where the facilities team can find them without calling the contractor.

Link to this answer
Which closeout item is most often missing?

The bonding diagram with trade responsibility marked. Grounding and bonding cross the line between the electrical contractor and the low voltage contractor. So unless the specification names an owner, often nobody documents the busbar, the bonding conductor to the building ground, the backbone bonding conductor or the rack bonding jumpers. When a ground loop shows up later, there's no drawing to work from.

Link to this answer

Didn't find your question? Ask us, and you'll talk to someone who does this work.

Call (916) 340-7503Email usOr send drawings to bid
TelelinkBusiness Services, home

Ready to apply this to a real building?

Send over the drawings or describe the scope. We'll tell you what we'd take on, what we'd coordinate with other trades and what it will take to do it right.