Restraint Consent and Monitoring Form
Record a restraint event with consent, justification, monitoring, and release details in one audit-ready form. Use it to document what happened, why restraint was used, and what follow-up is required.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Behavioral Health · Long Term Care · Education · Corrections · Social Services
Overview
This form captures the full record of a restraint event: the date, time, location, person identifier, restraint type, and the immediate risk that led to intervention. It also documents whether the person could provide consent, whether consent was obtained, what was disclosed, and why consent was not obtained if that was the case.
Use this template when restraint is a permitted last-resort intervention and your process requires a clear justification trail. The least-restrictive review section prompts staff to record alternatives attempted and supervisor notification, while the monitoring record section supports time-based observation during the event. The release and review section closes the loop by documenting when restraint ended, whether release criteria were met, and what follow-up actions are needed.
This template is a good fit for settings that need consistent, defensible documentation and a clear audit trail. It is not a substitute for policy, training, or clinical judgment, and it should not be used to normalize restraint or collect unnecessary PII. If your workflow does not involve physical restraint, or if you only need a general incident report, this form is too specific. It is also not appropriate for situations where anonymous reporting is required, since the submitter and signature fields are designed for accountability.
Standards & compliance context
- The consent fields support informed decision-making and a documented disclosure trail, which is important when restraint is governed by policy or law.
- The least-restrictive review and alternatives fields help show that restraint was not the first option and that escalation followed a documented decision path.
- The monitoring record and release criteria support an audit trail showing ongoing observation and timely discontinuation of restraint.
- Use only the minimum necessary PII in line with data minimization principles, and avoid collecting sensitive identifiers unless your policy specifically requires them.
- If the form is used in a care or disability-support setting, keep language accessible and allow reasonable-accommodation prompts where staff or participants need them.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Event Details
This section anchors the event in time, place, and context so the record can be reviewed without guesswork.
- Date of Event
- Time Restraint Began
-
Person Identifier
Use the facility identifier or record number. Do not enter unnecessary PII.
- Location
- Type of Restraint
-
Immediate Risk or Safety Concern
Briefly describe the behavior or condition that created the need for restraint.
Consent and Authorization
This section shows whether consent was possible, what was disclosed, and why consent was or was not obtained.
- Was the person able to provide informed consent at the time?
- Consent or Authorization Obtained
- Consent Method
-
Consent Disclosure and Explanation Provided
Confirm that the risks, purpose, and expected duration were explained using the least restrictive approach available.
- Reason Consent Was Not Obtained
Least Restrictive Review
This section documents the alternatives considered before restraint and the oversight steps taken.
- Alternatives Attempted Before Restraint
- Why Was This the Least Restrictive Effective Option?
- Supervisor Notified
Monitoring Record
This section proves the person was checked at the required interval while restraint was in effect.
- Monitoring Interval (Minutes)
- Monitoring Log
Release and Review
This section closes the event by showing when restraint ended, why it ended, and what follow-up is needed.
- Date of Release
- Time of Release
-
Release Criteria Met
Confirm the person was released when safe and clinically appropriate.
- Post-Event Review / Debrief
- Follow-Up Actions
Submitter and Audit Trail
This section identifies who filed the record so the form can support accountability and later review.
- Submitted By
- Role / Title
- Signature
How to use this template
- Create the event record first by entering the date, time, location, person identifier, and the restraint type used so the incident is anchored to a specific event.
- Document the immediate risk and complete the consent section by recording whether the person could provide consent, whether consent was obtained, and what disclosure was given.
- Record the alternatives attempted and the least-restrictive review, then note whether a supervisor was notified according to your policy.
- Enter the monitoring interval and add each monitoring observation in the record field using time-stamped, factual notes.
- Complete the release section by documenting the release date and time, whether release criteria were met, and any post-event review or follow-up actions.
- Submit the form with the submitter name, role title, and signature so the record has a clear audit trail and can be routed for review.
Best practices
- Use a date picker for event and release dates, and a time field for event and release times, so staff do not enter inconsistent free text.
- Mark only the truly required fields as required, and use conditional logic to hide consent-not-obtained details unless consent was not obtained.
- Write the immediate risk and monitoring notes in factual language that describes observable behavior, not opinions or blame.
- Set the monitoring interval before the restraint begins so staff know exactly when the next check is due.
- Document at least one alternative attempted before restraint whenever policy allows, because the least-restrictive review is often the first item auditors look for.
- Capture release criteria in plain language, such as stabilized behavior or reduced risk, so the end of the event is defensible and easy to review.
- Keep the person identifier to the minimum necessary for internal tracking and avoid collecting extra PII that is not needed for the event record.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this restraint consent and monitoring form be used?
Use it any time physical restraint is considered or applied and you need a clear record of consent, immediate risk, monitoring, and release. It is meant for a specific event, not for routine behavior tracking or general incident reporting. If your process requires a separate incident report, this form should sit alongside it, not replace it.
Who should complete this form?
The staff member who initiated or directly observed the restraint event should complete the form, with supervisor review where required by policy. If the person is unable to document immediately, the form should be completed as soon as practical while details are still accurate. The submitter field and signature support accountability and an audit trail.
What if the person cannot provide consent at the time of restraint?
The form includes a specific branch for whether the person can provide consent and a reason when consent is not obtained. That helps document the basis for action without forcing a false consent record. Use the consent disclosure field to capture what was explained, and keep the language factual and time-specific.
How often should monitoring be recorded during restraint?
Monitoring should follow your organization’s policy and the person’s condition, which is why the template includes a monitoring interval field. The interval should be set before use so staff know when to check and document. Do not leave the monitoring record vague; each entry should show the time, observations, and any change in status.
What are the main compliance concerns this form helps address?
This template supports documentation of informed consent, least-restrictive review, supervision, monitoring, and release decisions. Those elements help demonstrate that restraint was used only when justified and that the person was observed throughout the event. It also creates a clearer audit trail for internal review, incident follow-up, and policy compliance.
How does this template support least-restrictive practice?
It prompts staff to record alternatives attempted before restraint and to document the least-restrictive review. That makes it easier to show that less restrictive options were considered first, rather than defaulting to restraint. The supervisor notification field also helps confirm escalation and oversight.
Can this form be customized for different settings?
Yes. You can tailor restraint types, monitoring intervals, release criteria, and follow-up actions to match your policy, facility, or program. Many teams also add conditional logic so fields appear only when relevant, which reduces unnecessary data collection and improves usability.
What should happen after the form is submitted?
After submission, the record should be reviewed by the appropriate supervisor or compliance owner, then linked to any required incident follow-up, care plan update, or corrective action. The form should clearly state who receives the submission and what happens next so staff are not left guessing. That also helps preserve the audit trail.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
MangoApps NoCode Workflow Apps let teams build, customize, and deploy employee apps without IT—automating workflows and boosting operational efficiency fast.
Ready to use this template?
Get started with MangoApps and use Restraint Consent and Monitoring Form with your team — pricing built for small business.