The Engineer Who Knows Where Everything Is: The Hidden Risk Running America’s Fiber Networks

By Glenn Wilson, Founder & CEO, MapItRight

Every fiber and telecom network operator has one. Ask any field operations manager who built the network, and eventually the answer circles back to a single engineer — often one of the company’s earliest hires — who has spent years accumulating the knowledge that never quite made it into a formal system: which splice cabinet actually feeds which street after last year’s emergency reroute, which as-built drawing is stale, which spreadsheet tab is the real one.

That knowledge lives in spreadsheets, in scattered PDFs, in someone’s memory of a repair made at 2 a.m. three winters ago. It works, until it doesn’t. And the moment it doesn’t — when that engineer retires, changes jobs, or is simply out sick during an outage — is the moment a fiber operator discovers how much of its network map was never actually a map at all.

A problem that scales badly

Spreadsheets are not a bad tool. They’re a bad tool for tracking a physical network that changes every week, gets touched by multiple field crews, and has to stay accurate enough that an engineer can trust it during a 3 a.m. outage call. A spreadsheet has no way of representing that a splice point is physically located at a specific coordinate, connected to a specific strand, feeding a specific set of addresses — it can only represent that information as disconnected rows that a human has to reconcile in their head.

That reconciliation problem gets worse, not better, as a network grows. A 2,000-subscriber rural fiber build might survive on a well-maintained spreadsheet and a folder of as-built PDFs, because one or two people can still hold the whole picture in their heads. A network passing 20,000 or 100,000 homes cannot — and yet a surprising number of mid-sized ISPs, electric cooperatives, and regional telecom operators are still running exactly that setup, simply because it’s the system they started with a decade ago and never had a clean moment to replace.

The costs show up in ways that are easy to miss until they compound. Duplicate work, when two crews unknowingly plan overlapping builds because neither had visibility into the other’s in-progress work. Truck rolls that turn into two-hour searches because the as-built documentation doesn’t match what’s actually in the ground. Outages that take longer to resolve because the on-call engineer isn’t the one who has the network memorized. None of these show up as a single dramatic failure — they show up as a steady tax on operating cost that never gets its own line item, so it never gets fixed.

See also: 5StarsStocks.com Cannabis: Cannabis Stocks Investment and Business Expansion

Institutional knowledge isn’t a retention strategy

There’s a temptation to treat this as a staffing problem — keep your senior engineers happy, and the knowledge stays with the company. That’s necessary, but it isn’t sufficient. Even a company with zero turnover eventually hits the limit of what any individual person can hold accurately in their head as a network scales past a few thousand connections. And the fiber and telecom labor market of the past few years has made the retention assumption riskier than it used to be — experienced outside-plant engineers are in high demand, and the operators who depend on tribal knowledge rather than systematized network data are the ones most exposed when a key person leaves.

The alternative isn’t a matter of working harder to keep the spreadsheets updated — it’s structural. Purpose-built network asset management software replaces the spreadsheet-plus-memory system with a single source of truth: every splice, strand, cabinet, and drop tied to its actual physical location and connection, editable by the whole team in real time, so the map stays accurate regardless of who’s on shift or who’s still with the company. It turns institutional knowledge from something one person carries into something the organization owns.

That distinction — between knowledge a company has access to and knowledge a company merely hopes someone remembers — is quietly becoming one of the more consequential operational risk questions in the fiber and telecom industry. It rarely gets discussed with the urgency of a funding deadline or a regulatory mandate. But for the operators who’ve already lived through the moment their most experienced engineer walked out the door taking the real map of the network with them, it’s not a hypothetical.