For consultants closing out a client project
Lessons Learned Template and Example
Turn what a client project taught you into actions with owners: a lessons learned record, a 60-minute session guide, a worked example and a register.
Part by part
What goes in a lessons learned template
Fill in the parts in order, because each one feeds the next: agree what happened before you discuss why, and agree why before you write the lesson.
| Part | What to write | The mistake to avoid |
|---|---|---|
| What we set out to do | Each objective word for word from the statement of work, what happened and the evidence. Then planned and actual dates, fee and effort, and why they differ. | Working from memory. Without agreed facts, the session argues about what happened instead of why. |
| What went well, and why | Two to five successes, each with a figure, date, document or quote, and the reason it worked. | Praise with no cause. "The team was great" may be true, but nobody can repeat it on purpose. |
| What didn't go well, and why | Two to five problems, each with its effect on time, cost, quality or the client, and a cause in how the work was set up. | Blaming a person. Ask what made their choice sensible at the time, and keep asking why, as in a 5 whys analysis. |
| Lessons and actions | One lesson per item, starting "Next time, we will", with its evidence, when it applies, one owner and a date. | Observations such as "communicate better". If someone on another project couldn't act on it, rewrite it. |
| Where each lesson is filed | The checklist, template or agenda each lesson changes, a done-by date, and a status: Open or Built in. | Leaving it in the record. A lesson changes the next project only once it's built into something people use. |
| Lessons register | Every lesson from every project, tagged by when it applies, such as proposals, kickoff, workshops or reporting. | Deleting lessons once they're closed. Keep them, and filter the register before each proposal or kickoff. |
The record follows the UK government's guidance on learning from experience3. It asks each lesson to cover what happened, its impact, what was learned and the action taken, and says to keep closed lessons on the register. Checked October 29, 2026.
How it works
How do you run a lessons learned session?
Run the session as an after action review, which Wharton Executive Education traces to the US Army in the 1970s1. It asks four questions: what did we set out to do, what happened, why, and what will we do next time? It pays off: a 2013 meta-analysis of 46 samples2 found that debriefs like this improved effectiveness by about 25% on average. Invite four to eight people who did the work, and a facilitator who wasn't on the project.
Agree the facts before anyone explains them: planned and actual dates, fee and effort, approved change orders and accepted deliverables. Then give what went well as much time as what didn't. The UK government's guidance on learning from experience3 calls understanding success "equally important, if not more so." When a cause points at a person, ask what made their choice sensible at the time. Google's blameless postmortems4 assume everyone did the right thing with the information they had, because people who fear punishment stop raising problems.
Write each lesson as a next-time action with one owner and a date, and send the write-up to everyone who took part within two days. Each owner then builds their lesson into a document people already use, such as your weekly status report. Don't rely on a database alone. In a 2012 audit of NASA's lessons database5, the agency's Inspector General found that only 16 of the 28 project managers it surveyed said they had used it.
How it works
From retro notes to lessons that get used
Download it or open it in River
Download the three Word documents and the register sheet free, or paste your retro notes above and click Edit with AI.
River writes a first pass
With notes pasted, River sorts each point into what went well or didn't, and writes a next-time lesson for each.
Settle causes and owners
Missing evidence, causes, owners and dates stay in brackets. Settle them with the team, or let River walk you through each lesson.
Build each lesson in
Each owner adds their lesson to the checklist or template it changes. Check the register before your next proposal or kickoff.
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. Next-time lessons 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 raised routes in interviews in November, out of scope. 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. Drivers raised routes in November, but the client asked only 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.
What lands in your doc
What's inside the lessons learned template
- Lessons Learned Template
Five sections, from objectives to where each lesson is filed, with guidance in each and a final checklist. - Lessons Learned Session Guide
A 60-minute agenda built on the after action review, with a pre-read, ground rules and a 30-minute version. - Example Lessons Learned, Annotated
A finished record for an invented consulting project, with six lessons and a note on why each part works. - Lessons Register sheet
One row per lesson, with its evidence, owner, where it's built in and status, starting with the example's six. - Phrases that keep blame out
Five swaps, such as "Where did the handoff break, and why?" in place of "Who dropped the ball?" - Three tests for every lesson
Could someone on another project act on it? Does it say what to do? Does it have one owner?
Questions consultants ask
Common questions
What is a lessons learned template?
A lessons learned template is a form for recording what a project taught the team: what it set out to do, what happened, what worked, what didn't, and why. Its real output is a short list of actions for next time, each with one owner. A project closure report records the project for the client; this record is for your next one.
What questions should you ask in a lessons learned session?
Work through the four after action review questions: what did we intend, what actually happened, why were they different, and what will we do next time? Then look for causes, not culprits. Ask "What made that work? Could we do it again on purpose?" and "What made that the sensible call at the time?" End by asking who will build each lesson in.
What are good examples of lessons learned?
A good lesson is an action someone on another project could take. For example: "Name the person who can run each data export at kickoff, and test one export in week 1." Or: "Put the people who will run a new process in the design sessions, not only their managers." "Communicate better" isn't a lesson. Each needs evidence, one owner and a date.
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. Don't save every lesson for the end, though. The UK government's guidance says learning should happen throughout the work. On a long project, hold a 30-minute session at the end of each phase and a full one at close.
Should the client join the session?
Often, yes: the client saw things your team didn't. If trust is low or the project went badly, run two sessions, one internal and one with the client. With the client there, name your own side's misses first, which makes it easier for them to name theirs. Keep commercial lessons, such as pricing and staffing, in your internal register.
Is this lessons learned template free?
Yes. Download the three Word documents and the Lessons Register sheet as a CSV, with no signup. The register comes filled with the example's six lessons, so you can see how it works before you clear it. Edit with AI opens the same files in River, which is free to start. Paid plans add more AI use and access to the most advanced models.
What does Edit with AI do?
It opens all four files in a free River workspace. With your retro notes pasted, River writes a first pass into the template and register, using only facts from your notes. Missing evidence, causes, owners and dates stay in brackets, and a To confirm list names what each lesson still needs. Without notes, River offers to clear the example rows or draft your session pre-read.
Your next step