Every integrator has met this job: the gate camera ended up 130 meters from the rack — "relax, it's good cable" — and the link drops every time it rains. The installer swears it's genuine Cat6, box and all. Doesn't matter: the standard says 100 meters, and physics doesn't negotiate with the brand on the jacket.
The good news is that structured cabling holds no mysteries. The complete recipe has been sitting in the TIA-568 family since the nineties: how much cable, which kind, which order the colors go in, and how much room to leave in the pathway. What follows is that recipe, with the whys — because a tech who understands the why never pulls 130 meters "because it's good cable" again.
The 100-meter channel: 90 + 10, and not an inch more
The famous 100-meter limit is not a round number someone picked out of laziness. It's a channel with two well-defined parts: up to 90 m of permanent link (the solid-conductor cable running through walls, tray or trunking, from the outlet to the patch panel) and up to 10 m of patch cords split between both ends — typically 5 m in the cabinet and 5 m at the desk.
Why that split, instead of just "100 meters of cable"? Because patch cords use stranded conductors (so they can flex without breaking), and stranded wire attenuates on the order of 20 % more per meter than the solid conductor in the fixed run. The standard did its attenuation math with exactly that mix — 90 m solid plus 10 m stranded — and that is where the budget closes. Pull a 100 m permanent link and hang a 5 m patch cord on each end, and you're not "barely over": you're outside the model everything else was designed around. Before promising a far-away drop, run it through the TIA-568 channel calculator and settle it in ten seconds.
Categories, minus the marketing
The cable box promises wonders; the standard promises measurable things. Here is what each category actually delivers over a full 100 m channel:
| Category | Bandwidth | 1 Gb/s | 10 Gb/s | Where it makes sense |
|---|---|---|---|---|
| Cat5e | 100 MHz | 100 m | no | Budget bids, data drops without heavy PoE |
| Cat6 | 250 MHz | 100 m | 37–55 m | The sensible office default today |
| Cat6A | 500 MHz | 100 m | 100 m | WiFi 6/7, 4K cameras, floor backbones |
| Cat8 | 2000 MHz | 100 m | 25/40 Gb/s at 30 m | Datacenter only (switch to server) |
The number the marketing always leaves out: Cat6 does run 10 Gb/s, but only up to 55 m — and in a bundle with many cables running side by side (where alien crosstalk, the interference between neighboring cables, takes over), the recommendation drops to 37 m. If the project says 10G across a whole floor, the short answer is Cat6A. Worth knowing too: Cat5e supports 2.5GBASE-T at a full 100 m thanks to 802.3bz, which gave a second life to plenty of older plants feeding WiFi 6 access points.
What about shielding?
Shielded cable (F/UTP, S/FTP) isn't simply "better": it's a tool for specific problems. It earns its keep in industrial plants full of VFDs and motors, near radio transmitters, and in dense high-power PoE bundles where the shield also helps carry heat away. Outside those cases, well-installed UTP certifies just fine. And beware: a shield without proper grounding (bonded at the patch panel, with shielded hardware down the whole chain) turns into an antenna — worse than no shield at all.
T568B: the eight colors you should know cold
Across the Americas the de facto standard is T568B (T568A survives in government work and the residential standard). The order, pin by pin, holding the plug clip-down with the contacts facing you:
Here's the detail that separates memorizing from understanding: pins 3 and 6 form a single twisted pair. The twist is what cancels the noise — the two halves of the signal travel wrapped around each other, so interference hits both equally and subtracts itself out. That's why the color order matters: it's not aesthetics, it's guaranteeing every signal rides on a genuinely twisted pair.
Straight-through or crossover? Straight: T568B on both ends. Crossover: B on one end, A on the other (it swaps pairs 2 and 3). These days it's almost trivia: virtually every gigabit port ships with Auto-MDIX and crosses the pairs itself when needed. Still, don't mix A and B within one installation: pick B, write it into the as-built docs, done. If you want the pinout handy in the field, it lives in the color code tool.
PoE: the same cable now carries watts
For twenty years twisted pair carried nothing but signal. Now it powers cameras, APs, phones and even displays: 802.3af delivers 15.4 W from the switch, 802.3at raises that to 30 W, and 802.3bt reaches 90 W. Which introduces a cost that didn't exist before: the cable charges a toll in watts. Under af, up to 2.45 W can stay behind in the copper; under at, 4.5 W; under bt Type 4, up to 18.7 W — nearly a whole LED bulb's worth of heat cooking your cabling.
That toll depends on conductor resistance, and this is where gauge stops being fine print: 23 AWG Cat6 has 21 % less resistance than 24 AWG (66.6 vs 84.0 Ω/km per conductor). Less resistance means less drop, less heat, and more watts arriving at the device. For dense PoE or long runs, 23 AWG pays for itself. Size the total switch load with the PoE budget tool and check what distance costs you with the voltage drop calculator.
Heat also piles up wherever the cable can't breathe. Coiling the 8 spare meters into a tight loop behind the camera was harmless with data alone; with PoE, that coil is a miniature space heater where every turn warms its neighbor. Leave slack in a loose "S" on the tray — or better, cut to length. The same goes for fat bundles of 50 PoE cables: the tighter the bundle, the hotter its core, and attenuation gets worse as temperature climbs.
Pathways: the 40 % rule fills up faster than you think
The NEC caps conduit fill at 53 % with one cable, 31 % with two, and 40 % with three or more. The rule was written for conduit, but use it as the practical ceiling for trunking too: it leaves room to pull without tearing jackets, room to grow, and somewhere for PoE heat to go. Why 40 and not 100? Because cables are cylinders: you couldn't tile the area with circles even if you tried, and forcing them scrapes jackets and crushes twists.
Let's run the full calculation — the same one the conduit fill calculator does:
- Internal area of the trunking: 40 mm × 25 mm = 1000 mm².
- Apply the 40 % limit: 1000 × 0.40 = 400 mm² usable (three or more cables, so the 40 % rule applies).
- Area of one cable: typical Cat6 has an outside diameter (OD) of 6 mm → π × 3² = 28.3 mm². Always use the OD from the datasheet: across brands it ranges from 5.5 to 7.5 mm, and the result swings hard.
- Divide and round down: 400 ÷ 28.3 = 14.1 → 14 cables. The decimal never rounds in your favor: a cable either fits whole or it doesn't.
- Check: 14 × 28.3 = 396 mm² → 39.6 % fill. Just under the ceiling.
- Cable number 15 breaks the rule: you'd land at 42.4 % — out of spec, and in practice already pulling hard enough to scrape jackets.
Patch panels and the moment of truth
The same headroom philosophy applies in the rack. The rule of thumb: 25 % spare on top of day-one drops. Got 38 network points? 38 × 1.25 = 47.5 → 48 ports: two 24-port panels, with one horizontal cable manager per panel (yes, each "wastes" 1U — and it's the difference between a maintainable rack and a patch-cord salad nobody wants to reach into). The full count of panels, managers and rack units comes out of the patch panel planner.
And at the end of the project comes the question that separates a professional installation from a pile of pulled cables: certify, or "test with the LED"? The LED tester checks continuity and wire map — that each conductor lands where it should. Nothing else. It measures no attenuation, no NEXT, no return loss, not even true length. A split pair, an over-untwisted jack or a cable pinched by drywall all sail through the LED test. A certifier, by contrast, compares every link against the standard's limits, frequency by frequency, and produces a per-drop report: that is what backs the manufacturer's warranty (often 20+ years on structured cabling) and what defends you when the client says "the network feels slow".
Certifying costs money; going back on site costs more. If the budget won't cover your own certifier, rent one for handover or subcontract the certification: it's a small line item that deletes an entire category of ghost failures.
Now put it to work: check your runs against the 100 m channel, size pathway with the 40 % fill calculator, and build the rack with 25 % spare using the patch panel planner. The standard did the hard part thirty years ago; your job is simply not to argue with it.