Free Lessons Learned Template
A lessons learned review run as a small project of its own: gather the facts and the views, hold one workshop, write each lesson as a change with an owner, and check three weeks later that the change was made. Thirteen tasks and five milestones, ready to schedule from the day your project closes.
No credit card. Opens as a real project on the Free plan.
The spreadsheet is a 13-task plan with phases, durations and milestones, ready for Excel or Google Sheets. It carries no dates, so set your own start, or paste it into the Gantt chart generator to have the schedule built for you. Want to compare the plans side by side first? Every one of them is on the project plan template page, with the rows shown before you download.
The Microsoft Project file (.xml) is the same plan with its dates worked out: every task is scheduled from Monday 4 January 2027. Open it in Microsoft Project, or open it free in Onplana Schedule, the desktop app that edits Project files without Microsoft Project.
What’s inside
All 13 tasks are below, in four phases, each with its description, duration and priority. Most of the work comes before the workshop, so the meeting itself is short and ends in decisions.
13
Scheduled tasks
4
Phases
5
Milestones
~3
Weeks end to end
Lessons that change the next project, not a report nobody opens
Most lessons learned documents are written once, filed and never read again. The review itself is rarely the problem. The problem is what comes out of it: a list of observations such as "communication could have been better", with nobody responsible for doing anything about them. This template is built around the opposite end of the process. Every lesson leaves the review as a recommendation that names the practice it changes, with one owner and one date.
The first week gathers material before anyone meets. The project record (planned against actual dates, the budget, the changes, the risks and issues) gives the review facts to argue from, and a three-question survey collects views in writing from people who will not speak up in a group. A few short interviews cover the sponsor, suppliers and anyone junior, which is usually where the hardest lessons are. The answers are grouped into themes before the workshop, so the ninety minutes go on causes and fixes rather than on remembering what happened.
The last phase is the one most reviews skip. The lessons are put where the next team will meet them, in the kickoff pack, the checklist or the template they start from, and the next project team gets a short briefing. The final task checks that each action was taken. Run the review within two weeks of the project closing, or at the end of each major phase on a long project, while people still remember why they made the choices they made.
The plan, phase by phase
Prepare4 tasks
Set the purpose and scope of the review
Which project or phase is reviewed, which future decisions the lessons should feed, and who will act on them.
Collect the project record
Planned against actual dates, the budget, the change requests, and the risks and issues raised, so the review starts from facts.
Choose who takes part
The team, the sponsor and at least one person who received the result, invited while the project is still fresh.
Send a three-question survey
What went well, what went badly and what you would do differently, answered in writing before anyone meets.
Gather3 tasks
Interview the people a group will not hear
Short one-to-one talks with the sponsor, suppliers and junior team members, where the hardest lessons usually are.
Group the answers into themes
Five to eight themes, each with the facts behind it from the project record, sent round before the workshop.
Run the lessons learned workshop
Ninety minutes on the themes: what happened, why, and what to do next time. Blame stays out, and the facilitator is not from the project.
Decide3 tasks
Write each lesson as a recommendation
Not "communication was poor" but "agree a weekly update day at kickoff". Each lesson names the practice it changes.
Give every action an owner and a date
A lesson with no owner is a note. One name and one date per recommendation, agreed with that person.
Sign off the lessons with the sponsor
The sponsor agrees the recommendations and the owners, and decides which ones change the standard way of working.
Share and Act3 tasks
Put the lessons where the next project starts
In the kickoff pack, checklist or template the next team opens, not only in a report on a shared drive.
Brief the next project team
Fifteen minutes with the people starting similar work: the three lessons that matter most to them.
Check the actions were taken
Each owner reports done or not done. Book this for a few weeks after sign-off, and move the date if you need to.
Milestones
Five milestones: the survey closed, the workshop held, the lessons signed off by the sponsor, the lessons shared with the next team and the actions checked. The last one is the reason the review was worth holding.
Survey closed
Day 7 of the plan
Workshop held
Day 13 of the plan
Lessons signed off
Day 17 of the plan
Lessons shared
Day 19 of the plan
Actions checked
Day 20 of the plan
Frequently asked
What is in the download?
A CSV file with the 13 tasks of the review, each with its phase, duration in days, priority and notes, and the five milestones as zero-day rows. Excel opens it directly and Google Sheets imports it. It has no dates until you choose a start.
Is this a lessons learned log?
It is the plan for the review that produces the log. Add the lessons themselves as rows under the Decide phase, one row per recommendation with its owner in the notes, and the same file becomes the record. That keeps each lesson next to the task that turns it into an action.
When should a lessons learned review happen?
Within two weeks of the project closing, while people remember why they made their choices. On a project longer than six months, run a short one at the end of each major phase as well, so the later phases benefit from the earlier ones.
Who should run the workshop?
Someone who was not on the project. A facilitator from outside the team can keep the discussion on causes rather than people, and can ask the obvious questions the team has stopped noticing. The project manager takes part as a member, not as the chair.
Start with the plan already built
Open the Lessons Learned template free and your phases, tasks, and milestones are scheduled before the kickoff meeting. No credit card, no time limit.