What Good Incident Reporting Looks Like in Adult Social Care in 2026: Learning, Escalation and Documentation
Incident reporting is one of the most important parts of safe, well-led adult social care. When incidents are recorded clearly and acted on promptly, leaders can prevent repeat harm, identify patterns, support staff and demonstrate strong governance to the CQC.
When reporting is vague, inconsistent or delayed, it raises concerns about safety, risk management and the overall culture of the service. Poor incident documentation is also a common theme in CQC reports and one of the quickest ways inspectors assess how well a service understands and manages risk.
This guide explains what good incident reporting looks like, what the CQC expect, how to escalate concerns, and how to turn incidents into meaningful learning. It includes examples of poor and good practice, practical steps for staff and managers, and links to helpful Carevia resources.
If you have not already read these related guides, they offer strong foundations:
understand patterns such as falls, behaviour changes or repeated medication issues
escalate concerns quickly to health professionals when needed
share clear information across staff teams
support learning after incidents
evidence safe practice and governance to the CQC
Incident reporting is not about blame. It is about understanding what happened, why it happened and what needs to change to keep people safe.
Why incidents get missed or underreported
Many services want to improve incident reporting, but real barriers often get in the way. Understanding these helps leaders put the right systems and culture in place. Incidents are most likely to be missed or underreported due to:
Time pressure and competing demands – Staff may rush from one task to the next and assume the incident was “minor” or “already known” without documenting it.
Uncertainty about what counts as an incident – Falls without injury, near misses, behavioural changes or medication selection errors may be overlooked because staff are unsure whether they “need reporting.”
Fear of blame or getting into trouble – In services where learning culture is not yet embedded, staff may avoid reporting errors, behavioural incidents or near misses out of worry about being criticised.
Normalisation of risk – When incidents happen frequently, they can become viewed as “routine,” especially in services supporting people with complex needs. This leads to underreporting and missed learning opportunities.
Lack of confidence in documentation – Some staff worry they will “write it wrong” or feel unsure about what details matter most, so incidents are reported late or incompletely.
Poor handover communication – If incidents are spoken about informally but not recorded, important information is lost between shifts and never reaches senior staff.
No clear structure or accessible forms – Complicated paperwork or inconsistent templates can discourage timely reporting. Staff are more likely to complete incident forms when they are simple, familiar and clearly signposted.
Culture of coping without escalation – Some teams become skilled at managing situations independently but fail to escalate to seniors or health professionals when needed.
Good services remove these barriers by setting clear expectations, promoting a non-blame culture, simplifying documentation and making it easy for staff to escalate concerns. Outstanding services go further by routinely reviewing missed incidents, near misses and “almost events” as part of their learning cycle.
What the CQC expect from incident reporting
Inspectors want to see that incidents are:
reported promptly
recorded clearly and factually
reviewed by a senior member of staff
linked to risk assessments and care plans
acted on with clear follow-up and learning
Many services write incident forms, but do not analyse or learn from them. This is one of the key distinctions between Requires Improvement and Good services, and between Good and Outstanding.
Recording an incident is only the starting point. Inspectors will test what changed afterwards. Carevia Pro+ includes inspection rehearsal that helps managers practise answering that follow-up question with evidence.
What this guide will help you do
This guide explains how to record incidents clearly and consistently, what the CQC expect to see in your documentation, and how to link incidents to safe escalation and learning. It also covers:
what to record immediately after an incident in a care home or supported living service
how to write clear and factual incident reports that stand up to scrutiny
how to escalate concerns safely and when to notify the CQC
when RIDDOR reporting is required and what information must be included
how senior staff can review incidents and identify patterns or learning
examples of poor and good practice to support staff training
The aim is to give you practical guidance you can use straight away to strengthen your incident documentation, improve learning and provide clear evidence for inspection.
Want A Learning Culture?
Join Carevia Pro to access tools that cultivate a learning culture, strengthen documentation and support good inspection outcomes.
What to record after an incident in a care home or supported living service
A good incident form should include:
the date, time and exact location of the incident
witness names if relevant
a clear description of what happened, written factually
the person’s presentation and what staff observed
any immediate actions taken to make the person safe
who was informed (senior, on-call, family, health professionals)
follow-up required (observations, medical review, care plan updates)
recommendations for learning or improvement
This level of detail supports both staff and inspectors to understand the incident and any risks involved.
Carevia Auditing Practice: If you were auditing this, what would it really tell you?
Poor practice vs good practice examples
Poor practice example 1 (Falls Incident)
Incident date/time: 19.40 Location: Bedroom Staff involved: A. Smith
Description of incident: Found Mary on the floor next to her bed. She said she slipped. No visible injuries.
Immediate actions: Helped Mary back onto the bed. Completed incident form.
Notifications: Senior made aware.
Follow-up: None recorded.
This example follows a structured layout but still lacks essential information: no checks completed, no review of causes, no detail of how Mary was supported, no learning, and no updates to her falls plan. It gives inspectors very limited assurance about safety or decision-making.
Improved practice example 1 (Falls Incident)
Incident date/time: 19.40 Location: Bedroom Staff involved: A. Smith
Description of incident: Staff heard a thud and found Mary seated on the bedroom floor beside her bed. Mary stated she slipped while reaching for her blanket, which had fallen to the far side of the bed.
Immediate checks and actions: Mary was calm and responsive. Staff completed immediate post-fall checks: pain, movement, orientation and visible injury – none observed. Supported Mary to sit upright slowly and stand with her walking frame using agreed moving and handling guidance.
Person’s voice: When asked what would help her feel safer, Mary said she sometimes struggles to reach bedding at night and would like it folded closer to her side of the bed.
Environmental review: Staff checked the bedroom for contributing factors. The blanket had slipped to the opposite side of the bed, causing overreaching. Lighting adequate. Floor clear. Staff repositioned bedding and discussed with Mary whether she would like a bed rail or low-level bedding support; she preferred to keep current arrangements but agreed to trial a blanket clip.
Escalation and notifications: Senior on duty informed immediately. Daughter notified of fall. Post-fall observations commenced (2-hourly for 24 hours). GP not immediately required; to be contacted if any change noted overnight.
Care plan and risk assessment updates: Falls risk assessment reviewed and updated. Bedroom layout adjustments added to care plan. Staff reminded to check bedding position during evening checks.
Further actions and learning: Referral made to the community falls clinic for assessment. Incident added to weekly falls analysis. Team to discuss in next handover and consider whether others may benefit from similar bedroom layout reviews.
This example is factual, structured and shows safe action, person involvement, environmental review and meaningful follow-up.
Incident date/time: 15.20 Location: Lounge Staff involved: J. Patel
Description of incident: Resident hit staff during support. Behavioural incident form completed.
Immediate actions: Staff moved away. No injuries.
Notifications: Senior informed.
Follow-up: None recorded.
This example is vague, judgemental and gives no insight into triggers, communication attempts, de-escalation, environmental factors or the person’s emotional state. It also fails to show whether the behaviour support plan was followed, whether the person was checked afterwards, or whether learning was identified.
Improved practice example 2 (Behaviour Incident)
Incident date/time: 17.25 Location: Dining room Staff involved: K. Patel
Description of incident: During tea-time, John became visibly distressed when the dining room became noisy and crowded. He raised his voice and struck staff on the arm when approached.
Immediate checks and actions: No staff injury. Staff followed John’s Positive Behaviour Support Plan: reduced demand, asked John if he would like to a quieter area, used reassure–pause–offer routine. John accepted a glass of water and sat with staff. Distress reduced within 4 minutes.
Person’s voice: When calm, John said the noise made him feel overwhelmed. He requested to eat tea earlier or in a quieter space when the room is busy.
Environmental review: Dining room was at full capacity. Noise levels likely contributed. Plan to trial staggered mealtimes and offer John a quieter table.
Escalation and notifications: Senior informed. No safeguarding threshold met but discussed with on-call for oversight. Behaviour log completed. Family updated.
Care plan and risk assessment updates: PBS plan updated with new trigger information. Staff reminded in handover.
Further actions and learning: Behaviour team to review patterns over last 4 weeks. Environmental changes to be evaluated over next 7 days.
Incident date/time: 08.15 Location: Medication room Staff involved: J. Williams
Description of incident: Wrong tablet selected during medication round. Senior informed.
Immediate checks and actions: Tablet removed. No further action recorded.
Notifications: Senior made aware.
Follow-up and learning: Not documented.
This record gives no reassurance, no detail about safety checks, no reference to the care plan or PRN protocols, and no indication of monitoring, analysis or learning. There is no evidence that the person’s wellbeing was checked, that the error was reviewed by a competent clinician or that a reflective discussion took place. This weak documentation is a common reason for medication-related concerns during CQC inspections.
Improved practice example 3 (Medication Error)
Incident date/time: 08.15 Location: Medication room Staff involved: J. Williams
Description of incident: During the second administration check, staff identified that one incorrect tablet had been selected. The error was identified before administration and the incorrect tablet was removed.
Immediate checks and actions: Senior informed. GP contacted to confirm no monitoring required as the medicine was not administered. MAR corrected. Error form completed.
Person’s voice: Person reassured and informed of the incident and steps taken.
Review and learning: Medication competency for staff member to be refreshed within 48 hours. Trend analysis shows three similar errors in the last month; whole-team refresher session arranged and storage layout to be reviewed.
Governance actions: Incident added to weekly medication audit. Deputy to complete spot checks for 2 weeks.
These Carevia guides offer further support to improve medication governance and learning when things go wrong.
Some incidents must be reported to the HSE under RIDDOR. This includes:
accidents resulting in more than 7 days off work for staff
serious injuries such as fractures (excluding fingers and toes)
accidents linked to faulty equipment or unsafe environments
dangerous occurrences such as fires, gas leaks or equipment collapse
RIDDOR reporting is separate from CQC notifications. Both may be required depending on the situation.
The Carevia Pro Health & Safety Policy is fully editable and includes robust guidance on when incidents require reporting to external bodies including the CQC and Health and Safety Executive (HSE).
Linking incidents to learning
Good and outstanding services use incidents to strengthen practice. This means:
reviewing incidents in supervision
discussing patterns in team meetings
updating care plans
adjusting staffing levels or routines
introducing new risk controls
Inspectors want to see evidence of learning, not just recording.
Many services record “lessons learned” without demonstrating embedding. Carevia Pro+ helps leaders test whether learning can be articulated clearly under inspection-style scrutiny.
If you want to understand how learning culture links to safer practice, this guide may be helpful:
This approach aligns with the Well-Led and Safe quality statements and supports inspection readiness.
Governance maturity shows in how leaders describe their oversight of incidents. Through Carevia Pro+, managers can practise explaining how they sample, analyse and feed forward learning.
Tools to improve incident reporting and documentation
If you want ready-made templates that support consistent, safe and CQC-aligned recording, you may find the Carevia CQC Leadership and Learning Master Toolkit helpful.
For unlimited access to all current and future toolkits, including incident templates, PRN templates, audit tools and governance logs, you can join Carevia Pro.
Good incident reporting is not just about filling in forms. It is about understanding what happened, taking action and learning from experience. Clear, factual records supported by strong governance help keep people safe, support staff and reassure inspectors.
By improving how incidents are recorded, escalated and reviewed, services build a safer culture and stronger evidence for inspection. Clear documentation also supports better communication, more consistent care and a more confident staff team.
Subscribe to Our Newsletter
Incident reporting FAQs (2026)
These FAQs are designed to help registered managers, deputies and seniors strengthen learning, escalation and documentation in a way that stands up to CQC scrutiny.
What counts as an incident in adult social care
An incident is anything that could have caused harm, did cause harm, or indicates increased risk. This includes low level events that might be early warning signs.
Falls and near misses, even when there is no injury
Medication errors, omissions, delays or near misses
Choking events, seizure activity, unexplained bruising or injuries
Behaviour that communicates distress, especially when it is new or escalating
Deterioration concerns, reduced intake, new confusion, possible infection signs
Safeguarding concerns, allegations, unexplained injuries, or patterns of concern
If staff are saying “keep an eye on”, it usually means it should be recorded properly and reviewed.
What does good incident documentation look like to the CQC
CQC want documentation that is factual, clear and shows safe action and follow up. It should read like a reliable account of what happened and what changed as a result.
Date, time, location, who was involved and who witnessed it
What happened, written factually and without judgemental language
Immediate checks and actions taken to make the person safe
Who was informed and when, including escalation to senior or on call
What monitoring is now required, with timescales
What needs updating in the care plan or risk assessment
What learning was identified and how it will be embedded
How quickly should incidents be recorded and reviewed
Incidents should be recorded as soon as possible while details are accurate. Senior review should happen the same day for higher risk incidents, and within 24 hours as a minimum for all incidents.
Immediately: make safe, complete essential checks, document the facts
Same day: senior oversight for falls, injuries, medication issues, behaviours escalating, deterioration
Within 48 hours: care plan and risk assessment updates, referrals and follow up actions confirmed
Within 7 days: trend review, learning shared, competence and practice checks completed where needed
If review is delayed, learning is delayed, and that is where repeat incidents happen.
What is the difference between a near miss and an incident
A near miss is an event that could have caused harm but did not, either by chance or because something prevented it. Near misses should still be recorded and reviewed because they often show rising risk.
Examples include selecting the wrong tablet but catching it before administration, a slip without a fall, or finding a person in an unsafe situation before injury occurs.
Strong services treat near misses as early warning indicators and use them to strengthen prevention.
How should we write about behaviour that communicates distress
Avoid labels like “aggressive” or “non compliant” without context. Describe what was observed, what you believe it communicated, and what you did.
What happened and what staff saw and heard
Likely triggers such as noise, pain, task demand, change in routine
De escalation steps used and whether they worked
Person’s voice where possible, including preferences
What needs updating in PBS plans, care plans or risk assessments
When do we need to escalate and who should be informed
Escalation should be clear, consistent and documented. Staff should never be left guessing.
Senior on duty or on call: any injury, fall, deterioration concern, medication error, safeguarding concern, repeated distress
GP or community nurse: suspected infection, new pain, pressure area concerns, wound changes, clinical deterioration
Emergency services: serious injury, head injury concerns, severe breathing issues, unresponsive person, concerning NEWS-2, or documented signs that indicate the persons health is deteriorating.
Family or advocate: as agreed and appropriate, and especially after significant incidents
Local authority safeguarding: where there is suspected abuse, neglect, unsafe care, or repeated unexplained harm
The record should show what decision was made, why, and who it was shared with.
When must we notify the CQC
Some events require statutory notification to CQC. The notification must be factual, timely and consistent with your internal records.
Common examples include deaths, serious injuries, allegations of abuse, incidents involving the police, and events that may affect safe care. If you are unsure, seek advice and keep a record of what you checked and when.
When is RIDDOR relevant in a care home or supported living service
RIDDOR reporting is separate from CQC notifications. It usually relates to work related injuries, specified injuries, dangerous occurrences and certain incidents affecting staff or arising from work activity.
In practice, services often need to consider RIDDOR when there is a staff injury, equipment failure, unsafe premises issue, or an incident linked to work activity that results in serious harm.
If you are unsure, document your decision making, seek appropriate advice and ensure you complete internal investigation and learning regardless.
Why do services collect incident forms but still fail inspection
Because forms alone do not show governance. Inspectors look for learning, action and assurance.
No trend analysis across falls, medicines, behaviours or deterioration
Care plans and risk assessments not updated after incidents
Actions recorded but not followed through or checked in practice
Learning not shared across shifts, teams and agency staff
Leaders not observing high risk routines and not testing staff understanding
