Core Revision
Skip to content
For trainees · All years
Learning Event Analysis
A structured look at an event that could have gone better — or that went well because a system worked.
When, and how many
One per training year.
Choosing a case that will go well
- It does not have to be a disaster. A near miss, a delayed result, a communication breakdown all work well.
- System problems make stronger entries than individual errors, because the learning generalises.
- Something you were genuinely involved in. Analysing someone else’s event at a distance reads thinly.
What good looks like
- You separate what happened from why it happened.
- The changes you identify are specific and within somebody’s power to make.
- You say what happened to the change afterwards.
What commonly trips people up
- Writing it as a confession. The point is the system and the learning, not blame.
- Choosing an event so trivial there is nothing to analyse.
- No follow-through — an action agreed and never revisited.
Work out what you still need
The Evidence Tracker turns your training year and current post into the list that is actually outstanding.
Open the Evidence Tracker