Structured Cabling Systems

Introduction to As-Built Documentation and Record Handover

The final stage of any structured cabling installation is not just physical—it’s documentary. 

As-built documentation serves as the permanent record of what was installed, where, how, and to what specification. 

It plays a vital role in the ongoing operability of the data centre, especially during future moves, adds, changes, or troubleshooting events. 

Without accurate as-builts, facility management and future engineers are left guessing—introducing risk, delays, and unnecessary costs. 

This section unpacks the what, why, and how of as-built documentation and shows how structured cabling professionals can ensure high-quality, accepted handovers.

‍

9.3.1 Purpose and Importance of As-Built Documentation

As-built documentation is a formal set of drawings, schedules, and supporting records that show exactly what has been installed onsite—down to the last cable, tray, and termination. 

While “for construction” or “design intent” drawings represent planned work, the as-built version captures the final reality.

Why is this critical?

• It ensures that all future maintenance, changes, or fault-finding can be carried out based on fact, not assumption.
• It provides a commercial and legal record of deliverables, which can be referenced during Practical Completion (PC), Final Account negotiations, or warranty disputes.
• It supports traceability in the event of audits, compliance reviews, or incidents involving physical infrastructure.

A common issue occurs when engineers rely solely on red-line drawings—marked-up versions of construction plans—as a final deliverable. 

While red-lines are helpful onsite, they are not a replacement for professionally updated and validated as-built drawings. 

Red-lines are typically created in haste, often in pen, and can be misread or lack the clarity needed for client acceptance.

As-built documentation is also a gateway to financial sign-off. 

Clients often withhold part of the final payment until the Operations and Maintenance (O&M) handover package, including structured cabling records, has been formally submitted and approved. 

In this sense, the installer’s attention to documentation directly impacts project cash flow and completion.

‍

9.3.2 Types of Records Required

An effective as-built handover for structured cabling includes multiple interdependent documents. These records must not only be technically accurate but also formatted according to the client’s document control standards.

Essential records include:

• Cable Schedules: These list each cable run by ID, type (e.g., Cat6A, OM4, OS2), start and end points, length, and installation method.
  
  
• Patch Panel Layouts: A clear matrix showing which port is patched to what destination. This supports future moves/adds/changes and troubleshooting.
• Test Result Logs: Certified pass/fail reports from tools such as the Fluke DSX CableAnalyzer for copper, or Optical Time Domain Reflectometer (OTDR) results for fibre. Acronyms like OTDR must be explained at first use: OTDR – Optical Time Domain Reflectometer.
• Floorplans and Layout Drawings: These indicate final traywork routes, containment changes, rack positions, and cable pathways, usually generated in AutoCAD or Visio.
• Labelling Schedule: A mapping of all labelling applied to cables, panels, and racks, verifying compliance with the agreed scheme.
• Record of Deviations: Any client-approved deviations from the original design must be included and explained.
• Digital Photo Records (if permitted): These may show patching layouts, containment routes, or rack elevations, provided the client has given prior written consent.
  

Note: All photos must be pre-approved by the client before being taken in a live data centre environment.

Many clients require these documents in both hard copy (binder format) and digital versions, uploaded to cloud-based systems or dedicated project platforms.

‍

9.3.3 Creating and Verifying the Records

The process of producing accurate as-built records starts during installation. 

Good engineers mark up red-line drawings daily and ensure all cable IDs and routes are recorded at the point of installation—not weeks later when memory fades.

Steps for successful as-built preparation include:

1. Onsite Red-Lining: During install, red-line drawings should be kept tidy, dated, and updated daily by the lead engineer or supervisor.
   
2. Digital Drafting: After red-lining, drawings are updated in AutoCAD or Bluebeam Revu to reflect all final routes, dimensions, and notes. Tools like Microsoft Visio may also be used to illustrate patch panel maps or rack elevations.
   
3. Verification Walkdowns: Before finalising, the documentation team performs a physical walkdown of the site with the drawings in hand to validate accuracy.
   
4. Cable Test Uploads: Fibre and copper results are exported from the Fluke LinkWare platform or similar software. These should be sorted by cable ID and cross-checked against schedules.
   
5. Review by Project Manager: The complete as-built set should be internally reviewed before submission. This reduces the risk of rejections and improves client confidence.
   

Discrepancies between installed routes and approved drawings must be highlighted and explained. 

If undocumented shortcuts, containment variations, or re-routed cables are discovered during walkdown, they must be reconciled before handover.

‍

9.3.4 Submitting Records to the Client

Structured cabling records form a major part of the O&M documentation and are submitted during the final project handover phase. 

Each client will have their own preferences for file structure, metadata, and method of delivery.

Key considerations:

• Submission Platform: Many large-scale clients use document control systems like Aconex, Zutec, Viewpoint for Projects, or Procore. These require uploads to specific folders with version control and metadata.
  
• File Naming Conventions: Files must follow strict naming conventions. For example: IDS-FKQ-DAT-08-TRAY-REV03.DWG might refer to a tray layout for the FKQ data hall.
  
• Revision History: All files must be clearly marked with version numbers and include a change log if re-submitted.
  
• Required Metadata: Uploads usually require tagging (e.g., location, system, drawing type, issuing company, revision date).
  
• Handover Register: A register summarising each document and its status should accompany the upload.
  
• Client Review and Comments: Clients may reject documents that are incomplete, inaccurate, or poorly formatted. These are then sent back with comments for revision and resubmission.
  

The submission process must be scheduled in advance to avoid delays to Practical Completion. 

If the documentation team is unprepared, the entire commissioning or financial close-out can stall.

‍

9.3.5 Legal, Commercial and Operational Impacts

From a contractual point of view, as-built records are not just technical—they are legally binding. The client’s acceptance of these records forms part of project closure and may trigger:

• Practical Completion (PC): The milestone at which the client assumes operational control. Missing or unapproved as-builts may delay PC.
  
• Final Account Agreements: As-built submission is often a payment milestone under NEC, JCT, or FIDIC contracts. Delays in submission can delay final payment or trigger penalty clauses.
  
• Warranty Activation: Warranties on installed systems, especially vendor-backed structured cabling warranties (e.g., 25-year performance warranties), may be contingent on full record submission.
  
• Facility Operations: Facilities teams rely on structured cabling records for troubleshooting faults, patching new services, and complying with ISO/IEC standards.
  

Failing to submit accurate records can result in reputational damage, increased risk of site incidents, or even being excluded from future tenders.

‍

With the technical delivery now complete and records formally submitted, the final responsibility for structured cabling teams is ensuring a smooth and professional site exit. 

In the next lesson, we explore how to document lessons learned and manage the transition out of the live construction environment.