Every other element of a network gets replaced on a cycle — switches every five to seven years, wireless access points more often. Cabling is installed once, disappears into walls, ceilings and risers, and stays there for fifteen to twenty-five years. It is also, reliably, the first line to be cut when a fit-out budget comes under pressure.
What gets lost when it is cut
Specification reductions typically take one of three forms: a lower category of copper, fewer outlets per position, or reduced fiber count in the backbone.
The first constrains bandwidth per port for the life of the building. The second means that adding a device to a desk requires either a switch under it or a new cable pull through occupied space, at many times the original installed cost. The third is the most expensive mistake, because backbone routes are the hardest to revisit — risers are congested, containment is full, and the work is disruptive in a way that a horizontal pull is not.
The economics are stark. Additional fiber strands in a backbone during initial installation cost a small fraction of returning to add them later. The cable itself is rarely the significant cost; the labour and the access are.
Specify for the building, not the current fit-out
The useful question is not what today's tenant needs. It is what a plausible occupant needs in twelve years, given that ceiling and riser access will be harder and more expensive then than now.
That generally argues for one category above current requirement in copper, generous outlet density at each position, and materially more backbone fiber than the initial design calls for — often double.
Certification is not optional
Every link should be tested to standard with results documented per link and handed over as part of the project. This is the cheapest insurance available in the entire build and the first item to disappear when a contractor is cutting corners.
Without certified results there is no way to distinguish a cabling fault from a configuration fault when something intermittent appears two years later. Teams then spend weeks chasing a problem that a test report would have located in minutes. Ask for the results before final payment, and confirm the labelling scheme matches the documentation.