Skip to content

Lessons learned report

Look back at a project or incident without blame: what worked, what did not, why, and what to change.

Fill it in and preview

Lessons learned report

Project or event: Customer portal, release 3
Dates: 10 January to 16 April 2027
Review led by: Lucia Romero
Date of the review: 30 April 2027

Who took part: Lucia Romero, Jin Park, Priya Nair, Henrik Larsen, Mei Chen

The aim of this review is to learn, not to blame. We look at what happened and how our way of working can improve.

1. What we set out to do

Launch the portal with online payments by 5 April, for EUR 90,000.

2. What happened

Launched on 16 April, 11 days late, at EUR 96,500. Online payments work and 40 percent of clients use them in the first 2 weeks.

3. What went well

Daily short meetings kept everyone informed
The test team found problems early
Clients joined the demos and gave useful feedback

4. What did not go well

The payment test system was slow and unreliable
Changes were agreed by chat and not written down
Help texts were written too late

5. Why it happened

We did not test the bank connection before we planned the work.
There was no clear way to approve changes.

6. Lessons

Test every outside connection in the first month.
All changes go through a written change request.

7. Actions

Add a connection test to the project checklist: Lucia Romero, 14 May
Write the change process: Priya Nair, 21 May

We will check these actions at the next team meeting and record when each is done.

Shared with: All project managers, the management team

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

Plans and reports

What this template is for

A lessons learned report for the end of a project or incident: what was planned, what happened, what went well, what did not, causes and actions. Word or PDF.

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

Plans and reports

What you fill in

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

  • Project or event

    For example: Customer portal, release 3

  • Dates

    For example: 10 January to 16 April 2027

  • Review led by

    For example: Lucia Romero

  • Date of the review

    For example: 30 April 2027

  • Who took part

    For example: Lucia Romero, Jin Park, Priya Nair, Henrik Larsen, Mei Chen

  • What we set out to do

    For example: Launch the portal with online payments by 5 April, for EUR 90,000.

  • What happened

    For example: Launched on 16 April, 11 days late, at EUR 96,500. Online payments work and 40 percent of clients use them in the first 2 weeks.

  • What went well

    For example: Daily short meetings kept everyone informed The test team found problems early Clients joined the demos and gave useful feedback

  • What did not go well

    For example: The payment test system was slow and unreliable Changes were agreed by chat and not written down Help texts were written too late

  • Why it happened (root causes)

    For example: We did not test the bank connection before we planned the work. There was no clear way to approve changes.

  • Lessons

    For example: Test every outside connection in the first month. All changes go through a written change request.

  • Actions

    Each with an owner and a date.

    For example: Add a connection test to the project checklist: Lucia Romero, 14 May Write the change process: Priya Nair, 21 May

  • Who will receive this report (optional)optional

    For example: All project managers, the management team

Plans and reports

What is inside

The parts of this document, in order.

  1. 11. What we set out to do
  2. 22. What happened
  3. 33. What went well
  4. 44. What did not go well
  5. 55. Why it happened
  6. 66. Lessons
  7. 77. Actions

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

Plans and reports

Questions people ask

What details does this template ask for?

The form asks for 13 details, starting with Project or event, Dates, Review led by, Date of the review, Who took part. 1 more are optional.

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 planning 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.

How long should a business plan be?

As short as it can be while it says what you sell, to whom, how you earn money and what you need. Ten pages is plenty for most small businesses.

Will a plan get me funding?

It cannot promise that. A clear plan helps a bank or an investor understand you, and they decide by their own rules.