Implementation plan, new practice management system, Tallowgate Family Clinic

Implementation plan template with workstreams and dates

An implementation plan has to turn a decision that is already made into ordered work: who does what, by when, what depends on what, and what it costs. This five page plan for a medical clinic moving 14,200 patient records to a new practice system sets seven workstreams, eleven milestones to a 5 July 2027 go live, the dependencies on the critical path, resourcing, an $86,400 budget and risks.

Create a document with OneCraft5 A4 pages, editable, then download as a PDF

The document, page by page

Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.

Tallowgate Family Clinic
14 December 2026

Practice system implementation plan

Seven workstreams, one go live date, and the order things must happen in to move 14,200 patient records safely.

Prepared by
Practice manager and project lead
Date
14 December 2026
Tallowgate Family Clinic, practice system implementation planPage 2 of 5
Tallowgate Family Clinic, practice system implementation planPage 3 of 5
Tallowgate Family Clinic, practice system implementation planPage 4 of 5
Tallowgate Family Clinic, practice system implementation planPage 5 of 5
1. What is being implemented

Tallowgate Family Clinic is moving from a server based practice system, in use since 2011, to a cloud practice management system that handles appointments, clinical notes, prescribing, results, billing and patient reminders. The clinic has 9 doctors, 6 nurses, 8 reception and administration staff and 14,200 active patients.

The decision to buy has been made and the contract signed. This plan is about putting the system in: who does what, in what order, what depends on what, and what it costs. Go live is Monday 5 July 2027, chosen because July is the clinic's quietest month for appointments.

5 Jul 2027
Go live
7
Workstreams
23
Staff to train
$86,400
Budget
What success looks like
Every active patient record, with notes, allergies, medicines and results, moved and checked
No clinic session cancelled because of the change
Appointment capacity back to 100% by the end of the third week after go live
The old server switched off and its data archived by 4 October 2027
2. Workstreams
No.
Workstream
Scope
Lead
1
Data migration
Extract, map and load patient records, appointments and accounts; three trial loads
Practice manager with the vendor
2
Configuration
Appointment books, fee schedules, clinical templates, user roles
Nurse manager and practice manager
3
Integrations
Pathology and imaging results, electronic prescribing, SMS reminders, online booking
IT provider
4
Hardware and network
Internet link upgrade, backup link, card readers, label printers
IT provider
5
Training
Role based training, practice sessions, super users
Clinical lead doctor
6
Go live and support
Cut over weekend, reduced bookings, floor support, issue log
Project lead
7
Decommission
Read only access, archive, server shutdown
IT provider
No.
Workstream
Scope
Lead
1
Data migration
Extract, map and load patient records, appointments and accounts; three trial loads
Practice manager with the vendor
2
Configuration
Appointment books, fee schedules, clinical templates, user roles
Nurse manager and practice manager
3
Integrations
Pathology and imaging results, electronic prescribing, SMS reminders, online booking
IT provider
4
Hardware and network
Internet link upgrade, backup link, card readers, label printers
IT provider
5
Training
Role based training, practice sessions, super users
Clinical lead doctor
6
Go live and support
Cut over weekend, reduced bookings, floor support, issue log
Project lead
7
Decommission
Read only access, archive, server shutdown
IT provider
No.
Workstream
Scope
Lead
1
Data migration
Extract, map and load patient records, appointments and accounts; three trial loads
Practice manager with the vendor
2
Configuration
Appointment books, fee schedules, clinical templates, user roles
Nurse manager and practice manager
3
Integrations
Pathology and imaging results, electronic prescribing, SMS reminders, online booking
IT provider
4
Hardware and network
Internet link upgrade, backup link, card readers, label printers
IT provider
5
Training
Role based training, practice sessions, super users
Clinical lead doctor
6
Go live and support
Cut over weekend, reduced bookings, floor support, issue log
Project lead
7
Decommission
Read only access, archive, server shutdown
IT provider
3. Milestones
Week of
Milestone
Workstream
11 Jan 2027
Project start, kick off with the vendor
All
1 Feb 2027
Internet link upgraded and backup link in place
4
1 Mar 2027
First trial data load complete and checked
1
5 Apr 2027
Configuration signed off by doctors and reception
2
3 May 2027
Second trial load; integrations tested end to end
1, 3
31 May 2027
Training starts; super users certified
5
14 Jun 2027
Final trial load and go live readiness check
1, 6
28 Jun 2027
Go or no go decision, Tuesday 29 June
6
5 Jul 2027
Go live after the cut over on Saturday 3 July
6
2 Aug 2027
Full appointment capacity, support scaled back
6
4 Oct 2027
Old server archived and switched off
7
4. Dependencies

These links decide the critical path. If the earlier item slips, the later one slips with it unless the plan is changed.

This cannot start
Until
Why
Trial data loads
Link upgraded
Loads move about 60 GB to the cloud
Configuration sign off
First trial load
Templates are tested with real migrated records
Training
Configuration signed off
Staff must learn the screens they will use
Integration testing
Second trial load
Results must match migrated patients
Go or no go decision
Final trial load checked
The decision rests on its error rate being under 0.5%
Server shutdown
90 days after go live
Doctors may need the old record during settling in
This cannot start
Until
Why
Trial data loads
Link upgraded
Loads move about 60 GB to the cloud
Configuration sign off
First trial load
Templates are tested with real migrated records
Training
Configuration signed off
Staff must learn the screens they will use
Integration testing
Second trial load
Results must match migrated patients
Go or no go decision
Final trial load checked
The decision rests on its error rate being under 0.5%
Server shutdown
90 days after go live
Doctors may need the old record during settling in
This cannot start
Until
Why
Trial data loads
Link upgraded
Loads move about 60 GB to the cloud
Configuration sign off
First trial load
Templates are tested with real migrated records
Training
Configuration signed off
Staff must learn the screens they will use
Integration testing
Second trial load
Results must match migrated patients
Go or no go decision
Final trial load checked
The decision rests on its error rate being under 0.5%
Server shutdown
90 days after go live
Doctors may need the old record during settling in
5. Resourcing and budget

The clinic is too small for a full time project team, so the plan buys in a part time project lead and protects staff time with reduced appointment books.

Who
Time committed
When
Project lead, contractor
2 days a week
January to August 2027
Practice manager
1 day a week, 3 days from June
January to October 2027
Nurse manager
Half a day a week
February to July
Clinical lead doctor
2 sessions a month
March to July
Super users, 4 staff
12 hours each
June
All staff
6 to 10 hours training each
June
Cost
Amount
Share
Vendor implementation and data migration service
$28,000
32.4%
Project lead contractor
$16,000
18.5%
Additional data cleansing and checking
$14,500
16.8%
Training time, reduced bookings and backfill
$12,800
14.8%
Hardware: link upgrade, printers, card readers
$9,600
11.1%
Contingency
$5,500
6.4%
Total
$86,400
100.0%

Appointment books are cut to 60% in go live week, 80% in week two and 90% in week three, so doctors have time to learn on real patients. The lost billing is counted in the training line above.

6. Risks
Risk
Rating
Response
Migrated data has errors that harm care
High
Three trial loads, 200 records checked by clinicians each time, go live only under 0.5% errors
Results arrive in the wrong patient's file
High
Matching tested with each pathology and imaging provider before go live
Staff not confident on day one
Medium
Super user on every shift, practice sessions on migrated data
Internet outage after go live
Medium
Backup link from a second provider, downtime forms printed
Vendor timeline slips
Medium
Contract milestones; go live can move to 2 August 2027 without clinic impact
Old system needed after shutdown
Low
Read only archive kept for the legal retention period

The project lead reports to the clinic's partners every fortnight with milestones, budget spent, open risks and the decisions needed. The go or no go meeting on Tuesday 29 June 2027 uses a written checklist, and either answer is a good outcome if it is made on evidence.

Section by section

What each section is for, so you can keep the ones you need and drop the rest.

Cover
Document cover with the clinic, the project and the plan date.
1. What is being implemented
The system, go live date, four headline figures and four success measures.
2. Workstreams
Seven workstreams with scope and lead.
3. Milestones
Eleven milestones from January to October 2027.
4. Dependencies
Six links on the critical path with the reason for each.
5 and 6. Resourcing, budget and risks
People and time, six budget lines to $86,400 and six risks.

How to adapt this document

First, write the success measures before the workstreams, then cut any workstream that does not serve one. Second, build the dependencies table by asking of each task what it cannot start without; that table, more than the milestone list, tells you where a delay will hurt. Third, for a bigger rollout across sites, add a row per site to the milestones and a go or no go meeting before each wave rather than one big cut over.

What makes this document work

Dependencies show the critical path

The dependencies table pairs each task with what it waits for and why: configuration cannot be signed off until a trial load gives real records to test templates on, and the go or no go decision rests on the final trial load's error rate being under 0.5%. A slip upstream is visible before it reaches go live.

Success is defined before the work starts

Four tests open the plan: every active record moved and checked, no clinic session cancelled, appointment capacity back to 100% by the end of week three, and the old server archived by 4 October 2027. The milestones and budget then serve those four.

The cost of learning is budgeted

Appointment books drop to 60%, 80% and 90% over the first three weeks so doctors learn on real patients without rushing, and the lost billing is counted in the $12,800 training line. Six budget lines add to $86,400, with shares totalling 100.0%.

Questions people ask

What is the difference between an implementation plan and a project plan?

The terms overlap. A project plan often covers the whole life of a project, including the business case and the choice of option. An implementation plan starts once the decision is made and focuses on delivery: workstreams, sequence, dependencies, resources and the cut over. This clinic plan begins after the contract was signed.

What are workstreams in an implementation plan?

Workstreams are groups of related work that run in parallel, each with its own lead, such as data migration, configuration, training and go live support. Splitting work this way lets a small team see who owns what, while the milestones and dependencies show where the streams must meet. Seven is plenty for a project this size.

How should a go live decision be made on a system implementation?

A planned meeting shortly before go live where named people decide, against a written checklist, whether to proceed or delay. Typical criteria are data quality, testing results, training completion and support readiness. Setting the criteria in advance means the decision rests on evidence rather than on the pressure of a date already announced.

How much contingency should an implementation budget include?

Five to ten percent of the project cost is a common starting point, more where the work is new to the organisation or depends on outside vendors. This plan holds $5,500, about 6.4%. Contingency should be controlled by one person and reported, so it is used for real surprises rather than added scope.

How long should an old system be kept after a migration?

Long enough for staff to look up anything that did not move cleanly, often 60 to 90 days in read only mode, and then archived for as long as records must legally be kept. This plan switches the old server off 91 days after go live and keeps a read only archive for the retention period.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other document examples

Want the steps in the builder? Read Create a document with AI, then Document builder components. For everything this generator can do, see the document maker.

Sources

Written and checked by the OneCraft team. Last checked .