How to Avoid Common Problems in Structured Cabling Systems

Learn how to avoid the main structured cabling problems: undersizing, inadequate pathways, incompatibility, EMI, installation, identification, certification, and as-built documentation.

Check it out!

Structured cabling problems rarely result from a single isolated cause. In practice, recurring failures arise when poorly defined requirements, inadequate pathways, incompatible components, uncontrolled installation, deficient identification, and lack of testing accumulate throughout the project. Avoiding these problems requires treating cabling as an engineering system: specify before purchasing, coordinate interfaces before installation, inspect during execution, and accept only with documentation and performance evidence.

Prevention begins before construction. ABNT NBR 16869-1 establishes that the installation specification must be provided to the installer in advance and cover technical requirements, scope of work, and the quality plan. The same logic applies to expansions and retrofits: understanding existing conditions, defining responsibilities, identifying interfaces with electrical systems, HVAC, security, automation, and other systems, and establishing how the installation will be tested and documented drastically reduces the risk of rework.

Why cabling problems appear even when the network “works”

An infrastructure can support Ethernet communication and still be technically inadequate. The fact that a laptop obtains an IP address or accesses the internet does not demonstrate that the link meets the specified class, that transmission margin exists, that pathways support expansion, that identification is traceable, or that the system was built according to the design.

This distinction between immediate operation and infrastructure compliance is fundamental. Cabling is a passive asset whose life cycle is normally much longer than that of switches, access points, cameras, and other active equipment. An installation that “works today” can become the bottleneck in a migration to higher-power PoE, next-generation Wi-Fi, 10 Gigabit Ethernet, higher-resolution video surveillance, or user expansion.

The most relevant problems can be grouped into six families:

Problem family	How it appears in operation	Most common engineering cause
capacity	lack of ports, saturated racks, full pathways	requirements and expansion not planned
performance	certification failures, intermittent errors	inadequate components, termination, or installation
physical infrastructure	compressed cables, improvised routes, maintenance difficulties	undersized pathways and spaces
interfaces	interference, lack of equipotential bonding, conflicts with other disciplines	insufficient multidisciplinary coordination
administration	unidentified outlets, inconsistent documentation	lack of record and as-built standards
acceptance	network delivered without objective evidence	quality plan and tests defined too late

The best time to correct these problems is before installation. The second-best time is while construction is still underway and corrections can be made without dismantling completed spaces.

Problem 1: undersizing outlets, racks, and pathways

Undersizing does not simply mean installing too few network outlets. A system may have enough outlets and still be undersized because it lacks patch-panel ports, rack units, thermal capacity, fiber trays, available fibers, working space, or usable pathway cross-section.

ABNT NBR 16869-1 recommends considering expansion in pathways and cable distribution systems, cabinets and racks, termination points, and electrical power demand. This turns “spare capacity” into a design requirement that must be measurable rather than a generic statement such as “allow for future growth.”

Spare capacity must be defined by subsystem

Appropriate spare capacity may differ in each part of the infrastructure. In one building, the greatest uncertainty may be in work areas; in another, at Wi-Fi, camera, access-control, or automation points. On a campus, the limitation may be the optical backbone between buildings.

The design should verify, among other aspects:

• number of current and planned positions;
• points intended for fixed devices and building systems;
• patch-panel ports and rack occupancy;
• space for managers and cords;
• capacity of pathways and pull boxes;
• spare fibers or pairs in the backbone;
• PoE growth and its impact on power and temperature;
• physical space for distributor expansion.

The consequence of ignoring these variables appears during the first retrofit: a new switch fits electrically but there is no rack space; new cables would fit the patch panel but not the conduit; spare fibers exist, but the topology does not reach the space where the new service will be deployed.

Pathway capacity cannot be confused with “one more cable still fits”

Pathways must be sized for installation, maintenance, and expansion. ABNT NBR 16415 establishes occupancy and geometry criteria that prevent conduits and other pathways from becoming physical bottlenecks. For conduits, the reference design fill is limited to 40%, preserving pulling conditions and technical reserve.

Another recurring mistake is to consider only the available geometric area. Bends, boxes, transitions, rack entries, level changes, and cable concentrations can make the route impractical before the area limit is reached.

Problem 2: choosing category and components without considering the complete channel

Cabling performance results from the installed system, not from the name printed on the cable. Cable, connectors, patch panels, outlets, patch cords, and installation practices are all part of the channel. Mixing components or selecting a higher category for only one element does not automatically turn the assembly into a higher class.

ABNT NBR 14565 associates, among others, Category 5e with Class D, Category 6 with Class E, and Category 6A with Class EA. The channel is limited by the lowest-performing component and by actual installation conditions.

“Cat6A is better” is not an engineering specification

The category must derive from application requirements, life cycle, distance, environment, PoE, density, interfaces, and expansion strategy. For applications requiring 10GBASE-T in a new design, Class EA/Cat6A is the appropriate reference. Cat6 can support 10GBASE-T under specific conditions, but that should not be turned into a simplified design rule.

Likewise, shielding is neither synonymous with category nor a universal solution for interference. A shielded channel requires shield continuity, compatible components, and proper equipotential bonding. Using shielded cable without a coherent architecture can add complexity without solving the source of the problem.

Compatibility must be verified before purchasing

NBR 16869-1 requires the quality plan to detail procedures for verifying compatibility among new components and also with existing cabling when integration is involved. This requirement is especially important in retrofits, where an existing patch panel, connector type, pinout, or cable construction may be incompatible with the proposed new material.

Technical bid leveling should compare objective requirements, not merely commercial descriptions. Relevant items include category/class, construction, operating environment, mechanical compatibility, cable diameter, shielding, optical performance when applicable, fire reaction required for the location, and manufacturer technical documentation.

Problem 3: starting installation without specifications and a quality plan

When the field team receives only a floor plan with outlets and a bill of materials, important decisions are left to improvisation. Who defines the identifier? Which limit will be used for certification? How should a blocked route be handled? Which design revision applies? Who approves material substitutions? How is redline information recorded? What condition generates a nonconformity?

NBR 16869-1 structures installation around three prior elements: technical specifications, scope of work, and quality plan. These documents must establish responsibilities and criteria before execution makes them urgent.

The quality plan reduces subjective decisions

A well-structured quality plan should address:

1. receipt and acceptance of components;
2. compatibility verification;
3. inspection and test equipment;
4. instrument calibration status;
5. test procedures;
6. handling of marginal or nonconforming results;
7. team competence;
8. mandatory records;
9. responsibilities for correction and retesting.

The purpose is not to bureaucratize a simple installation. It is to prevent quality criteria from being invented after a discrepancy appears.

Problem 4: pathways and spaces incompatible with the installation

Cabling depends on suitable physical infrastructure. Conduits, cable trays, ladder trays, raceways, shafts, boxes, telecommunications rooms, and racks are not accessories: they are part of the system that allows cables to be installed, protected, administered, and expanded.

Typical errors include:

• conduits with excessive fill;
• too many bends between pulling points;
• small or inaccessible boxes;
• insufficient support;
• cables laid directly on suspended ceilings;
• improper sharing with other services;
• cable entry into racks without bend-radius management;
• lack of front and rear access;
• lack of expansion space.

NBR 16415 limits the total number of bends between pull boxes and establishes pathway criteria. In suspended systems using J-hooks, support must control spacing and sag. These details directly affect cable mechanical integrity and maintainability.

Dry infrastructure should be inspected before cable pulling

Waiting for the cable reel to arrive before discovering that a conduit is blocked, a box was cast in the wrong position, or a shaft was occupied by another discipline creates delays and improvisation. Release of dry infrastructure should function as a construction gate: pathways completed, accessible, clean, with supports, reserves, and interfaces verified.

Problem 5: ignoring interfaces with electrical systems, HVAC, security, and automation

The telecommunications installer does not work in a vacuum. NBR 16869-1 requires the specification to provide information about other building services, including electrical distribution and grounding, BMS, security, fire detection, HVAC, and industrial machinery.

This exists because many problems attributed to the “cable” are actually interface problems.

Separation between power and telecommunications must reflect the actual installation

Separation between power and telecommunications cables should not be defined by memorizing a universal distance. The criterion depends on infrastructure, electrical conditions, pathways, presence of dividers, cable type, and applicable standards.

When symptoms of electromagnetic interference exist, the correct response is to investigate the source, coupling path, and affected receiver. Automatically replacing U/UTP with shielded cable may not eliminate the problem. In some scenarios, routing correction, separation, equipotential bonding, functional grounding, properly implemented shielding, or migration to fiber are distinct alternatives.

HVAC and temperature also affect infrastructure

Cables installed in hot environments or grouped in PoE bundles may operate under conditions different from those considered in the initial design. Temperature affects attenuation and, in PoE applications, bundle temperature rise must be considered together with conductor gauge, bundling, and delivered power.

Problem 6: termination and pulling without mechanical control

A significant share of certification failures originates in the field: excessive pulling force, bending, compression, excessive untwisting, poor termination, unsuitable connectors, or cable damage during pulling.

Cable quality does not compensate for poor installation practices. The link is measured after installation precisely because its performance depends on the combination of materials and workmanship.

Respecting bend radius and pulling tension prevents invisible damage

Mechanical damage may not break the conductor. The cable can continue to show continuity even though its internal geometry has changed and transmission parameters have degraded. Therefore, manufacturer criteria for bend radius, pulling force, fastening, and dressing must be part of the installation method.

Overtightened cable ties, metal edges, improper support, and bundles crushed by other installations are classic examples of problems that appear only during certification or application upgrades.

Termination must preserve pair geometry

In balanced cabling, termination must maintain the twist as close as possible to the connecting hardware. NBR 14565 limits untwisting in Category 5e and higher and requires consistency with the selected pinout. Mixing T568A and T568B on the same link creates an incorrect wire map even if all conductors are physically connected.

Problem 7: racks that look organized but lack technical administration

A rack may look organized in a photograph and still be difficult to operate. Administration involves consistent identification, port–patch panel–outlet–device relationships, reserved space, cord management, and updated records.

NBR 16869-1 treats identification and records as part of cabling management. Labels need identifiers consistent with documentation, and records must make it possible to relate physical elements to their locations.

Cable management is not just aesthetics

Horizontal and vertical managers, patch-cord routing, functional separation, port access, and slack control reduce patching errors and intervention time. Excessively long cords create bulk, hinder ventilation, and obscure identification. Cords that are too short introduce tension and improper bend radii.

For high-density port environments, the patching strategy should be planned together with the selection of patch panels, switches, and managers, not after the rack has been assembled.

Problem 8: identification that does not match drawings and reports

One of the clearest signs of low maturity is finding three names for the same point: one on the label, another in the certifier report, and another in the as-built documentation. In that situation, each maintenance activity requires investigation to determine which record represents the physical asset.

The identifier must follow the link throughout its life cycle. The same coding must appear at the termination point, distributor, test files, and final documentation.

Redline documentation should begin during construction

Reliable as-built documentation is not produced from memory at the end. Route changes, relocated points, changed ports, and substituted components must be marked during execution. Redlines are the intermediate evidence that makes it possible to consolidate the as-built condition afterward.

When change records do not exist, final documentation tends to reproduce the original design instead of the actual installation.

Problem 9: treating certification as a closeout formality

Certification should not appear only on the final day of construction. The test model, class, limits, link identification, file format, and retest policy must be specified before installation.

NBR 16869-1 recommends the Permanent Link model as a design requirement because it provides adequate margin for the different patch cords that may form the channels. For installed balanced cabling, the standard establishes basic and transmission verification parameters that include, according to the applicable class, continuity, insertion loss, return loss, NEXT, PSNEXT, ACR, loop resistance, delay, and delay skew.

Connectivity testing does not replace certification

A simple tester can identify continuity and wire map, but it does not prove the transmission parameters required to certify a cabling class. Likewise, a throughput or ping test verifies another layer of the system and does not replace evaluation of the passive infrastructure.

The acceptance plan should distinguish between:

Verification	Objective
visual inspection	confirm installation, identification, and apparent integrity
wire map/continuity	identify opens, shorts, and pinout errors
certification	compare link/channel performance against defined limits
functional network test	verify active equipment and services
commissioning	integrate evidence, interfaces, documentation, and readiness

A failure must generate correction and a traceable retest

The purpose of the report is not to produce a PASS percentage. Each failure must be linked to the link, diagnosis, correction, and new result. Renaming a file or deleting a failed test without recording the intervention destroys acceptance traceability.

Problem 10: accepting only PDF files and losing native test files

PDF reports are useful for reading, but native certifier files preserve information that may be required for audits, diagnosis, warranty, and reprocessing. The deliverable must define in advance which formats will be provided.

The delivery package may include:

• certification reports in PDF;
• native instrument files;
• equipment and calibration records;
• port-to-outlet matrix;
• as-built drawings;
• updated diagrams and details;
• photographic report when required;
• nonconformity and retest records;
• list of materials actually installed.

Final documentation must allow a team that did not participate in construction to understand the system without reconstructing it through field inspection.

Problem 11: changing materials in the field without change control

Substitutions may be necessary due to availability, schedule, or technical improvement. The mistake is to treat them as informal decisions. Replacing cable, patch panels, connectors, or optical components can change performance, warranty, compatibility, installation method, or test criteria.

Change control should record the originally specified item, reason for the change, technical equivalence, impact on interfaces, and approval. This discipline is particularly important when products from different manufacturers are combined or when the proposed commercial solution departs from the design reference system.

Technical procurement prevents equivalence from becoming an opinion

An equivalent proposal must satisfy performance and integration requirements, not merely provide a similar description. Bid leveling should separate mandatory requirements, desirable attributes, and differences that require analysis. This reduces both the risk of overly restrictive specifications and the opposite risk: accepting an unsuitable product because it “is also Cat6.”

Problem 12: confusing active-network redundancy with cabling redundancy

Availability does not result simply from “running two cables.” A resilient architecture depends on identifying the failure domain and designing real diversity where needed. Two links in the same conduit, terminated in the same rack, and connected to the same equipment share several failure modes.

In critical applications, the analysis may involve route diversity, separate distributors, physically separated pathways, active-equipment redundancy, and power redundancy. Cabling provides the required physical infrastructure, but protocols and logical topologies belong to the active-network architecture.

This distinction avoids simplistic statements such as “a cabling ring topology guarantees availability.” At the passive layer there are pathways, links, and interconnections; functional redundancy depends on the complete architecture.

Problem 13: failing to consider PoE as a cabling requirement

IP cameras, access points, phones, access-control devices, sensors, and IoT devices make the infrastructure carry power in addition to data. PoE capacity must be included in the design together with category, conductor gauge, resistance, connectors, bundling, and temperature.

The greater the density of powered devices, the more important it becomes to avoid excessively large bundles under unfavorable thermal conditions. The design should also verify switch power budget and link distance, but these elements belong to the electrical and active architecture of the system, not only to the cable.

Problem 14: using MPTL as a shortcut for any fixed point

MPTL is useful for access points, cameras, and other fixed devices, but it does not simply mean crimping a plug onto permanent cable. The plug must be compatible with the cable construction, the configuration must be planned in the design, and testing must use the appropriate method and limit.

In a work area with frequent changes, the telecommunications outlet continues to provide better administration and flexibility. For a fixed ceiling device, MPTL can eliminate an intermediate connection when properly specified.

How to structure effective prevention in six gates

Instead of waiting for failures, the owner can structure the project around verifiable gates.

Gate 1 — requirements and survey

Confirm users, systems, areas, applications, constraints, existing infrastructure, growth, interfaces, and criticality.

Gate 2 — design and specification

Define topology, categories, backbone, pathways, racks, terminations, identification, documentation, and acceptance criteria.

Gate 3 — material receiving

Compare received materials with submittals and specifications; verify quantity, integrity, compatibility, and traceability.

Gate 4 — infrastructure release

Inspect pathways, rooms, racks, supports, boxes, access, and interfaces before cable pulling.

Gate 5 — installation inspection

Monitor pulling, termination, identification, organization, changes, and nonconformities while they can still be corrected without extensive rework.

Gate 6 — testing, documentation, and acceptance

Certify, address failures, consolidate as-built documentation and records, and release the system only after consistent evidence is available.

Checklist for auditing an installation before acceptance

An objective audit can verify that:

• the design and revision used in the field are identified;
• installed components match the specification or approved substitutions;
• pathways and boxes remain accessible;
• cables show no improper compression, tension, or bending;
• racks have consistent organization and identification;
• patch panels and outlets follow the defined pinout;
• shielded systems preserve the intended continuity and equipotential bonding;
• PoE points were treated as a design requirement;
• physical identification matches reports and drawings;
• all planned links were tested according to the plan;
• failures have corrections and retests;
• native files and PDFs are available;
• as-built documentation represents the constructed condition;
• open items are recorded and assigned to a responsible party;
• formal acceptance is conditioned on technical evidence.

Final considerations

Avoiding structured cabling problems depends less on “good cables” and more on a coherent engineering process. Clear requirements, a verifiable design, compatible pathways, technically leveled components, controlled installation, consistent identification, certification, and as-built documentation form a chain. When one of these stages is omitted, the problem usually reappears later as a performance failure, expansion difficulty, or maintenance cost.

Prevention also protects the owner’s independence. A design with objective criteria allows suppliers to be compared; inspection with records allows deviations to be controlled; acceptance tests make performance demonstrable. Decisions then depend less on the installer’s assertion and more on evidence that can be audited throughout the life cycle.

Technical references

[1] ASSOCIAÇÃO BRASILEIRA DE NORMAS TÉCNICAS. ABNT NBR 14565:2019 — Cabeamento estruturado para edifícios comerciais. Rio de Janeiro: ABNT, 2019. Available at: https://www.abntcatalogo.com.br/

[2] ASSOCIAÇÃO BRASILEIRA DE NORMAS TÉCNICAS. ABNT NBR 16415 — Caminhos e espaços para cabeamento estruturado. Rio de Janeiro: ABNT. Available at: https://www.abntcatalogo.com.br/

[3] ASSOCIAÇÃO BRASILEIRA DE NORMAS TÉCNICAS. ABNT NBR 16869-1:2020 — Cabeamento estruturado — Parte 1: Requisitos para planejamento. Rio de Janeiro: ABNT, 2020. Available at: https://www.abntcatalogo.com.br/

[4] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION; INTERNATIONAL ELECTROTECHNICAL COMMISSION. ISO/IEC 11801-1 — Information technology — Generic cabling for customer premises — Part 1: General requirements. Available at: https://www.iso.org/standard/66182.html

[5] INTERNATIONAL ELECTROTECHNICAL COMMISSION. IEC 61935-1 — Testing of installed balanced cabling. Available at: https://webstore.iec.ch/

Frequently asked questions

What is the most common problem in structured cabling?

There is no single dominant failure, but many problems begin with insufficient requirements and design. Undersizing, inadequate pathways, incompatible components, uncontrolled installation, deficient identification, and lack of certification tend to combine.

Does a working network mean the cabling is certified?

No. Connectivity or internet access does not prove the link transmission parameters. Certification compares measurements of the installed cabling against defined limits for the applicable configuration and class.

Does shielded cable solve electromagnetic interference?

Not necessarily. The source, coupling path, and affected receiver must be investigated. Shielding may be part of the solution, but it requires compatible components, continuity, and proper equipotential bonding. Separation, routing, or optical fiber may be more appropriate in other scenarios.

What should be delivered with certification?

In addition to readable reports, the scope may require native instrument files, link identification, calibration data, failure and retest records, a port-to-outlet matrix, and consistent as-built documentation.

Why should as-built documentation begin during installation?

Because route, point, port, and component changes occur during construction. Continuous redlining preserves these changes and reduces the risk that the final as-built documentation reproduces the original design rather than the condition actually built.

How can you prevent the supplier from choosing materials only by lowest price?

The design and procurement process should define performance, compatibility, environment, documentation, and acceptance requirements. Technical bid leveling compares proposals against these criteria before the commercial decision.

Supplementary technical materials

Related solutions

• Structured Cabling: design, implementation, certification, and management

Related services

• Structured Cabling Design
• Owner’s Engineering
• Technical Testing and Verification

Main content on this topic

• Structured Cabling Design: stages, NBR 14565, NBR 16869, and deliverables
• Structured Cabling Installation: How to Ensure Performance

Related technical content

• Network Certification: process, tests, reports, and technical acceptance
• NBR 16869: Structured Cabling — Parts 1 to 5
• NBR 14565: Structured Cabling for Commercial Buildings