Lessons Learned and Safety Alerts

Lessons learned capture the knowledge gained from incidents, near misses, and successful practices to prevent future harm.
A safety alert is a communication issued after an incident to warn other projects and teams about a hazard or failure.
The purpose of lessons learned is improvement, not blame — focusing on what can be changed rather than who was at fault.
Lessons must be specific, actionable, and communicated to the people who need them — vague observations change nothing.
Safety alerts should be issued quickly after an incident — delays allow the same conditions to cause another event elsewhere.
Toolbox talks are the most effective method for communicating lessons learned directly to operatives on the front line.
Lessons from one project must be shared across the organisation — the same hazard exists on every similar project.
Industry safety alerts from the HSE, CITB, and client organisations provide lessons from incidents on other companies' sites.
A lessons learned register tracks what was identified, what action was taken, and whether the action prevented recurrence.
Reviewing lessons learned at the start of new projects applies past experience to prevent repeating the same mistakes.

Prevent recurrence	A lesson identified but not communicated allows the exact same incident to happen again on the next project.
Speed matters	A safety alert issued within hours reaches other sites before the same conditions cause another casualty.
Industry learning	The HSE and industry bodies share lessons from incidents across the sector — reading and acting on them protects your site.

Do

Don't

Issue safety alerts promptly after any significant incident or near miss.
Write lessons in specific, actionable language that tells people what to change.
Communicate lessons to the workforce through toolbox talks and team briefings.
Share lessons across all projects in the organisation, not just the affected site.
Read and act on industry safety alerts from the HSE, CITB, and client bodies.
Maintain a lessons learned register tracking issues, actions, and outcomes.
Review relevant lessons learned at the start of every new project.
Include lessons from successful practices, not only from incidents and failures.
Follow up to confirm that actions taken from lessons are actually preventing recurrence.
Create a culture where sharing lessons is valued as a contribution to everyone's safety.

DON'T delay issuing safety alerts — other sites need the warning now, not next week.
DON'T write vague lessons — be specific about what happened and what must change.
DON'T keep lessons in management reports — communicate them to the front line.
DON'T limit lessons to the affected project — share them across the entire organisation.
DON'T ignore industry safety alerts — other companies' incidents can happen on your site.
DON'T let the lessons learned register become a filing cabinet — track actions and results.
DON'T start new projects without reviewing lessons from previous similar work.
DON'T only learn from failures — capture what went well and share good practices.
DON'T assume issuing a lesson means it was effective — check if it changed behaviour.
DON'T treat lessons learned as a blame exercise — focus on what can be improved.

See also: Near Miss Reporting and Learning | Incident Investigation Process

Presenter		Project
Location		Date

Toolbox Talk Record