What should a structured-cabling handover include?

Detailed answer

What this means for your project

The agreed pack can include outlet and patch-panel schedules, consistent labels, certification results, cabinet elevations, marked-up drawings, photographs, product information and a record of exceptions or agreed variations. Test files should map clearly to physical identifiers rather than arriving as an unexplained data dump. Where an installation is eligible for a manufacturer warranty, the records required by that scheme should also be assembled. LGN defines the handover format during scope development so evidence is captured throughout delivery.

The appropriate specification and delivery method still depend on the site, programme and evidence available. LGN can review those constraints before recommending a practical next step.

What a usable handover looks like

A handover should let someone who was not present during installation identify a connection, find its test evidence and understand any exception. Outlet labels, patch-panel identifiers, cabinet names and test-result filenames therefore need to use the same convention.

Evidence to agree before installation

• Outlet and patch-panel schedules with unique identifiers.
• Permanent-link or channel certification results and the agreed pass limit.
• Marked-up plans, cabinet elevations and route information where required.
• Photographs of completed cabinets, containment and concealed work.
• Variations, failed links, corrective work and items excluded from scope.

Why timing matters

Records assembled retrospectively are often incomplete. LGN agrees the required deliverables during scope development, labels while installing and closes exceptions before practical completion. Where a manufacturer warranty is proposed, its component and test-file requirements are treated as part of delivery rather than an administrative task after handover.