5 FTTH High-Level Design Mistakes That Cost Fiber Providers Millions

We've reviewed hundreds of FTTH high-level designs over the past decade, and the same errors keep surfacing — not subtle miscalculations, but fundamental structural mistakes that get locked in during HLD and then compound through every subsequent phase. By the time construction crews hit the field, the damage is already done. You can't fix a bad HLD with good LLD work. And you absolutely cannot fix it in the field without change orders that blow your budget wide open.

HLD mistakes are uniquely expensive because they're invisible until it's too late. A wrong splitter ratio on an HLD looks like a checkbox. It doesn't cost anything on paper. But it means your FDHs are sized wrong, your fiber counts are wrong, your splice points are in the wrong locations, and your capacity assumptions are wrong across the entire service area. Six months into construction, when your build crews start reporting that the FDH enclosures are full and there's no room for expansion, you're not looking at a design revision — you're looking at a re-engineer.

FTTH HLD Mistake #1: Treating Splitter Ratio as a Financial Decision Instead of an Engineering One

Treating FTTH splitter ratio as a financial decision — defaulting to 1:64 to minimize FDH count — without engineering validation against actual address density and terrain is one of the costliest HLD design mistakes. Uniform 1:32 or 1:64 assumptions break down when serving area boundaries, drop lengths, or take-rate projections don't match the architecture, forcing mid-construction redesigns at 10x the cost of getting it right in HLD.

The pressure to go 1:32 on every feeder segment is real. It minimizes the number of FDHs, reduces infrastructure cost on paper, and makes the budget model look cleaner. We understand why it happens. But a uniform 1:32 deployment assumes a specific set of conditions that rarely exist uniformly across a service area — consistent span lengths, consistent take rates, consistent terrain — and when those conditions break down, the whole cascade fails.

A 1:32 passive optical network has an insertion loss budget of roughly 28–32 dB depending on connector and splice losses. That's non-negotiable physics. In a dense urban deployment with short feeder runs, you have headroom. In a rural system where your feeder fiber is running 8–12 miles from the CO or hub site, you're often already at 18–20 dB before the first splitter. Run a 1:32 in that scenario and you're looking at optical power levels below the receiver sensitivity threshold for even the most capable XGS-PON ONTs at -29 dBm.

What we see constantly is HLD teams modeling splitter ratios without actually calculating optical link budgets for each feeder segment. They pick 1:32 across the board and move on. The LLD engineers discover the loss problem and try to compensate — shortening drop lengths, specifying higher-quality connectors, sometimes even recommending different equipment — but the HLD topology is already locked in. The fix is almost always a re-segmentation that should have happened at HLD.

Mistake #2: FDH Sizing That Ignores Future Splice Capacity

FDH sizing is one of those things that looks straightforward until you've been in the field watching a crew try to terminate additional fiber runs into an enclosure that was designed with exactly zero spare capacity. A 144-fiber FDH serving 128 subscribers at 1:32 sounds perfectly efficient. It is, until the service area expands, or until the take rate hits 80% instead of the modeled 65%, or until a network extension needs to pass through the same geographic area.

The standard we apply is a minimum 20% spare splice capacity at every FDH, sized not just for the initial build but for a 10-year subscriber growth model. For a 1:32 deployment targeting 256 potential passings, that means we're looking at an FDH that can accommodate at least 384 fibers with the spare splice trays already mounted and wired — not as an afterthought, but in the original design. The incremental cost of a larger enclosure at HLD is trivial compared to the cost of an FDH swap-out in year three.

We also see a recurring mistake where HLD teams locate FDHs based purely on geographic centrality within a serving area, without accounting for conduit access points, power availability for active equipment at the FDH, and maintenance vehicle access. An FDH in the mathematical center of a 500-home serving area is useless if it's in a drainage easement with no conduit stub-outs and no truck access within 300 feet.

Mistake #3: NAP Placement That Ignores Drop Length Limits and Terrain

Network Access Points — whether passive NAPs or distribution points — need to be positioned based on actual drop lengths, not idealized service areas drawn on a GIS map. This is where HLD meets real-world OSP engineering, and it's where a lot of HLD packages fall apart under scrutiny.

The typical FTTH drop is 300–500 feet of pre-connectorized drop cable, blown or direct-buried to the premise. That's not a hard limit everywhere, but it's the practical optimum for cost and signal integrity on a passive drop. When HLD teams place NAPs at 800-foot or 1,000-foot spacing to reduce NAP count, they're creating a scenario where a significant percentage of the drops will require either non-standard cable lengths, intermediate splice points, or active equipment at the premise — all of which add cost and complexity that wasn't in the original budget model.

Terrain matters enormously here. A flat subdivision with regular lot depths is forgiving. A rural hillside deployment with irregular parcel shapes, ravines, and non-navigable rights-of-way is not. We've seen HLD packages that looked reasonable in GIS until our field survey teams walked the terrain and found that the NAP-to-premise paths require bridging a drainage channel, crossing through private property with no existing easement, or running 600 feet of drop along a rock face that can't be direct-buried. Every one of those discoveries is a change order waiting to happen.

Mistake #4: Feeder Route Assumptions That Don't Account for Conduit Availability

HLD feeder routes are often drawn as straight lines — or near-straight lines — between the central office or hub site and the serving area. In reality, those feeder routes live or die on conduit availability: existing utility conduit, municipal duct banks, franchise agreements with telecom incumbents, and the cost of boring or trenching new pathways where conduit doesn't exist.

We once reviewed an HLD for a Tier 2 provider in the Mid-Atlantic that had drawn feeder routes directly through a commercial district with underground utilities so congested that any new bore would have required a full utility conflict study and likely directional boring at $120–$160 per foot instead of the trenched-conduit cost the budget assumed. The HLD was technically valid. But the construction cost was 40% higher than the model because nobody had looked at the conduit environment before drawing those routes.

The fix isn't complicated. It just requires discipline. Before any feeder route is finalized in HLD, our team pulls utility records from the relevant municipalities, checks 811 data where available, reviews existing franchise agreements, and does a preliminary conduit availability study. This adds time to HLD — maybe 2–3 weeks for a large service area — but it eliminates the catastrophic construction cost surprises that come from route re-engineering in the field.

Mistake #5: HLD vs. LLD Handoff Without a Fiber Count Reconciliation

The HLD-to-LLD handoff is where design errors compound fastest. HLD establishes the network topology, fiber counts, and equipment sizing. LLD adds the route-level detail: splice point locations, cable segment lengths, conduit fill ratios, pull point spacing. When HLD fiber counts aren't formally reconciled against LLD-level calculations before LLD begins, you get cascading errors that nobody catches until the cable is being pulled.

The specific failure mode we see most often is a mismatch between the feeder fiber count established in HLD and the actual count needed when LLD engineers model the specific route. An HLD might specify a 144-fiber feeder from hub to FDH. When LLD engineers trace the actual route — accounting for service loops, slack storage, mid-span joints — they find they need 168 or 192 fibers to maintain the required spare capacity ratios at each splice point. If this isn't caught and reconciled before the BOM is finalized and material orders are placed, the project either proceeds with undersized cable or requires emergency re-procurement mid-build.

Our standard is a mandatory fiber count reconciliation meeting at the HLD-to-LLD transition. Every feeder segment gets a paper reconciliation: HLD specified count, LLD calculated count, delta, and disposition. It's not glamorous work. But it's the single most effective quality gate we've found for catching HLD errors before they become construction problems.

The Real Cost of FTTH HLD Design Mistakes in Construction

Bad HLD decisions don't show up as line items on the original budget. They show up as change orders — sometimes dozens of them, scattered across months of construction, each one individually manageable but collectively devastating. We've worked with providers whose construction change order rates ran 25–35% of original contract value, traced almost entirely back to HLD decisions made in a few weeks at the beginning of the project.

The math is punishing. On a $10M fiber deployment, a 25% change order rate is $2.5M in unplanned cost. That's the difference between a project that meets IRR targets and one that doesn't. It's the difference between a network that performs as designed and one that's a patchwork of field corrections and compromises.

Getting HLD right requires time, discipline, and engineers who've actually been in the field enough to know what the feeder routes look like on the ground. At Draftech, our HLD teams include engineers who've spent years on construction crews and field survey teams — not just design professionals who model networks from satellite imagery. That field experience is what catches the conduit conflicts, the terrain surprises, the splitter ratio problems before they become line items on a change order log.

If you're planning a FTTH deployment and want a second set of eyes on an existing HLD package — or need a complete HLD from scratch — reach out to our engineering team at info@draftech.com. We've reviewed enough bad HLD packages to know exactly what to look for.