7.1 As-Built Documentation

BICSI Technician INST2/TECH

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Cabling Fundamentals

1.1 BICSI Technician Exam Facts 1.2 Structured Cabling Overview 1.3 Cabling Standards Bodies 1.4 Certification and Career Path

2 Chapter 2: Copper Cable Systems

2.1 Copper Cable Overview and Categories 2.2 Cat 5e, 6, 6A, and 8 Performance 2.3 Twisted-Pair Theory and Crosstalk 2.4 T568A and T568B Color Codes 2.5 Termination Blocks and RJ45 Connectors 2.6 Copper Installation Practices 2.7 Copper Field Testing 2.8 Certification: Permanent Link vs Channel 2.9 Troubleshooting Copper Performance

3 Chapter 3: Optical Fiber Systems

3.1 Optical Fiber Overview and Light Propagation 3.2 Singlemode vs Multimode Fiber 3.3 OM1 Through OM5: Bandwidth, Distance, and Sources 3.4 Fiber Connectors: LC, SC, ST, and MTP/MPO 3.5 Fiber Termination and Polishing Methods 3.6 Fusion Splicing 3.7 Mechanical Splicing and Quick-Connect Options 3.8 OTDR Operation and Trace Reading 3.9 Optical Loss Budgets and Certification Testing

4 Chapter 4: Troubleshooting and Diagnostics

4.1 Systematic Fault Isolation 4.2 OTDR Trace Analysis 4.3 Copper Certification Test Interpretation 4.4 Fiber Certification Test Interpretation 4.5 Corrective Action Strategies 4.6 Common Cable Faults 4.7 Retrofit and Cutover Planning

5 Chapter 5: Bonding, Grounding, and Firestopping

5.1 Grounding and Bonding Overview 5.2 TMGB, TGB, and TBB 5.3 Grounding Conductors and Bussing Methods 5.4 NEC and J-STD Compliance 5.5 Firestop Systems and Ratings 5.6 Firestop Installation Practices

6 Chapter 6: Pathways, Spaces, and Safety

6.1 Pathways: Conduit, Cable Tray, and Raceway 6.2 Spaces and Work Areas 6.3 Worksite Safety and PPE 6.4 Electrical and Laser Safety 6.5 Blueprint Interpretation 6.6 Project Coordination

7 Chapter 7: Documentation, Project Management & Career

7.1 As-Built Documentation 7.2 Project Documentation and Reporting 7.3 Estimation and Project Management 7.4 Career and Continuing Education

7.1 As-Built Documentation

Key Takeaways Explain This Topic AI

As-built drawings record what was actually installed; design drawings record what was intended — the two diverge on every real project.

A link map ties each work-area outlet identifier to a patch-panel port and switch port, and is the single most-used as-built artifact for MAC work.

TIA-606-C requires unique identifiers for every cable, pathway, space, and bonding component, with the identifier appearing at both ends of the cable and on the record.

A complete as-built package includes the outlet schedule, cable schedule with per-run installed lengths, pathway record, firestop design numbers, bonding resistance values, certification results, and a deviations log.

The Technician signs off the as-built, attesting that redlines were resolved, the link map was verified against the patch panel, and any warranty-affecting deviations are flagged.

Last updated: July 2026

Why as-builts matter

Design drawings show what the designer intended; as-built drawings show what the installer actually built. On any real ICT project the two diverge: pathways shift to avoid ductwork, outlets move at the owner's request, spare conduits are pulled to future-proof a run, and a cable that was specified at 85 m ends up at 92 m because of a detour. If those deviations are not captured, the next technician on the site — troubleshooting, expanding, or retrofitting — works from a fiction. The BICSI Technician is responsible for producing accurate as-builts, and the written exam tests the conventions, content, and workflow that make them trustworthy.

Design vs as-built: what changes

A design package typically contains floor plans with outlet locations, a pathway plan (conduit, tray, J-hooks), a patch-panel schedule, and a cable schedule listing each run with from/to, type, and estimated length. The as-built retains the same sheet format but records the installed reality:

• Element Design drawing As-built drawing
• Outlet location Planned position Actual installed position, with any added or dropped outlets
• Cable route Specified pathway Actual pathway, including field-routed detours
• Cable length Estimated (often "≤90 m") Measured length, recorded per run
• Patch-panel port Planned assignment Actual port assignments, verified by link map
• Label text Planned identifier Identifier actually applied at both ends
• Deviations None expected Documented with reason (RFI, field condition, owner direction)
• Redlines

A redline is the field-marked working copy of the design drawing used during installation. The crew annotates changes in red (or another contrasting color) as they occur: a conduit moved 300 mm to clear a beam, an outlet added in a niche, a run abandoned because the pathway was inaccessible. Redlines are not the final deliverable — they are the input to the as-built. The Technician reviews the crew's redlines, resolves ambiguities, and transfers the verified information onto a clean as-built sheet (now usually CAD or BIM rather than Mylar).

Best practice for redlines:

Mark changes daily, not from memory at the end of the job.

Use consistent symbols and a legend that matches the project's drawing standard.

Note the reason for each deviation in a remark, not just the geometry.

Cross-reference each redline to an RFI, change order, or owner directive when one exists.

Date and initial every change so the reviewer can trace accountability.

What to record post-install

A complete as-built package for an ICT cabling project should contain:

Outlet/faceplate schedule — every work-area outlet (WAO) with its unique identifier, location, serving telecommunications room (TR), and media type.

Cable schedule — each horizontal and backbone run with cable ID, type (e.g., Cat 6A UTP, OS2 singlemode), from-device, to-device, installed length, and test-pass reference.

Pathway record — conduit runs with size and fill, cable trays with loading, sleeved penetrations, and any firestopped penetrations (with firestop system design number).

Patch-panel and cross-connect schedules — port-level assignments tying each cable ID to a physical port.

Link maps — the cross-reference that lets a technician trace any user outlet to a specific switch port. A link map pairs the work-area cable ID (e.g., WAO-3F-012 ) with the patch-panel port (e.g., PP-1/Port-14 ) and the active equipment port. Without a link map, MAC work turns into tone-and-trace labor.

Bonding and grounding record — TMGB, TGB, and TBB locations, conductor sizes, and resistance measurements per TIA-607 and J-STD-607.

Certification test results — imported from the certifier (e.g., Fluke Versiv, WireXpert) in PDF and machine-readable format, linked by cable ID.

Deviations and change orders — a log of every deviation from the design, with the authorizing reference.

Photographs — pathway congestion, firestop details, bonding connections, and any unusual conditions; these are invaluable for future troubleshooting.

Labeling per TIA-606-C

Accurate labeling is what makes the as-built usable. TIA-606-C (Administration Standard for Telecommunications Infrastructure) defines the identifier scheme. Each cable, pathway, space, and grounding/bonding component gets a unique identifier, and that identifier appears at both ends of the cable and on the record. A horizontal cable label typically encodes the building, floor, telecommunications space, and sequence — for example, B3-F2-TR1-C-0147 for building 3, floor 2, TR 1, copper cable 0147. The patch-panel label, the work-area label, and the cable schedule entry all carry the same identifier, so a technician reading any one of them can find the others without guessing.

The Technician's responsibility

On a BICSI project the Technician is typically the person who signs off the as-built package before it goes to the owner and the design engineer of record. That sign-off means:

The redlines have been reviewed and resolved.

The cable schedule matches the certification records by cable ID.

The link map has been verified against the patch panel and switch — not just transcribed from the design.

The bonding/grounding record reflects the measured values, not the specified ones.

Any deviation that affects warranty (e.g., a pathway change that increases cable length beyond 90 m for a permanent link) is flagged.

Common as-built defects

Exam questions often test defects that invalidate an as-built:

Length not recorded per run — listing "≤90 m" for every cable hides the few that exceed the limit.

Link map copied from design — never reconciled with the actual patch panel, so port assignments are wrong.

Firestop penetrations not documented — the firestop design number is missing, so the AHJ cannot inspect.

Bonding resistance not measured — the record says "grounded" but has no ohm value.

Redlines not transferred — the as-built sheet still shows the design layout.

Why this is on the TECH exam

The 15% "Safety and Documentation" domain treats documentation as a craft skill, not paperwork. The hands-on exam may require the candidate to produce a link map for a small installation or to mark up an as-built from a given set of redlines. The written exam tests identifier conventions, the elements of a complete package, and the difference between a design record and an installed record. Expect one or two scenario questions where you must identify which as-built defect caused a troubleshooting failure.