What this is
What is a lessons learned record?
What is a lessons learned record?
It is the structured capture of what an incident, investigation, audit or project revealed, written so that a team who had nothing to do with the original event can still act on it. It exists separately from the source record because an investigation report is written for the people closest to the event, not for the site as a whole.
How is a lesson different from a corrective action?
A corrective action closes a specific gap on a specific record — it fixes the thing that went wrong. A lesson generalises beyond that: it asks whether the same weakness exists anywhere else the same conditions apply, and pushes the answer out as a briefing, a procedure change or a training update, whether or not any other area has had an incident yet.
Why does a lesson need checking again six months later?
Because sharing a lesson and a lesson actually changing behaviour are different things. A toolbox talk delivered once fades; a procedure quietly reverts once the person who changed it moves on. The six-month check exists to catch the gap between 'we told people' and 'the change is still in place'.
Scope
When is a lessons learned record required?
This engine is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use this template when
- An investigation, audit, project or drill has just closed and something in it is worth acting on elsewhere
- The finding could plausibly recur in an area, shift or site other than the one it happened in
- The detail is still fresh enough to write accurately — this is not for reconstructing an event from memory months later
- You are running the Incident and Investigation programme and this is one of its closing steps
- A linked record needs this one to exist: links RCA, project closure, incidents
Do not use it for
- Root Cause Analysis, which finds out why the original event happened rather than what to do about it elsewhere.
- Corrective and Preventive Action, which is the single action record used everywhere, not the vehicle for sharing a generalised lesson.
- Improvement Suggestion Record, which captures a new idea volunteered by someone, not a lesson extracted from a closed event.
- Effectiveness Verification, which checks whether a specific corrective action worked, not whether a shared lesson is still being followed.
- Anything outside General, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.10.3 requirements does this satisfy?
The form maps onto ISO 45001 cl.10.3's expectation that organisations identify opportunities for improvement from incidents and nonconformities, then act on them beyond the immediate area affected.
| Clause | Requirement | Where it lands |
|---|---|---|
| cl.10.3 — improvement | The source event is named and linked, so the lesson can be traced back to its origin | Header |
| cl.10.3 — lessons from incidents | What happened, what was learned, and what should change are captured as distinct statements | The lesson |
| cl.7.4 — communication | Whether the lesson applies beyond the originating area or site is explicitly assessed, not assumed | The lesson |
| cl.7.4 — communication | The lesson is shared through a method capable of changing behaviour, not just distributed | Sharing |
| cl.7.2 — competence | Where relevant, training content is updated to reflect the lesson rather than left to individual awareness | Sharing |
| cl.9.1 — monitoring | The record is checked again after a defined interval to confirm the change is still in place | Did it stick |
| cl.10.3 — continual improvement | A similar event since the lesson was shared is captured and routed to action if it occurs | Did it stick |
What it does not cover
- Method Of Sharing, recorded as 'Email only' with 'Shared With Affected Teams' marked 'Yes' regardless of whether anyone read it.
- Applies Beyond This Area, marked 'Yes' with no areas actually named in 'Areas It Applies To'.
- Checked Six Months Later, left at 'Scheduled' long after the six-month mark has passed with no follow-up date reset.
- Change Still In Place, unanswered or skipped on a record that was otherwise closed as complete.
- Similar Event Since, answered 'Yes' with no action record raised or CAPA ID linked to it.
Global
Lessons Learned Record requirements by country
ISO 45001 sets the improvement expectation internationally, but how hard a lessons-learned failure is enforced depends on the sector and, in a few places, on statute rather than a management-system standard.
OSHA Process Safety Management (29 CFR 1910.119)
Incident investigation findings must be resolved and the resolution documented, and PSM audits routinely check whether findings were communicated to affected operating areas, not just closed on paper.
A lesson from a process safety incident that never reaches the other shifts or units running the same process is a documented audit gap, not a minor communication miss.
ISO 45001:2018
Cl.10.3 requires organisations to determine and implement action needed, including reviewing worker participation and updates to the OH&S management system arising from incidents.
A certification audit can and does sample closed incidents specifically to check whether the resulting lesson changed anything beyond the immediate corrective action.
ICAO Annex 13 / sector safety management systems
Safety management systems in aviation and comparable high-hazard sectors formalise lessons-learned as a distinct SMS process, often with mandated cross-fleet or cross-site distribution.
In these sectors a lesson confined to one site or one crew, when the same equipment or procedure is used elsewhere, is itself treated as an SMS deficiency.
How to complete it
How to complete a lessons learned record, step by step
Filling in what happened is usually the easy part. The judgement calls are what decide whether the lesson actually travels.
The honest test is whether the same conditions — equipment, procedure, shift pattern, contractor — exist anywhere else, not whether the exact event could recur identically. Marking 'No' because 'it hasn't happened there' undercuts the entire purpose of the record.
A toolbox talk or procedure change forces the lesson into a moment people are already paying attention, or into a document people are already required to follow. An email relies entirely on the reader choosing to engage, which is exactly the behaviour the original event already showed cannot be relied on.
Not every lesson needs a rewritten procedure. But if the failure mode is one a briefing alone will not prevent next time a new person joins the team, the lesson needs to be built into training content, not left as something everyone was 'told once'.
High-turnover roles, contractor-heavy sites and shift patterns with long gaps between the same task recurring can all mean six months is too slow to catch drift. The interval on the form is a default, not a ceiling — some lessons need checking sooner.
What auditors find
Most common lessons learned record findings
The patterns below are the ones that keep surfacing when lessons-learned registers get audited, and each one traces back to a specific weak field.
| Finding | Clause | What fixes it |
|---|---|---|
| Lessons written weeks after closure, once memory of the specifics has already faded | cl.10.3 timeliness of improvement action | Trigger the record automatically at investigation or project closure rather than leaving it to be raised manually later. |
| 'Applies Beyond This Area' marked 'Yes' with no areas actually named | cl.7.4 communication scope | Make 'Areas It Applies To' mandatory whenever 'Applies Beyond This Area' is 'Yes', pulling from the site's own area list. |
| Sharing recorded as complete on the strength of an email send | cl.7.4 effectiveness of communication | Exclude 'Email only' from counting toward 'Shared With Affected Teams' equalling 'Yes' in reporting. |
| Six-month checks left permanently at 'Scheduled' | cl.9.1 monitoring of improvement actions | Auto-flag any record where the six-month date has passed and 'Checked Six Months Later' is still 'Scheduled'. |
| Similar events recur with no link back to the earlier lesson | cl.10.3 continual improvement | Require a CAPA ID whenever 'Similar Event Since' is answered 'Yes', and surface the original lesson alongside the new event for the investigator. |
| Training content referenced as updated with no course or module actually identified | cl.7.2 competence | Link 'Training Content Updated' to the specific course record it changed, rather than accepting a bare 'Yes'. |
Case in point
Case in point: the lesson that was true everywhere except where it was written down
A near miss on one production line traced back to a guard interlock that could be defeated with a single tool, a design flaw shared across every line of that machine type on site. The investigation was thorough, the lesson record was written the same week, and 'Applies Beyond This Area' was correctly marked 'Yes' with all four lines named.
Sharing was logged as a toolbox talk on the originating line only — the other three lines were named in the record but never actually briefed, because the toolbox talk had been delivered to the shift that reported the near miss, not the shifts running the other machines. Eight months later a second near miss happened on a different line, with an operator who had never heard of the first one. The record showed the lesson as 'shared'; the field that would have caught the gap — confirming which teams actually received the briefing, not just that one was delivered — was never asked.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- FDN-031
- Archetype
- Engine
- Record ID
- LL-2026-000
- Scoring
- Lessons shared
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.10.3
- Links
- Links RCA, Project closure, Incidents
- Tags
- Engine, Learning
- Sections
- 4
- Fields
- 33
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 2
Header
10 fieldsRecord ID*
Auto sequence. Format LL-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Written While It Is Fresh
The value of a lesson decays fast. Capture it at closure, in a form somebody in another area can actually use, or it stays inside one investigation report.
Source Type*
Source Record ID*
Immediate predecessor record
Captured By*
The lesson
6 fieldsWhat Happened*
What We Learned*
What Should Change*
Applies Beyond This Area*
- Yes3 pts
- No1 pt
Areas It Applies To
Applies To Other Sites*
- Yes3 pts
- No1 pt
Sharing
6 fieldsShared With Affected Teams*
- Yes3 pts
- Partly1 pt
- No0 pts
Method Of Sharing*
Toolbox talk, briefing, procedure change or training update. An email nobody opens is not sharing.
- Toolbox talk4 pts
- Briefing3 pts
- Procedure change4 pts
- Training update4 pts
- Email only0 pts
Turned Into A Toolbox Talk*
- Yes3 pts
- No1 pt
Procedure Or Standard Changed*
- Yes3 pts
- Not needed2 pts
- No0 pts
Training Content Updated*
- Yes3 pts
- Partly1 pt
- No0 pts
Design Standard Updated
- Yes3 pts
- Not applicable3 pts
- No0 pts
Did it stick
11 fieldsChecked Six Months Later*
- Yes3 pts
- Scheduled1 pt
- No0 pts
Change Still In Place
- Yes3 pts
- Partly1 pt
- No0 pts
Similar Event Since*
- No3 pts
- Yes0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Captured By*
Signature*
Area Owner*
Second Signature*
FDN-031 · record IDs look like LL-2026-000 · Links RCA, Project closure, Incidents
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Writing the lesson is the easy part. Chasing whether it actually reached every affected area, and whether the change survived past the first few weeks, is the work that actually slips.
Tracks every open lesson against its six-month check date, flags any still at 'Scheduled' once that date passes, and holds any write back to the record for your approval.
Cross-checks a lesson's named areas against actual toolbox talk attendance, so 'shared' means the affected shifts were actually in the room.
Links a lesson's training update directly to the course record it changed, and confirms the updated content has actually been delivered, not just scheduled.
Watches for a second incident against a lesson already marked shared, and surfaces the earlier record alongside the new one so the gap is visible immediately.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Glossary
Lessons Learned Record definitions and key terms
- Lessons learned
- A generalised statement of what an event revealed and what should change, written so a team outside the original event can act on it without reading the source investigation.
- Source record
- The incident, investigation, audit, project or drill the lesson was extracted from, linked by ID rather than duplicated into the lesson itself.
- Effective sharing
- Distribution of a lesson through a method capable of changing behaviour — a toolbox talk, briefing, procedure change or training update — as distinct from simply sending information.
- Applies beyond this area
- The judgement of whether the conditions behind an event exist anywhere else on site or across sites, independent of whether an incident has occurred there yet.
- Stick check
- A follow-up review, typically at six months, confirming that a shared lesson's resulting change is still in place and no similar event has occurred since.
FAQ
Frequently asked questions about lessons learned record
Who is responsible for writing the lessons learned record?+
Whoever ran the source work — the investigator, project lead or audit owner — because they hold the detail while it is still fresh. Ownership does not transfer to the areas the lesson gets shared with; they receive the lesson, they do not author it.
Does every incident need a separate lessons learned record?+
No. It is reserved for findings judged to have value beyond the immediate corrective action on the source record. A minor, fully local issue with no wider applicability can be closed through its corrective action alone without a separate lesson.
What counts as proof that a lesson was actually shared?+
The method matters more than the fact of sending something. A toolbox talk, briefing, procedure change or training update all count; an email with no evidence anyone engaged with it does not, and the form's own scoring reflects that directly.
What happens if the six-month check finds the change did not stick?+
'Change Still In Place' is marked 'No' or 'Partly', and the record should route to an action rather than simply being noted and closed — the same 'Action Required' field used elsewhere on the form applies here.
Can a lessons learned record trigger a procedure change on its own?+
Yes, and it is meant to. 'Procedure Or Standard Changed' and 'Design Standard Updated' exist precisely so a lesson can result in a document control action, not just a verbal briefing that fades with staff turnover.
How is this different from a toolbox talk record?+
A toolbox talk is one delivery method the lesson can use to reach a team; the lessons learned record is the source document that decides what needs saying, to whom, and checks later whether it actually changed anything.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Incident and Investigation
A single case thread from the event to a verified corrective action, with regulatory reporting handled.
Master Data and Foundations
One place for each thing, so a change updates everywhere rather than in eight lists.
Continuous Improvement
Improvements with a measured baseline, and ideas that always get an answer.
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Engines
Risk Assessment
The single risk assessment used across the whole business
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 — cl.10.3 Continual improvement
- ISO 45001:2018 — cl.7.4 Communication
- OSHA Process Safety Management, 29 CFR 1910.119(m) — Incident investigation
- ICAO Annex 13 — Aircraft Accident and Incident Investigation
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.