Manifestation Determination Review Documentation Form
This Manifestation Determination Review Documentation Form captures the team’s review of a student incident, the disability and support context, and the final determination before discipline moves forward.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: K 12 Public Schools · K 12 Private Schools · Special Education Services · School District Administration
Overview
This Manifestation Determination Review Documentation Form is used to record the team’s review of a student incident before discipline is finalized. It captures the submission purpose, privacy acknowledgment, and consent to record; the student and case details; the incident and proposed discipline; the student’s IEP or 504 status; the disability and support review; the team’s reasoning; and the follow-up actions and sign-off.
Use it when a student with an IEP or Section 504 plan is facing discipline and the school needs a clear written record of whether the conduct was directly related to the disability or whether a failure to implement the plan contributed to the incident. The form is especially useful when multiple staff members need to align on the facts, document the determination, and preserve an audit trail for later review.
Do not use it as a general behavior log or for routine classroom corrections that do not require a manifestation review. It is also not the right template if the school has no disciplinary action under consideration or if the case does not involve disability-related protections. Keep the content factual, avoid unnecessary PII, and use conditional logic so staff only see the fields that apply to the student’s case.
Standards & compliance context
- The form supports data minimization by collecting only the student, incident, disability, and determination fields needed for the review.
- The privacy disclosure and consent-to-record section helps staff explain how PII will be used, stored, and shared within the school process.
- Accessible field labels, logical tab order, and clear validation support WCAG 2.1 AA expectations for public-facing or parent-accessible forms.
- The disability and support review section helps teams document whether accommodations or services were implemented before discipline decisions are made.
- The audit trail fields support internal accountability by showing who reviewed the case, when the meeting occurred, and what follow-up actions were assigned.
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
Submission Notice and Privacy Disclosure
This section sets expectations for how the review record will be used and explains any consent or privacy language before PII is entered.
- Purpose of Submission
- Privacy and Data Minimization Acknowledgment
- Consent to Record Review Findings
Student and Case Identification
This section ties the review to the correct student and incident so the record can be audited and retrieved later without confusion.
- Student Full Name
- Student ID
- School Name
- Grade Level
- Case Number
Incident and Discipline Context
This section captures the facts of the incident and the proposed discipline that triggered the manifestation review.
- Date of Incident
- Location of Incident
- Conduct Category
-
Incident Summary
Briefly describe what happened, using observable facts only.
- Proposed Discipline
Disability and Support Review
This section documents the student’s disability status and whether accommodations, services, or behavior supports were in place at the time.
- Does the student have an IEP?
- Does the student have a Section 504 plan?
- Disability Category
-
Relevant Accommodations, Supports, or Services
List only supports relevant to the review, such as accommodations, behavior supports, or related services.
- Was a behavior intervention plan or behavior support plan in place?
Team Review and Determination
This section records the team’s analysis of causation and implementation issues, which is the core decision point of the form.
- Was the conduct caused by, or did it have a direct and substantial relationship to, the student's disability?
- Was the conduct the direct result of the school's failure to implement the IEP or Section 504 plan?
-
Team Reasoning
Summarize the facts, records reviewed, and rationale for the determination.
- Manifestation Determination Outcome
Follow-Up Actions, Sign-Off, and Audit Trail
This section assigns next steps, records the meeting outcome, and preserves the sign-off needed for accountability.
- May the proposed discipline proceed?
- Required Follow-Up Actions
-
Responsible Staff
List the staff roles responsible for each follow-up action.
- Team Meeting Date
- Team Chair Signature
How to use this template
- 1. Start by entering the submission purpose, privacy acknowledgment, and consent-to-record language so staff understand how the review record will be used and stored.
- 2. Fill in the student and case identification fields with the minimum necessary details, using structured fields for name, ID, school, grade, and case number.
- 3. Record the incident facts, including date, location, conduct category, incident summary, and proposed discipline, before the meeting begins or while the facts are still fresh.
- 4. Complete the disability and support review by selecting whether the student has an IEP or 504 plan, noting the disability category, and documenting relevant accommodations, services, or behavior plans.
- 5. Capture the team’s determination, required follow-up actions, responsible staff, meeting date, and chair signature, then confirm whether discipline may proceed based on the final review.
Best practices
- Use conditional logic so staff only see IEP, 504, or behavior-plan fields that apply to the case.
- Keep the incident summary factual and time-bound, and avoid subjective labels that do not help the team determine causation.
- Mark required fields only where the record cannot be complete without them, and leave optional fields available for incomplete cases.
- Use a date picker for incident and meeting dates, a multi-select for conduct categories, and structured fields for staff names and roles.
- Document whether the behavior plan or accommodations were actually implemented before the incident, not just whether they existed on paper.
- State what happens after submission so staff know whether discipline may proceed, whether a re-review is needed, or whether follow-up actions must be completed first.
- Keep the form accessible with clear labels, keyboard-friendly controls, and validation messages that explain how to fix missing or invalid entries.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this form be used?
Use this form after a disciplinary incident when the school must determine whether the conduct was a manifestation of the student’s disability before discipline is imposed. It is meant for case-by-case review, not for routine classroom incidents. If the student has an IEP or Section 504 plan, this documentation helps the team record the facts, the support review, and the final decision.
Who should complete the review and sign off?
The form is typically completed by the team chair or case manager and reviewed by the people who participated in the manifestation determination meeting. That usually includes school administrators, special education staff, general education staff, and others with relevant knowledge of the student. The chair signature and meeting date create a clear audit trail of who made the determination.
How often is this form needed?
It is used whenever a disciplinary decision triggers a manifestation determination review, not on a fixed schedule. Some students may never need it, while others may need it more than once if separate incidents occur. Each incident should be documented separately so the record matches the specific conduct, date, and proposed discipline.
What information should be included in the incident summary?
Include only the facts needed to explain what happened, where it happened, and what conduct led to the proposed discipline. Keep the language specific and neutral, and avoid adding unrelated personal details. The summary should support the team’s reasoning without collecting unnecessary PII.
How does this template support compliance and privacy?
The structure supports data minimization by collecting only the fields needed to document the review, the disability context, and the outcome. It also includes a privacy disclosure and consent-to-record field so the team can explain how the information will be used and stored. For accessibility, the form should be built with clear labels, required-versus-optional fields, and accessible validation that works with keyboard and screen readers.
What are the most common mistakes when using this form?
Common mistakes include leaving the reasoning too vague, skipping the review of whether the behavior plan was implemented, and marking every field as required even when some details are not available. Another frequent issue is using free-text fields where structured fields would be clearer, such as a date picker for the meeting date or a multi-select for conduct category. The form should also state what happens after submission so staff know whether discipline may proceed or follow-up actions are required.
Can this template be customized for district workflows?
Yes. Districts can adjust the conduct categories, add local routing fields, or include conditional logic for IEP versus 504 cases. You can also add role-based assignment for the chair, case manager, or administrator, plus an audit trail field if the form needs to support internal review. Keep the core review fields intact so the determination remains consistent across cases.
Does this replace the team meeting or the written record?
No. This template documents the meeting and the determination; it does not replace the actual review process. The form is the written record that captures the facts, the team’s reasoning, and the follow-up actions. It works best when completed during or immediately after the meeting so the record is accurate and complete.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
Compare 11 frontline hiring platforms on mobile apply, automated screening, and onboarding handoffs to find the right fit for hourly and shift-based workforces.
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
Spring '26 brings AI Course Creation, Power BI-connected AI Agents, and smarter content governance to MangoApps. See what's new across the platform.
Ready to use this template?
Get started with MangoApps and use Manifestation Determination Review Documentation Form with your team — pricing built for small business.
