The Importance of As-Built Documentation

What makes a drawing an as-built instead of a plan?

A plan is an intention. An as-built is a measurement. The difference is not the title block, it is whether the numbers on the sheet came from the field or from the design.

Three things separate a real as-built from a plan set with a stamp on it. It records values that were measured after installation. It shows deviations from the design as dimensioned changes rather than as notes. And it is reconciled, meaning someone compared the field redlines against the design file and resolved the conflicts instead of stapling them together.

The test is simple. Hand the drawing to a locate technician who has never been to the site and ask them to find a specific splice point. If they can walk to it, the document is an as-built. If they have to call someone, it is a plan.

What does a directional bore as-built need to contain?

A bore is invisible the moment it is complete, so the as-built is the only description of it that will ever exist. Endpoint coordinates alone are not enough, because a bore that lands on the exit stake can still have dipped, climbed, or drifted between the two ends.

Walkover tracking gives the data for free if the crew logs it. The transmitter behind the bit reports depth, pitch, and roll at every rod. Recorded rod by rod, those readings rebuild the vertical profile on paper and let anyone check the path against the design. Recorded only at the ends, they prove almost nothing about the middle.

The as-built also has to say what each depth is measured from. A depth column with no stated reference surface cannot be checked, and a later grading job or road widening can make a correct number look wrong. State the vertical reference once, and note wherever the surface at the time of the bore differed from finished grade.

• Entry and exit coordinates, plus rod by rod pitch and depth along the path.
• Depth of cover referenced to finished grade at every crossing and at any low point.
• Horizontal offset from a permanent reference line, not from a temporary stake.
• Measured vertical and horizontal separation at each foreign utility crossing.
• Product installed: conduit or cable size, type, and count, with duct assignment.
• Any deviation from the permitted alignment, dimensioned and explained.

Why is measured separation from other utilities worth recording?

Separation is the number that everyone needs later and almost nobody writes down. When a bore crosses a gas main, a water line, or an electric duct bank, the crew that potholed it knows the exact clearance at that moment. That knowledge evaporates at demobilization unless it lands on a sheet.

The next contractor working that corridor will file a Sunshine 811 ticket and get a paint line on the surface. A paint line tells them where a facility is horizontally. It does not tell them what is below it, how deep, or how much room they have. Recorded separation is what converts a locate mark into a safe excavation plan.

Recording separation also protects the installing contractor. When a third party damages a line and claims it was not where the records said, a dimensioned crossing detail with a date and a measurement is a far better position than a recollection.

How do as-builts affect locatability?

Buried nonmetallic conduit is only locatable through a tracer wire, and a tracer wire is only useful if it is continuous, terminated somewhere accessible, and documented. An as-built that shows tracer wire routing, access points, and continuity test results is the difference between a quick locate and an excavation.

Slack locations deserve the same treatment. An OTDR reports distance along the fiber, which includes every slack coil, every splice point loop, and the curvature of the route. Without documented slack storage, a fault at a given optical distance can sit a meaningful distance away from where a tape measure along the surface would put it.

Structures anchor everything else. Handholes and vaults are the physical index to the route, so their coordinates, type, and lid marking belong in the as-built attribute table rather than in a photo folder.

What does an aerial as-built need that an underground one does not?

Aerial plant is visible, which makes people assume it does not need documenting. The opposite is true, because aerial plant lives on structures owned by someone else and is governed by clearance rules that get audited.

The record should identify each pole by the owner's tag number, not by a sequential count on the drawing, since that tag is the only identifier the pole owner and the next attacher will recognize. Span lengths, attachment height, strand size, and the position of the attachment relative to other occupants all belong on the sheet.

Make-ready work performed by others should be captured too. If a power company raised a secondary or a prior attacher moved down, that changed the pole and changed the clearance envelope. An as-built that documents the pole as found and as left is what keeps a later joint use audit from turning into a dispute about who moved what.

How should as-built data be captured in the field?

The cheapest as-built is the one captured while the trench is open and the crew is standing in it. Everything after that is reconstruction, and reconstruction is where errors enter.

Practically, that means a field data workflow rather than a memory workflow: mapping grade GPS or measured ties to permanent features, structured attribute entry rather than free text, photos tagged to a station, and a same day handoff to whoever maintains the drawing file.

It also means deciding the accuracy class before mobilization. Mapping grade GPS is appropriate for routine distribution work. Signed and sealed survey is appropriate for easement documents, plats, and critical crossings. The requirement drives equipment and time, and it cannot be added after backfill.

Who uses an as-built after the project ends?

Mostly people who were never on the job. The crew that built the route remembers where it runs for a few months. Everyone who touches it over the following decades depends on the record instead.

Locate technicians use it to mark the facility when a Sunshine 811 ticket comes in, since Florida Statute Chapter 556 requires member operators to locate their own facilities. A designer uses it to route the next project through a crowded corridor. A maintenance crew uses it to turn an OTDR fault distance into a place to dig. The permitting agency uses it to close the permit and release the bond, and a pole owner's auditor uses the aerial portion to check attachment heights.

Each of those users needs different fields. That is why an as-built prepared only for permit closeout often fails the maintenance crew. Build the record for the hardest user, which is usually the person trying to find a fault at night with a locator and a shovel.

How long should as-built records be kept, and in what form?

For as long as the plant stays in the ground or on the poles, which for conduit and structures can be decades. The record outlives the first cable, the first owner's staff and often the first owner.

Keep the data in working formats, not only as PDFs. A georeferenced file with attributes can be loaded into the next GIS platform. A scanned sheet has to be redrawn by hand, and every redraw adds error. Store native bore logs and trace files with the drawings so the measurements behind them survive as well.

Plan for transfer. Networks are sold, merged and handed to new operators. A record set with a clear index, a stated coordinate system and consistent identifiers moves to a new owner intact. One that lives in a former employee's folders usually does not.

What does a missing or wrong as-built actually cost?

The costs are rarely charged to the project that created them, which is why they get tolerated. They land on the next project, on the maintenance budget, or on an insurance claim.

A wrong depth becomes a strike. A missing tracer wire becomes an excavation to find a duct. An undocumented deviation becomes a redesign when the next fiber build tries to occupy the same corridor. A missing test baseline becomes a week of troubleshooting on a span that was marginal from the day it was spliced.

There is also a regulatory dimension. Restoration bonds, permit closeouts, and agency acceptance all depend on documentation the agency can read. Work that was performed correctly but recorded poorly can fail an inspection that the same work, recorded well, would have passed.

How do you tell a good as-built from a bad one before you accept it?

Spot check it against the ground. Pick two or three points the drawing describes precisely, go find them, and see whether the description holds. A package that survives three random checks is usually honest throughout, and one that fails the first check is rarely wrong in only one place.

Then check internal consistency. Station numbering should be continuous, footages should sum to the route length, structure counts should match the material records, and splice diagrams should match the fiber assignments in the test data. Documents that disagree with each other were assembled, not verified.

• Field verify two or three described points before accepting the set.
• Confirm stationing is continuous and totals reconcile to installed footage.
• Match structure and material counts against the schedule and submittals.
• Confirm splice diagrams and test records use the same fiber identification.
• Confirm the vertical reference is stated and used consistently throughout.