A supervisor receives three incident reports before noon: a minor fall with no injury, a medication refusal with possible health concern, and a community safety incident that ended quickly but frightened staff. Each report needs action, but not the same action. Strong providers do not treat severity as a label added at the end. They use severity review to match response level with real risk, person impact, escalation need, and evidence strength.
Severity review helps leaders act proportionately without missing hidden risk.
Within incident reporting and learning systems, severity review guides what happens next. It helps determine whether the incident requires monitoring, supervisor review, clinical advice, case manager update, funder notification, regulatory action, or protective escalation.
Severity review also supports audit review and continuous improvement, because leaders can test whether similar incidents are graded consistently. Across the Quality Improvement and Learning Systems Knowledge Hub, severity grading is a practical control that links frontline reporting with reliable oversight.
Why severity review needs evidence
Severity should not be based only on the incident title. A “fall” may be low, moderate, or serious depending on injury, history, environment, and change in mobility. A “missed visit” may be minor or high risk depending on essential tasks, medication timing, and whether the person is alone. A “behavioral escalation” may require local support or wider clinical coordination depending on pattern, impact, and support plan fit.
Providers can strengthen this by using incident reporting workflows that guide severity decisions with clear evidence prompts. The strongest systems help supervisors make proportionate decisions without relying on memory, habit, or inconsistent local practice.
Operational example 1: A fall severity review avoids both underreaction and overreaction
In a community-based residential service, a person slips while moving from a chair to a walker. Staff support them safely, complete an injury check, and contact the supervisor. The person reports no pain and resumes normal movement, but they have had two previous falls in the last month.
The supervisor reviews severity using both immediate impact and pattern. Required fields must include: fall location, time, witness account, injury check, pain or mobility change, prior fall history, environmental condition, staff action, monitoring plan, and notification decision.
The incident is not graded as serious because there is no injury, no hospital transfer, and no immediate clinical red flag. It is not treated as low significance either, because repeat falls suggest rising risk. The supervisor grades it as moderate and opens a fall trend review.
Cannot proceed without: confirmation that the person remains safe, next-shift monitoring instructions, family or representative communication where required, support plan review, and decision on whether the case manager needs an update due to repeat risk.
Auditable validation must confirm: severity rationale, previous incident comparison, monitoring evidence, support plan review, notification record, and follow-up after later transfers. The outcome is proportionate control. The provider avoids unnecessary emergency escalation while still recognizing that repeated minor falls require stronger review.
Operational example 2: Medication refusal severity depends on timing, pattern, and person impact
A home care worker reports that a person declined a medication prompt during a morning visit. The person says the medication makes them feel unwell. The worker follows the care plan and contacts the supervisor before leaving. The incident title might appear straightforward, but severity depends on the medication, timing, and whether this has happened before.
Required fields must include: medication prompt time, medication type where recorded in the plan, whether dose was refused or delayed, person’s stated reason, previous refusal history, current presentation, clinical advice decision, and next support point.
The supervisor identifies that this is the second refusal in four days. The medication may be clinically important, and the person has linked refusal to feeling unwell. The severity review therefore moves beyond routine documentation. Clinical advice is sought, and the case manager update is considered if the support plan or authorization may need review.
Cannot proceed without: medication record update, person welfare check, clinical guidance where required, clear instruction for the next visit, and documented decision about representative or case manager communication.
Auditable validation must confirm: severity rationale, clinical advice, worker action, medication record, next-visit guidance, and follow-up outcome. If the refusals continue, leaders may need root cause analysis that turns repeated incident evidence into practical service fixes.
The outcome is better clinical coordination. Severity is not inflated unnecessarily, but it is strong enough to protect the person and guide timely review.
Operational example 3: Community safety severity supports positive risk decisions
A residential support provider reports that a person became distressed at a busy public event and moved away from staff for less than one minute while remaining in sight. Staff followed the support plan, supported the person to a quieter area, and returned home safely. No injury occurred.
Required fields must include: location, trigger, staff ratio, whether the person remained in sight, duration of separation, de-escalation steps, person’s account where possible, public safety impact, support plan guidance, and case manager notification decision.
The supervisor decides that the incident does not meet serious missing-person or emergency criteria. However, it does require moderate severity review because the same transportation and crowding trigger has appeared previously. The focus becomes safer preparation rather than restriction.
Cannot proceed without: confirmation that the person is safe, revised community preparation plan, staff briefing, case manager update where required, and review after the next comparable activity.
Auditable validation must confirm: severity decision, rationale for not escalating as a missing-person event, support plan adjustment, staff briefing, communication with the case manager where needed, and outcome after future community participation.
The outcome protects dignity and opportunity. Severity review helps the provider respond seriously enough to reduce risk while avoiding an unnecessary withdrawal from meaningful community life.
Using severity review to guide action tracking
Severity review should determine follow-through. Low-severity incidents may need local monitoring and closure checks. Moderate incidents may need supervisor review, trend analysis, or case manager communication. Serious incidents may require leadership oversight, external notification, protective escalation, or formal investigation.
The Quality Improvement Action Plan Builder can help providers connect severity decisions to action owners, deadlines, evidence checks, and review dates. This makes the response visible and proportionate.
What governance should review
Governance should review severity consistency across services, supervisors, shifts, and incident types. Leaders should sample falls, medication concerns, missed visits, community incidents, behavioral escalation, injuries, allegations, and repeated low-level patterns.
They should ask whether severity was based on evidence, whether rationale was recorded, whether escalation matched risk, and whether repeated incidents changed the grading. They should also check whether staff understand what information supervisors need to grade severity accurately.
Commissioner relevance is clear. Severity decisions affect safety, continuity, clinical coordination, funding discussions, care authorization, regulatory confidence, and family trust. If severity is repeatedly understated, people may not receive timely protection. If it is repeatedly overstated, systems may become noisy and less focused. Strong governance keeps severity proportionate, evidence-led, and connected to action.
Conclusion
Incident severity review helps providers match response level with real risk. It supports timely escalation, fair decision-making, and stronger evidence for why action was taken.
In HCBS, home care, and community-based residential services, severity review improves safety, accountability, commissioner confidence, and quality learning. When severity decisions are clear, consistent, and evidence-led, incident reporting becomes a stronger system for protecting people and improving service control.