FTTH network design • New housing developments
FTTH network design for new housing developments: work backward from move-in
The first resident’s move-in date should shape FTTH network design for new housing developments. Design the shared route for the planned development, then coordinate construction, plot connections and acceptance around the homes that will be occupied first.
What should the design prioritize? A continuous, accepted connection path from the operator’s network to each released plot, supported by accurate address records, order eligibility and a workable installation appointment. Ducts, chambers, fiber and premises preparation must be scheduled with the developer’s handover programme.
The executive decision: protect long-term civil capacity while phasing equipment and customer visits against verified plot readiness. The tradeoff is between efficient batching and the need to serve the first residents without waiting for later phases.
Infrastructure ready, ready to order and customer activated are separate milestones. A home can have fiber available without an active subscription. A resident still needs to select a provider, authorize the order and complete any required installation. Your launch plan must cover both the physical network and that customer process.
Current guidance: engage early and identify the first property
As checked on October 4, 2026, Openreach’s site registration guidance asks developers to register at least eight weeks before site start and/or six months before broadband is wanted at the first property. It also asks for plot information and build order for larger developments. The requested date supports scheduling; it is not a guaranteed delivery date.
That is an operator-specific UK process, not a universal lead time. Its useful principle is to identify the first service date and build sequence early enough for joint planning. Obtain the actual operator’s lead times, responsibilities and acceptance requirements for your development.
The FOA installation standard, Version 1.0 issued in October 2025, provides an installation, testing and documentation reference. Use current component specifications and applicable construction requirements with it. A project schedule needs evidence of acceptance, rather than a contractor’s statement that the cable has been laid.
FTTH = fiber to the home. ONT = optical network terminal at the premises. OLT = optical line terminal in the operator’s network. The schedules and USD examples below are proposed planning scenarios, not operator guarantees or local market rates.
Failure scenario: the shared network is finished, but the first homes cannot order
Consider a hypothetical 120-home development. The operator completes the feeder and the developer reports the common duct route finished. Sales announces availability for the site. However, several early plots have incomplete lead-in ducts, permanent address records have not been reconciled with plot numbers, and the ONT locations lack agreed power arrangements.
The result is avoidable: the first residents place orders that fail eligibility or installation checks. Crews return for incomplete work, support handles complaints about a service the customer cannot use, and the operator’s billed connections lag behind the construction forecast.
The design failure was treating the development as one readiness unit. Correct it by keeping a plot register that links construction sequence, civil acceptance, fiber test evidence, premises preparation and order eligibility. A late plot should not block a ready plot, and a ready feeder should not make an incomplete plot available for sale.
A joint developer and operator schedule, built backward
Set T as the planned first move-in date for the first released group. Give every later group its own T date. The following 26-week example shows dependencies, not prescribed task durations. Use local permits, operator lead times, procurement and the construction programme to establish the actual dates.
| Target | Joint activity | Lead owner | Evidence or dependency |
|---|---|---|---|
| T minus 26 weeks | Agree the first handover group, development layout and operator engagement. | Developer programme lead | Plot register, first occupancy target, phased build order and named contacts. |
| T minus 20 weeks | Approve routes, equipment locations, civil interfaces and responsibilities. | Operator design lead, with developer approval | Access rights, approved drawings, capacity plan, materials and civil scope. |
| T minus 14 weeks | Construct and inspect the shared ducts and chambers serving the first group. | Developer civil lead | Path continuity, entry arrangements, construction access and remedial actions. |
| T minus 8 weeks | Install and test shared fiber and commission required network equipment. | Operator delivery lead | Accepted pathway, upstream connection, equipment power and test records. |
| T minus 4 weeks | Verify each early plot’s lead-in, premises preparation and address mapping. | Developer plot lead and operator delivery | Access authorization, ONT location, power provision and plot-to-address match. |
| T minus 2 weeks | Release verified addresses for ordering and confirm installation arrangements. | Operator serviceability lead and Sales | Network acceptance, product eligibility, order-system checks and actual handover dates. |
| T and first occupancy | Complete authorized customer activation and confirm support ownership. | Service delivery | Valid order, safe premises access, accepted installation and correct billing state. |
External feeder delivery, crossing permissions and utility works can determine the critical path even if on-site civil work is progressing. Record those dependencies separately. Bring remedial inspections forward enough to repair a blocked duct before road surfacing or landscaping makes access more expensive.
Design the shared civil network for growth, then phase delivery
Coordinate duct routes and chamber positions with road construction, drainage, other utilities and planned access. Preserve continuous reserve through constrained crossings. Later phases need a feasible extension path that does not require disturbing already occupied streets without a costed reason.
Plan cable counts, splitter locations, terminal capacity and optical budgets from the full development layout and staged demand. A reserved port is useful only if it serves the right plot through a usable path. Equipment can often be introduced in stages, but any saving must be compared with remobilization and later installation access.
Inside each home, agree the lead-in route, fiber termination or ONT location, accessible power provision and the router/data arrangement. Confirm the actual installed condition before offering an appointment. Place the ONT for an acceptable installation; plan Wi-Fi coverage separately rather than assuming its location also makes the best router position.
Role-specific evidence before approval
| Role | Evidence required | Approval question |
|---|---|---|
| CNO / Network | Approved route and capacity plan; accepted ducts and chambers; feeder availability; optical tests; plot paths; power and commissioning; restoration records. | Can this released group receive the approved service, and can operations maintain it? |
| CSO / Sales | Plot handover dates, verified address eligibility, accepted product terms, appointment capacity and agreed customer communications. | Which addresses can receive an offer and an achievable activation commitment? |
| CEO / Finance | Scoped local quotes, stage expenditure, occupancy assumptions, mobilization costs and a contribution forecast based on billed customers. | Does the release plan balance timely service with capital exposure and repeated visits? |
| Developer | Construction sequence, common-route access, completed plot lead-ins, premises preparation, remediation records and authorized handover access. | Have the developer’s obligations been met for the exact plots being released? |
Set responsibilities in the agreement rather than assuming a universal split. Record who supplies materials, constructs and proves ducts, provides premises power, corrects defects, owns the installed assets and authorizes plot access. Assign a named coordinator on each side to resolve changes to the build programme.
Working example: batch visits without delaying the first residents
Assume the hypothetical development has 120 planned homes, 30 first-occupancy plots and 24 authorized customer installations in the first release. Later plots are not treated as occupied or paying customers. Compare two visit plans that both meet the same first-resident service deadline.
| Item | Fragmented appointments | Coordinated release |
|---|---|---|
| Crew mobilization | 8 mobilizations × USD 450 = USD 3,600 | 3 mobilizations × USD 450 = USD 1,350 |
| Completed installations | 24 × USD 180 = USD 4,320 | 24 × USD 180 = USD 4,320 |
| Incomplete-plot return visits | 6 × USD 90 = USD 540 | 2 × USD 90 = USD 180 |
| Total visit expenditure | USD 8,460 | USD 5,850 |
The coordinated scenario saves USD 2,610 in visit expenditure. It assumes the agreed installation throughput and access windows make three mobilizations feasible. It does not justify postponing an early resident’s installation until enough later homes are ready. Where batching would miss the first handover, price a smaller early visit explicitly.
For capital exposure, suppose shared infrastructure costs USD 40,000. If all 120 customer endpoints cost USD 100 and are purchased immediately, endpoint expenditure is USD 12,000. Buying 30 initially costs USD 3,000 and defers USD 9,000. That is deferred cash outlay, not a permanent saving; procurement lead times and later unit prices can change the result.
At USD 20 monthly contribution per billed customer, 24 customers contribute USD 480 per month. If only 12 complete activation and billing, contribution is USD 240. The distinction explains why equipment capacity and plot handovers should not be counted as recurring revenue.
Visit expenditure = mobilizations × cost per mobilization + installations × installation cost + return visits × revisit cost.
Monthly contribution = billed customers × (monthly revenue per customer − attributable recurring cost per customer).
No project-specific local quotes were supplied. The figures are transparent planning allowances. Obtain separate quotations for common civil work, fiber installation, equipment, mobilization, customer visits, remedial work and testing. Confirm that installation and mobilization charges do not overlap before using the calculation.
Approval gate: release plots, not a blanket development status
The developer signs off the agreed civil and premises obligations. Network accepts the infrastructure and service capability. The operator’s serviceability owner reconciles addresses and releases only approved plots. Sales commits installation timing within available delivery capacity. Executive approval of expenditure does not replace technical acceptance.
Block release for a missing permission or safe access arrangement, unaccepted pathway, failed fiber test, uncommissioned upstream service, incomplete premises preparation or an address that the order system cannot resolve. Keep the issue linked to the affected plot or release group. Offer conditional presales separately from confirmed service availability.
A representative installation and order test should prove the full process before the first resident depends on it. For a wholesale network, distinguish infrastructure operator acceptance, retail ISP order readiness and end-customer activation. One party’s completion status is not evidence that every party’s task is finished.
Operating measures for the first occupancy period
| Measure | Definition | What it reveals |
|---|---|---|
| Readiness at handover | Plots verified serviceable by handover ÷ plots handed over in the cohort. | Whether construction and network delivery align. |
| First-visit installation success | Accepted installations completed on first visit ÷ attempted first visits. | Premises preparation and qualification quality. |
| Activation time | Elapsed time from valid order acceptance to working service; report median and 90th percentile. | Typical delivery and slower cases. Track customer-requested delays separately. |
| Capacity utilization | Active connections ÷ installed serving capacity for the defined release area. | Use of deployed assets; this is different from adoption among occupied homes. |
| Restoration time | Time from a defined incident start to verified restoration; report the incident cohort. | Access, records, staffing and recovery capability. |
| Contribution | Revenue from billed customers less attributable recurring costs for the same period. | Realized value rather than construction progress. |
Review the register jointly each week during handover. When the developer changes occupancy dates, update customer appointments, crew demand and the revenue forecast together. Keep planned homes, handed-over homes, occupied homes and billed customers separate.
New housing development FTTH questions
When should a developer involve the fiber operator?
Early enough to agree the shared network, civil interfaces and first-property service date before relevant construction closes access. Confirm the chosen operator’s lead times rather than assuming a universal schedule.
Does fiber infrastructure mean broadband is active at move-in?
No. The network and plot need acceptance and order eligibility. The resident also needs a valid service order and any required appointment. Plan those milestones separately.
Should every plot be connected before the first phase opens?
Not necessarily. Build the shared infrastructure and future extension path appropriately, then align plot completion and customer visits with handover. Check the cost of deferral against later access and remobilization.
What should block a development launch?
Block the affected plots or release group when required access, civil acceptance, network tests, premises preparation or order records remain unresolved. A blanket launch must not hide those exceptions.
Evidence and planning method
Sources were checked on October 4, 2026. Openreach provides a current operator-specific engagement example; FOA’s October 2025 standard provides installation and acceptance context. The backward schedule, plot examples, allowances and reporting definitions are proposed planning tools by The Writer ID Team.
No project quotations or client outcomes are represented as factual results. Final responsibilities, dimensions, permissions, lead times and acceptance criteria must be agreed for the actual developer, operator and construction programme.