# Fiber Network Distribution Area Planning: Boundaries and FDH Placement

**Author:** Omar Molina

**Published:** October 9, 2026

**Last updated:** October 9, 2026

**Category:** FTTH & Fiber Network Design

**URL:** https://draftech.com/blog/fiber-network-distribution-area-planning

**Title tag:** Fiber Network Distribution Area Planning 2026

**Meta description:** Fiber network distribution area planning: address clustering, FDH placement, split ratios, drop length limits, growth spares, and serving-area boundary rules.

**Visible word count:** 2721

---

A balanced address count can hide an unbuildable serving area. A cabinet placed at the center of a polygon may put its longest branch across a road the owner cannot cross, while the nearest homes face terminals on the wrong side of their lots. Start with routes that reach the premises. The polygon follows.

This guide covers local FTTH distribution areas and the FDH or cabinet locations that serve them. We connect address clustering to split capacity and route limits, then show how to preserve room for growth without leaving boundary addresses unassigned. The upstream transport network needs its own design; it does not decide which neighborhood terminal can accept a customer's drop.

## Fiber Network Distribution Area Planning Starts with Address Ownership

Fiber network distribution area planning assigns serviceable premises to an FTTH hub and its downstream terminals using feasible cable routes and capacity limits. In a centralized 1:32 arrangement, each splitter provides 32 outputs; several splitters may occupy one FDH. The serving boundary must fit those assignments and the permitted route to each premises.

### Build the premises register before clustering

**The demand unit must be explicit.** A building point is not necessarily a subscriber location, particularly where an apartment property contains several living units behind a common entrance. We preserve the building relationship while counting the units the operator intends to serve. Otherwise, a cluster can look comfortably below cabinet capacity until the building survey reveals the missing demand.

We separate existing serviceable premises from proposed development. A recorded future parcel does not prove an available building entrance, and a marketing lead does not establish a usable drop route. The register should retain the basis for each assignment so the owner can change a forecast without overwriting the physical facts that support today's design.

Address reconciliation comes before automated clustering because duplicate geocodes can consume capacity twice while an omitted rear building disappears from the plan entirely. We compare the owner-approved service list with the mapped premises and carry discrepancies into a resolution queue. Do not delete a difficult address just because the clustering tool cannot place it neatly.

### Draw boundaries along service paths

Street connectivity matters more than straight-line proximity. We group premises along usable distribution corridors and test the boundary against physical barriers before balancing address totals. A divided highway can justify separate areas even when the homes face each other. Conversely, a winding road may connect a dispersed cluster without the extra crossing implied by a compact geometric partition.

**Each premises needs one normal serving assignment.** Overlapping polygons must not create duplicate ownership, and a gap between polygons must not make an approved premises disappear. We identify boundary exceptions by address and explain the intended path. A shared street segment may carry cables for neighboring areas without making their customer assignments interchangeable.

A boundary also controls changes after design release. If a proposed cabinet move transfers homes to another area, we update the receiving area's demand and optical checks before accepting the move. The adjacent designer needs the actual address transfer, not an instruction to adjust the polygon later. Our preferred route-first method has a weakness: an outdated route layer can make a precise assignment wrong.

That is why we flag unverified corridors before running the final allocation. The [field survey data accuracy guide](https://draftech.com/blog/field-survey-data-accuracy-fiber-construction) explains the evidence needed to turn mapped plant into a usable design input. We can compare candidate boundaries while a survey is open, but we keep the affected cabinet location provisional until the corridor is confirmed.

The next decisions test whether the address groups survive physical design. We use the same address identifiers throughout those checks, so a split-capacity revision cannot quietly change the service commitment. The table summarizes the decisions that follow; none substitutes for the operator's approved design criteria or the selected equipment's installation requirements.

| Planning decision | What to test | Reason to revise the area |
| --- | --- | --- |
| Cabinet location | Usable site and routed access to assigned terminals | Unavailable site or avoidable crossing |
| Split capacity | Assigned outputs and complete optical paths | Insufficient capacity or unacceptable path loss |
| Drop reach | Terminal-to-premises route under owner limits | Unsupported drop or missing access permission |
| Growth reserve | Usable spare capacity at the expected demand location | Reserve stranded away from expansion |

## Place the FDH Where the Distribution Routes Work

The geometric center is only a candidate. It is not a construction location. We compare cabinet positions by the routes they create and reject sites that lack a credible access path. An apparently shorter distribution network can lose its advantage when the cabinet requires a difficult feeder crossing or blocks the working space needed to service its connectors.

### Establish site feasibility before fixing capacity

Cabinet siting needs property permission and a workable installation footprint. We check the proposed enclosure against the location's physical constraints, including how the technician reaches and opens it. The receiving owner supplies the applicable setback and access criteria. We do not convert a convenient roadside point into an approved equipment site merely by assigning it an FDH identifier.

CommScope's **FTTH network ePlanner overview**, document CO-115267-EN, marked 03/21 (March 2021), describes centralized splitting as a single splitter layer, typically 1:32, at an FDH or closure. Its architecture discussion is useful here: the hub is a connection point within a routed network. That topology does not prescribe a universal cabinet spacing or a fixed number of homes per area.

Keep downstream terminal assignments visible. Then compare the cabinet candidates. Moving the hub may shorten one branch while lengthening another, and a feeder approach that looks direct can conflict with the available right-of-way. The comparison needs the full routed arrangement. We retain the reason for the selected site so a later reviewer can distinguish an intentional offset from a drafting error.

**Keep a rejected site's reason beside its location.** If the preferred property becomes unavailable, the next designer should know whether the alternate failed because of access or because its distribution paths could not meet the design criteria.

For a centralized layout, cabinet port capacity and splitter mounting space both need attention. An enclosure's headline capacity does not prove that its installed configuration can accept the intended connections. Our [FDH sizing guide](https://draftech.com/blog/fiber-distribution-hub-sizing-ftth-pon) covers the cabinet-level selection; the serving-area plan supplies the premises assignments that make that selection meaningful.

## Keep Split Ratios Separate from Cabinet Capacity

A PON path has a split ratio; a cabinet has an installed and ultimate connection capacity. They are different quantities. We reconcile both before setting the area boundary because unused enclosure positions cannot overcome an overloaded splitter path, and an available splitter output is useless when no assigned distribution fiber reaches the intended terminal.

### Track the complete split path

CommScope's ePlanner overview distinguishes centralized splitting from a distributed arrangement with splitter stages nearer the customer. In the latter arrangement, we retain the parent-child relationship between stages. A first-stage output feeding a downstream splitter is not an available customer port. Treating it as one inflates the apparent spare capacity before a single subscriber is connected.

The Fiber Optic Association's online reference **Fiber To The Home Network Design**, an unnumbered web reference, explains that cascaded split ratios multiply. A 1:4 stage feeding 1:8 splitters produces a 1:32 total split on each complete customer path. The arithmetic defines the branching, but the actual devices and connections determine the path loss that must fit the selected equipment.

We calculate the loss for the proposed physical route, including the installed splitters, and compare it with the equipment's permitted operating range and the owner's margin requirement. The FOA reference also notes approximately 3 dB of ideal division loss for each doubling of an equal split, before excess loss. That is why increasing the split to absorb extra addresses is an optical decision.

Take rate belongs in the activation plan. It does not erase the eventual premises demand unless the owner has deliberately limited the build's service commitment. We distinguish the outputs installed for initial connections from the capacity reserved for later activation, then show how the cabinet can reach that later configuration without reassigning customers behind the operator's back.

Our [FTTH serving-area design services](https://draftech.com/services/ftth-design) connect the premises register to the splitter and terminal assignments. The useful deliverable is a traceable connection, not just a shaded map: the owner can follow an address to its allocated capacity and see which unbuilt or unverified segment still prevents service.

## Test Drop Length from the Terminal to the Premises

Drop length starts at the assigned terminal, not automatically at the FDH. A cabinet-to-home radius mixes distribution length with the final connection and can produce the wrong boundary. We first place terminals against the actual premises approaches, then measure the proposed drop route under the owner's criteria. Keep the measurement basis on the drawing.

### Separate installation limits from optical reach

The owner needs a defined maximum drop length for the selected installation method and product. We do not supply a universal footage limit because an acceptable optical path can still fail the cable's mechanical requirements or the operator's installation policy. Available preconnectorized lengths also affect the decision when the design uses factory-terminated drops rather than field termination.

A terminal may sit close to a house while the usable entrance lies around the far side of the property. We measure the actual proposed path and account for the installation allowances required by the owner and manufacturer. A diagonal measurement across a parcel is not a substitute for that route, especially where the customer access agreement confines the work.

**Review the exception addresses individually.** A favorable average drop length can conceal the premises that need a different terminal position. Keep each over-limit route visible until the owner accepts a revised design or a documented exception.

When a drop fails the limit, we first test terminal relocation within the same serving area. A distribution extension may solve the reach problem without moving the cabinet or changing the split hierarchy; our [LLD splice-point placement guide](https://draftech.com/blog/ftth-lld-splice-point-placement-guide) addresses how those local connections enter the construction design. If the better terminal belongs to a neighboring area, transfer the address explicitly and rerun the receiving capacity check; do not let the installer make that allocation in the field.

Boundary rules should also explain road crossings. Serving opposite sides from the same terminal can require separate permissions or a different construction method even when both homes fall inside the drop limit. We show the crossing on the proposed path. A serviceable address is more than a point within reach of an available port.

## Reserve Capacity Where Growth Can Connect

Spare capacity needs a location and a purpose. A vacant cabinet position cannot serve a future street if the outgoing cable has no usable fiber to that branch. We therefore review reserve along the complete connection path and keep committed future demand separate from maintenance capacity. One spare cannot satisfy both obligations.

### Give each reserve an assignment rule

We record whether a spare is available for ordinary connections or protected for a stated purpose. An unused splitter output and an unassigned distribution strand are related resources, but they are not interchangeable. The reserve schedule should show how the operator can connect a new premises without consuming capacity already promised to an approved development or reserved for restoration.

Growth forecasts need an owner-approved horizon and a trigger for augmentation. We show what changes when the next development becomes real, rather than applying a blanket percentage that conceals where demand will arrive. If expansion requires another enclosure position or a new distribution cable, that dependency belongs in the plan before the original cabinet site is accepted.

Test growth at the boundary, too. A future parcel may be geographically closer to the neighboring FDH yet reachable only from the first area's corridor. Holding it in a generic growth polygon leaves the ownership question unresolved. Assign the forecast to its plausible service path, identify the uncertainty, and revisit the assignment when the development's entrance is fixed.

## Fiber Network Distribution Area Planning: Choose the Release Basis

**For a rural cooperative:** prioritize routed reach and cabinet access before equalizing area counts. Widely separated premises should not be forced into a compact cluster whose remote branches cannot satisfy the selected design criteria. We recommend retaining a larger geographic area only when the terminal plan and complete optical paths support it.

**For an overbuilder:** resolve boundary addresses against the actual connection side of the street before fixing the construction package. Neighboring areas can share a corridor while keeping distinct customer assignments. We recommend a premises-by-premises exception review where that shared corridor makes it easy for the field package to imply the wrong terminal.

**For a phased development owner:** reserve the physical route into later phases before relying on empty splitter outputs. The first cabinet needs a credible expansion arrangement, and the area register needs a clear distinction between current premises and forecast units. We recommend releasing the current phase with those dependencies stated, so future capacity is neither sold twice nor mistaken for installed plant.

A release review should reproduce an address trace without the original designer explaining it. We check that the assigned terminal leads to the intended FDH and that the capacity record agrees with the route drawing. Changed boundaries require changed assignments. Keep unresolved access or length exceptions open instead of hiding them behind a completed HLD status.

**[Discuss the serving-area constraints with Draftech.](https://draftech.com/#dt-contact)** Send the proposed address register and cabinet locations so the engineering scope starts with the assignments that need a decision.

When boundary exceptions or stranded spares keep the package from release, Draftech's [engineering and construction services](https://draftech.com/services) connect the area plan to delivery. Engineering is 100% in-house; full turnkey construction is delivered by Draftech-managed subcontract crews. Active in 24 states. Available across all 50 U.S. states. For a serving-area scope discussion, contact [info@draftech.com](mailto:info@draftech.com).

For a route that needs its cabinet locations and serving boundaries worked through, the [Draftech free design offer](https://draftech.com/free-design) covers engineering for the first 20,000 linear feet of a qualifying route at no cost, from feasibility and field survey through permit approval. The owner reviews each request before Draftech commits the package.

## Frequently Asked Questions

### How many homes belong in one FTTH distribution area?

There is no single home count that defines every area. A 1:32 splitter has 32 outputs, but an FDH may contain several splitters, and its assigned premises must also fit the routed network. Set the boundary from the approved demand and usable terminal paths, then confirm installed and ultimate capacity separately before accepting the cabinet configuration for that area.

### Should the cabinet sit at the center of the serving area?

Use the center as a candidate rather than a fixed requirement. A centralized 1:32 arrangement still needs a usable cabinet site and feasible distribution routes to its assigned terminals. Compare candidate locations by their routed connections and access constraints; the preferred position may sit away from the geographic center because a crossing or property restriction controls the build.

### How do cascaded splitters affect area capacity?

Cascaded ratios multiply: a 1:4 stage feeding 1:8 splitters creates a total 1:32 split on a complete customer path. Preserve the relationship between stages so an output feeding another splitter is not counted as a free customer connection. Capacity allocation must also pass the optical review using actual device losses and the selected equipment limits for that route.

### Does a 1:32 split set the maximum drop length?

Use the operator-approved limit for the selected drop product and installation method, measured along the proposed terminal-to-premises route. A 1:32 split ratio does not establish a universal drop distance because optical loss and installation constraints are different checks. Identify any over-limit premises individually, then revise its terminal assignment or obtain a documented design exception before releasing the affected connection.

### How should growth spares be recorded?

Record spare capacity by its physical location and permitted use, distinguishing future customer connections from protected maintenance reserve. An unused output on a 1:32 splitter does not establish that a distribution strand is available at the future terminal. Trace the proposed expansion through the whole connection path and identify the augmentation needed when the owner-approved demand forecast becomes committed.