A field-ready inspection, certification, exception and signoff checklist.
Print-ready checklistTechnical Acceptance ChecklistStructured Cabling Acceptance and Certification Checklist
Structured Cabling Acceptance and Certification Checklist
from pathway inspection through signed closeout.
Accept structured cabling only after the installed scope matches the drawings and drop schedule, pathways and penetrations pass visual inspection, every required link has a valid result under the correct link model and test limit, failures have been corrected and retested, labels reconcile across outlets and panels, and the owner has received native test files, as-builts, photographs, exceptions, warranties when applicable, and signed acceptance.
Acceptance joins physical inspection, correct test setup, traceable results, and complete closeout
1996
Founded
900+
Deployments
10,000+
Sites served
the 48 contiguous states, Alaska, and Hawaii
Coverage
SRS Networks is a nationwide IT infrastructure deployment partner headquartered in South San Francisco, California, serving multi-site enterprises across the 48 contiguous states, Alaska, and Hawaii since 1996. This page turns field-delivery requirements into a scope, comparison, and acceptance record a buyer can use.
Free and Ungated
Download the actual template
Choose the print-ready copy or complete the interactive PDF electronically. No email form or account is required.
An interactive copy for electronic completion and project closeout.
Fillable PDF checklistAcceptance Workflow Diagram
Four gates connect the installed plant to signed acceptance
Each gate produces evidence that carries the same link identifiers into the next decision.
1
Reconcile scope
Drawings, drop schedule, changes and installed counts
2
Inspect plant
Pathways, supports, penetrations, racks, outlets and labels
3
Certify links
Correct topology, test limit, native results, failures and retests
4
Close and sign
As-builts, photographs, exceptions, warranties and approval
Structured cabling acceptance gate
| Gate | Required evidence | Acceptance decision |
|---|---|---|
| Scope reconciliation | Approved drawings, outlet schedule, change record, and installed counts | Every installed, omitted, and relocated link is accounted for |
| Pathways and support | Visual walk, support method, bend control, separation, and penetration photos | No unsupported cable, damaged pathway, or unresolved firestop exception |
| Identification | Outlet, cable, panel, rack, and grounding labels matched to the schedule | A label resolves to one physical link at both ends |
| Test basis | Specified category, link model, test limit, adapter type, and tester status | The setup matches the contract and installed topology |
| Results | Native result file plus human-readable report for every required link | All required links pass; failures and retests remain traceable |
| Closeout | As-builts, rack elevations, schedules, photos, exceptions, and warranty records | Another qualified team can support the plant without rediscovery |
| Signoff | Punch-list closure and acceptance by the named owner representative | Open items have owners and dates or are expressly accepted |
Define acceptance before mobilization
Name the installed category, topology, link model, governing project documents, test limit, labeling convention, sampling rules if any, and closeout format in the scope. A generic requirement to test all cables does not tell the field team what constitutes an acceptable result.
Keep the native evidence
Require the original tester result set in addition to a PDF summary. The native file preserves link identifiers, selected limits, measured values, dates, and retest history that a pass-count spreadsheet cannot establish.
Close the physical and documentary work together
Do not demobilize with labels, redlines, photographs, test exports, or punch items waiting to be reconstructed later. Reconcile the documentation while the crew can still inspect and correct the installed plant.
Field Guide
Build the acceptance record step by step
1. Freeze the acceptance basis
The acceptance record begins with the contract, not the tester. Capture the exact topology and performance basis before results arrive.
Project documents
List the approved drawings, specifications, addenda, requests for information, change orders, and manufacturer requirements that govern the installed work. Record the revision used in the field.
Link model
State whether each population is a permanent link, channel, modular plug terminated link, backbone segment, or another expressly defined topology. The adapter and test limit must agree with that model.
Acceptance owner
Name who can approve exceptions, witness testing, receive the closeout folder, and sign the final acceptance. Do not leave approval distributed across emails with no accountable decision maker.
Pass rule
Define whether marginal results, informational flags, field re-certification, or manufacturer-specific warranty limits require review. The project specification controls; the tester's green indicator is evidence, not the entire contract.
2. Inspect the installed plant
Certification cannot detect every workmanship or documentation defect. Conduct a physical walk before accepting the result set.
Pathway and support
Check cable support, fill, bend control, service loops, transitions, protection from sharp edges, separation from interference sources, and compliance with the approved pathway design.
Penetrations
Confirm that sleeves and openings match the approved assembly and that required firestopping, sealing, identification, and photographs are complete. Route unresolved conditions through the responsible design or code authority.
Telecommunications spaces
Inspect rack anchorage, patch-panel placement, cable management, grounding and bonding elements within scope, working clearance, cabinet condition, and the legibility of every identifier.
Work-area outlets
Verify location, faceplate condition, identifier, port count, mounting, and any environmental protection specified for the space. Reconcile moved or deleted outlets to the change record.
3. Audit the certification results
A result set is acceptable only when its setup, population, naming, and exceptions can be traced back to the installed links.
Instrument record
Capture the tester manufacturer and model, main and remote identifiers, software version, adapter type, reference procedure when applicable, and current service or calibration status required by the project.
Correct limit
Confirm the selected limit matches the specified category and link model. Testing Cat6A components to a Cat6 limit does not establish Cat6A acceptance, and a channel setup does not substitute for a required permanent-link result.
Complete population
Match every required link identifier to exactly one final result. Investigate duplicates, missing IDs, impossible lengths, inconsistent naming, aborted tests, and results created outside the project date window.
Failure history
Retain the failed result, correction note, and passing retest under a consistent identifier. Deleting the first result hides recurring termination, component, or handling problems that may affect the rest of the installation.
4. Assemble a supportable closeout
The final package should let another qualified team identify, test, change, and troubleshoot the plant without recreating the project.
Required folder
Include approved as-builts, outlet and panel schedules, rack elevations, native and PDF test results, labeled photographs, product data, approved substitutions, open exceptions, warranty records when applicable, and signed acceptance.
Naming reconciliation
Use the same identifiers on drawings, schedules, tester files, photographs, and physical labels. A complete folder with conflicting names is not a usable closeout.
Punch-list control
Record the issue, exact location, owner, disposition, completion evidence, and approval date. Do not convert an unresolved exception into an accepted condition by omitting it from the final folder.
Retention
Set the system of record, file format, access rights, and retention period before turnover. Confirm that native tester files and large photo sets survive any project-platform export or account closure.
Primary technical references
Use the current project specification, adopted code, approved design, and manufacturer instructions for the final decision. These primary references explain the testing and planning basis used in this resource.
TIA TR-42 telecommunications cabling standards programOfficial TIA committee overview covering premises cabling, pathways, copper, fiber, administration, and testing standards.Fluke Networks: permanent-link definitionManufacturer explanation of what a permanent-link measurement includes and excludes.Fluke Networks: choosing the test limitPrimary guidance on matching the test limit, adapters, installed components, contract, and warranty requirement.
When this is not the right approach
This checklist does not replace the project specification, adopted code, authority having jurisdiction, manufacturer warranty procedure, or a qualified designer's acceptance criteria. Project-specific requirements control whenever they are more restrictive.
Straight answers
The installed quantities and locations should reconcile to approved documents; pathways, supports, penetrations, racks, outlets, and labels should pass inspection; required links should have valid final results under the correct test setup; failed links should be corrected and retested; and the owner should receive usable as-builts, native result files, schedules, photographs, exceptions, warranty records when applicable, and signed acceptance.
Put a field-executable scope in front of the crew
Email the site count, geography, schedule, and current documents. Cheryl routes the request to the right deployment lead.
Discuss Cabling Acceptancepartners@srsnetworks.com · (866) 224-3636