Nevantin Learn

Fiber As-Builts and Network Documentation

A fiber network you can't document is a network you can't operate. As-builts — the record of what was actually constructed, where, and how it tested — are the difference between a five-minute outage diagnosis and an excavation hunt, and between an asset a lender will finance and a liability under the dirt.

What a complete closeout package contains

Route documentation: the actual constructed alignment — depths, offsets, GPS-located structures — ideally as GIS data, not just marked-up drawings. Splice documentation: a diagram for every closure and cabinet showing which strand lands where, plus strand-assignment tables from end to end. Test records: the bidirectional OTDR traces and loss readings per strand, in native tester files. The boring log: bore paths and depths for drilled segments, which future excavators will bet their locates on. Redlines captured in the field are the raw material; the closeout package is the finished product.

Why it's worth real money

Every future event prices the documentation: a restoration crew with accurate as-builts finds a cut in minutes; without them, hours — at outage rates. Lenders and buyers diligence network assets against their records; grant programs require closeout documentation before final draws; and locate accuracy — the thing that keeps the next excavator out of your cable — is only as good as what was recorded. Undocumented spare conduit is the classic tragedy: paid for once, findable never.

Getting it from your contractor

Put the package in the contract: format (GIS schema or template), granularity, test-file types, and the rule that pay apps track documentation delivery — not just footage. Then hold the line: documentation delivered months after crews demobilize was reconstructed, not recorded. It's a standing deliverable of our splicing and testing work and every network Nevantin constructs.

Common Questions

What format should fiber as-builts be in?

GIS data (or an agreed schema) for routes and structures, standard splice-diagram formats for closures, and native tester files for OTDR results — PDFs alone lock the data away.

Who owns the as-builts?

The network owner should, by contract — including the underlying data files, not just printouts. Contractors keep copies; ownership belongs with the asset.

Can old undocumented plant be reconstructed?

Partially: toning, potholing, and OTDR mapping can rebuild a usable record — at real cost. It's the expensive proof of why documentation should ride with construction.

Keep Learning

Planning actual construction? Nevantin Services builds fiber, power, gas, and water infrastructure across 12 states — talk to us or explore what building in your state involves.