Seclusion and Restraint Incident Reporting and Debrief Form

Use this form after any seclusion or restraint event involving a student, including incidents that require parent or guardian notification, administrator review, or state reporting. It is meant to capture the facts of the event, not to justify the intervention after the fact. If your district has separate behavior, safety, or restraint logs, this template can serve as the incident record that ties them together.

The staff member who directly observed or participated in the incident should usually complete the initial report, with review by an administrator or designated compliance lead. If multiple staff were involved, one person should enter the core timeline and others can add supporting details through the debrief section. Keep the reporter role field specific so the record shows who had first-hand knowledge.

Complete it as soon as practical after the event, while the timeline, actions taken, and notification details are still accurate. The notification fields should be filled in the same day whenever possible, especially when policy requires prompt parent or guardian contact. The debrief section can be completed later, but it should still be linked to the original incident record.

Yes, it is structured to support school compliance workflows by documenting the incident, de-escalation attempts, duration, monitoring, injuries, notifications, and debrief follow-up. It helps create an audit trail for internal review and any required state or district reporting. You should still align the form with your local policy, since reporting triggers and retention rules vary by jurisdiction.

Common issues include vague behavior descriptions, missing start and end times, and leaving out the de-escalation attempts that were tried before seclusion or restraint. Another frequent problem is recording the event but not documenting who was notified and when. The form works best when staff use concrete, observable language and complete every applicable section.

Yes, you can tailor the fields for elementary, secondary, special education, or alternative program settings. Many schools add conditional logic for restraint type, injury follow-up, or whether an incident involved a classroom, hallway, bus, or sensory space. You can also adjust the debrief prompts to match district policy or team roles.

An ad-hoc note or email often misses key details, uses inconsistent wording, and makes later review harder. This template standardizes the fields that matter for compliance, including the timeline, notifications, and debrief outcomes. It also makes it easier to review patterns across incidents instead of piecing together information from multiple messages.

The debrief should capture who participated, what was learned, and what preventive actions will be taken next time. It is useful to note environmental triggers, supervision changes, staff supports, or behavior plan updates that may reduce recurrence. The goal is to turn the incident into a documented follow-up plan, not just a retrospective summary.