The Complete Guide to FTTH Network Design

FTTH design decisions shape capital cost, construction complexity, and operating cost for years. This guide walks through architecture selection, the full design lifecycle, splitter strategy, BEAD-aligned practices, and the mistakes operators most often regret after construction starts.

FTTH architecture options

Most greenfield and overbuild projects in 2026 still choose between GPON, XGS-PON, or point-to-point Active Ethernet. The choice affects split ratios, OLT planning, drop strategy, and upgrade path.

GPON

• ·Shared PON architecture with mature vendor ecosystem.
• ·Typical practical splits: 1×32 to 1×64 depending on service tier targets.
• ·Good fit when capital efficiency matters and 1 Gbps-class residential service is the primary goal.
• ·Upgrade path often involves XGS-PON cards and ONT replacement on the same passive plant.

XGS-PON

• ·10 Gbps symmetric shared PON on passive outside plant.
• ·Strong fit for new builds that need multi-gig headroom without replacing aerial or underground routes.
• ·Often favored when grant programs expect a credible upgrade path beyond minimum service tiers.
• ·OLT and optics cost more than GPON, but outside plant costs are largely the same.

Active Ethernet (point-to-point)

Point-to-point gives each customer a dedicated fiber path and predictable bandwidth, but it uses far more fiber and active electronics than PON. It is usually reserved for business customers, campus networks, and MDUs with strict SLA requirements — not typical low-density residential builds.

The six phases of FTTH design

FTTH design is a sequence, not a single drawing exercise. Decisions in early phases constrain what is possible later.

Phase 1: Feasibility analysis

Feasibility answers three questions: how many locations can you pass, what will it cost per location, and what take rate makes the build viable? That work is inherently spatial. You need service area boundaries, premises or parcel context, existing infrastructure, and — for grant builds — funded location overlays on the same map.

Phase 2: Network routing and plant placement

Routing is where you decide aerial vs underground, distribution architecture, splitter placement, and how plant reaches each location. MapItRight is built for project-based manual design on Google Maps: you place locations and cables, draw fiber routes, and model connectivity yourself. That matches how most regional operators and engineering firms plan builds today.

Compare at least two scenarios before committing — aerial-primary, underground-primary, or hybrid — and document cost-per-location assumptions for each. Scenario comparison is what prevents expensive reversals mid-build.

Phase 3: Bill of materials generation

Once plant is modeled, the BOM should come from the design — cable by type and length, closures, splitters, hardware, and make-ready assumptions. In MapItRight, BOM reports export to PDF or XLSX from live project data. Validate unit costs before procurement; material pricing moves faster than most teams update spreadsheets.

Phase 4: Construction handoff

Construction crews need route-level clarity: where plant goes, what splices are expected, what materials apply to each segment, and what changed since the last export. Digital handoff beats a single giant PDF that nobody opens in the truck. MapItRight supports Construction Staking Sheets and project exports so crews can work from the same map the office uses.

Phase 5: As-built documentation

Every FTTH build deviates in the field. The failure mode is treating as-built as a post-construction cleanup task. By then crews have moved on and memory has faded. Capture deviations during construction: photos, marker flags, and plant updates tied to the project map while work is happening.

Phase 6: Operations and maintenance

After activation, the design record becomes the operations record. Tracing, outage isolation, service upgrades, and customer support all depend on whether Phase 5 was done well. There is no reliable operations fix for a bad as-built.

Splitter strategy: cabinet, pedestal, and MDU

Cabinet-based splitting

Best for denser suburban and urban areas where distribution can converge at roadside cabinets. Higher feeder cost, easier maintenance access, flexible splitter expansion.

Pedestal-based splitting

Common in rural and low-density builds where shorter drops matter more than centralized cabinet economics.

MDU splitting

Requires building access, riser planning, fire-stopping, and coordination with property owners. Treat MDUs as their own design workstream, not as standard OSP drops.

Scenario comparison methodology

Compare scenarios on capital cost per location, drop length distribution, optical loss at the farthest premises, splitter headroom at target take rate, and operational complexity. For grant-funded builds, also compare how completely each scenario covers the funded location set.

BEAD-aligned design practices

• ·Start with the funded service area as a project, not a loose collection of routes.
• ·Import reference overlays for boundaries, parcels, or location lists where your program requires them.
• ·Keep buildout plant in Planned state until construction is complete, then move served locations to Active.
• ·Attach field evidence to locations during construction instead of rebuilding proof at filing time.
• ·Confirm export formats early so compliance teams know what data the map can produce.

Common FTTH design mistakes

Wrong splitter ratio for the take-rate model

Design for the take rate you expect at maturity, not just launch. A split that looks fine at 30% penetration can feel tight at 70%.

Loss budget without real-world slack

Connector loss, splice loss, cable attenuation, and service-loop slack all matter. Designs that ignore slack look valid on paper and fail in the field.

Poor handoff to construction

If crews cannot see current plant on a phone or tablet, deviations will not make it back to the office map. Define capture expectations before mobilization, not after the first week of build.

Tools for FTTH design in 2026

A useful FTTH design stack should support project-based planning, manual fiber design on Google Maps, light path validation, GIS overlays, BOM and splice exports, construction staking sheets, mobile browser field updates, and a clean Planned-to-Active handoff into operations.

See /solutions/ftth-deployment and /solutions/fiber-network-planning for how MapItRight handles the design-to-field workflow, or book a demo at /book-demo to walk through a project similar to yours.