Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 13 tasks across 4 phases, about 12 weeks if every task runs in sequence.
What's in the template
Current network inventory and assessment
Requirements and design
Change approval
Hardware and license procurement
Staging and configuration
Lab testing
Pilot site cutover
Pilot review
Phase one cutover window
Phase two cutover window
Monitoring and fixes
Network documentation update
Handover and decommission old gear
| Phase | Task | Example duration |
|---|---|---|
| Assess | Current network inventory and assessment | 7 days |
| Assess | Requirements and design | 10 days |
| Assess | Change approval | 3 days |
| Procure | Hardware and license procurement | 21 days |
| Procure | Staging and configuration | 7 days |
| Procure | Lab testing | 5 days |
| Rollout | Pilot site cutover | 2 days |
| Rollout | Pilot review | 5 days |
| Rollout | Phase one cutover window | 3 days |
| Rollout | Phase two cutover window | 3 days |
| Close | Monitoring and fixes | 7 days |
| Close | Network documentation update | 5 days |
| Close | Handover and decommission old gear | 3 days |
Durations are examples to replace with your own estimates, not benchmarks.
About this it network upgrade
Network upgrades are scheduled around downtime. Equipment has to arrive and be staged and tested before anyone touches production, and cutovers happen in approved change windows. This plan puts a pilot site ahead of the phased rollout so problems surface on a small scale.
It fits switch, wireless or firewall refreshes across one or more offices.
Who it's for: IT managers, network engineers and managed service providers.
How to use it
- Open the plan. Click Open in the editor.
- Use your vendor's lead time. Replace the procurement duration with the quoted delivery time.
- Label the downtime. Keep each cutover window as a bar so its full length shows, and name it clearly, for example "Phase one cutover (downtime)".
- Share the schedule. Send a read-only link to site contacts and the change board.
Planning tips
- Have a tested rollback plan for every cutover window.
- Label equipment during staging, not on cutover night.
- Decommission old hardware only after the monitoring period.
Frequently asked questions
- Why run a pilot site?
- A pilot exposes configuration and process problems on a small site, where fixing them affects fewer people.
- Can I add more sites?
- Yes. Add a cutover row per site or per phase and set dependencies as needed.
- Is it free?
- Yes. Opening and editing the template is free; a free account saves one project.
Related templates
The free plan saves one project. Downloads (PDF, CSV) and more projects are on Solo, $12/month.