FTTH BOQ and BOM Audit Before Material Release: Eight Checks for US Fiber Builds

A fiber bill of quantities can be numerically correct and still be unsafe to release for procurement. The problem is rarely one dramatic error. It is usually a chain of small mismatches between the route design, equipment schedule, splice plan, approved material list and construction assumptions.

For US FTTH programs, that chain matters even more when public funding or client controls require traceable material decisions. NTIA's current Build America, Buy America guidance explains that BEAD deployments may require manufacturer certification letters for equipment subject to domestic-production requirements, while certain waived electronics carry reporting obligations. The practical implication is simple: procurement evidence should be connected to the design quantity record, not collected as an afterthought.

This guide sets out eight checks an engineering or construction team can complete before issuing an FTTH BOQ or BOM for purchase.

First, separate the BOQ from the BOM

The two terms are often used interchangeably, but they answer different questions.

A BOQ records measured work and installed quantities. It may include trench length, duct length, aerial span length, handholes, cabinets, closures, splitters, cable placement, splicing units and restoration.

A BOM lists the physical products required to deliver that work. It should identify cable types, duct sizes, enclosures, connectors, splitters, mounting hardware, grounding components and other approved items at a level that procurement can order.

The BOQ explains how much work the design creates. The BOM explains what must be bought. A reliable material release connects both to the same approved design revision.

1. Lock the design baseline

Do not audit quantities against a moving target. Record the drawing revision, GIS export date, splice-plan version and premises dataset used for the takeoff.

This baseline should answer:

• Which route geometry was approved?
• Which service locations were included?
• Which aerial and underground decisions were final?
• Which cabinet, terminal and closure locations were accepted?
• Which design comments remain open?

If the takeoff was produced before the latest route change, label it superseded and regenerate it. Manual quantity edits without a linked design change create a second source of truth that becomes difficult to defend later.

2. Reconcile route lengths by installation condition

A single total cable length is not enough. Split route quantities by installation condition because each condition drives different materials and labor.

At minimum, distinguish:

• existing duct
• new conduit
• direct-buried construction
• aerial strand
• self-supporting aerial cable
• building or riser sections
• bridge, railroad or other special crossings

Then compare GIS-derived lengths with plan dimensions and construction notes. Check that slack, vertical transitions, pole risers, structure entries and termination tails are governed by a documented rule. Contingency should be visible as a separate allowance, not hidden inside rounded route lengths.

3. Test cable quantities against topology

Cable quantities must agree with the logical network, not just the mapped route.

For every feeder and distribution segment, verify the origin, destination, fiber count, cable identifier and termination point. Confirm that parallel routes are not collapsed into one length and that reused infrastructure has not been counted as new material.

The splice plan is a useful control. Every new cable in the BOM should appear in the splice documentation, and every planned splice cable should have a corresponding material line. A missing relationship usually signals an incomplete route transition, an outdated cable ID or a segment that was measured twice.

4. Reconcile passive equipment with served locations

Cabinets, splitters, terminals and ports should be checked against the approved serving-area model.

For each service area, confirm:

• passed locations
• planned connection points
• splitter hierarchy
• port utilization
• spare capacity policy
• terminal port counts
• feeder and distribution capacity

The objective is not to maximize theoretical utilization. It is to confirm that the equipment schedule implements the approved topology and provides only the defined level of growth or operational spare.

This is also where location-data discipline matters. The FCC's fixed-broadband reporting guidance ties availability to locations that are actually served or can receive a standard installation. A design team should therefore maintain a controlled relationship between serviceable locations, network endpoints and the quantities used to construct them.

5. Check civil quantities against constructability notes

Civil takeoffs often fail because the plan geometry and the construction notes are reviewed separately.

Compare conduit lengths with trench or bore lengths, allowing for the actual duct configuration. Confirm handhole spacing, road-crossing details, duct-bank changes, pole risers, marker systems, warning tape, draw rope and restoration.

Special crossings deserve individual BOQ lines. A railroad, controlled-access highway, watercourse or congested utility corridor may use the same route length as ordinary construction but require very different design evidence, permits and installation methods.

If a method remains unconfirmed, do not bury it in a generic quantity. Isolate it as a provisional item with an explicit design hold.

6. Map every material line to an approved specification

Each controlled line should connect to an approved product description, specification or client material code. Check fiber type, cable construction, environmental rating, duct size, enclosure capacity, connector interface, splitter ratio and mounting arrangement.

For federally funded US broadband work, the project team should also determine which items require domestic-manufacturing evidence and which waived electronics require reporting. NTIA maintains the current BABA compliance framework and self-certification resources. The project-specific award terms still govern, so the design team should not treat a supplier's marketing statement as the complete compliance record.

7. Make allowances explicit

Allowances are necessary, but invisible allowances make audits unreliable.

Separate design quantity from procurement allowance. Typical controlled additions may cover cable slack, drum optimization, breakage, minor route adjustment or spare components. Each percentage or fixed quantity should have an owner and a rule.

Avoid applying one blanket percentage to every material. Cable, conduit, closures, splitters and mounting hardware have different risk profiles. For example, drum optimization affects cable ordering, while closure quantities should normally remain tied to discrete network nodes.

A reviewer should be able to see the base quantity, allowance and final purchase quantity without reverse-engineering a rounded total.

8. Run a three-way release check

Before procurement, compare three records:

1. the approved design and GIS quantities 2. the BOQ and BOM 3. the procurement schedule and compliance evidence

The release review should confirm revision alignment, product approval, quantity logic, allowances, open holds and ownership of exceptions. Record the result in a short signed checklist or controlled review log.

This final check is not a substitute for detailed QA. It is the gate that confirms detailed QA has been completed and that procurement is buying against the same network the field team is expected to construct.

A practical acceptance checklist

A material package is ready for release when:

• all quantities reference one approved design baseline
• route lengths are separated by construction condition
• cable IDs and fiber counts match the splice plan
• passive equipment matches the serving-area model
• civil materials reflect the stated construction method
• each product maps to an approved specification
• allowances are visible and justified
• compliance documents are identified where required
• exceptions and provisional quantities have owners
• the final procurement schedule reconciles to the BOQ and BOM

The value of a controlled pilot package

When a delivery team has a large backlog, it is safer to test the process on one bounded serving area than to outsource an entire program immediately. A pilot can include the route drawing, quantity takeoff, cable and equipment schedule, splice documentation, exception log and QA checklist.

Acceptance criteria can be measured: zero unexplained quantity differences, complete cable-to-splice traceability, approved material codes, documented allowances and closure of review comments.

Pathworks Engineering can support defined FTTH design-production and documentation packages within a client's existing standards, templates and controls. For teams facing a quantity, revision or closeout backlog, a small paid pilot provides a practical way to test quality and handoff discipline before increasing volume.

Sources

• [NTIA: Build America, Buy America](https://www.ntia.gov/programs-and-initiatives/build-america-buy-america)
• [BroadbandUSA: 2026 BEAD Program General Terms and Conditions](https://broadbandusa.ntia.gov/funding-programs/policies-waivers/BEAD_GTCs_Nov_2025)
• [FCC: Fixed Broadband Availability Data Overview](https://help.bdc.fcc.gov/hc/en-us/articles/5290946484763-Fixed-Broadband-Availability-Data-Overview)