How to Report a Sentinel Event Correctly

Author: A. Ant, CADC-II, Licensing & Accreditation Expert

Disclaimer: This content is provided for general informational purposes only and should not be construed as medical, clinical, legal, financial, tax, accounting, insurance, licensing, accreditation, regulatory, billing, employment, or compliance advice. Requirements change often. Consult qualified professionals or contact Continued Compliance, Inc. for guidance specific to your situation. This article was created by the compliance expert cited above and reviewed by AI. A compliance expert approved and edited it for accuracy before publication.

Photo: A compliance leader reviewing an incident-reporting workflow and corrective action file at a behavioral health facility.

As defined by The Joint Commission, a sentinel event isn’t the moment for an informal conversation or a delayed email chain. When something serious happens, leaders have to protect the individual, preserve the facts, and figure out fast whether external notification is required. Knowing how to report a sentinel event can protect people, protect your organization’s credibility, and keep an already serious situation from turning into a much bigger regulatory failure.

For behavioral health and SUD organizations, the real challenge is rarely just filling out a form. It’s coordinating a disciplined response while the facts are still coming into focus. Your process needs to move fast enough to meet the required timelines and stay structured enough to keep speculation out of the record entirely.

What qualifies as a sentinel event?

A sentinel event generally means an unexpected occurrence involving death or serious physical or psychological injury, one that’s usually unrelated to the natural course of the person’s underlying condition, or that points to a real breakdown somewhere in care or supervision.

The exact definition and reporting threshold shift by accrediting body, state agency, and your own internal policy. A death, an elopement with real risk attached, alleged abuse, or a serious assault may all demand immediate escalation. Not every serious incident automatically becomes a sentinel event, but every potentially qualifying one deserves a prompt look from trained leadership.

That distinction genuinely matters. Under-reporting creates one kind of regulatory exposure. Overstating facts before an investigation wraps up creates a completely different one. The right move is reporting the known facts promptly, naming what’s still unknown honestly, and holding off on conclusions until the review is actually done.

How to report a sentinel event: the first response

Safety comes first, not paperwork. Get the affected individual appropriate emergency support, secure the environment, and notify the on-call administrator or designated incident leader without delay.

Your organization needs a written escalation pathway naming exactly who gets called after hours and who decides whether the event actually meets the sentinel-event threshold. If an employee has to guess who to call at 2 a.m., the policy simply isn’t strong enough to do its job.

Document facts, not assumptions

Capture the basic facts while they’re still fresh: who was involved, what happened, when it was discovered, and what immediate action was taken. Use direct observations, and clearly flag anything that’s secondhand rather than witnessed directly.

Keep blame and conclusions out of it entirely. A line like “staff negligence caused the incident” has no place in an initial report unless the organization has actually verified that through a proper review. A strong report keeps documented fact separate from allegation and pending investigation, never blurring the two together.

Preserve every relevant record right away: observation logs, staffing schedules, video footage, medication administration records, whatever applies to this specific event. Don’t alter, backdate, or quietly “clean up” documentation after the fact. Any correction needs to follow your organization’s actual documentation policy, in writing, with a clear trail.

Activate the internal review team

A sentinel event response shouldn’t sit on one program director’s desk alone. Pull in executive leadership, quality, compliance, clinical leadership, and legal counsel where appropriate. The team’s first job is establishing command and preserving a reliable record before anything else happens.

Assign one person to manage the event file and another to coordinate outside communications. That single step prevents conflicting messages and lost documentation, and it helps leadership control the timeline once multiple agencies and family members are all involved at once.

Determine external reporting requirements

Internal notification happens immediately. External reporting depends entirely on the facts and whatever rules actually apply to your organization. State licensing agencies, law enforcement, and accrediting bodies can each carry separate deadlines that don’t overlap neatly.

Don’t assume filing one report satisfies every obligation at once. A state incident report may not meet an accreditor’s own notification standard, and a law-enforcement notification never replaces a required licensing report. California SUD facilities, for example, have their own distinct DHCS reporting timeline and form. See DHCS Mandatory Incident Reporting: What BHIN 26-007 Changed. On the flip side, reporting externally before leadership has actually confirmed the right process can end up disclosing something inaccurate or simply unnecessary.

Before submitting anything externally, nail down the event category, the actual deadline, and who’s authorized to submit it. For high-risk events, document the reasoning behind whether a report was or wasn’t required, not just the final decision itself.

When there’s real uncertainty, treat the deadline as urgent regardless. Waiting for a complete root cause analysis before making any initial notification can be a genuine mistake if the rule requires prompt reporting. A preliminary report can simply state the investigation is ongoing, with more to follow.

Build a report that holds up under scrutiny

A credible report is clear and organized, explaining the immediate response without turning defensive or speculative. It should also show the organization actually grasped how serious this was and moved fast to reduce ongoing risk.

Cover the event timeline, who was involved, the immediate safety actions taken, and what records got preserved. If the investigation isn’t finished yet, say so plainly rather than filling the gap with a guess just because the form has a narrative field waiting to be completed.

If a resident eloped and was later found, for instance, the report should lay out the known timeline and the search actions taken. It shouldn’t claim staffing was adequate or policy was followed until those specific points have actually been checked against the evidence.

Complete a meaningful root cause analysis

Reporting is only the first phase here. A sentinel event calls for a structured look at the systems that let it happen in the first place, not a hunt for one person to blame.

Look past the immediate action. Was the policy actually unclear? Was staffing out of step with the organization’s real acuity level? Were staff trained but never actually observed for competency afterward? Did leadership already know about earlier warning signs and do nothing?

A real root cause analysis leads to specific corrective actions with real owners and deadlines attached. “Retrain staff” rarely covers it on its own. Stronger corrective actions revise the actual workflow, change supervisory review, or add recurring compliance audits at set intervals.

Verify that corrective action works

A corrective action plan isn’t complete the moment it’s approved. It’s complete once the organization can show the new control was implemented, understood, and actually effective in practice.

Set real follow-up expectations. If the event involved missed observation rounds, audit the observation records directly and validate staff practice firsthand rather than trusting the paperwork alone. If it involved a breakdown in escalation, actually test the after-hours notification chain instead of assuming staff already know how to use it.

Leadership should review these findings at the right quality and governing-body level. That review is what shows a regulator the organization did more than just close a file and move on.

Common mistakes that create additional exposure

The most damaging reporting failures tend to be entirely avoidable: delayed escalation, altered records, or a corrective action plan that never got verified at all.

Another common mistake is treating a sentinel event purely as a personnel issue. Individual accountability might genuinely be necessary, but it should never replace a real system-level analysis. Regulators want to see that the organization actually examined supervision, training, and any recurring risk pattern underneath the single event.

For multi-site operators, consistency matters even more. Each location may face different state requirements, but the organization should still run one core incident-response framework, with local requirements layered on top rather than a completely separate, confusing process at every single facility.

When reporting support is needed

A sentinel event can put a license, an accreditation status, and an operating future all at risk at once. If your organization is responding to a serious event or a threat to licensure, don’t lean on a generic policy pulled from a binder. Build a response that actually matches the event, the evidence, and the rules governing your specific operation.

For the specific behavioral health standards a sentinel event may implicate, see What Do Joint Commission Behavioral Health Standards Require?

Continued Compliance helps healthcare organizations assess reporting obligations, strengthen incident-response systems, and regain control when regulatory trouble threatens operations. You can reach us at (213)864-8554.

Frequently Asked Questions