A Fibre Network Without As-Built Records Is an Asset No One Can Read Anymore.

A technician arrives to fix a fault on a fibre run. The chamber is open, the cable is black like all the others, and no one can tell him which splice has failed, or where the route actually runs compared with the original design. It happens more often than you’d think: the physical network was laid to a proper standard of workmanship, but its representation — diagram, labels, register — hasn’t kept pace. The result: a fault that should have cost an hour costs a day instead, and no one really knows any more what the infrastructure they paid for is actually worth.

As-built records are not the design — they are site truth.

The detailed design describes what is meant to be laid. The as-built record describes what was actually laid — and on site the two almost never coincide: a diversion around an unforeseen utility, a splice moved twenty metres from where it was planned, a cabinet recabled at the last moment. The standard ISO/IEC 14763-2, which covers the planning, installation and administration of building and campus cabling, treats documentation as part of the handover, not as an optional attachment. A complete as-built record shows the real route run by run, the physical position of every splice — including the coil, not just the cabinet — the actual lengths, and a precise match with the OTDR test traces, which we wrote about here. Without that match, a certification report stays an isolated PDF: it says the run worked on the day it was tested, and it says nothing at all five years later.

Labelling: a code, not a photo on someone’s phone.

The second thing that’s almost always missing is a coherent labelling system. Writing something on a sticky label isn’t enough: what’s needed is a unique code linking every splice, every coil and every patch port to a precise position on the diagram — the same principle behind industry standards such as TIA-606-C, which specifies how to identify technical spaces, cabinets, panels, cables and routes so that anyone, not just whoever laid the network, can find their way around. In practice: if the technician called out in three years’ time isn’t the one who did the installation, labelling is the only thing that lets them work without starting the survey from scratch.

The fibre asset register: from internal map to legal obligation.

There is also a level that goes beyond the single contract: the infrastructure register. Italy has a national register, SINFI (Sistema Informativo Nazionale Federato delle Infrastrutture — the National Federated Information System of Infrastructures), established by Legislative Decree 33/2016 implementing EU Directive 2014/61/EU on reducing the cost of deploying high-speed electronic communications networks. Anyone who owns or holds a concession over network infrastructure — and anyone who carries out excavation works to lay new infrastructure — is required to report their data to SINFI: the administrative fines for failing to do so range from €5,000 to €50,000. It’s an obligation aimed mainly at telecommunications operators and utility network managers, not at every private company network — but the principle behind it applies to everyone: infrastructure that no one can locate precisely is infrastructure that gets damaged by other people’s excavation works and duplicated by mistake. For a campus network, a hospital or a data centre, an internal register — even just a georeferenced survey linked to the as-built record — isn’t a legal requirement, but it is the same logic applied on a smaller scale.

Why it matters for maintenance and for the value of the infrastructure.

Documentation isn’t paperwork for the archive: it determines how much every future job will cost. A low mean time to repair depends almost entirely on how quickly a technician can locate the fault — and that depends on the quality of the as-built records and labelling, not on the experience of whoever turns up. It also matters for the value of the infrastructure: in a network sale, in due diligence, in a contractor handover after a tender, whoever is buying or taking over assesses first and foremost what they’re inheriting. A well-documented network can be handed over in a few days of shadowing. A network with no documentation has to be reconstructed in the field, often fault by fault, at the expense of whoever has to manage it afterwards.

What to do

Insist on the as-built record as part of the handover, not as an optional extra: the real route, the position of every splice, and correspondence with the test reports.
Adopt a unique labelling system written into the specification, not left to the discretion of whoever installs the cabling.
Check whether your network falls under the SINFI reporting obligation, and who handles it internally.
Even without a legal obligation, keep an internal register linked to the as-built record: even a simple survey cuts response times.
Update the documentation with every network change, not only at initial handover: an as-built record that’s five years out of date is often worse than no as-built record at all.

The bottom line.

A fibre network is worth only as much as its documentation allows it to be used and maintained. That’s why our approach closes every job with as-built records and certification, not just with the cable laid — both for telecommunications networks and for public-sector infrastructure, where the SINFI obligation adds to what is simply good practice.

Do you have a fibre network without up-to-date as-built records, or need to work out whether it falls under the SINFI obligations? Get in touch: a free site visit and quote, even just to put existing documentation in order.