As-Built Documentation
Records that capture the actual, physically installed condition of a fiber network — including any field changes from the original design.
As-built documentation is the set of records — drawings, geographic data, attribute information, photos — that capture the actual, physically installed condition of a fiber network at a specific point in time. As-built records reflect not just the original design intent but every field change made during construction, every redirect around an obstacle, every splice that ended up in a slightly different location than the design specified.
In fiber networks, as-built documentation is operationally critical for three reasons. First, fault localization: when a fiber is cut or a splice fails, accurate records let the OSP team find the problem in minutes instead of hours. Second, future builds: planning a new route through existing infrastructure requires knowing exactly what's already installed. Third, compliance: BEAD and similar federal programs require structured as-built reporting tied to the FCC's location fabric.
The traditional as-built workflow — paper redlines from the field, retyped into a GIS or CAD system, reviewed weeks later — produces records that are often months out of date. Modern fiber GIS replaces this with field-app-based capture (mobile redlines, photo evidence, GPS-stamped) that syncs to the office in real-time. The as-built data IS the inventory data; there's no separate reconciliation step.
In MapItRight, as-built capture happens in the field via the iOS/Android app, sync's to the office instantly, and is reviewable/approvable by designers via the web. Every change is audit-logged with who, when, and what changed — meeting both operational and compliance needs.
As-built data requirements under BEAD are specific: the NTIA's BEAD Final Rule requires operators to submit per-location records including GPS coordinates (horizontal accuracy ±3 m or better), service technology type, maximum advertised download and upload speeds, and service availability date. These records must be tied to FCC Broadband Map location fabric IDs — a 14-digit BSL (Broadband Serviceable Location) identifier for every address. Paper redline workflows cannot produce BSL-linked data directly; operators must perform a post-hoc address-match that introduces 5–15% location error in typical rural builds where addressing is imprecise.
As-built documentation vs design drawings: Design drawings represent engineer intent — what the network should look like if installation goes perfectly. As-built records reflect reality — actual splice locations, conduit offsets around obstacles, drops that were aerial instead of buried, fiber counts that changed during splicing. The difference between the two can be 10–30% in a typical build with field-improvised changes. Using design drawings as a substitute for as-built documentation generates fault localization errors of 50–500 ft when crews are dispatched to repair a break — because the splice closure is where it was actually installed, not where the design placed it.
Accurate as-built records reduce recurring operational costs measurably. Utilities that maintain current GIS-based as-built records resolve network outages 40–60% faster than those relying on paper records, according to operator self-reported benchmark data. For BEAD-funded operators, as-built inaccuracies at the time of the closeout audit can trigger partial reimbursement holds; program administrators in multiple states have required re-survey of 10–25% of locations when initial submissions failed GPS accuracy standards. The cost of retroactive field survey typically runs $50–$150 per location, making up-front field capture economics clear.
As-built documentation workflows vary across operator types. Large incumbents often have dedicated OSP drafting teams who process field redlines in 2–6 week backlogs. Municipal fiber operators frequently operate lean teams where field technicians are also expected to capture as-builts — a workflow that only succeeds with mobile-first capture tools. Rural cooperatives building their first fiber network under BEAD often start with no OSP documentation infrastructure at all, requiring them to adopt a modern GIS-based as-built system as part of the initial build process. The choice of as-built workflow directly determines the operator's ability to meet BEAD reporting deadlines and maintain network performance over the 20-year asset life.