- The Core Construction Package: What Belongs in Every Build
- Deliverable 1: Cover Sheet and Drawing Index
- Deliverable 2: Route Overview / Key Map
- Deliverable 3: Plan and Profile Sheets
- Deliverable 4: Fiber Cable and Conduit Schedule
- Deliverable 5: Splice Diagrams
- Deliverable 6: Cable Assignment / Fiber Assignment Table
- Deliverable 7: Bill of Materials
- Deliverable 8: Permit Set Drawings
- Deliverable 9: Traffic Control Plans
- Deliverable 10: Make-Ready Transfer Sheets (Aerial Projects)
- What Happens When Something's Missing
A fiber construction package is the document set that everything downstream depends on. Construction crews build from it. Splice technicians work from it. Permit offices review it. The project manager tracks progress against it. When a construction package is complete and accurate, builds run on schedule and within budget. When something is missing — a splice diagram that wasn't produced, a BOM that doesn't match the plan sheets, a traffic control plan that covers only part of the route — the problems surface in the field at the worst possible moment.
We've issued a lot of construction packages over the years — for municipal builds, BEAD-funded projects, rural electric cooperative fiber deployments, and commercial overbuild scenarios. The list of required deliverables is fairly consistent, but the quality and completeness of what gets delivered varies enormously. This is a breakdown of every document that should be in a fiber construction package, what it contains, who actually uses it, and what happens when it's missing or wrong.
The Core Fiber Construction Package: What Belongs in Every Build
A complete fiber construction package includes 10 core deliverables: cover sheet and drawing index, route overview map, plan and profile sheets, cable and conduit schedule, splice diagrams, fiber assignment tables, bill of materials, permit set drawings, traffic control plans, and make-ready transfer sheets for aerial projects. Each deliverable serves a distinct purpose — missing any one creates field decisions that should have been made at the design desk.
Before listing individual deliverables, one framing point: a construction package is not a design package. The distinction matters. A design package shows the engineer's work — network topology, optical budget calculations, splitter architecture, route options considered and rejected. A construction package is the output that crews use in the field. It tells the construction contractor exactly what to build, where, at what specifications, with what materials. Everything in the construction package should be actionable. Nothing in it should require interpretation by someone who isn't present on the job site.
The foundation of all of this is solid CAD and GIS work — which is why we've written about how GIS-driven fiber network planning reduces deployment costs and why it's worth investing in that process upstream. A construction package that's built on poor GIS data will have errors that are hard to catch in document review and obvious in the field.
Deliverable 1: Cover Sheet and Drawing Index
Cover Sheet
Contains: Project name, project number, client name, design engineer and firm, PE stamp and license number (state-specific), issue date and revision history, drawing count and index, general notes applicable to all sheets (NESC grade of construction, applicable standards, permit reference numbers).
- General notes must reference the applicable NESC edition. For most current projects, that's the 2023 edition, though some utilities still require the 2017 edition — confirm with the joint use authority before issuing.
- Permit reference numbers belong on the cover sheet so that any inspector can cross-reference the permit set without hunting through the package
- Revision history is non-negotiable — partial revisions to multi-sheet packages that aren't tracked correctly create situations where construction crews are working from different revision levels on different sheets
Deliverable 2: Route Overview / Key Map
Route Overview Sheet
Contains: Full project route shown on a GIS-derived basemap at a scale that shows the entire build area on a single sheet (typically 1:5,000 to 1:25,000 depending on project size), with sheet index grid showing which detail plan sheets cover which route segments, all major landmarks, road names, municipality boundaries, fiber route alignment, and approximate locations of major facilities (hubs, FDHs, splice vaults).
- Sheet break lines with sheet numbers are essential — without them, crews in the field can't quickly determine which plan sheet they need for a given location
- Include a north arrow and scale bar. A scale bar, not just a stated scale — construction crews make copies at non-standard sizes and a scale bar remains accurate where a stated scale does not
- Mark any areas with special construction requirements (e.g., historic districts requiring open-cut restrictions, railroad crossings, highway crossings) so they're visible on the overview before crews reach the detail sheets
Deliverable 3: Plan and Profile Sheets
This is the core of the construction package. Plan and profile sheets — often called "P&P sheets" or simply "plan sheets" — show the fiber route in detail with all the information a construction crew needs to build each segment. On underground projects, the profile view is essential; on aerial-only projects, a plan view with pole schedules may suffice for simpler segments.
Plan View (for all projects)
Contains: Fiber route alignment plotted on current aerial imagery or survey base, all utility crossings shown (including overhead crossings), right-of-way lines and property boundaries, conduit route with stationing, bore locations with bore lengths annotated, splice point locations identified and labeled, FDH/hub/vault locations with facility IDs, pole numbers on aerial routes, existing underground utilities (from 811 records), street and road names, north arrow, scale bar, and sheet match lines.
- Bore lengths annotated on the plan view — not just the bore location symbol. "Bore 147 LF" on the sheet prevents the contractor from having to measure it from the drawing
- All conduit transitions (from aerial to underground, from conduit to direct-buried) annotated with transition type
- Crossing angles for highway crossings where permit specifications require specific crossing geometry
Profile View (underground segments)
Contains: Vertical alignment of the conduit route with stationing matched to plan view, existing grade surface, proposed conduit depth at key stations (minimum at crossings and driveways), utility crossing depths where known from survey data, bore path elevation on HDD crossings, manhole and pull box rim/invert elevations.
- On highway crossings, profile depth must match what's in the permit application — if the permit says 36 inches minimum depth under the pavement, the profile view must show it
- HDD bore profiles should show both the proposed bore path and the surface grade, with the vertical exaggeration noted on the sheet
- Missing profiles on underground construction packages are a genuine problem — bore contractors sometimes proceed based on plan view only and hit utility conflicts that a profile would have flagged
Deliverable 4: Fiber Cable and Conduit Schedule
Cable and Conduit Schedule
Contains: A tabular listing of every cable segment in the project by segment ID, with columns for: from-node (splice point, FDH, hub), to-node, cable type (count, manufacturer type, sheath type), conduit type, conduit inner diameter, segment length in feet, placement method (aerial lash, underground pull, direct-buried), and notes for any special installation requirements.
- Segment IDs on the schedule must match the IDs on the plan view exactly. Mismatches between the schedule and the plan sheets are a common source of material procurement errors
- Lengths should include service loops — if the design calls for 100 feet of slack loop at each splice vault, the cable quantity in the schedule should reflect the total installed length including those loops, not just the route footage
- Separate rows for each conduit segment and each cable segment — a single conduit might carry multiple cables at different installation times, and the schedule needs to reflect that
Deliverable 5: Fiber Splice Diagrams
Fiber splice diagrams are the primary working document for the splicing technician, showing exactly which fiber in which cable connects to which fiber at every splice point — tray by tray, buffer tube by buffer tube. Missing or incorrect splice diagrams are not minor omissions: without them, technicians make field decisions that belong in the design office, generating errors that don't surface until OTDR testing fails at commissioning.
Splice diagrams are among the most important deliverables in the package and the most frequently produced poorly. A splice diagram tells the splicing technician exactly which fiber in which cable connects to which fiber in which cable at a given splice point. Without it — or with an incorrect one — the splicing tech either works from incomplete information (and has to make decisions that should have been made in the design office) or makes errors that don't surface until OTDR testing fails.
Splice Diagram
Contains: One sheet per splice location (splice vault, splice enclosure on aerial, FDH splice tray). Each sheet shows: splice location ID and name, all cables entering the splice point with their fiber counts and buffer tube colors, tray-by-tray assignment of each splice (showing which fiber connects to which, using standard buffer tube color codes per TIA-598), splice enclosure type and tray count, through-splices vs. fusion splices, any fibers designated as spares at this location, OTDR test direction notation.
- Use standard TIA-598 buffer tube color codes and document the code on every splice diagram — blue, orange, green, brown, slate, white, red, black, yellow, violet, rose, aqua for the 12-fiber sequence. Don't assume the splicing tech knows which convention you're using
- Document which fibers are "through" (pass-through splices) vs. which are terminated at this location for distribution — they require different tray management and different labeling
- On FTTH builds with passive optical splitters at FDHs, the splice diagram must show both the feeder fiber assignments and the distribution fiber assignments, keyed to the splitter module locations in the FDH
- Missing splice diagrams are not a minor omission. We once had a project where the splice diagrams weren't issued before splicing began, and the splice tech spliced everything passthrough on a segment that needed distribution taps. Complete re-splice on 23 closures. That's what a missing deliverable costs in practice.
Deliverable 6: Cable Assignment / Fiber Assignment Table
Fiber Assignment Table
Contains: A master table showing every fiber pair in the network assigned to a function or subscriber group. Columns typically include: cable ID, buffer tube color, fiber number within tube, fiber function (feeder, distribution, spare), assigned FDH port (for FTTH), assigned circuit ID (for enterprise or transport circuits), and notes. On large FTTH builds, this is sometimes maintained in a separate spreadsheet keyed to the splice diagrams rather than on a drawing sheet.
- The fiber assignment table is the document that network operations references when activating circuits — if it's wrong or missing, the NOC team can't match fiber to port without a full OTDR trace and inventory
- Spare fiber designations should be specific: "spare, available for future distribution" vs. "dark spare, reserved for future express route" — not just "spare"
- On BEAD-funded builds, some states are requiring the fiber assignment table as part of as-built documentation. Starting with a well-structured table during design makes compliance significantly easier at close-out
Deliverable 7: Bill of Materials
Bill of Materials (BOM)
Contains: A complete tabular list of every material item in the project, with columns for: item description, manufacturer part number or specification, unit of measure, quantity, and notes. Major categories include: fiber cable (by segment, type, and length), conduit (by type, size, and length), innerduct, conduit fittings (couplings, end caps, reducers), manholes and pull boxes (by type), FDH enclosures, splice closures, cable hangers and lashing wire (aerial), pole hardware (through-bolts, eyebolts, brackets), traffic control materials if included.
- The BOM quantity should include a stated overage factor — typically 5–10% on cable and conduit for waste and corrections. Document the overage factor so procurement knows it's intentional
- Manufacturer part numbers on the BOM reduce procurement errors significantly. "4-inch schedule 40 PVC conduit" generates multiple interpretations; a specific spec number or manufacturer PN does not
- The BOM should match the plan sheets. This sounds obvious, but on multi-revision projects where the design changes after the BOM was originally prepared, the BOM often doesn't get updated. This is a QA problem that costs money when the crew is in the field with the wrong quantity of a key material
On BOM accuracy: The BOM is the document that determines what gets ordered. A BOM error on a large project — say, underestimating conduit by 15% on a 40-mile build — means the crew runs out of material mid-build, the superintendent has to scramble for emergency procurement, and the schedule slips. We do a formal BOM-to-plan reconciliation on every package before issue: every item on the BOM traced back to a quantity source on the plan sheets. It's tedious. It catches errors every time.
Deliverable 8: Permit Set Drawings
Permit Set
Contains: A subset of the plan sheets produced specifically for permit submission, typically reformatted to include only the information relevant to the permitting authority. Highway encroachment permits require plan views showing crossing geometry, depth, and conduit type. Railroad crossing permits require plan, profile, and casing detail sheets. Municipal ROW permits may require just the plan view with utility conflict information. Each permit set should be a self-contained package — not a reference to the construction package — because permit reviewers don't always have access to the full construction drawing set.
- PE stamp and seal on every permit sheet. Not on the cover sheet only — some permit offices require the stamp on every individual sheet in the submittal
- Railroad permit drawings have additional specific requirements covered in our guide to railroad crossing permits for fiber construction — confirm those requirements before finalizing the drawing detail
- Traffic control plans often require separate PE seal from a licensed traffic engineer in addition to the OSP engineer of record — confirm jurisdiction requirements early
Deliverable 9: Traffic Control Plans
Traffic Control Plan (TCP) / MOT Plan
Contains: A plan view of each work zone showing: road geometry, existing lane configuration, proposed lane closure or traffic shift layout, sign locations and sizes (per MUTCD standards), cone and barrel placements, flagging locations if required, construction work zone boundaries, and temporary pavement markings where required. A separate typical section diagram is often included showing the standard lane closure sequence for repeated similar conditions on the project.
- TCP must reference the applicable MUTCD edition and any state supplement that modifies federal standards — most states have supplements, and permit offices will reject TCPs that don't comply with the state version
- Sign spacing tables from MUTCD Table 6C-3 or equivalent should be reproduced on the TCP or referenced explicitly — permit reviewers check this
- Separate TCP sheets for each road type (residential street, two-lane rural, multi-lane arterial, highway) — a single "typical" TCP that's applied to all conditions will not be accepted by most highway departments
- On BEAD builds, some state offices are requiring TCPs to be submitted with the permit applications, not after permit issuance. Plan for this in the schedule
Deliverable 10: Make-Ready Transfer Sheets (Aerial Projects)
Make-Ready Transfer Drawings
Contains: For each pole requiring make-ready work prior to fiber attachment, a pole diagram showing the existing attachment configuration (pre-make-ready) and the proposed configuration (post-make-ready), with annotated attachment heights for all attachments in both states. Includes: which attachments need to transfer to different heights, which attachments belong to which utility company, and any pole replacements required. These drawings are submitted to the joint-use administrator or utility company for make-ready approval.
- Make-ready transfer drawings are a separate deliverable from the main plan sheets — they serve a separate approval process with a different audience
- O-Calc Pro or SPIDA Calc output sheets are sometimes included as supporting documentation with the transfer drawings to show the structural basis for the proposed configuration
- Any poles flagged for replacement rather than transfer work should be clearly identified with the reason (overloaded, rotten, insufficient height margin) — utilities need this to initiate their own replacement process on their schedule
What Happens When Fiber Construction Package Deliverables Are Missing
Each missing deliverable has a predictable downstream consequence. Missing splice diagrams mean the splice crew has to call the design office for fiber assignments, which takes time and creates errors when answers are given verbally. A missing or wrong BOM means material shortages mid-build. An incomplete TCP means the permit office inspector shuts down the work zone.
But the most expensive missing deliverable, consistently, is one that isn't recognized as missing until the project is well underway. A fiber assignment table that was never produced gets discovered when network operations tries to provision circuits and has no record of which fiber serves which node. Recreating it from field traces and OTDR records is slow and expensive work — we've seen it add six to eight weeks to the project close-out timeline on mid-size builds.
The other common problem is a construction package issued in sections — plan sheets first, BOM later, splice diagrams "to follow" — where the later deliverables never materialize before construction starts. Construction crews adapt; they build from the plan sheets and figure out the splicing as they go. The result is a network that's built correctly structurally but has undocumented fiber assignments, non-standard splice configurations, and no record of what went where. As-built documentation becomes a forensic exercise instead of a straightforward record update.
Our CAD/GIS services produce complete, verified construction packages — every deliverable listed here, issued together, with internal consistency checks before any sheet is stamped. If you're planning a build and want to talk through what the package should look like for your specific project, reach out to our engineering team at info@draftech.com. We've done this across FTTH deployments, middle-mile builds, and commercial fiber routes — and the package structure does matter.
For BEAD projects specifically: NTIA and state program offices are requiring as-built documentation that traces directly back to the construction package — same cable IDs, same splice point IDs, same fiber assignment numbering. Build that consistency into the construction package from the start. Retrofitting it after construction is genuinely painful. The FTTH design standards we apply on funded builds are structured to make this handoff clean.