Knowella

Lessons Learned Record

Captures what an event or project taught the organisation, in a form other areas can use. Written at closure while the detail is fresh. Owned by whoever ran the work. The step that turns a single investigation into something the whole site benefits from.

EllaGeneralEngineFDN-031
Completed by
Owned by whoever ran the work
Raised
Automatically, whenever the upstream record it watches cha

Summary

In short

  • A lessons learned record is an engine used in General that captures what an event or project taught the organisation, in a form other areas can use. It is built against ISO 45001 cl.10.3 and forms part of the Incident and Investigation programme.
  • Written at closure while the detail is fresh. Owned by whoever ran the work.
  • The template holds 33 fields across 4 sections.
  • Scoring is lessons shared, where high is good.
  • ISO 45001 is occupational health and safety management systems. The international standard for managing worker health and safety. Certifiable, and the backbone of most of this library.
  • It connects to the rest of the library: links RCA, Project closure, Incidents.

What it is

What it is

What is a lessons learned record?

A lessons learned record is an engine used in General that captures what an event or project taught the organisation, in a form other areas can use. It is built against ISO 45001 cl.10.3 and forms part of the Incident and Investigation programme.

When is a lessons learned record completed?

A lessons learned record is completed automatically, whenever the upstream record it watches changes. Written at closure while the detail is fresh.

When to use it

When to use it, and when not to

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 it for

  • The event or activity this engine covers has occurred, or is about to
  • A new record is needed; each one gets its own ID in the form LL-2026-000
  • You are running the Incident and Investigation programme and this is one of its steps
  • A linked record needs this one to exist: links rca, project closure, incidents

Not for

  • Risk Assessment, which the single risk assessment used across the whole business.
  • Root Cause Analysis, which finds out why something happened rather than who was involved.
  • Corrective and Preventive Action, which the single action record used everywhere.
  • Anything outside General, which belongs in the workspace that owns that process

Standards

What it is built against

ISO 45001Occupational health and safety management systems

The international standard for managing worker health and safety. Certifiable, and the backbone of most of this library.

ISOInternational Organization for Standardization

A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.

FAQ

Frequently asked questions

What is the lessons learned record template based on?+

It is built against ISO 45001 cl.10.3. ISO 45001 is occupational health and safety management systems. The international standard for managing worker health and safety. Certifiable, and the backbone of most of this library. ISO is international Organization for Standardization. A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.

What sections does the lessons learned record contain?+

There are 4 sections: header, the lesson, sharing, did it stick. Together they hold 33 fields, 26 of which are required.

How often is a lessons learned record raised?+

A new record is raised automatically, whenever the upstream record it watches changes. Each one is given an ID in the form LL-2026-000, so it can be traced and referenced from other records.

Which programme does the lessons learned record belong to?+

It is part of Incident and Investigation, Master Data and Foundations, Continuous Improvement. A single case thread from the event to a verified corrective action, with regulatory reporting handled.

How is a lessons learned record scored?+

Scoring is lessons shared. High is good. Scores exist to make the form tell you something, not to produce a percentage for its own sake.

Can the lessons learned record template be changed?+

Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.

The agents

What the agents do with it

The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.

Ella

Holds the lessons learned record library against your registers, routes each record to its owner, and keeps the evidence trail together.

Ella

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.

This template lives in Generalcontrol tower. The orchestration layer. Registries and engines every other workspace reads from.

Meet General

Sources

Sources

  • ISO 45001 — Occupational health and safety management systems
  • ISO — International Organization for Standardization

General

Also in Engines

6Browse the whole library
EllaAssessment

Risk Assessment

The single risk assessment used across the whole business. Choose a method to suit the work, from a simple matrix through to FMEA, LOPA, bowtie or exposure assessment. Completed by a trained assessor with the people who do the task. Produces a score that can be compared with any other risk in the organisation.

EllaRecord

Root Cause Analysis

Finds out why something happened rather than who was involved. Opened after any incident, failure or nonconformance where the potential loss justifies it. Led by a trained investigator with a team drawn from the areas involved. Produces coded causes and feeds actions that address the real weakness.

EllaAction

Corrective and Preventive Action

The single action record used everywhere. Captures what will be done, who owns it, when it is due and how you will know it worked. Raised from any incident, finding, audit or assessment. Completed by the action owner and checked later by someone independent.

EllaRecord

Finding

Records a single deficiency picked up during an audit, inspection or check. Raised whenever an item fails a check. Completed by the person carrying out the check. Each finding carries its own severity and links to the action that closes it, so nothing is lost in a long report.

EllaRecord

Effectiveness Verification

Checks whether an action actually worked, some time after it was put in place. Scheduled 30 to 180 days after the action is completed. Carried out by someone other than the action owner. If the check fails, the action reopens and a fresh investigation is triggered.

EllaRecord

Just Culture Determination

Separates a system problem from a genuine choice to take a risk, using a consistent set of questions. Completed during any investigation involving a person's actions. Carried out by a manager with HR input. Protects workers from unfair blame and keeps people willing to report.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.