More than serious harm
Near-misses, system failures, and positive events all qualify. A window left open that triggers the alarm is still an SEA. The more small things you log, the fewer big things happen.
SEA Report Generator
Generate your significant event analysis in two minutes.
Describe what happened and get a structured, CQC-compliant significant event analysis. Consistent output every time, regardless of who writes it up. You do the thinking. The tool does the typing.
Free to start No credit card required NHS DSPT verified
< 2 min
per SEA report
6
CQC Mythbuster 3 criteria met
1 hr+
saved per SEA vs manual
Why SEAs Matter
Learning, not blame. That is what CQC expects.
A significant event analysis is a structured review of any event that could have or did lead to harm. The purpose is to understand what happened, why the system allowed it, and what needs to change. CQC assesses it under the Learning Culture quality statement.
Systems thinking, not blame
A good SEA asks “what in our system made this possible?” not “whose fault was it?” This aligns with NHS England's Being Fair framework and the principles embedded in PSIRF.
Contractual requirement
The 2025/26 GP contract requires patient safety events to be reported to LFPSE. The AI flags when reporting is required.
For a deeper look at building a practice-wide SEA system, see the complete SEA implementation guide (8,500 words covering governance, triage, staff training, and audit cycles).
How It Works
From discussion notes to SEA report in three steps
Describe what happened in plain English. Get a complete, structured report with event summary, contributing factors, root cause analysis, SMART actions, and learning points.
1
Describe what happened
Write three to four sentences about the event. Include what happened, when, who was involved, and whether the patient was harmed. You do not need clinical detail or formal language.
2
The AI structures your analysis
The tool generates a complete SEA report using systems-based thinking, following the RCGP’s five core questions. Contributing factors, root cause analysis, and SMART actions are all included.
3
Review and share
Review the output, adjust details specific to your practice, and present it at your next SEA meeting. Export to PDF or Word and log it in your event register.
Try the SEA Writer Now
No credit card required. Takes under two minutes.
Safe Delegation
Delegate SEA write-ups and get consistent output every time
The biggest problem with SEAs is not the analysis — it is the write-up. Depending on who you ask, the output varies wildly. The AI SEA writer solves this with guardrails.
Without guardrails
- ×GP writes two lines between consultations
- ×Admin lead produces something unstructured
- ×New starter is not sure what good looks like
- ×You spend an hour rewriting their draft
- ×Quality varies every time, across every team member
With My Practice Manager
- Same structured output regardless of who uses it
- CQC-aligned structure, systems-based analysis built in
- Deputy managers and new starters produce CQC-ready reports
- You spend five minutes reviewing, not rewriting
- Delegation becomes safe delegation
The SEA is just the starting point
The actions in your SEA often require a policy update, an audit, or a staff communication. Practices using My Practice Manager feed the completed SEA straight into the policy writer or SOP generator to update the relevant documents, then cascade the changes to staff through the document manager. What used to be a full day of follow-up work becomes a connected workflow that takes under an hour.
SEA report→Policy update→Staff sign-off→Audit setup
The Halfway Point Podcast
Hear how a practice manager uses the SEA writer day to day
In this episode, Jermaine (practice manager and My Practice Manager co-founder) and Tom walk through how the tool fits into real practice operations — delegation, consistency, and logging small events before they become big ones.
Worked Example
Prescription error caught at pharmacy
Generated from a four-sentence description of a repeat prescription near-miss. This is the most common type of SEA in general practice.
AI-generated example
Significant Event Analysis Report
Ref: SEA-2026-017Event: 4 March 2026Harm level: No harm (near-miss)Prepared by: Practice Manager
1. Event Summary
A 72-year-old patient on repeat metformin 500mg twice daily had their prescription reauthorised by the duty GP without the required annual diabetic review having been completed. The prescription was processed through the clinical system's repeat prescribing module and sent electronically to the pharmacy. The community pharmacist identified that the patient's last HbA1c was recorded 14 months previously and contacted the practice before dispensing. The patient was not harmed, but the safety net that caught this error was external to the practice.
2. Contributing Factors
| Factor | Detail |
|---|---|
| Workflow design | The repeat prescribing module does not display overdue review alerts when a prescription is being reauthorised. The duty GP saw the prescription request but had no visual prompt indicating the review was overdue. |
| Workload | The duty GP was processing 47 repeat prescription requests alongside a full morning surgery. Repeat prescriptions were being batch-signed between consultations. |
| System config | The clinical system can flag overdue reviews on repeat prescriptions, but this alert was not enabled for the diabetic review template specifically. |
| Process gap | No pre-authorisation check by admin or pharmacy staff before prescriptions reach the duty GP. The GP is the sole safety net within the practice. |
3. Root Cause Analysis
The system made this error likely: no automated alert, high workload during batch signing, no pre-screening by support staff, and a single point of failure (the GP) in the authorisation chain. This is a systems issue, not an individual failing. Any GP processing 47 prescriptions between consultations under the same conditions would face the same risk.
4. Lessons Learned
- •Near-miss events caught by external safety nets indicate that the practice's internal safety nets are insufficient for that process.
- •Batch-signing 47 prescriptions under time pressure is a known risk factor. The workload model for repeat prescribing may need review.
- •Clinical system alerts are only effective if configured for all relevant review types, not just some.
5. Actions
| Action | Owner | Deadline | Review |
|---|---|---|---|
| Configure overdue annual review alerts on the repeat prescribing screen for all chronic disease templates | IT Lead | 18 Mar | 18 Jun |
| Introduce a pre-authorisation check by trained prescription clerk before prescriptions reach the duty GP | PM | 1 Apr | 1 Jul |
| Review repeat prescribing workload model and consider spreading across the day | Clinical Lead | 15 Apr | 15 Jul |
6. Learning Points for the Team
- •When an error is caught outside the practice, the question is: “Why didn't we catch it first?”
- •“Human error” is the starting point of the investigation, not the conclusion.
- •This event will be reported to LFPSE as a no-harm near-miss event.
This report was generated in under two minutes from a four-sentence event description.
Worked Example
Delayed two-week-wait referral
A clinically significant event — the kind that requires formal investigation and generates the most anxiety about write-up quality. Generated from a five-sentence description.
AI-generated example
Significant Event Analysis Report
Ref: SEA-2026-018Event: 24 February 2026Harm level: Low harmPrepared by: Practice Manager
1. Event Summary
A GP consulted with a 58-year-old patient presenting with rectal bleeding and a change in bowel habit persisting for six weeks. The GP documented a plan to refer urgently on the two-week-wait (2WW) pathway for suspected lower GI cancer, in line with NICE NG12 criteria. The referral was dictated into the clinical record but was not submitted electronically. The patient contacted the practice 18 days later having not received a hospital appointment. On investigation, the referral was found in the GP's unsigned task list. Colonoscopy findings were benign, but the patient experienced 18 days of avoidable delay and significant anxiety.
2. Contributing Factors
| Factor | Detail |
|---|---|
| Workflow design | The referral process requires dictating the referral and then navigating to a separate screen to submit via e-RS. Two distinct actions; the second can be missed if the GP is interrupted. |
| Workload | Fully booked surgery. The referral was dictated at 11:47, next patient seen at 11:52. Five-minute gap likely used for admin catch-up. |
| No safety net | No end-of-day check for unsigned or unsubmitted referrals. The clinical system does not generate alerts for referrals created but not sent. |
| Patient communication | The patient was told “we'll refer you urgently” but not given a specific callback instruction if they hadn't heard from the hospital. |
3. Root Cause Analysis
A two-step electronic referral process with no automated verification that the second step has been completed. The GP completed the clinical task (dictating the referral) but not the administrative task (submitting it). Compounded by the absence of a patient-side safety net — if advised to call back after seven days, the delay would have been 7 days, not 18.
4. Lessons Learned
- •Any process relying on a single individual completing two separate system actions under time pressure will eventually fail.
- •2WW referrals are among the highest-risk administrative processes in general practice. The process must have at least two independent safety nets.
- •Patient communication at the point of referral should include a specific callback instruction.
5. Actions
| Action | Owner | Deadline | Review |
|---|---|---|---|
| Implement end-of-day referral check: admin reviews unsubmitted referral queue at 17:00 daily | Admin Lead | 18 Mar | 18 Jun |
| Create patient information sheet for 2WW referrals including “Call us if you haven't heard within 7 days” | PM | 25 Mar | 25 Jun |
| Audit all 2WW referrals for past 6 months for late submissions | Clinical Lead | 1 Apr | N/A |
| Contact patient to apologise and explain changes (Duty of Candour) | GP Partner | 12 Mar | N/A |
6. Learning Points for the Team
- •A referral that has been dictated but not submitted is clinically invisible. Until it arrives at the hospital, it does not exist.
- •Duty of Candour applies: the patient experienced avoidable delay causing anxiety (CQC Regulation 20).
- •This event will be reported to LFPSE as a low-harm patient safety event.
This report addresses a clinically significant event with systems-based analysis, Duty of Candour requirements, LFPSE reporting, and specific actions with named owners and review dates.
CQC Compliance
How the AI-generated SEA meets CQC Mythbuster 3
No other SEA resource online maps its output to CQC's six inspection criteria. The existing resources tell you what CQC expects. This tool produces it.
| CQC criterion | Where it appears in the AI-generated report |
|---|---|
| 1. Staff can identify and prioritise a significant event | The harm level classification (no harm / low harm / moderate / severe) in the report header demonstrates event prioritisation. The report distinguishes near-misses from harm events. |
| 2. Information is gathered with factual documentation and personal testimonies | Section 1 (Event summary) provides a factual, chronological account based on clinical records and staff accounts. |
| 3. Facilitated team-based meeting that occurs regularly | The report header records the analysis date and reviewers. The report is designed to be presented at a team meeting, not filed in isolation. |
| 4. Analysis addresses what happened, why, what could be different, lessons learned, required changes | Sections 2–4 (Contributing factors, Root cause analysis, Lessons learned) address the “why” using systems thinking. Section 5 (Actions) addresses “what changes.” |
| 5. Changes are agreed, implemented, and monitored at preset intervals | The action table includes SMART actions with named owners, specific deadlines, and three-month review dates for monitoring. |
| 6. Written report shared with involved staff | The complete report is the written record. Section 6 (Learning points) provides the summary to share with the wider team. |
What the AI adds that blank templates cannot
Consistent output
Same structure and depth regardless of who uses it. No more varying quality depending on who you delegated the write-up to.
Systems-based contributing factors
Structured as a table identifying people, activity, and environment factors — the kind of analysis CQC inspectors describe as evidence of genuine learning.
Root cause analysis beyond “human error”
Frames causes in terms of system conditions, not individual blame. Aligned with NHS England’s Being Fair framework and PSIRF.
SMART actions with review dates
Not “improve communication” but specific actions with named owners, deadlines, and three-month review dates.
LFPSE and Duty of Candour prompts
Flags when events should be reported to LFPSE and when Duty of Candour obligations apply. No other template does this.
Feeds into your compliance workflow
SEA actions often need policy updates. Feed the completed SEA into the policy writer or SOP generator to keep everything connected.
Pricing
Start free. Upgrade when you are ready.
The SEA writer is available on Essentials and above. No credit card required to start.
Free
£0
Try the AI tools, no strings attached.
- 3 lifetime AI document generations
- 1 compliance library domain (your choice)
- 5 active tasks
- 1 user
- 4 AI templates (Policy, Risk Assessment, SOP, General Assistant)
Starter
£12/month+ VAT
For practice managers getting started with AI compliance tools.
- Unlimited AI document generations
- Full compliance library (all 11 domains)
- 15 active tasks
- 1 user
- 4 AI templates (Policy, Risk Assessment, SOP, General Assistant)
Most Popular
Essentials
£20/month+ VAT
Everything your practice needs for complete CQC compliance.
- Unlimited AI document generations
- Full compliance library (all 11 domains)
- All 12 AI templates
- Unlimited active tasks
- Multi-user access
- Rota management
- Email support
Pro
£45/month+ VAT
Full platform access with document distribution and CQC readiness tools.
- Everything in Essentials, plus:
- Document Manager
- Read receipts and acknowledgements
- CQC compliance check
- Priority email support
Prices shown for a 9,001–12,000 patients practice. Starter is a flat rate. See pricing for your practice size
Want someone to do it for you? See our Policy Review Service — from £25 per policy area.
Security and compliance credentials
Cyber Essentials
Independently verified cybersecurity controls
NHS DSPT
Published and verified
UK GDPR
UK-hosted infrastructure, DPA available
Verify: Cyber Essentials certificate | NHS DSPT entry
FAQ
Frequently asked questions
How many SEAs should a GP practice do per year?
CQC does not specify a number. A practice that discusses two to three events per month, including near-misses and quick discussions, demonstrates a healthier learning culture than one that produces four formal SEAs per year. Volume reflects reporting culture, not risk. The key mindset shift: log the small things — a window left open that triggered the alarm, a prescription request that sat in a queue too long — so they do not become big things. If writing up an SEA takes an hour, teams only report serious events. If it takes two minutes, the threshold drops and you catch patterns before they cause harm.
Can a significant event be positive?
Yes. CQC Mythbuster 3 explicitly expects practices to learn from what goes right, not just what goes wrong. A cancer diagnosed promptly through good safety-netting, a deteriorating patient identified early by a receptionist, or a complaint handled exceptionally well are all significant events worth analysing. Understanding why something went right tells you which systems and behaviours to reinforce.
What is the difference between an SEA and a complaint?
A complaint is a formal expression of dissatisfaction from a patient. An SEA is an internal learning process. They overlap: some complaints reveal patient safety events that should be investigated as SEAs. The key distinction is purpose — a complaint process aims to resolve the patient’s concern; an SEA aims to understand why the event happened and prevent recurrence. Both may run in parallel for the same event.
Do SEAs need to be reported to the ICB?
Not SEAs themselves, but the underlying patient safety events often do. Under the 2025/26 GP contract, practices must record patient safety events in the Learn from Patient Safety Events (LFPSE) service within two working days of identification. LFPSE replaced the old NRLS, which was decommissioned in June 2024. Your SEA investigation may take longer, and LFPSE allows you to update records as your investigation progresses.
Who should attend the SEA meeting?
SEA meetings should be team-based, not limited to the clinician involved. CQC Mythbuster 3 specifically requires “facilitated team-based meetings.” Include clinical and non-clinical staff — receptionists and administrators often spot system failures that clinicians never see. Rotating facilitation between GPs, practice managers, and nurse leads prevents the meeting from feeling like a clinical hierarchy exercise.
Can I delegate SEA write-ups to other staff?
Yes — and this is one of the most common ways practices use the tool. Deputy managers, admin team leads, and secretaries who took the meeting minutes can all produce a structured SEA report. The guardrails built into the tool — CQC-aligned structure, systems-based analysis, SMART actions with owners and review dates — mean the output meets a consistent standard regardless of who uses it. You review the output and confirm the clinical details rather than rewriting their draft from scratch. Try the SEA writer.
Are AI-generated SEAs accepted by CQC?
CQC assesses whether your SEAs are structured, evidence-based, systems-focused, and acted upon — not how the report was drafted. An AI-generated SEA that has been reviewed by the clinical lead, discussed at a team meeting, and results in implemented actions meets CQC expectations in the same way as a manually written one.
Stop spending an hour on each SEA write-up
You do the thinking — the discussion, the clinical judgement, the systems analysis. The tool does the typing. Consistent, CQC-ready output every time, regardless of who writes it up.
No credit card required. No sales calls. Write your first SEA free.
This page describes the features and capabilities of My Practice Manager software as of March 2026. Generated SEA reports are starting points for professional review and should be checked against your practice's specific circumstances. Always refer to the latest guidance from CQC, NHS England, and the GMC.