Free template

Free Implementation Plan Template

A plan for putting something new into use: a system, a tool or a new way of working. Twelve weeks from agreeing the goal to handing it over to the people who will run it, with a pilot before go-live, training before launch and a support period after it, because an implementation is finished when people use it, not when it is switched on.

No credit card. Opens as a real project on the Free plan.

The spreadsheet is a 16-task plan with phases, durations and milestones, ready for Excel or Google Sheets. It carries no dates, so set your own start, or paste it into the Gantt chart generator to have the schedule built for you. Want to compare the plans side by side first? Every one of them is on the project plan template page, with the rows shown before you download.

The Microsoft Project file (.xml) is the same plan with its dates worked out: every task is scheduled from Monday 4 January 2027. Open it in Microsoft Project, or open it free in Onplana Schedule, the desktop app that edits Project files without Microsoft Project.

The Implementation Plan template as a real project in Onplana: its first phases in order, each task with a status, an owner and a due date. The full plan is below.

What’s inside

All 16 tasks are below, in five phases, each with its description, duration and priority. Rename the build task for your own system or process; the shape around it, pilot, training, go-live and support, is the part worth keeping.

16

Scheduled tasks

5

Phases

5

Milestones

~12

Weeks end to end

Switched on is not the same as in use

An implementation plan differs from a build plan in where it ends. The build is done when the thing works; the implementation is done when the people it was meant for use it in their daily work and someone owns it. That is why this template gives as much room to the last two phases as to the build. Training comes before launch, a go or no-go decision sits in front of go-live, and the two weeks after go-live are planned work, not whatever is left of the budget.

The first phase names the owners and the decision makers before any configuration starts, and maps how the work is done today. That map is what the changed procedures are written from, and it is the baseline the success measures are compared against at the end. The preparation phase holds the configuration or build, the data and the integrations, and the procedures that change, each as its own task so none of them hides inside another.

Testing ends with a pilot: one team uses the new system for real work for two weeks before everyone else does. A pilot finds the problems that test scripts do not, such as the report nobody mentioned and the step that takes twice as long as it did. If your implementation is mostly about moving data from an old system, the data migration cutover template covers that part in more detail; this plan is the wider rollout around it.

The plan, phase by phase

Plan4 tasks

Confirm the goal, scope and success measures

What changes, for whom, and the two or three measures that will show it worked, written down before anything is built.

3 daysHigh

Name the owners and the decision makers

The sponsor, the person who will own it after go-live, and who decides go or no-go.

1 dayHigh

Map the current way of working

How the work is done today, step by step, with the people who do it. It is the baseline for the procedures and the measures.

4 daysMedium

Agree the plan, budget and go-live date

The sponsor approves this plan, the budget and a go-live date that avoids the busiest weeks of the year.

2 daysCritical

Prepare3 tasks

Configure or build the solution

Rename it for your system or process and split it into pieces of no more than two weeks each.

15 daysCritical

Prepare the data and the integrations

What moves from the old way, what connects to other systems, and a test load of each.

10 daysHigh

Write the changed procedures

Short, step-by-step notes for each task that changes, written from the map of the current way of working.

5 daysMedium

Test and Pilot3 tasks

Test with real scenarios

Real cases from the people who will use it, not only scripted ones. Every failure logged with an owner.

8 daysHigh

Fix what testing found and retest

In order of harm, with each fix retested by the person who found the problem.

5 daysHigh

Run a pilot with one team

One team uses it for real work for two weeks. Collect what slowed them down and fix it before everyone starts.

10 daysHigh

Train and Go Live3 tasks

Train the people who will use it

Short sessions by role, as close to go-live as possible, using the changed procedures.

5 daysHigh

Decide go or no-go

The decision maker reads the test and pilot results and the open issues; a no-go names what must change.

1 dayCritical

Go live

Switch over on the agreed day, with support on hand and a way back agreed in advance.

1 dayCritical

Support and Hand Over3 tasks

Give extra support in the first two weeks

A named person to ask, a daily check on problems, and quick fixes to the procedures where people get stuck.

10 daysHigh

Measure against the success measures

The measures agreed in the first week, compared with the baseline, with an honest note on any gap.

3 daysMedium

Hand over to the team that runs it

The owner accepts it, with the open issues, the procedures and who to call, and the project closes.

2 daysHigh

Milestones

Five milestones: the plan approved, ready for testing, the pilot complete, live, and handed over to the team that runs it. The last one is the real finish line.

Plan approved

Day 10 of the plan

Ready for testing

Day 40 of the plan

Pilot complete

Day 63 of the plan

Live

Day 70 of the plan

Handed over

Day 85 of the plan

Frequently asked

What is in the download?

A CSV file with the 16 tasks, each with its phase, duration in days, priority and notes, and the five milestones as zero-day rows. Excel opens it directly and Google Sheets imports it. It has no dates until you choose a start.

What should an implementation plan include?

The goal and how success is measured, the owners and decision makers, the build or configuration, the data and integrations, testing, training, the go-live decision, support after go-live and the handover. This template has a task for each, in that order.

Do I need the pilot?

For anything more than a handful of users, yes. Two weeks of one team doing real work finds the problems that testing misses, and it gives you people who can help their colleagues on the day everyone else starts. For a very small rollout, shorten it to a few days rather than dropping it.

Is this for software only?

No. The same phases fit a new process, a new tool or a reorganised service. Rename the build task for whatever is being put into use; planning, a pilot, training, go-live and handover apply to all of them.

Start with the plan already built

Open the Implementation Plan template free and your phases, tasks, and milestones are scheduled before the kickoff meeting. No credit card, no time limit.