A significant event analysis is a structured reflection on a single event in patient care: what happened, why, what you learned and what changed. For the Portfolio Pathway it is one of the GMC's six supporting information types, and it doubles as revalidation evidence. Most senior doctors already do the underlying work at M&M meetings, incident reviews and after action reviews; the portfolio task is to write it up in a form an assessor can credit. The marks are won in the last two stages: the specific change you made, and the evidence it held.
What a significant event analysis actually is
A significant event analysis (SEA) is a structured, written reflection on a single event in patient care: what happened, why it happened, what you learned, and what changed as a result. It is one of the six types of supporting information the General Medical Council (GMC) expects for revalidation, and it does double duty as Portfolio Pathway evidence. The other five are continuing professional development, quality improvement activity, patient feedback, colleague feedback, and a review of compliments and complaints.
The word "significant" trips people up. It does not mean a catastrophe, an inquest, or a referral. It means an event significant enough to be worth analysing, which is often a near miss, a delay, a communication breakdown, or a case that went well against the odds and is worth understanding. The analysis is the point, not the drama. A small event examined honestly is worth more than a serious incident described defensively.
If you are a senior NHS doctor, you almost certainly do the underlying work already. Mortality and morbidity (M&M) meetings, Datix or Learn from Patient Safety Events (LFPSE) reports, after action reviews, complaint responses, structured judgement reviews: these are significant event analysis under different names. The Portfolio Pathway task is rarely to generate new events. It is to write up the ones you have reviewed in a form an assessor can read and credit. For the wider picture of how the evidence types fit together, the complete guide to the Portfolio Pathway sets out the full framework.
SEA vs audit vs quality improvement
Assessors see these three muddled together constantly, and the muddle costs marks. They are not interchangeable. Each answers a different question, and a strong portfolio shows you understand the difference rather than filing everything under "governance".
- Unit of analysis: a single event
- Looks backward, then forward
- Qualitative: insight and learning
- Output: a change and proof it held
- Unit of analysis: a population
- Measures against an explicit standard
- Quantitative: before and after data
- Output: a closed loop, re-measured
- Unit of analysis: a process over time
- Tests changes in repeated cycles
- Iterative: PDSA, run charts
- Output: sustained measurable change
The cleanest way to hold them apart: audit asks whether a population meets a standard, quality improvement asks how to move a process reliably, and SEA asks what one event teaches you. They overlap in practice. A significant event often triggers an audit, which then feeds a quality improvement project. But for the portfolio, label each piece for what it is. An assessor who sees a single case described as an "audit" reads it as a category error, and category errors raise doubt about everything else in the file.
The GMC harm threshold
The GMC defines a significant event as any unintended or unexpected event that could have led, or did lead, to harm of one or more patients. The phrase "could have led" is doing real work. A near miss that was caught before it reached the patient meets the definition. So does a preventable event with no lasting harm. You do not need an adverse outcome to have a significant event worth analysing.
This matters because senior doctors routinely under-claim. The instinct is to reserve "significant event" for the case that went to coroner or claim, and to treat everything else as routine practice not worth writing up. That instinct loses you the best material. The near miss is often the most useful event to analyse precisely because the learning arrives without the harm, which means you can be honest about the contributory factors without the conversation becoming about blame or defence.
A near miss caught at the final check. A delayed diagnosis where the system, not a single decision, caused the delay. A handover failure that nearly led to a missed dose. A complaint that changed how you consent. A resuscitation that went unusually well and is worth understanding so it can be repeated. All of these meet the threshold and all of them produce stronger reflection than a defensive write-up of a serious incident.
The GMC also asks you to declare significant events honestly, including a nil return. If you genuinely have had no events meeting the threshold in the period, you say so and reflect on your local reporting culture and how you would recognise an event if it occurred. A thoughtful nil return is acceptable. What does not survive review is a nil return that reads as though you have simply not looked.
You already have the raw material
Most senior doctors arrive at the SEA section convinced they have nothing to write about, then realise within ten minutes that they have too much. The activity you already do at work converts directly into portfolio evidence. The table below maps common hospital activity to the SEA write-up it can become, and flags how much extra work each one needs.
The "ready" rows are the ones to start with. If you presented a case at M&M last month, the hard thinking is done; the portfolio task is to capture it in the SEA structure before the detail fades. The "reconstruct" row is legitimate but needs care: be honest that you are writing retrospectively, and never invent contemporaneous documentation that did not exist. Assessors prefer an honest reconstruction to a polished account that does not ring true.
The anatomy of a strong SEA
A weak SEA describes an event. A strong SEA analyses one. The difference lives in the last two stages, which most write-ups skip. The seven stages below are the spine. The first five are familiar from any reflective model. The final two, the change you made and the evidence it held, are where assessors separate genuine analysis from a tidy story.
What happened
The event, factually and concisely. Dates, setting, your role, what occurred. Anonymise fully. No interpretation yet, just the account.
Why it happened
The contributory factors, looking past the immediate cause to the system. This is where systems thinking earns its place. Rarely one person, usually several conditions lining up.
The impact
On the patient, on the team, on you. Honest about actual and potential harm, including the near miss that did not reach the patient.
What went well
The defences that worked, the catches that prevented worse. Naming these is not self-congratulation; it tells you which safeguards to protect.
What you learned
Your genuine reflection, in the first person. What you now understand that you did not before, and what it means for your practice specifically.
What changed where marks are won
The specific action taken: a protocol amended, a checklist introduced, a rota changed, a teaching session delivered. Named, dated, attributable. "I will be more careful" is not a change.
How you know it held the differentiator
The evidence the change worked and stuck: a re-audit, a follow-up at the next M&M, a count of incidents since, feedback from the team. This closes the loop and is the single most common thing missing from portfolio SEAs.
If you write only the first five stages, you have a reflective note, which has its place but is not a significant event analysis. Stage six turns reflection into action. Stage seven turns action into evidence. When an assessor reads "I introduced a pre-procedure checklist, and at the following quarter's M&M no further events of this type had been reported", they see a doctor who closes loops. That is the impression the whole exercise exists to create. For the reflective writing underneath stages three to five, the reflective practice writing guide goes deeper on tone and depth.
Systems thinking after PSIRF
If your last formal training on incidents predates 2022, the language has moved on, and the portfolio rewards keeping up. In August 2022 NHS England published the Patient Safety Incident Response Framework (PSIRF), and trusts adopted it through late 2023. PSIRF replaced the 2015 Serious Incident Framework. The category "serious incident", with its thresholds and mandatory root cause analyses, has gone. The vocabulary now is patient safety incidents, patient safety incident investigations (PSIIs), after action reviews, and the national Learn from Patient Safety Events service.
The change is not only terminology. PSIRF is built on the principle that safety comes from understanding systems, not from finding the individual to blame. Its aims are compassionate engagement with those affected, system-based learning, a proportionate response matched to the event, and supportive oversight. For your SEA, this is the frame to write in. Stage two of the anatomy above, why it happened, is where you show it.
The fastest way to weaken an SEA is to land the analysis on a person: "the locum should have checked". Even when an individual made an error, the assessor wants to know why the system let the error reach the patient. Why was a locum covering unsupported? Why did no check catch it? What about the conditions made the error likely? Writing in systems terms is not excuse-making. It is the difference between an analysis that prevents recurrence and one that simply allocates fault.
A practical way to structure stage two is to group contributory factors under headings, an approach NHS Education for Scotland builds into its enhanced SEA model: the task itself, the individual, the team, the working conditions, and the organisation. Walking those five headings forces you past the first obvious cause and surfaces the systemic ones. In a busy acute medicine take, for example, the "conditions" heading often reveals more than the "individual" one. The GMC explicitly recognises that organisations use different labels for these events, so do not worry if your trust calls it a PSII while your appraisal toolkit calls it an SEA. The analysis is what counts.
Mapping to the GMC domains
Portfolio Pathway evidence is assessed against the four domains of Good Medical Practice. A significant event analysis is unusual in how much of the framework a single well-written piece can touch. Most evidence types sit mainly in one domain. A strong SEA reaches across all four, which is part of why assessors value it. The four domains explained guide covers the full mapping logic; here is where a single SEA lands.
Safety and quality
The natural home of the SEA. Recognising risk, contributing to and acting on incident review, and improving systems sits squarely here. This is the domain your SEA evidences most directly.
Knowledge, skills and performance
Your clinical reasoning in the case, the evidence you applied, and the learning you took into future practice all demonstrate maintaining and developing competence.
Communication, partnership and teamwork
How the event was discussed with the team, the multidisciplinary review, and any duty of candour conversation with the patient or family evidence working in partnership.
Maintaining trust
Honesty about what went wrong, acting with candour, and showing you take responsibility for improvement demonstrate the openness that maintains public trust.
You do not need to force every SEA to hit all four. The point is the opposite: when you write one event up properly, the domain coverage falls out of it naturally. Where a candour conversation took place, domain four writes itself. Where the change involved the wider team, domain three is evident. Tag the domains lightly in your write-up rather than contorting the analysis to tick boxes. Assessors notice manufactured coverage.
Good vs weak: the same event
The gap between a weak and a strong SEA is easier to see than to describe. Below is the same event, a missed dose of time-critical medication on a busy ward, written two ways. The facts are identical. The analysis is not.
"What happened?"
A patient missed a dose of their Parkinson's medication overnight. The nurse was busy and the drug was not given on time. I spoke to the nurse and reminded the team about the importance of time-critical medications.
"What changed?"
I will be more vigilant about time-critical medications in future and have asked the nursing team to be more careful.
"Why did it happen?"
The dose was due at 02:00, outside standard drug rounds. The drug was not flagged as time-critical on the chart, agency staff were covering, and the ward had no alert system for off-round timings. Several conditions lined up; no single person failed.
"What changed, and how do I know it held?"
We added a time-critical medication flag to the e-prescribing template and a 7-day check at handover. At the next M&M, two months on, no further missed time-critical doses had been reported on the ward. I shared the change with the directorate governance lead.
The weak version is not dishonest. It is just thin. It locates the cause in a person, proposes a change that cannot be measured, and offers no evidence anything improved. The strong version reads the same event as a systems problem, makes a specific change, and shows the change held. That second feature, the proof it held, is what most senior doctors leave out, and it is the cheapest mark to win because the follow-up usually already exists at your next governance meeting. You simply have to write it down.
How many, and how recent
There is no fixed number of significant event analyses set by the GMC for the Portfolio Pathway, and Royal College Specialty Specific Guidance (SSG) varies by specialty. Quality and recency beat volume every time. Two or three well-analysed events, each showing systems thinking, a specific change, and evidence the change held, outweigh a long list of thin descriptions. Check your specialty SSG for any indicative expectation; the guide to Specialty Specific Guidance explains how to read it.
Recency carries real weight. The Portfolio Pathway, like revalidation, is looking for current engagement with patient safety, so events from the last few years are far more useful than older ones. The practical habit that solves this is simple: write one up whenever a suitable event occurs, rather than reconstructing a back catalogue under deadline pressure. A rolling file of two or three recent SEAs, kept current, is one of the lowest-effort, highest-value evidence streams in the whole portfolio. It also reads as authentic, because it is.
Specialty shapes what counts as a typical event. In intensive care medicine and anaesthetics, the source is often an airway or sedation incident reviewed through morbidity review. In acute medicine, it is frequently a diagnostic delay or a deterioration not escalated in time. The structure is identical across specialties; only the clinical content changes. Build your evidence from the events your specialty actually generates rather than chasing a textbook example.
Download the SEA write-up template
Two-page A4. Page 1 is a significant event analysis template structured around the seven stages above, with prompts for each, including the two most doctors skip. Page 2 is a worked hospital example and a GMC four-domain mapping checklist so you can sense-check coverage before you write the evidence section.
The SEA write-up template
Seven-stage template, a worked hospital example, and a four-domain mapping checklist.
Where this sits in the evidence cluster
Significant event analysis is one of the clinical governance evidence types, alongside audit and quality improvement. Read it next to the cluster below and build them in parallel rather than one at a time.
Some departments run open, supportive incident review where significant events are discussed without blame and learning is shared, which makes this evidence easy to build. Others treat incidents defensively, which makes it hard to gather anything you would want to put your name to. If your current post offers no real route into governance work, that is a structural constraint worth naming, not a personal gap. The pragmatic move is often to look for a Trust where clinical governance is part of how the department operates, then build the evidence trail from inside it.
Official sources used
Frequently asked questions
What is the difference between a significant event analysis and an audit?
They answer different questions. An audit measures current practice against an explicit standard, you make a change, then you re-measure to see whether practice improved: a closed loop with before and after data. A significant event analysis takes a single event, a harm, a near miss or a notable success, and works out what happened, why, and what should change. Audit is about a population and a standard; SEA is about one event and the learning from it. Most strong portfolios include both.
Do I need to have been the doctor involved to write an SEA?
No. The GMC asks you to declare and reflect on significant events in which you were involved or personally named, and that includes events you took part in reviewing, not only events where you were the treating clinician. An analysis of a case discussed at your morbidity and mortality meeting, with your genuine reflection and a clear account of your role and the change agreed, is legitimate evidence. What matters is that the reflection is real and the learning is yours.
How many significant event analyses do I need for the Portfolio Pathway?
There is no fixed number set by the GMC for the Portfolio Pathway, and Royal College Specialty Specific Guidance varies. Quality and recency matter more than count. A small number of well-analysed events, each showing systems thinking, a specific change and evidence the change held, is stronger than a long list of thin write-ups. Check your specialty SSG for any indicative expectation, and if you have genuinely had no events meeting the GMC harm threshold, declare that and reflect on your local process instead.
Can a complaint or a near miss count as a significant event?
Yes to both. A near miss, an event that could have harmed a patient but did not, meets the GMC definition of a significant event and is often the most useful kind to analyse because the learning comes without the harm. A complaint that changed your practice is also legitimate evidence, paired with your reflection. Positive events and examples of good practice can be analysed too, although the strongest portfolio evidence usually comes from events with a clear learning point and a change that held.
We use PSIRF and after action reviews now, not significant events. Does SEA still count?
Yes. Since 2022 the Patient Safety Incident Response Framework has replaced the Serious Incident Framework across the NHS, and the term serious incident has gone. The underlying activity, reviewing patient safety incidents to learn and improve, has not. An after action review or a patient safety incident investigation gives you a structured starting point; the SEA is your personal reflective write-up of it. The GMC explicitly recognises that organisations use different labels for these events.
How recent do my significant event analyses need to be?
Recent evidence carries more weight. The Portfolio Pathway, like revalidation, looks for current engagement with patient safety, so analyses from the last few years are far more useful than older ones. As a working rule, prioritise events from the period your application covers and keep a rolling habit of writing one up whenever a suitable event occurs. Your specialty SSG may set its own expectation on how recent supporting evidence should be, so check it.