For consultants closing out a client project
Lessons Learned Template and Example
Three documents and one sheet: the lessons record, a 60-minute session guide that keeps blame out, a worked client example and a lessons register.
Went well, and why
- Depot leads designed the processNorthfield ran it from day one. Keep: invite the people who will run it.
- Change requests within 3 daysBoth approved within 3 business days. Keep: written options, every time.
Didn't go well, and why
- Data arrived 3 days lateThe export needed IT. Next time: name who runs it at kickoff. Owner: Leo.
- The holidays split the pilotWeek 1 fell in peak. Next time: check the calendar first. Owner: Sam.
What you'll get
Lessons with evidence and owners, a session guide, a register and an example
- What went well and what didn't, each with its evidence
- Every lesson as a next-time action with one owner
- A 60-minute session guide that keeps blame out
Before and after
Your retro notes in. Lessons with owners out.
Retro notes, Larkfield project. Data came 3 days late, the export needed IT. Depot leads in all 3 design sessions, pilot smooth from day 1. Holiday split the pilot, week 1 in peak. Drivers mentioned routes in November, client only asked in January.
3. What didn't go well, and why. The data arrived three days late. Why: the export needed IT access. The routes question reached the client in January. Why: [why]. 4. Lessons and actions. L-01 · Name the person who can run each data export at kickoff. Owner: [owner]. L-02 · Put the people who will run a new process in the design sessions. Owner: [owner]. L-04 · Tell the sponsor the same week when interviews raise something outside scope. Owner: [owner].
Causes your notes don't give, and every owner and date, stay in brackets for the team to settle.
Why it works
What goes in a lessons learned template?
A lessons learned template records what a project set out to do, what went well and what didn't, why, and what to do differently next time. The UK government's project delivery guidance on lessons asks each lesson to record what happened, its impact, what was learned and the action taken, with a named owner. This template follows that shape. It gives what went well the same space as what didn't, because the same guidance says understanding success matters just as much.
Most lessons logs fail in two ways. The lessons are vague, like "communicate better", and they're filed where nobody looks again. Here, each lesson is a specific action for next time, with evidence, an owner and a date. It goes into the lessons register sheet and into the document it changes, such as your proposal checklist. The session guide spends 60 minutes on the four questions of an after action review, which Wharton describes as a US Army practice for learning from mistakes and achievements alike.
The worked example closes the invented project from our statement of work template, including two change requests along the way. Download it as Word and CSV with no account, or open it in River and paste your retro notes. River sorts them into what went well and what didn't, turns each into a next-time action, and brackets owners your notes don't name. The project closure report template carries the headline lessons into the client's record, and the change order template handles requests like those two.
What lands in your doc
What's inside the lessons learned template
- What we set out to do
Objectives from the SOW against what happened, with evidence, plus planned and actual dates, fee and effort. - What went well, and what didn't
Two tables with evidence and causes, so successes get repeated on purpose and problems get fixed at the source. - Lessons as next-time actions
Each one starts "Next time, we will", with the evidence behind it, when it applies, one owner and a date. - The lessons register
A sheet holding every lesson across projects, tagged by when it applies, to check before the next proposal or kickoff. - A 60-minute session guide
A pre-read, ground rules, a timed agenda and phrases that keep the conversation on the work, not the person. - An annotated client example
A finished record for an invented consulting project, with six lessons and a note on why each section works.
How it works
From retro notes to lessons that get used
Open the template
Click Edit with AI. The template, session guide, example and lessons register open in River.
Paste your retro notes
Optional. Paste notes from your session or a project summary, and River drafts the record and the lessons.
Check causes and owners
Confirm each cause, then fill in the evidence, owners and dates River left in brackets.
File every lesson
Each owner builds their lesson into a checklist or template, and the register is ready for the next kickoff.
Questions consultants ask
Common questions
What is a lessons learned template?
A lessons learned template is a structured record of what a project taught the team: what was planned, what happened, what went well and what didn't, and why. Its real output is a short list of actions for next time, each with an owner and a place where it gets built in.
When should you hold a lessons learned session?
Within two weeks of the last deliverable, while people remember the details and before the team moves on. The UK government's guidance also says lessons should be captured throughout the work, not just at the end. On a long project, hold a short session at the end of each phase and a full one at close.
Should the client join the session?
Often, yes, because the client saw things your team didn't. If trust is low or the project went badly, run two sessions: one for your team and one with the client. Agree beforehand what gets shared, and keep commercial lessons, such as pricing and staffing, in your internal register.
How do you keep blame out of a lessons learned session?
Set the rule at the start: talk about what happened and why, not who. Google's postmortem guidance starts from the assumption that everyone "had good intentions and did the right thing with the information they had". Ask what made a choice sensible at the time, start with what went well, and let senior people speak last.
What makes a good lesson learned?
One that changes what someone does next time. "Communicate better" isn't a lesson. "Next time, we will name the person who can run each data export at kickoff" is. A good lesson names the action, the evidence behind it and when it applies, with one owner who builds it into a checklist or template.
Is a lessons learned report the same as a closure report?
No. A closure report records whether the project met its objectives, what was accepted and who owns what's left, for the client's records. A lessons learned record is for the next project: what to repeat and what to change. The closure report usually carries a short summary of the lessons.
Where should lessons learned be stored?
Somewhere you'll look before the next project starts. This template files every lesson in a register sheet, tagged by when it applies, and builds it into the document it changes, such as your weekly status report template. Filter the register whenever you scope a new project.
Your next step
More for your project
Make the next project go better
Open the template with the session guide and an example beside it, or paste your retro notes for a first pass.