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
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| Assess | Current network inventory and assessment | 7 days | Day 1 | Nothing (starts first) |
| Assess | Requirements and design | 10 days | Day 8 | Current network inventory and assessment |
| Assess | Change approval | 3 days | Day 18 | Requirements and design |
| Procure | Hardware and license procurement | 21 days | Day 21 | Change approval |
| Procure | Staging and configuration | 7 days | Day 42 | Hardware and license procurement |
| Procure | Lab testing | 5 days | Day 49 | Staging and configuration |
| Rollout | Pilot site cutover | 2 days | Day 54 | Lab testing |
| Rollout | Pilot review | 5 days | Day 56 | Pilot site cutover |
| Rollout | Phase one cutover window | 3 days | Day 61 | Pilot review |
| Rollout | Phase two cutover window | 3 days | Day 64 | Phase one cutover window |
| Close | Monitoring and fixes | 7 days | Day 67 | Phase two cutover window |
| Close | Network documentation update | 5 days | Day 74 | Monitoring and fixes |
| Close | Handover and decommission old gear | 3 days | Day 79 | Network documentation update |
Durations are examples to replace with your own estimates, not benchmarks. Every task waits for the one before it, so the whole chain is the critical path until you overlap work that can run in parallel.
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 Use this template.
- 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 and guides
- Data Migration Plan Gantt chart template
- ERP Implementation Plan Gantt chart template
- Office Move Plan Gantt chart template
- Sprint planning on a Gantt chart
- Microsoft Project alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.