What to Do When School Restraint or Seclusion Happens Repeatedly

Lock the events and exposure

Define the start and end dates, school days attended, locations, programs, and event definition. Reconcile notices, incident records, student reports, health records, attendance, and video status. Count one event once and preserve linked documents. Report events per exposed school day or relevant opportunity alongside raw counts when that denominator is valid.

Look for missed safeguards and services

Compare prevention, AAC, health information, trained staff, thresholds, monitoring, release, notice, and recovery across events. Track classroom removals and educational services separately. The Department discipline Q&A explains when removal patterns and other IDEA discipline duties may matter. Verify current eligibility, state law, local policy, and facts.

Request higher-level review

Ask who reviews recurrence outside the immediate team, which state or district reporting applies, whether an IEP or Section 504 meeting is needed, and which complaint or appeal routes exist. The OCR restraint and seclusion page identifies disability discrimination concerns and examples of remedies. Qualified legal or advocacy support can address case-specific rights.

Track prevention to verified use

For every corrective action, record the setting, owner, deadline, interim safeguard, training or resource, implementation observation, student feedback, and recurrence window. A revised plan or completed training is an input. Validate whether communication stayed available, staff used the support, and the unsafe event pattern changed.

Prepare an escalation packet

When repeated school restraint or seclusion is reported, build a concise packet with the frozen event table, attendance and exposure, injuries and medical care, AAC access, notices, educational services, plan versions, preventive supports, prior corrections, and recurrence results. State the decision requested from each school, district, disability-rights, medical, or legal owner. Include the student's account and desired changes. Ask for written interim safeguards while review proceeds. Keep urgent protective action separate from longer complaint or meeting timelines, and update the packet as new events occur without changing the original cohort. Date every addition and preserve the prior version. Mark each new event and immediate response separately.

Build one controlled event record

Create a restricted repeated-event review for event, exposure period, duration, setting, staff, support, injury, medical response, notice, removal, service, plan state, correction, and recurrence. Keep original school, health, student, family, witness, video, device, and provider evidence separately attributed. Record the governing source and event-date version, responsible owner, current state, action, due date, correction, and closure evidence.

For this repeated-event review, distinguish immediate safety, event classification, legal or policy authority, medical judgment, educational decision, private clinical review, disclosure, and family communication. One plan, signature, incident label, or completed training cannot establish every state.

Protect the student's account and ordinary access

Offer Dante speech, AAC, writing, drawing, a trusted partner, private time, and the choice to pause or decline a nonemergency retelling. Keep food, water, bathroom access, mobility, prescribed care, pain reporting, education, rest, and emergency help available. Record the student's message separately from adult interpretation.

Within the repeated-event review, the BACB Ethics Code guides covered professionals on communication, involvement, consent and assent when applicable, assessment, documentation, risk, and restrictive procedures. It does not govern schools or create legal authority for restraint or seclusion.

Ask eight record-specific questions

Use these questions for the repeated-event review:

• What exactly happened, and which sources support each fact?
• Which definition, policy, law, and version apply to the event?
• What immediate health, communication, and protective actions occurred?
• Who had authority, training, and responsibility for each step?
• What did the student communicate, and how did adults respond?
• Which instruction, service, plan, record, or private care was affected?
• What remains missing, disputed, overdue, or unsafe?
• Which evidence will show that a correction works?

Classify each field as complete, failed, pending, disputed, or inapplicable with a reason. A pending answer remains visible and blocks only the action that depends on it.

A fictional school-event example

Dante is fictional and involved in a six-week review after four reported events. The reviewers lock 28 event and follow-up fields and complete 21 of 28, or 75%, by the due date. Missing notices, records, health checks, communication observations, and disputed classifications stay in the denominator with an owner, age, and next action.

The repeated-event review reports evidence completeness separately from policy compliance, lawfulness, injury, educational quality, clinical quality, and Dante's experience. Reviewers preserve the original cohort and source files. They test the affected safeguard after repair instead of closing it from a meeting note alone.

Use denominators that keep harm visible

For the repeated-event review, report complete event reviews divided by all events due; timely notices divided by events requiring notice under the same rule; verified health responses divided by events requiring the defined response; communication available divided by observations due; and validated corrections divided by corrections due.

Segment repeated-event review findings by school, program, student, event type, duration, injury, service loss, support access, staff role, and governing rule. Publish raw counts with percentages. Do not compare rates built from different definitions or discovery methods. Process measures cannot prove safety, benefit, compliance, or causation.

Create a dated action and escalation path

List the event, first notice, record requests, medical care, school meetings, educational decisions, private clinical reviews, complaints, corrections, and retests in chronological order for the repeated-event review. Distinguish when something happened from when it was documented, received, interpreted, or amended.

For the repeated-event review, send each unresolved question to the owner with authority to answer it. Immediate danger, urgent medical care, mandated reporting, or protective action proceeds under the applicable emergency route. Policy, IDEA, Section 504, FERPA, licensing, payer, and legal questions follow their separate qualified routes without delaying urgent support.

Explain scope and recheck change

Give the student and authorized adult an accessible repeated-event review summary naming confirmed facts, disputed facts, decisions, owners, deadlines, interim safeguards, and review dates. The 2025 Department letter and federal resource document provide policy guidance rather than one national restraint-and-seclusion statute.

The CASP organizational overview supplies general operations and risk context, not school authority for restraint or seclusion. Evaluate repeated events under current state law, district policy, school type, disability-rights processes, health requirements, and the student's records. Reassess whenever another event, plan or setting change, medical restriction, AAC failure, or promised correction alters the pattern. This page remains draft and noindex pending named review.