What's included
A fibre rollout is not one long build; it is the same six steps repeated across areas, offset in time. The template shows the pattern explicitly so you can copy a wave rather than invent a new plan for each area:
- Programme setup & high-level design, Demand assessment and area prioritisation, network and PoP design, contractor framework, core and backhaul procurement, and the as-built data model everything downstream depends on. Milestone: rollout plan baselined.
- Permits, wayleaves & survey, Street works permits, private wayleave negotiation, MDU landlord agreements, duct and pole availability survey and infrastructure access orders. Milestone: wayleaves cleared for wave 1.
- Area A, wave 1 build, Detailed design and splice plan, duct clearance and civils, cable blowing and pole overlash, splicing and cabinet build, OTDR testing and as-built handover. Milestone: Area A RFS.
- Area B, wave 2 build, The identical sequence, started while Area A is still in civils so crews and permits flow continuously. Milestone: Area B RFS.
- Area C, wave 3 build, The third wave, with its own wayleave lead time in front of it, the step teams most often forget to offset. Milestone: Area C RFS.
- Activation, sales & connections, PoP commissioning, OSS/BSS provisioning, pre-marketing, install crew scaling and the per-area connection campaigns that generate revenue. Milestone: take-up review and next-wave decision.
Who uses this template
Telecom program managers, network build planners, and civils contractors use this to deliver FTTP across a town or region. It tracks wayleaves, permits, duct surveys, and area-by-area build waves through OTDR testing and ready-for-service milestones, helping crews and connection teams keep multiple concurrent areas moving toward activation.
How to customize it
- Copy the Area A block once per build area and shift the offsets; the sequence is deliberately identical so it can be duplicated rather than rewritten.
- Set the wayleave and permit bars to your own authority's statutory notice periods, which vary widely and are not negotiable by pushing the contractor.
- Add a duct remediation bar with realistic contingency, blockages and collapsed ducts are found during survey, not during design, and they reroute whole streets.
- Split cable blowing from splicing if separate crews do them; they have different day rates and different weather sensitivities.
- Insert an MDU (apartment block) sub-plan where relevant, landlord agreements and in-building distribution run on a completely different clock from street works.
- Mark each area's RFS as a milestone and start that area's connection bar from it, so the chart shows revenue following build rather than running alongside it.
Scheduling tips
- Start wayleaves before design is finished. They are the longest-lead item in the whole programme and they depend on other people's solicitors, not on your engineers.
- Survey the ducts before you commit an area to a wave. Infrastructure access records are frequently wrong, and discovering a blocked duct after crews mobilise costs the area its slot.
- Overlap the waves deliberately, not accidentally. The point of wave planning is to keep one civils crew, one splicing crew and one install crew continuously loaded; gaps between waves are pure cost.
- Get OSS/BSS provisioning working during wave 1, not before wave 3. An area can be physically RFS and still unsellable because ordering, provisioning and billing are not integrated.
- Pre-market an area before it goes RFS. Registration of interest during the civils phase converts far better than a cold campaign after the vans have left, and it front-loads the connection curve.
- Track cost per premise passed by area, not programme-wide. One difficult area with heavy remediation will hide inside an average and quietly consume the contingency for three easy ones.
Related templates
- EV Charging Station Installation Schedule Template
- Data Center Build Schedule Template
- Franchise Rollout Plan Template
- Browse all Gantt chart templates
Frequently asked questions
How long does a fiber rollout take per area?
A typical build area of a few thousand premises runs four to six months from detailed design to RFS, which is what the template uses. The programme length comes from how many areas you run in parallel, not from the per-area duration.
What does RFS mean?
Ready for service, the point at which an area has been built, tested and loaded into the ordering systems so customers can actually be connected. It is the milestone that starts revenue, and it should be tracked per area.
Why are wayleaves on the critical path?
Because they involve third-party landowners with no incentive to move at your pace. They typically take months, cannot be compressed by adding resource, and a single refusal can force a redesign of an area.
How many waves should run at once?
Enough to keep your civils and splicing crews continuously loaded without exceeding your permit throughput with the highway authority. Two to three overlapping waves is common; the template shows three.
Why is homes connected so much lower than homes passed?
Because connection depends on marketing, install appointment capacity and customer contract end dates, none of which happen on the day an area goes RFS. Model the take-up curve separately from the build curve.
Is the fiber rollout template free?
Yes. Free Excel, PowerPoint and CSV downloads, and free online editing with no account and no watermark.