Skip to content

Post-implementation review

Check a finished project a few months on: did it deliver the benefits, at what cost, and what to do next.

Fill it in and preview

Post-implementation review

Project: New booking system
Sponsor: Marta Silva, Operations Director
Review led by: Jin Park, Project office
Go-live date: 1 March 2030
Review date: 3 June 2030

1. Goals and expected benefits

Cut booking time from 10 minutes to 3
Remove double bookings
Save 2 days of admin work a week

2. What was achieved

Booking time is now 4 minutes. Double bookings fell from 12 a month to 1. Admin saving is about 1.5 days a week.

3. Cost and schedule

Cost: Planned 85,000. Actual 92,500, 9 percent over
Schedule: Planned go-live 1 February. Actual 1 March, 4 weeks late

4. Quality and stability

3 serious faults in the first month, all fixed. No faults in the last 6 weeks.

5. Feedback from users

Front desk staff like the speed. Managers want better reports. Two people still use the old paper diary.

6. What went well

Clear weekly updates. Staff were trained before go-live.

7. What did not go well

Data cleaning took longer than planned. Testing started late.

8. Actions

Action Owner Due date
Build the manager report Jin Park 30 July
Retire the paper diary Marta Silva 30 June
Share lessons with the IT team Jin Park 15 June

9. Conclusion

The project delivered most of its benefits. Two actions are needed to finish the job.

Templates are a careful starting point, not legal advice. Where the law matters, check what applies where you are.

IT and projects

What this template is for

A post-implementation review to check a finished project against its goals: benefits, costs, schedule, quality, user feedback and lessons. Word or PDF.

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

IT and projects

What you fill in

The form asks for 15 details. The document fills itself in as you type.

  • Project name

    For example: New booking system

  • Project sponsor

    For example: Marta Silva, Operations Director

  • Review led by

    For example: Jin Park, Project office

  • Go-live date

    For example: 1 March 2030

  • Review date

    For example: 3 June 2030

  • Original goals and benefits

    One per line, as in the project case.

    For example: Cut booking time from 10 minutes to 3 Remove double bookings Save 2 days of admin work a week

  • What was achieved

    Give numbers and say how you measured them.

    For example: Booking time is now 4 minutes. Double bookings fell from 12 a month to 1. Admin saving is about 1.5 days a week.

  • Planned cost and actual cost

    Name the currency.

    For example: Planned 85,000. Actual 92,500, 9 percent over

  • Planned and actual schedule

    For example: Planned go-live 1 February. Actual 1 March, 4 weeks late

  • Quality and stability

    What went wrong after launch, and what is stable now.

    For example: 3 serious faults in the first month, all fixed. No faults in the last 6 weeks.

  • Feedback from users

    Summarise what users and customers said.

    For example: Front desk staff like the speed. Managers want better reports. Two people still use the old paper diary.

  • What went well

    One per line.

    For example: Clear weekly updates. Staff were trained before go-live.

  • What did not go well

    One per line.

    For example: Data cleaning took longer than planned. Testing started late.

  • Actions to take

    One row for each action.

    For example: Build the manager report | Jin Park | 30 July Retire the paper diary | Marta Silva | 30 June Share lessons with the IT team | Jin Park | 15 June

  • Conclusion

    A short verdict.

    For example: The project delivered most of its benefits. Two actions are needed to finish the job.

IT and projects

What is inside

The parts of this document, in order.

  1. 11. Goals and expected benefits
  2. 22. What was achieved
  3. 33. Cost and schedule
  4. 44. Quality and stability
  5. 55. Feedback from users
  6. 66. What went well
  7. 77. What did not go well
  8. 88. Actions
  9. 99. Conclusion

Templates

How it works

  1. 01

    Fill in

    Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

  2. 02

    Check

    Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

  3. 03

    Download

    Save it as a Word document to edit further, or as a PDF to send or print.

Make it yours with AI

Open it in the chat and ask for changes: shorter, firmer, another situation, another language.

Adapt it with nerix

IT and projects

Questions people ask

What details does this template ask for?

The form asks for 15 details, starting with Project name, Project sponsor, Review led by, Go-live date, Review date.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.