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.
| Core deliverable | Native test database, one record per link |
|---|---|
| Labeling | TIA-606 identifiers matching the drawings |
| Firestop record | Photographs with the listed system number |
| Credentials | Turned over to the owner, not retained |
| Worst defect | Identifiers that disagree across documents |
| Second worst | Scanned 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.
| 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 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 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 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.