When something happens, write it once.
Log an incident in minutes, route it to the right people, and close it with a review — a defensible record from the event to its resolution.
Every incident closes the same way: reviewed.
Any staff member records what happened — type, severity, people involved — from any device.
Severity decides who's alerted, instantly — supervisor, clinical, or leadership.
Actions taken are documented as they happen, tied to the residents involved.
A designated reviewer signs off — with follow-ups assigned if anything needs to change.
The closed incident lives on the record — searchable, reportable, defensible.
The right people know, at the right moment.
Define your incident types and severity levels once. From then on, a medication error wakes the clinical director; a maintenance issue doesn't. No group texts, no guessing who to call.
An incident isn't a form — it's part of the story.
Incidents attach to the clinical record of every resident involved, in context with their care.
Every log, edit, and sign-off is audit-trailed — who wrote what, and when.
Incident counts and categories flow to state and funder reports without a re-count.
Questions, answered.
Any staff member with access to the program — house managers on tablet, counselors at a desk. Filing is deliberately simple; review is where rigor lives.
Amendments are allowed, deletions aren't. Every version is kept with its author and timestamp, so the record shows exactly how the account evolved.
Reportable categories can be flagged in your configuration, and the export carries the fields your state requires — you submit through your state's channel with the record already assembled.
No. Incidents follow the same role-based access as the rest of the record — staff see what their role needs, and sensitive incidents can be restricted further.
Documented, reviewed, closed.
We'll log a sample incident with you and walk it through notification, review, and sign-off.