Loading...
compliance

Manifestation Determination Review Documentation Form

Document the team review of whether a student's conduct was a manifestation of their disability before discipline is imposed. Capture incident details, supports reviewed, team determination, and follow-up actions in one record.

Fill it now — Free Get Started
Customize with AI →

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: K 12 Education · Special Education · School Administration

Overview

This Manifestation Determination Review Documentation Form records the team’s review of a student incident before discipline is finalized. It captures the incident context, whether the student has an IEP or 504 plan, the supports and behavior interventions reviewed, the team’s determination, and any follow-up actions.

Use this template when a school needs a clear, consistent record of the meeting and decision-making process. It is especially useful for administrators, special education staff, and case managers who need to document what was considered and why the team concluded that discipline may or may not proceed. The form also creates an audit trail that can be stored with the student’s record.

Do not use this template as a general behavior incident report or a substitute for the underlying disciplinary record. It is also not the right form if no disability-related review is required. Keep the submission focused on the minimum necessary information: the incident, the supports reviewed, the team rationale, and the next steps. If your district handles IEP and 504 reviews differently, use conditional logic so only the relevant fields appear. A clear submission notice and what-happens-after-submit line help staff and families understand the process and reduce follow-up confusion.

Standards & compliance context

  • Limit collection to the minimum necessary information needed to document the review and support the decision-making record.
  • If the form includes student identifiers or other PII, add a disclosure explaining how the information will be used and who can access it.
  • Keep the record aligned with district discipline procedures and special education documentation requirements so the audit trail is complete.
  • If your workflow includes parent or guardian communication, document the notice and follow-up in a way that matches your local process.

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

This section tells staff and families what the form is for and what will happen after it is submitted.

  • Review notice
  • What happens after I submit?

Student and Incident Details

These fields establish the factual record of who was involved, what happened, and what discipline is being considered.

  • Student ID (required)

    Use the internal student identifier if available. Avoid entering unnecessary personal details.

  • Date of incident (required)
  • Incident summary (required)

    Briefly describe the conduct being reviewed, using observable facts only.

  • Is discipline currently pending? (required)
  • Proposed discipline action

Disability and Support Information

This section captures the student’s plan status and the supports the team reviewed before making a decision.

  • Does the student have an IEP? (required)
  • Does the student have a Section 504 plan? (required)
  • Supports reviewed by the team (required)

    Select the records or supports considered during the review.

  • Were behavior supports in place at the time of the incident? (required)

Manifestation Determination Questions

These questions document the core legal and procedural review that drives the team’s determination.

  • Was the conduct caused by, or did it have a direct and substantial relationship to, the student's disability? (required)
  • Was the conduct the direct result of the school's failure to implement the IEP? (required)
  • Team rationale (required)

    Summarize the facts, records, and discussion that support the team’s determination. Avoid unnecessary PII.

Team Determination and Follow-Up

This section records the outcome, whether discipline may proceed, and the actions that should happen next.

  • Final determination (required)
  • May the proposed discipline proceed? (required)
  • Required follow-up actions (required)
  • Follow-up notes

    Add any deadlines, responsible parties, or implementation notes.

Team Attestation

This final section confirms when the meeting occurred, who documented it, and that the team’s record is complete.

  • Meeting date (required)
  • Recorded by (required)

    Enter the name or role of the staff member completing the record.

  • I confirm this record accurately reflects the team's manifestation determination review. (required)

How to use this template

  1. 1. Set up the form with the student identifier, incident date, and discipline fields preconfigured to match your district’s terminology.
  2. 2. Add conditional logic so the IEP, 504, and behavior support questions appear only when they apply to the student’s case.
  3. 3. During the meeting, enter the incident summary, the supports reviewed, and whether the team found a link between the conduct and the disability or a failure to implement the plan.
  4. 4. Record the team’s determination, note whether discipline may proceed, and list any follow-up actions such as plan review, parent communication, or additional supports.
  5. 5. Save the meeting date, recorded-by name, and team attestation so the completed form functions as a reliable audit trail.

Best practices

  • Use conditional logic to hide 504, IEP, or behavior-plan fields that do not apply so the form stays focused during the meeting.
  • Keep the incident summary factual and brief, and avoid adding opinions that are not supported by the team’s review.
  • Mark only the truly required fields as required so staff can complete the form without unnecessary friction.
  • Document exactly which supports were reviewed, including behavior plans, accommodations, and implementation notes, rather than writing a generic summary.
  • Capture the team rationale in plain language that explains how the determination was reached, not just the final outcome.
  • Include a clear what-happens-after-submit line so staff know who receives the record and what follow-up occurs next.
  • Use field types that match the data, such as a date picker for meeting and incident dates and multi-select for supports reviewed.

What this template typically catches

Issues teams running this template most often surface in practice:

The team determination is recorded without explaining the rationale behind it.
The form omits whether the student’s IEP, 504 plan, or behavior supports were actually reviewed.
Staff use free-text fields for dates or discipline types, which makes records inconsistent and harder to search.
Too many fields are marked required, slowing down completion during a live meeting.
The form does not capture whether the plan was implemented as written before the incident.
Follow-up actions are left blank, so the next steps are unclear after the meeting ends.

Common use cases

Middle school special education coordinator
A coordinator documents a manifestation review after a suspension referral and needs a clean record of the incident, supports reviewed, and team decision. The form helps keep the meeting notes aligned with the student file and district process.
High school assistant principal
An assistant principal uses the template during a discipline meeting to capture the facts, the IEP or 504 context, and whether discipline may proceed. The completed form becomes the official record for follow-up and internal review.
District special education compliance team
A district team standardizes manifestation review documentation across schools so each case includes the same core fields and attestation. This makes audits easier and reduces missing information.
School psychologist and case manager
A psychologist and case manager use the form to document the supports reviewed, the behavior history considered, and the rationale behind the team’s conclusion. It helps ensure the record reflects the full discussion, not just the final outcome.

Frequently asked questions

When should this form be used?

Use it when a school team needs to document a manifestation determination review before disciplinary action moves forward. It is typically used after a disciplinary incident involving a student with an IEP or, in some cases, a 504 plan. The form helps capture the facts reviewed, the team’s reasoning, and the final determination in one place. It is not meant for routine behavior notes or general student discipline logs.

Who should complete the form?

A case manager, special education coordinator, administrator, or other designated team member usually records the meeting details. The actual determination should reflect the team review, not one person’s opinion. The recorded-by field helps show who documented the outcome and supports an audit trail. If your district assigns a specific role for this process, customize the form to match that workflow.

Does this form apply to students with a 504 plan as well as an IEP?

Yes, if your district uses a similar review process for students with a 504 plan, the form can be adapted to document that review. The template includes separate fields for IEP and 504 status so the team can record the correct context. Keep the language aligned with your district policy and applicable procedures. If the process differs by plan type, use conditional logic to show only the relevant fields.

What should the team review before making the determination?

The team should review the incident summary, the student’s disability-related information, and the supports or behavior interventions already in place. It should also check whether the IEP or behavior plan was implemented as written. The rationale field should explain how the team reached its decision based on those facts. Avoid vague statements that do not connect the incident to the reviewed supports or the student’s plan.

What happens after the form is submitted?

After submission, the record should be routed to the appropriate school or district staff for follow-up actions, documentation, and any required next steps. The form includes a submission notice and a what-happens-after-submit field so families and staff know what to expect. This helps reduce confusion and supports a clear audit trail. If your process includes notifications, meetings, or service adjustments, add them to the follow-up section.

How can we customize the template for our district?

You can tailor the discipline options, team roles, and follow-up actions to match your local process. Many districts add conditional logic so the form expands only when an IEP, 504 plan, or behavior support plan is present. You can also adjust the wording to reflect your internal terminology while keeping the core documentation fields intact. Keep required fields limited to what the team truly needs to complete the review.

What are the most common mistakes when using this form?

Common mistakes include leaving the rationale too vague, skipping the supports reviewed, and failing to record whether the IEP or behavior plan was implemented. Another issue is marking too many fields required, which can slow down completion and create incomplete records. Teams also sometimes forget to document what happens after the decision, which makes follow-up harder to track. Use clear field types and progressive disclosure so the form stays usable during a real meeting.

Can this form be integrated with our student information system or case management tools?

Yes, the template can be connected to a student information system, special education case management platform, or document repository. Common integrations include pre-filling student identifiers, storing the completed record, and routing the submission to the right staff. If you integrate it, make sure the data mapping preserves the audit trail and does not expose unnecessary PII. Use only the fields needed for the review to support data minimization.

Related templates

Forms

Industry Certification Attainment Tracking Log (CTE Concentrators)

Track each CTE concentrator’s industry-credential attainment in one log built for Perkins V repor...
Forms

Industry Certification Attainment Tracking Log (CTE Concentrators)

Track each CTE concentrator’s industry credential, verification method, and reporting year in one...
Forms

Seclusion and Restraint Incident Reporting and Debrief Form

Log each seclusion or restraint incident, required notifications, and the post-incident debrief i...
Forms

Provisional Immunization Admission Tracking Record

Track conditionally admitted students who are mid-series on required immunizations, with dose sta...
Forms

Vision and Hearing Screening Results and Referral Notification Form

Records school vision and hearing screening results, then documents parent or guardian referral n...
Inspections

49 CFR Part 392 School Bus Operations Compliance Audit

Audit school bus driving practices against 49 CFR Part 392 with a route-by-route checklist for pr...
Sop

Pediatric Dysphagia Feeding Safety Plan SOP

A pediatric dysphagia feeding safety plan SOP for verifying the feeding plan, preparing the envir...
Hr Policy

Anti-Harassment & Anti-Discrimination Policy

Anti-Harassment & Anti-Discrimination Policy template for defining prohibited conduct, reporting ...

Go deeper on the topic

Related concepts
  • Lockout/Tagout
    Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
  • Job Hazard Analysis
    Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
  • Near-Miss Reporting
    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
    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...
Related guides

Ready to use this template?

Get started with MangoApps and use Manifestation Determination Review Documentation Form with your team — pricing built for small business.

Get Started
Customize with AI →