As-Built Documentation

What is an as-built actually for?

An as-built is not a closeout formality. It is the document that every future interaction with the plant depends on. A locate ticket, a repair, a capacity upgrade, a third party excavating nearby, all of it resolves back to what the as-built says is there.

That gives it a much longer life than the project. The design drawing describes an intention. The as-built describes reality, and reality is what the next crew has to work with.

Why does timing determine accuracy?

Buried plant stops being verifiable the moment it is covered. Once backfill goes in, the only sources are what was recorded and what someone remembers. Memory is not a survey instrument.

Capturing data at the point of installation, while the conduit is visible and the structure is open, produces a record that is checkable. Reconstructing it a week later produces a record that is plausible. The difference is invisible at closeout and expensive later.

This is the single most common quality gap in outside plant documentation, and it is entirely a process decision rather than a technical one.

What gets captured?

Route alignment and bore profile, with depth recorded along the run rather than at the endpoints only. Handhole and vault coordinates. Conduit count, size and color coding. Splice locations and slack positions. Footage installed, reconciled against the take-off.

Photographs are keyed to a station or coordinate so they can be tied back to a location, and taken at the point where the feature is still visible.

• Route alignment with depth recorded along the run
• Bore logs showing profile rather than endpoints alone
• GPS coordinates for every access structure
• Conduit count, size and color coding
• Splice and slack locations
• Footage and material reconciled against the take-off
• Photographs keyed to station or coordinate

How are positions and depths captured in the field?

Structure positions are captured with GPS receivers at the time each structure is set. The accuracy required, and the coordinate system and datum used, are agreed with the client up front so the data drops straight into the client's mapping system without conversion errors.

Bore depth comes from the locating system that tracks the drill head during the pilot bore. A reading is logged at regular points along the bore, typically at each drill rod, which builds the profile from entry to exit. That log is the most accurate depth record a buried route will ever have, because it is taken while the drill head is in the ground at that point.

Trenched and plowed sections are recorded differently, with depth checked and photographed in the open trench before backfill. Either way, the measurement happens while it can still be verified.

How do redlines become a final as-built?

Redlines are field markups on the design drawings, made as the work happens, showing where the installed plant differs from the plan. A moved handhole, a shifted bore, an added sweep or a changed duct count all go on the redlines on the day they happen.

The final as-built is the clean version produced from those redlines, the bore logs, the coordinates and the photographs. If the redlines are complete, the final drawing is a drafting task. If they are thin, the final drawing becomes guesswork, and that guesswork is what later misleads a locator.

How do as-builts support future locating?

When someone calls Sunshine 811 before digging near your route, the locator marks it in orange, the APWA color for communications, using a signal on the tracer wire and the records the owner holds. The as-built is what tells the locator where to expect the line, how deep it may run and where the access points are.

A record that shows depth along each bore, structure coordinates and tracer wire test points gives the locator what they need. A record that shows only a line on a map, drawn from the design, leaves them guessing in exactly the places where third party excavators are most likely to dig.

Format and handover

Where a client specifies an as-built template or a particular data format, such as CAD drawings, GIS layers or map files, that format is used. Delivering accurate data in a shape the client's system cannot ingest solves only half the problem.

The package is assembled and delivered together rather than trickled out over the weeks after demobilization. A closeout that arrives in pieces is a closeout that stays open on someone's list.

Can you document a route that was built without records?

Yes, with honest limits. A documentation-only engagement can locate the route using its tracer wire, open and record every accessible structure, verify duct occupancy and condition, and produce a drawing and structure schedule of what is there.

What it cannot do is recover the bore profile with the accuracy of a log taken during drilling. Depth estimates from a surface locator are useful, but they are estimates. The record states which values were measured and which were estimated, so no one later treats an estimate as a survey.

What does poor documentation actually cost?

It costs a mis-marked locate and a strike. It costs a maintenance crew an afternoon finding a handhole. It costs a designer a field survey to establish what already exists before an upgrade can be planned. And it costs the contractor the next contract, because a project manager remembers which vendors left them with a usable record.

None of those costs appear on the original invoice, which is exactly why documentation is the first thing cut when a job runs tight, and exactly why it should not be.