Manifestation Determination Meeting Notice: Template and the Ten-Day Rule

Nobody in this worked example made a bad decision. The threshold was crossed by a transport office that did not know the count, and it was crossed two removals after the point where a pattern analysis should already have been running. Note that the two ISS entries are counted differently, because the difference is what was delivered on the day, not what the room is called. Reconcile the discipline log, the transport log and the front-office sign-out sheet monthly, and flag at seven.

The meeting invitation

[DISTRICT LETTERHEAD] — NOTICE OF MANIFESTATION DETERMINATION REVIEW MEETING

[DATE]

Dear [GUARDIAN NAME],

[STUDENT NAME] has now been removed from school for [N] school days this year. Because that is more than ten cumulative days, federal special education law requires the district to hold a meeting called a manifestation determination review before any further removal takes effect.

What the meeting decides. Two questions, and only two. First: was the conduct caused by, or did it have a direct and substantial relationship to, [STUDENT FIRST NAME]’s disability? Second: was the conduct the direct result of the district’s failure to implement the IEP? If the answer to either question is yes, the conduct is a manifestation of the disability and the disciplinary removal cannot proceed in the ordinary way.

You are a required member of the team that makes this decision. It is not a meeting where the district tells you an outcome.

When and where. [DAY, DATE] at [TIME], [LOCATION]. If that time does not work, call [NAME] on [PHONE] and we will find one that does, within the timeframe the law allows.

Who will attend. [NAMES AND ROLES: the district representative, the special education teacher, a general education teacher, someone able to interpret evaluation results, and any other person with knowledge or expertise about [STUDENT FIRST NAME]]. You may bring anyone you choose, including an advocate or attorney.

What we will review. [STUDENT FIRST NAME]’s IEP, teacher observations, any recent evaluations, the behaviour incident records, and any information you provide. If you have reports from doctors, therapists or anyone else who knows [STUDENT FIRST NAME], please bring them or send them to [EMAIL] before [DATE].

Your procedural safeguards are enclosed. If you would like them explained, call [NAME] on [PHONE]. An interpreter will be provided at no cost on request.

[NAME], [TITLE] — [PHONE], [EMAIL]

SMS companion. [DISTRICT]: a meeting about [STUDENT]'s IEP and recent removals is set for [DATE] at [TIME]. Your participation is required by law. Details posted. Call [PHONE].

The two outcome letters

When the behaviour was a manifestation. The letter must state the determination, that the disciplinary removal will therefore not proceed, that the student returns to the placement from which they were removed unless the team agrees otherwise, and what the team will do next — conduct a functional behavioural assessment and implement a behaviour intervention plan, or review and modify an existing plan.

The team determined that the conduct on [DATE] was a manifestation of [STUDENT FIRST NAME]’s disability. Accordingly, the removal recommended on [DATE] will not proceed and [STUDENT FIRST NAME] will return to [PLACEMENT] on [DATE]. The team will [CONDUCT AN FBA BY DATE / REVIEW THE EXISTING BIP ON DATE] and will meet again on [DATE] to agree the plan. This determination does not mean the conduct was acceptable, and the plan will address it directly.

That last sentence prevents a great deal of misunderstanding in both directions.

When it was not. The letter must state the determination and the reasoning, that the disciplinary consequence proceeds as it would for any other student, and — critically — that services continue.

The team determined that the conduct on [DATE] was not a manifestation of [STUDENT FIRST NAME]’s disability. The team’s reasoning: [SUMMARY]. The disciplinary consequence will therefore proceed: [DESCRIBE, WITH DATES]. During the removal, [STUDENT FIRST NAME] will continue to receive educational services enabling continued participation in the general curriculum and progress toward IEP goals. Those services will be [SPECIFIC: SUBJECTS, HOURS, LOCATION, STAFF]. The IEP team determined this on [DATE]. If you disagree with this determination you may request a due process hearing; the procedural safeguards enclosed explain how, and an expedited hearing is available.

The specificity of the services paragraph is what distinguishes a defensible letter. “Services will be provided” is not a plan.

Section 504, in parallel

Most templates online conflate IDEA and Section 504, and the differences matter.

• The concept exists in both. Under Section 504, a significant change in placement — commonly understood as more than ten consecutive days, or a pattern of shorter removals — requires a group of persons knowledgeable about the student to determine whether the conduct was caused by the disability before the removal proceeds.
• The team is defined differently. IDEA names required participants; 504 requires a knowledgeable group, which in practice means the 504 team plus anyone with relevant expertise.
• The two-question test is IDEA’s. The 504 analysis is framed as causation rather than as IDEA’s two limbs, though districts commonly apply the same structure.
• Services during removal differ. IDEA requires services from the eleventh cumulative day. Section 504 does not carry the same explicit services obligation, though other obligations may apply.
• Dispute routes differ. IDEA offers due process including an expedited hearing; 504 disputes route through the district’s 504 grievance process and to the Office for Civil Rights.

The practical rule: if a student has a 504 plan and removals are accumulating, run the analysis rather than assuming the ten-day machinery does not apply to you. Districts get into trouble by treating 504 students as though the discipline code operates on them unmodified.

Scheduling it, and the record you keep

The meeting has to happen within a short window of the decision to remove, which means the notice competes with a family’s work schedule under time pressure. Three habits: offer two time options in the first contact rather than one, call as well as writing, and document every scheduling attempt, because a meeting held without the parent needs a record of genuine efforts to arrange a mutually agreeable time.

Kastr’s role here is narrow and worth stating precisely. It sends and it records: every notification writes to a per-district hash-chained append-only audit log, so the scheduling attempts, their channels and their outcomes are evidenced rather than remembered. Contact points carry validation and consent state independently, so you can see which number has actually been confirmed before you rely on it. Retention defaults are published per record class, with student PII, guardian and staff records classed separately.

What it does not do: there is no rule engine that notices a student has crossed seven cumulative days and prompts you, no SIS integration that reads your discipline log, and no configurable retention enforcement job behind the published defaults. The count and the trigger remain a human process, and any vendor telling you otherwise should be asked to demonstrate it with live data.

Questions people actually ask

Related