Communications closeout lives or dies on cabling certification: every link has to pass TIA-568 testing before the manufacturer system warranty activates. Architects, the owner's IT group, and the cable manufacturer all review these records.
Every document required in a Division 27 Communications closeout package, including who provides it and when it applies.
| Document | Applies |
|---|---|
| Copper Cabling Certification Report (per-link) | Always |
| Fiber Optic Test Results (OTDR + power meter) | Always |
| Structured Cabling System Warranty (manufacturer) | Always |
| Cable Schedule / Port Labeling Records | Always |
| Telecom Room (TR/IDF/MDF) As-Builts | Always |
| Telecom Bonding & Grounding Records (TGB/TMGB) | Always |
| AV System O&M and Configuration Backup | If applicable |
| PA / Intercom / Mass Notification O&M | If applicable |
| DAS Coverage / Acceptance Test Report | If applicable |
Division 27 closeout is driven by test data more than by narrative documentation. The structured cabling installer, usually a low-voltage subcontractor working under the electrical contractor or directly for the GC, generates the bulk of the package: a certification report for every copper link and an OTDR plus power-meter result for every fiber strand. Equipment-specific manuals and configuration records come from separate parties, including the AV integrator (Crestron, Extron, AMX, Biamp), the paging or intercom installer (Bosch, Aiphone), and on healthcare projects the nurse call vendor. Standing behind all of it is the cable manufacturer (CommScope, Belden, Panduit, Leviton, Corning), because the long-form system warranty is issued only after the manufacturer reviews the installer's certification data.
The reason these packages arrive incomplete is volume and timing. A mid-size building can have two thousand or more copper drops, and certification produces one record per link, so the real deliverable is a structured results export, not a tidy binder. Installers frequently hand over a one-page 'all links passed' letter instead of the full per-link results, or deliver native tester files that the owner's IT team cannot open without the right software. Fiber shows up as power-meter readings with no OTDR traces, or OTDR traces with no loss-budget calculation to measure them against. The telecom room as-builts, port-to-port cable schedules, and labeling records required by TIA-606 are the most commonly skipped items because they take real drafting time after the cable is already in the wall.
What is at stake is the manufacturer warranty and the owner's ability to operate the network. The 15 to 25 year structured cabling system warranty (the headline reason owners specify a single-manufacturer solution) is contingent on submitting complete certification data through a manufacturer-certified installer; miss the data and the warranty never registers, even though the cable is physically fine. Beyond warranty, an owner who receives a passing summary but no per-link records and no accurate cable schedule cannot troubleshoot a dead port, move a circuit, or plan an expansion without re-surveying the building. Because comms work is often value-engineered and compressed at the end of the schedule, it is also a frequent source of withheld retainage on the low-voltage subcontract.
What each document is, why it's required, and what to watch for. Written for the GC PM collecting documents from multiple subs and engineers.
Every installed copper permanent link or channel must be tested with a field certification tester and pass the performance limits for its category (Cat 6, Cat 6A, or Cat 8). A complete report contains one record per cable run showing the link ID, length, wire-map, insertion loss, return loss, and NEXT measured against the TIA-568 limit line, with an overall PASS result. The deliverable is the full results export, not a one-page summary.
Insist on the native tester results or a per-link PDF, not an 'all links passed' cover letter. The manufacturer will not register the system warranty on a summary, and the owner cannot find a marginal link without the per-link data.
Backbone and any horizontal fiber must be tested two ways: a bi-directional OTDR trace that maps every connector, splice, and event along the strand, and an optical power meter (insertion loss) test that confirms the link falls within the calculated loss budget for its length and connector count. Each strand should have both results with the loss budget shown. Single-mode and multimode strands carry different acceptance limits and must be tested against the correct one.
A power-meter pass with no OTDR traces, or OTDR traces with no loss-budget calculation, is an incomplete fiber package. Require both, per strand, with the budget documented.
Manufacturers such as CommScope, Panduit, Belden, Leviton, and Corning offer an extended system warranty, commonly 15 to 25 years, covering the cabling components and the application performance of the channel. It is issued only when the work is installed by a manufacturer-certified installer and the certification data is submitted to and accepted by the manufacturer. The closeout package should contain the issued certificate registered in the owner's name, not a promise that it is coming.
The warranty is a registration process, not an automatic right. Confirm the installer holds current certified status with that manufacturer and that the data was actually uploaded; the certificate can take weeks to issue after submission.
TIA-606 requires that every outlet, patch-panel port, cable, and pathway carry a unique identifier and that those identifiers be recorded. The deliverable is a cable schedule (administration spreadsheet) mapping each work-area outlet to its patch-panel port and switch location, plus as-built drawings of each telecommunications room showing rack elevations, patch-panel layouts, and pathway entries. This is what lets the owner's IT staff trace a connection without opening walls.
This is the single most skipped Division 27 deliverable because it is drafting work done after the cable is in. Make the as-built cable schedule a named line item, not part of a generic 'as-builts' catch-all.
Per ANSI/TIA-607, each telecommunications room needs a telecommunications grounding busbar (TGB) bonded back to the main telecommunications grounding busbar (TMGB) and the building electrical grounding system. The closeout record documents busbar locations, bonding conductor sizes, and the continuity or resistance verification. Proper bonding protects equipment and personnel and is routinely checked against the spec.
Coordinate the grounding scope with the electrical contractor early. TMGB/TGB bonding often sits in a gray area between Division 26 and Division 27, and unassigned scope is a common reason it arrives untested at closeout.
Integrated AV systems (conference rooms, divisible spaces, digital signage, sound reinforcement) from integrators using Crestron, Extron, AMX, or Biamp require more than a parts manual. The deliverable includes the as-programmed control system source code or project file, DSP configuration files, a system functional test record, and device-level O&M for displays, projectors, and processors. Without the source files, a future integrator cannot modify the system without rebuilding the programming.
Ask specifically for the control system source code and DSP files on backup media, not just the user guide. Owners routinely discover at the first room change that they never received the programming.
Paging, public address, intercom, and mass notification systems require as-programmed zone maps, amplifier and speaker layout drawings, intelligibility or audibility test results where specified, and system O&M. Where mass notification interfaces with fire alarm, the integration and any required acceptance testing must be documented. Healthcare projects add nurse call system documentation with its own acceptance records.
If the PA or mass notification system ties into fire alarm or is life-safety rated, its acceptance can be on the path to occupancy, not just final payment. Confirm whether the AHJ witnessed a test.
The codes and standards that define what's required in a Division 27 Communications closeout package. Reference these when an owner or architect pushes back.
Defines the copper performance categories and the field-test pass/fail limits (insertion loss, return loss, NEXT, and others) that the per-link certification report is measured against.
Governs fiber acceptance, including loss-budget methodology and the insertion-loss and OTDR testing that the fiber test results must demonstrate for single-mode and multimode links.
The basis for labeling and the cable schedule / administration records. A closeout package without TIA-606 identifiers and an accurate schedule is incomplete.
Defines the TMGB/TGB grounding architecture and the bonding documentation required to verify the telecommunications grounding system at closeout.
The industry design and installation reference for telecom rooms, pathways, and cabling administration. Specs frequently invoke BICSI practices for TR layout and as-built expectations.
These are the specific issues that cause owner rejection, AHJ refusal, or retainage holds. Each one is documented with the root cause and how to prevent it.
Installers often hand over a single page stating that all links passed, or a partial set covering only a sample of runs. Owners and cable manufacturers require the complete per-link results so they can confirm 100% coverage and review marginal results. A summary cannot be reconciled against the drop count on the drawings and will not support the system warranty.
Compare the number of certified links in the report to the outlet/drop count on the telecom drawings. Every drop must have a result.
Export the full per-link results from the tester rather than writing a cover letter. The manufacturer needs the raw data to register the warranty anyway.
A power-meter reading shows total loss but not where the loss occurs; an OTDR trace maps each event but does not by itself prove the link is within budget. Reviewers reject fiber packages that contain one without the other, or that show readings with no calculated loss budget to compare against. Mixed single-mode and multimode strands tested against the wrong limit are also rejected.
Require both OTDR traces and power-meter results per strand, with the loss budget calculation shown for each link length and connector count.
Labels get changed in the field, ports get re-terminated, and outlets get relocated, but the administration spreadsheet still reflects the original design. When the owner's IT team cannot find the documented port behind a labeled jack, the TIA-606 records are rejected as inaccurate. A schedule that does not match the field is worse than none, because it sends technicians to the wrong panel.
Spot-check several outlets against the cable schedule before accepting it: trace a jack label to the patch-panel port listed in the spreadsheet.
The package includes a marketing sheet describing the warranty program rather than the issued, project-specific certificate, or the certificate is registered in the installer's or GC's name instead of the building owner's. An unregistered or misdirected warranty leaves the owner without the coverage they paid for, even though the cabling itself is compliant.
Confirm the actual certificate has been issued, lists this project, and names the owner. Allow several weeks after data submission for the manufacturer to process it.
Per-link tests show up but the rack elevations, patch-panel layouts, pathway as-builts, and TIA-607 bonding and grounding documentation are absent. Engineers reviewing against the spec treat the package as incomplete because the physical infrastructure is undocumented. Grounding records in particular are often never produced because the scope was split between trades.
Treat TR as-builts and grounding verification as separate named deliverables. They are commonly the last items produced and the first ones forgotten.
The MasterFormat specification sections that govern Division 27 Communications closeout. Pull these from the project spec to confirm exact requirements for your project.
Sets the general execution, labeling, and administration requirements that the cable schedule and TIA-606 records satisfy.
Governs TGB/TMGB bonding and the grounding documentation due at closeout (aligns with ANSI/TIA-607).
The umbrella section for the cabling system; review it for certification-testing scope and the manufacturer system warranty requirement.
Backbone copper and fiber between the MDF and IDFs; the fiber OTDR and loss-budget testing requirements usually live here.
Work-area-to-TR horizontal runs; the per-link copper certification requirement is normally specified here.
AV system scope, functional testing, and the as-programmed configuration deliverables where the project includes AV.
Use this checklist when collecting documents from your subs and engineer. Print or save as PDF for your project files.
The things that don't appear in the spec but that experienced GC PMs know from hard experience. These are the insights worth sharing.
Certification testers from Fluke, AEM, and others save proprietary project files. The PDF is readable, but the native file lets the owner's IT team re-open, re-baseline, and append future test results. Require both, and confirm the owner can open the native format before you accept it.
The 15 to 25 year system warranty only exists once the installer submits certification data and the manufacturer issues the certificate. Because that happens after field work, it slips easily. Make the issued, owner-named certificate a condition of the cabling sub's final payment so the registration actually gets done.
Telecommunications bonding and grounding (TIA-607) frequently sits between the electrical contractor and the cabling installer. When neither owns it, the TGB/TMGB bonding gets installed informally and never tested or documented. A short scope conversation at the start prevents a missing closeout record.
AV integrators sometimes deliver a user manual and a few photos of the touch panel. The asset the owner actually needs is the control processor source code and the DSP configuration file. Without them, the next conference-room change means reprogramming from scratch at full cost.
Questions GC PMs and subcontractors ask most often about Division 27 Communications closeout.
Closeout Desk collects, classifies, and organizes all your Division 27 Communications documentation, plus every other division on the project. We flag what's missing before you submit, so you're not discovering gaps after the owner reviews the package. Fixed-fee pricing. Delivered in 1–10 business days depending on urgency.
Related reading
Closeout Documentation: DIY vs. Hiring a Service (Real Cost Breakdown)
9 min read
Division 26 Electrical Closeout: Arc Flash Study, Panel Schedules, and NETA Testing
9 min read
Free Warranty Transmittal Log Template for Commercial Construction
6 min read
What Is Substantial Completion? Retainage, G704, and What Happens Next
8 min read
Other division guides