By Glenn Wilson, Founder & CEO, MapItRight
Every fiber network starts with a design: a set of drawings showing exactly where each conduit, splice cabinet, and drop is supposed to go. And almost every fiber network, once built, deviates from that design in dozens of small ways a construction crew never formally reports — a conduit rerouted around an unexpected rock formation, a splice point moved ten feet because of a property line dispute, a drop run along a slightly different path than planned because the original route turned out to be blocked.
None of these individual changes are unusual, and none of them are necessarily a problem in the moment — field crews make reasonable judgment calls on the ground every day, and that flexibility is part of how construction actually gets done. The problem is what happens after: in a large share of fiber builds, that final in-ground reality never fully makes it back into an updated set of records. The design drawings stay exactly as they were before construction started, and the network operator inherits a set of “as-built” documentation that isn’t actually as-built at all.
Where the gap comes from
This isn’t usually a case of anyone cutting corners. It’s a structural handoff problem. Construction crews are focused, correctly, on building the network — not on maintaining a parallel paper trail of every field adjustment in real time. Updating formal design records after the fact is typically a separate task, assigned after the crew has moved on to the next segment, competing for time against the next project’s deadline. Over the course of a multi-month build touching hundreds of individual splice points and routing decisions, it’s easy for that reconciliation work to fall permanently behind — and once a network is marked complete and the crew has demobilized, the institutional memory of exactly what changed and why leaves with them.
The consequences surface later, and usually at the worst possible time. A field technician responding to an outage pulls up the official documentation, drives to the location it shows, and finds nothing there because the actual splice point is a block away. A new fiber build from a different provider damages an existing line because the records used for locate requests didn’t reflect where the cable actually runs. An insurance claim or warranty dispute over damaged infrastructure turns into a disagreement about what the network was actually supposed to look like, because the only records available are the pre-construction design, not reality.
Treating as-built accuracy as a workflow, not an afterthought
The operators who avoid this problem consistently share one trait: they don’t treat as-built documentation as a paperwork task to be completed after construction wraps. They build the update into the construction workflow itself, so that a field change gets captured at the moment it happens, by the crew that made it, rather than reconstructed weeks later from memory.
That’s the specific gap purpose-built as-built fiber documentation tools are designed to close — giving field crews a way to record deviations from the original design directly, tied to the actual network asset it affects, so the documentation an operator relies on six months or six years later reflects what a technician would actually find in the ground, not just what a design engineer originally planned before the first shovel went in.
It’s an unglamorous problem compared to the funding announcements and buildout milestones that get the industry’s attention. But for the field technician standing at 2 a.m. trying to find a splice point during an outage, the accuracy of that record is the difference between a fifteen-minute repair and a two-hour search — and that gap between paper and reality is exactly where a network’s documentation is worth the most and trusted the least.
Glenn Wilson is the founder and CEO of MapItRight, a fiber network mapping and outside-plant management platform for ISPs, electric cooperatives, and telecom engineering firms.
