skip to main content
career toolkits

Significant Event Analysis (SEA): Template + Guide

How to write a SEA that satisfies appraisal, demonstrates learning, and actually improves practice — without spending 3 hours on it.

Review date
Mar 2026
Reading time
10 min read
Author
Dr Kola Tytler MBBS CertHE MBA MSt MRCGP
On this page
Career toolkitPractical prompts and templates for applications, portfolios and professional development. Check local employer and regulator requirements before use.

Key points

  • A SEA is a <strong>structured analysis of a significant event</strong> — positive or negative — that leads to identified learning and action.
  • Appraisers look for: <strong>honest reflection, system-level thinking, and concrete actions taken</strong> — not blame allocation.
  • A good SEA takes <strong>30–45 minutes to write</strong> if you use a template and have the event fresh in mind.
Significant Event Analysis is a core component of medical appraisal in the UK. It is also one of the most commonly misunderstood — doctors either write defensive incident reports or generic reflections that satisfy no one. A well-written SEA demonstrates professional maturity: you noticed something important, analysed it honestly, identified learning, and changed your practice. This is exactly what appraisers and the GMC want to see.
1

Step 1 — Choose the right event

A significant event is anything that made you stop and think: a near-miss, a complaint, a diagnostic delay, a positive outcome from a new process, a learning moment from a colleague, or a system failure. It does not have to be a disaster — positive events and near-misses are equally valid and often more useful for demonstrating proactive learning.
2

Step 2 — Describe what happened (factual, anonymised)

Write a concise factual account: what happened, when, who was involved (roles, not names), and what the outcome was. Keep this to 100–150 words. Use clinical language but avoid jargon. Anonymise completely — no patient-identifiable information.
3

Step 3 — Analyse why it happened (system thinking)

This is where most SEAs fail. Don't just describe what went wrong — analyse why. Was it a system failure (unclear pathway, missing information, communication breakdown)? A knowledge gap? A process gap? A human factors issue (fatigue, distraction, cognitive load)? Good SEAs look beyond individual blame to system-level causes.
4

Step 4 — Identify what you learned

Be specific: 'I learned that...' followed by a concrete insight. Not 'I learned to be more careful' (vague) but 'I learned that the referral pathway for X condition requires Y step which I had previously been omitting' (specific, actionable).
5

Step 5 — Describe what you changed (action taken)

What did you do as a result? Examples: updated your personal clinical protocol, shared the learning with the team, initiated a guideline review, changed your consultation template, or arranged additional training. If the action was team-level (discussed at practice meeting, updated practice protocol), note this. Appraisers want to see that the learning was converted into behaviour change.
6

Step 6 — Close the loop (follow-up)

If applicable: did the change work? Was there a re-audit or follow-up? Even a simple statement like 'I have not encountered the same issue since implementing this change' closes the loop. If the event is recent, note that follow-up is ongoing.

SEA template (copy and adapt)

<strong>Event:</strong> [100–150 words: what happened, when, outcome]<br/><strong>Analysis:</strong> [100–150 words: why it happened, system/process/knowledge factors]<br/><strong>Learning:</strong> [50–100 words: specific insights]<br/><strong>Action taken:</strong> [50–100 words: concrete changes made]<br/><strong>Follow-up:</strong> [1–2 sentences: outcome of changes or plan for review]

What not to do

Do not: write a defensive account that minimises your role, blame other individuals by name, include patient-identifiable information, or treat the SEA as a box-ticking exercise with generic reflections. Appraisers read hundreds of these — they can tell the difference between genuine learning and performative compliance.

References

GMC — Significant events (supporting information for appraisal)
Your learning path

Save your place and choose what comes next

sign in to save your learning
Work through this guide (6 steps)

Use the actions from this article to track what you have worked through.

Sign in using the reading controls above to save your steps.

  • A significant event is anything that made you stop and think: a near-miss, a complaint, a diagnostic delay, a positive outcome from a new process, a learning moment from a colleague, or a system failure. It does not have to be a disaster — positive events and near-misses are equally valid and often more useful for demonstrating proactive learning.

    Return to this section

  • Write a concise factual account: what happened, when, who was involved (roles, not names), and what the outcome was. Keep this to 100–150 words. Use clinical language but avoid jargon. Anonymise completely — no patient-identifiable information.

    Return to this section

  • This is where most SEAs fail. Don't just describe what went wrong — analyse why. Was it a system failure (unclear pathway, missing information, communication breakdown)? A knowledge gap? A process gap? A human factors issue (fatigue, distraction, cognitive load)? Good SEAs look beyond individual blame to system-level causes.

    Return to this section

  • Be specific: 'I learned that...' followed by a concrete insight. Not 'I learned to be more careful' (vague) but 'I learned that the referral pathway for X condition requires Y step which I had previously been omitting' (specific, actionable).

    Return to this section

  • What did you do as a result? Examples: updated your personal clinical protocol, shared the learning with the team, initiated a guideline review, changed your consultation template, or arranged additional training. If the action was team-level (discussed at practice meeting, updated practice protocol), note this. Appraisers want to see that the learning was converted into behaviour change.

    Return to this section

  • If applicable: did the change work? Was there a re-audit or follow-up? Even a simple statement like 'I have not encountered the same issue since implementing this change' closes the loop. If the event is recent, note that follow-up is ongoing.

    Return to this section

Portfolios and governance · Article 11 of 12