Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 16 tasks across 5 phases, about 11 weeks from start to finish with the parallel work shown.
What's in the template
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| Prepare | Confirm objectives and scope | 3 days | Day 1 | Nothing (starts first) |
| Prepare | Name the implementation team and owners | 2 days | Day 4 | Confirm objectives and scope |
| Prepare | Current-state review | 5 days | Day 6 | Name the implementation team and owners |
| Prepare | Readiness and risk assessment | 3 days | Day 11 | Current-state review |
| Configure | Design the future process | 6 days | Day 11 | Current-state review |
| Configure | Configure the system or tools | 10 days | Day 17 | Design the future process |
| Configure | Data preparation and migration | 8 days | Day 17 | Design the future process |
| Configure | Training materials | 6 days | Day 17 | Design the future process |
| Pilot | Pilot with one team | 10 days | Day 27 | Configure the system or tools, Data preparation and migration, Readiness and risk assessment |
| Pilot | Pilot review and fixes | 4 days | Day 37 | Pilot with one team |
| Roll out | Communications to all staff | 3 days | Day 41 | Pilot review and fixes |
| Roll out | Train all users | 5 days | Day 41 | Pilot review and fixes, Training materials |
| Roll out | Go-live by group | 10 days | Day 46 | Train all users, Communications to all staff |
| Sustain | Support and issue log | 15 days | Day 56 | Go-live by group |
| Sustain | Benefits review | 3 days | Day 71 | Support and issue log |
| Sustain | Hand over to business as usual | 2 days | Day 74 | Benefits review |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 75 days instead of the 95 it would take one task at a time. The 12 darker bars are the critical path: a day lost on any of them moves the finish date.
About this implementation plan
Implementation is the part after the decision. The software has been chosen, or the new process has been agreed, and now it has to work for real people on a real date. Implementation plans fail in predictable places: data that is not ready, users who were trained too early or too late, and a go-live for everyone at once with no pilot to learn from. This template builds in a pilot and a phased rollout to avoid those.
It is written for an internal rollout of a new tool or process across several teams, over about eleven weeks. Configuration, data preparation and training material run in parallel after the future process is designed, and the pilot waits for all three plus a readiness check. Training for everyone waits for the pilot's lessons, which is the main reason to have a pilot at all.
For a specific system, the CRM, ERP, cloud migration and customer onboarding templates have more detailed task lists. This one is the general version: use it for a new policy, a new process, a new internal tool or anything else that changes how people work.
Who it's for: Implementation leads, operations managers and project managers responsible for getting a new system or process adopted.
How to use it
- Use this template. Click Use this template. The plan opens in the editor with prepare, configure, pilot, roll out and sustain as lanes and every link drawn.
- Name your pilot group. Pick one team that is representative but forgiving, and put its name in the pilot task. The pilot should use real data and real work, not a demo.
- Size the rollout groups. Split go-live into groups (by team, site or region) if you have more than a few dozen users. Add one task per group so each has its own date and owner.
- Share the plan with the business. Send a read-only link to managers whose teams are affected. They see when their team is trained and goes live, without needing an account.
Why the plan has a pilot
A pilot is the cheapest place to find out what the design missed. One team using the new system or process for two weeks will find the missing fields, the confusing steps and the reports nobody asked for. Fixing those before training everyone means the training covers the version people will really use.
In this template the pilot waits for configuration, data preparation and the readiness assessment. Data is the item to watch: it has only two days of slack here, and it is often the task that takes longer than expected, because the old data has to be cleaned before it can be moved.
After go-live: sustain, then hand over
An implementation is not finished at go-live. The support period keeps an issue log and a named person to answer questions, so problems are fixed rather than worked around. The benefits review then checks the objectives set at the start: did the new system or process do what it was meant to?
The last task hands ownership to the people who run things day to day. Writing it down as a task makes it happen on a date, instead of the implementation team quietly remaining the support desk for months.
Planning tips
- Train people as close to their go-live date as you can. Training given weeks earlier is mostly forgotten.
- Keep the old way of working available but read-only for a short period after go-live, so people can check history without using it to work around the new system.
- Write the objectives as things you can check in the benefits review, and put the review date in calendars at the start.
- Give every rollout group a named contact for the first week. Questions get answered faster, and you learn what to fix.
Frequently asked questions
- What is an implementation plan?
- A plan for putting a decision into practice: a new system, process or policy. It sets out the tasks, owners, timeline and dependencies from preparation through go-live and support, and how success will be checked.
- What should an implementation plan template include?
- Objectives and scope, the team and owners, a readiness and risk check, configuration or design work, data preparation, training and communications, a pilot, the rollout schedule, post-go-live support and a review of benefits. All of these are tasks on this template.
- How is an implementation plan different from a project plan?
- An implementation plan is a project plan focused on adoption: pilots, training, rollout groups and support matter as much as the build. The project plan template is the general version.
- Can I download the implementation plan?
- Yes. Download CSV gives every task with its phase, start and end date and dependencies, for Excel or Google Sheets. It is free on this page.
Related templates and guides
- Cutover Plan Gantt chart template
- Change Management Plan Gantt chart template
- CRM Implementation Plan Gantt chart template
- ERP Implementation Plan Gantt chart template
- SaaS Customer Implementation Gantt chart template
- Project Plan Gantt chart template
- Smartsheet 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.