Capacity planning timeline
Infrastructure growth plan with procurement, provisioning, and rollout phases.
Every infrastructure team runs out of capacity eventually. The window between "we need more" and "it's live" is 3–4 months: forecasting, vendor negotiations, procurement lead times, testing, and phased rollout. This template maps the complete timeline so you can work backward from your peak-traffic date.
The template includes parallel tracks (forecast and procurement can happen simultaneously) and staged rollout (phase 1 tests the setup, phase 2 expands it). The monitoring phase at the end is critical — you don't declare success until production has run stably for weeks.
When to use this template
- Annual capacity planning — sync with finance and procurement on budget and timelines before peak season hits.
- Growth initiatives — when a customer acquisition campaign or feature launch will double traffic, use this to kick off infrastructure planning early.
- Vendor negotiation — show this timeline to vendors so they understand their deadlines. Equipment delivery is often the critical path.
How to adapt it
Customize the phases and timelines to match your infrastructure:
- Add approval gates — insert 'Finance_Approval' and 'Security_Review' tasks to model your governance process.
- Extend for multi-region — if you deploy to multiple regions, add parallel rollout tracks for each.
- Include fallback options — add a parallel track for temporary cloud scaling while permanent infrastructure provisions.
Visual edits regenerate clean code for sharing with procurement, finance, and operations teams.
Mermaid code
Copy it anywhere Mermaid is supported — GitHub, Notion, or your docs.
gantt
title Capacity Planning Timeline
dateFormat YYYY-MM-DD
section Infrastructure
Demand Forecast :demand, 2026-08-01, 30d
Capacity Gap Analysis :analysis, demand, 14d
section Procurement
Vendor RFQ :rfq, analysis, 21d
Equipment Purchase :purchase, rfq, 30d
section Deployment
Lab Testing :testing, purchase, 14d
Staged Rollout Phase 1 :rollout1, testing, 7d
Staged Rollout Phase 2 :rollout2, rollout1, 7d
section Monitoring
Production Monitoring :monitoring, rollout2, 30d
Frequently asked questions
- What is a capacity planning timeline?
- It maps the journey from 'we need more infrastructure' to 'it's live and stable': forecasting demand, analyzing the gap, requesting quotes from vendors, purchasing and receiving equipment, testing in staging, rolling out in phases, and monitoring production. Each phase depends on the one before.
- Why break rollout into phases instead of deploying all at once?
- Phased rollout lets you catch configuration mistakes, performance bottlenecks, and integration issues on a small subset of traffic before committing all capacity. If phase 1 shows a problem, you fix it in phase 2. All-at-once deployment risks a production incident affecting all users.
- How do I customize this for my infrastructure?
- Replace the phases with your actual process: add 'Approval' gates, change vendor lead times, adjust rollout phases based on your traffic patterns. If you use spot instances or cloud auto-scaling, shorten procurement to just configuration time. Visual edits regenerate clean Gantt code.
- What should I track alongside this timeline?
- Track peak traffic forecasts, current capacity utilization, the growth rate, and lead times for your bottleneck component (often network or storage). Annotate the timeline with these numbers so stakeholders understand why the timeline is 4 months instead of 2 weeks.