GIS As-Built Documentation Services
GIS as-built documentation for fiber builds: route, pole, vault, and splice data captured to GPS, normalized to your schema, delivered as GIS-ready files.
GIS as-built documentation is the process of recording exactly what was built in the field, aerial routes, underground conduit and duct bank, splice enclosures, pedestals, vaults, handholes, and pole attachments, and converting that field record into GIS-ready data that matches (or corrects) the design issued before construction. It is the record a network owner relies on for locate tickets, permit closeout, maintenance, and future design work, so it has to reflect what is actually in the ground and on the pole line, not just what the design drawing said should be there.
What GIS As-Built Documentation Covers
A complete as-built package covers the route centerline, splice enclosure and pedestal locations, vault and handhole positions, conduit and innerduct paths with depth of cover, and utility crossing data for underground work. For aerial work it covers pole locations, attachment heights, and span data. The package also includes redline markups from the construction crew, GPS-tagged photos at key structures, and a comparison against the permitted design so any field deviation is documented, not buried. This is the record that gets handed to locate services, maintenance crews, and the next engineering project that touches the same corridor.
How Fiber Construction Company Delivers As-Built Data
Field crews capture location data with GPS or GNSS equipment during construction and mark up redlines as they build, so the record starts accurate rather than getting reconstructed from memory afterward. Office staff run QA/QC against the issued design, flagging and resolving discrepancies before delivery. Data is normalized to the client's GIS schema and attribute requirements rather than handed over in whatever format is easiest for the field crew, and delivered in the format the client's system actually ingests, whether that is an Esri geodatabase, shapefile, KMZ, or CAD file.
Methods and Scope
Standard capture uses handheld GPS/GNSS for route and structure positions, with RTK survey-grade equipment used when a project calls for tighter tolerance than standard GPS provides. Underground work ties in locate and pothole data at utility crossings so depth and clearance are documented, not estimated. Aerial work ties pole and attachment inventory to the as-built map. Splice and test data from /services/splicing-testing.html work gets referenced back to the as-built record so the network map and the physical layer stay in sync. Deliverables can integrate directly with a client's existing GIS or OSS platform rather than sitting as a standalone file.
What a Buyer Should Know Before Hiring
Accuracy requirements are not the same everywhere. A municipal franchise agreement, a utility joint-use permit, and an internal carrier standard can each specify different GPS tolerance and attribute schema, so confirm the requirement before construction starts rather than after. As-builts should be delivered promptly after construction close, since a locate ticket or a permit closeout that references a map still in progress is a liability, not paperwork. Ask any contractor how field data gets QA'd against the issued design before delivery, because an as-built that was never checked against the permit is just a guess with coordinates attached.
GIS As-Built Documentation Services, answered
What file formats does GIS as-built documentation come in?
Typical deliverables include Esri geodatabase, shapefile, KMZ, and CAD files, along with PDF redlines for internal review. The right format depends on what GIS or OSS platform the client uses, and that should be confirmed at project kickoff.
How accurate is GPS-based as-built capture?
Standard handheld GNSS capture is typically sub-meter, which is adequate for most route and structure documentation. RTK survey-grade GPS is used when a project or a client standard requires tighter tolerance. Set the accuracy target in scope before construction begins, not after.
Do you document both aerial and underground builds?
Yes. Aerial documentation covers pole locations, attachment heights, and span data. Underground documentation covers conduit and duct bank paths, depth of cover, vault and handhole locations, and utility crossing data captured during locate and potholing.
How does GIS as-built documentation relate to permitting?
As-built data is what closes out a permit with the issuing authority and supports future locate requests against the route. It is downstream of the design and permitting work covered on the parent /services/engineering-permitting.html page.
Can you match our existing GIS schema and attribute structure?
Yes. Field data is normalized to the client's schema and attribute requirements before delivery rather than handed over in a generic format, so it drops into an existing GIS or OSS platform without a separate conversion step.