What is the difference between an as-built and a design drawing?

A design drawing shows what was planned. An as-built shows what was actually installed, including every change made in the field: a bore pushed deeper to clear a utility, a handhole moved to avoid a driveway, an extra crossing. Locators and repair crews rely on the as-built, so it must reflect installation, not the original design intent.

How often will we receive production reports?

Daily, through active construction. Each report covers the day's footage by activity, structures set, splices completed, any conflicts or field changes, and photos keyed to location, along with the next day's plan. Daily reporting means you see progress and problems as they happen, without having to chase the crew or wait for a weekly summary.

Can you deliver as-builts in our GIS or CAD format?

Yes, where the format is agreed before construction starts. Owners use CAD drawings, GIS data and marked up PDFs, often with their own layer standards or title blocks. Agreeing the format up front means field data is captured in a form that converts cleanly. Changing format after the work is done adds time and creates chances for transcription errors.

Why should documentation be captured during construction?

Because data recorded while a feature is exposed is an observation, and data recorded after backfill is a guess. Depths, crossing separations and structure positions can be measured and photographed accurately only while they are visible. Reconstructing them from memory at the end of a job produces as-builts that are approximately right, which is not good enough for locating.

Does a small project get the same documentation as a large one?

Yes. A single driveway bore gets the same standard as a multi week build: daily reporting, keyed photographs, a bore log with depth along the run and a closeout package. The volume is smaller, but the contents are the same. Small jobs are where documentation is most often skipped, and a missing record causes the same problem whatever the project size.

What happens to field changes in the documentation?

Field changes are recorded the day they happen in the daily report, with photographs and location. Changes that affect cost or scope go through the change order process with written approval. At closeout, the as-built reflects every change, and the change order record lists approvals, so the documentation explains both what was built and why it differs from the design.

Projects

Documentation Standards

TLDR

Documentation on every project follows the same standard regardless of size: daily production reporting through construction, field data captured as installation happens rather than reconstructed afterward, and a complete closeout package assembled and delivered as one submittal.

The standard applied to every project

A single driveway bore and a multi week backbone build receive the same documentation discipline. The volume differs, the standard does not.

That matters because the small job is exactly where documentation tends to be skipped, on the reasoning that it is too minor to matter. It matters equally, because a locator does not care how large the project was that installed the plant they cannot find.

Capture during construction, not after

Data recorded while a feature is exposed is an observation. Data recorded after backfill is a recollection. That distinction is the difference between an as-built that can be relied on and one that is approximately right.

This is a process decision rather than a technical one, which is why it is a standard rather than a capability.

What does a daily production report contain?

A daily report tells the project manager what was built, where, and what changed, without a phone call. It arrives each working day during active construction, so problems are visible the day they appear rather than at the end of the job.

Date, crew and work location by street, station or segment
Footage installed by activity: bore, conduit, cable, strand
Structures set and splices completed
Conflicts, field changes and anything that stopped work
Locate and permit issues found on site
Photographs of the day's work keyed to location
Planned work for the next day

How are photographs made useful?

A photograph is only useful if someone can tell where it was taken and what it shows. Project photos are keyed to a station, coordinate or structure ID, and they are taken at the moments that matter: before work starts, while crossings and conduit are exposed, and after restoration is complete.

Before photos protect both parties if a property owner later questions the condition of a driveway or lawn. Exposed photos prove depth and separation at crossings. After photos prove restoration was done, and they are taken once it is actually finished.

Why agree the format before construction?

Every network owner stores records differently. One wants CAD drawings, another wants GIS data, another wants marked up PDFs on its own title block. Agreeing the format before construction means data is captured in a form that converts cleanly, rather than retyped from field notes at the end.

What is delivered

Daily reports through active construction. A closeout package containing as-built data, bore logs, coordinates, keyed photographs, test records where applicable, reconciled quantities, restoration verification and permit closure.

Delivered together, in the agreed format, within the agreed window.

Key takeaways

An as-built records what was actually installed, including every field change, not the original design intent.
Data recorded while a feature is exposed is an observation, while data recorded after backfill is a recollection.
Daily production reports let a project manager see progress and problems the day they happen.
Agreeing the documentation format before construction avoids retyping field notes into the owner's system at closeout.

Key terms

As-built: An as-built is a drawing or data set showing what was actually installed: alignment, depth, structure positions, conduit counts and every field change. It replaces design intent in the owner's records and is what locators and repair crews rely on.
Daily production report: A daily production report summarizes each working day on a construction project: location, footage installed by activity, structures set, conflicts, field changes, keyed photographs and the next day's plan. It keeps the project manager informed without a phone call.
Keyed photograph: A keyed photograph is a project photo tied to a specific station, coordinate or structure ID. The key lets anyone reviewing the record later know exactly where the photo was taken and what it shows.
Take-off reconciliation: Take-off reconciliation compares installed quantities, such as footage of bore, conduit and cable or the number of structures, against the quantities estimated from the design. It confirms what was built and supports accurate final billing.

Documentation created at each project stage

Stage	Records created	Who relies on them
Locate and plan	Locate tickets, pothole records, bore path plan	Crew, permitting authority, utility owners
Mobilize	Pre-construction photos, traffic control setup	Project manager, property owners
Execute	Bore logs, daily reports, exposed condition photos	Project manager, inspectors
Document	As-built data, splice and test records	Network owner, engineers, locators
Closeout	Reconciled quantities, restoration photos, permit closure	Owner, accounting, permitting authority

Outside plant project lifecycle

What this means for your project

Documentation is the part of a project that outlasts the crew. If it is wrong or missing, the cost shows up later as a strike, a slow locate or an expensive repair on plant nobody can find, long after final payment.

For schedule, daily reporting removes the need to chase status and surfaces problems early enough to act on them. A conflict reported the day it is found can be resolved in a day. One discovered at the end of the job can hold up closeout for weeks.

For closeout, agreeing the format and contents up front is the single best way to avoid delays. When the package arrives in the form your systems expect, review is quick and the project file can close.

Typical scope

Format and detail level agreed before construction starts
Daily production reporting through active construction
Field data captured at the point of installation
Photographs keyed to station or coordinate
Quantities reconciled against the take-off
Restoration verified and photographed after restoration
Closeout compiled and delivered as one package

What you receive

Daily production reports
As-built drawings or route data
Bore logs with depth and profile
Access structure coordinates
Keyed photographic documentation
Reconciled footage and material record
Restoration verification photographs
Permit closure support

Frequently Asked Questions

What is the difference between an as-built and a design drawing?: A design drawing shows what was planned. An as-built shows what was actually installed, including every change made in the field: a bore pushed deeper to clear a utility, a handhole moved to avoid a driveway, an extra crossing. Locators and repair crews rely on the as-built, so it must reflect installation, not the original design intent.
How often will we receive production reports?: Daily, through active construction. Each report covers the day's footage by activity, structures set, splices completed, any conflicts or field changes, and photos keyed to location, along with the next day's plan. Daily reporting means you see progress and problems as they happen, without having to chase the crew or wait for a weekly summary.
Can you deliver as-builts in our GIS or CAD format?: Yes, where the format is agreed before construction starts. Owners use CAD drawings, GIS data and marked up PDFs, often with their own layer standards or title blocks. Agreeing the format up front means field data is captured in a form that converts cleanly. Changing format after the work is done adds time and creates chances for transcription errors.
Why should documentation be captured during construction?: Because data recorded while a feature is exposed is an observation, and data recorded after backfill is a guess. Depths, crossing separations and structure positions can be measured and photographed accurately only while they are visible. Reconstructing them from memory at the end of a job produces as-builts that are approximately right, which is not good enough for locating.
Does a small project get the same documentation as a large one?: Yes. A single driveway bore gets the same standard as a multi week build: daily reporting, keyed photographs, a bore log with depth along the run and a closeout package. The volume is smaller, but the contents are the same. Small jobs are where documentation is most often skipped, and a missing record causes the same problem whatever the project size.
What happens to field changes in the documentation?: Field changes are recorded the day they happen in the daily report, with photographs and location. Changes that affect cost or scope go through the change order process with written approval. At closeout, the as-built reflects every change, and the change order record lists approvals, so the documentation explains both what was built and why it differs from the design.

Related services

Request a Bid

Ready to start your next directional drilling or fiber project?

Send the scope and we will come back with a clear, documented bid. Owned crews, aerial and underground under one contract, and a closeout package that lets you close the file.

Request a Bid Call (386) 396-2033

Most bid requests receive a response within one business day.