Behavior Data Collection for Manifestation Determination

D.K.’s manifestation meeting was in four school days. Compliance had the dean’s packet: dates, witness statements, the hallway camera still. My folder had something else—whether the break card was on his desk in science the week before the push, how many times a counselor offered the cool-down pass during unstructured transitions, and a two-week frequency log for defined verbal escalation that matched his IEP goal line, not the office discipline code. The facilitator needed evidence for §300.530(e)—disability relationship and implementation failure—not a character sketch.

Behavior data collection for manifestation determination is the timed evidence pull teachers and case managers run when a disciplinary removal may be a change of placement: dated logs, setting-specific counts, BIP fidelity notes, and disability-linked observations the IEP team must review within 10 school days (34 CFR §300.530(e)). The meeting itself—two questions, parent participation, outcomes—is in IEP meeting manifestation determination. This article is what you collect and organize before parents sit down.

Federal rules require the team to consider all relevant information in the student’s file, including the IEP, teacher observations, and information supplied by the parents (34 CFR §300.530(e)(1)). Behavior data does not answer the vote for you. It keeps question one (disability relationship) and question two (direct result of failure to implement the IEP, including behavior supports) grounded in dates and settings, not hallway memory.

I am a case manager, not a lawyer. District manifestation forms, police notification, and who may present discipline summaries vary by LEA—confirm FERPA sharing before you email raw sheets. Pair this guide with IEP meeting behavior plan requirements, behavior intervention plan data collection, and ABC data collection: a complete guide when antecedent patterns matter.

Manifestation data vs discipline forms vs BIP monitoring vs annual packets

Teams dump referrals into the manifestation folder and wonder why question two stalls.

Short answer for snippets: Behavior data collection for manifestation determination means assembling dated, setting-labeled evidence—implementation logs, goal-aligned counts, observations tied to present levels, and parent input—so the IEP team can answer both manifestation questions from the file, not from debate.

What to collect for each federal question

The team must document answers to both tests in §300.530(e). Your clipboard should map to one or both columns.

Question 1 — Disability relationship: Was the conduct caused by, or did it have a direct and substantial relationship to, the child’s disability?

Collect:

• Present levels language you can point to—executive function, emotional regulation, sensory needs—without inventing a diagnosis in the room.
• Pattern data before the incident: escalation frequency, transition failures, peer conflict in named settings (hallway between periods, unstructured lunch).
• Antecedent summaries from ABC data collection or behavior observation form examples—crowding, noise, task difficulty, social conflict.
• Related service notes (counseling, BCBA) that describe regulation skills in context, not generic “good session.”

Question 2 — Implementation failure: Was the conduct the direct result of the district’s failure to implement the IEP, including behavior supports?

Collect:

• Strategy checklist per setting: break offered, modified work provided, check-in completed, BIP page visible to staff.
• Training gaps with dates—gen-ed teacher never received BIP copy, sub had no crisis steps.
• Service minutes delivered vs IEP (counseling, SLP, resource) for the weeks before removal.
• Fidelity tallies from the signed BIP data plan—same verbs as behavior data collection for BIP.

D.K.’s team spent forty minutes on question two because science had no card on the desk and the hallway aide did not know the de-escalation script in his BIP. That is implementation evidence. A dean’s “he knew better” line is not.

Timeline: when collection starts (the 10-school-day clock)

Manifestation reviews are scheduled, not discovered at the coffee cart.

While the review is pending, the student must still receive services toward IEP goals (34 CFR §300.530(d)). Log what instruction and behavior support actually happened during removal—those rows matter if question two reopens after return.

Minimum packet: seven items case managers should request from teachers

Parents remember implementation, not jargon.

1. Current IEP and BIP with strategies highlighted—what you were supposed to do in the setting where conduct occurred.
2. Implementation log (daily or per-incident): strategy name, Y/N, staff initials, date.
3. Goal-aligned counts for 4–6 weeks before the incident—same definition as the portal goal; see frequency data sheet examples if you need a row model.
4. Incident timeline aligned to the discipline file: time, setting, antecedent, adult response—without copying confidential witness names into your teacher log.
5. Parent/student input routed to the case manager: “overwhelmed before lunch,” medication change, sleep—dated.
6. Training record or honest note: who received BIP training and when.
7. Services delivery summary: counseling minutes, check-ins, related service sessions in the lookback window.

If hypothesis is still unknown after structured collection, flag for post-meeting FBA work—functional behavior assessment templates belong in the follow-up plan, not as a substitute for answering implementation with “we think he’s manipulative.”

Worked example: D.K., hallway push, co-taught science + transitions

Context: ADHD and anxiety in present levels; BIP includes break card, pre-transition check-in, and reduced hallway time when possible. Removal followed a push during a crowded passing period after a failed negotiation with a peer.

What we did not rely on: Office referral code alone, clip chart colors, “he’s been fine all year” from one teacher.

What we brought:

At the table we separated disability-related regulation (question one) from missed BIP steps (question two). The hallway aide had never seen the de-escalation steps. Science had dropped the card after a seating change. Those rows drove a manifestation finding on implementation failure and an immediate BIP revision with hallway training—not a lecture about “accountability.”

After adjournment, the same definitions fed sample IEP progress reports for behavior goals during a messy reporting quarter—see behavior data collection for progress reports for parent-facing language.

How to present behavior data without drowning the room

Use a dedicated evidence block on the agenda—see IEP meeting agenda template and the flow in IEP meeting manifestation determination.

Do:

• Lead with one timeline slide: incident date, settings, what the IEP/BIP required that week.
• Show implementation separate from outcome—strategies missed vs counts rising.
• Cite present levels phrases the team already adopted; do not diagnose on the fly.
• Invite parents to add information before the team votes.

Avoid:

• Reading every discipline narrative aloud.
• Mixing discipline codes with goal definitions without a legend.
• Arguing “character” when the federal question is relationship to disability and failure to implement.

Auditors and hearing officers read dates. Passion without rows wastes the ten-day window.

Common mistakes with manifestation behavior data

1. Meeting-only scramble — starting tallies after the compliance email instead of using existing BIP logs.
2. Definition drift — referral says “defiance,” goal says “work refusal,” BIP says “noncompliance.”
3. Wrong setting — science graphs when the conduct was in the hallway; still document hallway plan gaps.
4. Discipline-only packet — no IEP, no BIP fidelity, no service minutes.
5. FBA dump — 40 ABC pages with no summary tying antecedents to the incident week.
6. Anonymous blame — “the sub didn’t read the BIP” without dates and names in the internal file (share with FERPA rules).
7. Forgetting removal weeks — no log of what FAPE looked like during alternative placement.

When safety crises trigger separate procedures, bring dated implementation notes to the reconvene compliance schedules—same definitions as before the incident.

What I’d do Monday

1. Ask whether D.K.’s removal triggered a change of placement and confirm the 10-school-day manifestation clock with compliance.
2. Open his IEP, BIP, and the goal measurement lines—highlight verbs collectors must match.
3. Start a manifestation folder: implementation log template, 30-day trend, parent input log, training note.
4. Email each setting one sample row and a turn-in deadline 48 hours before the meeting.
5. Block 30 minutes to write a one-page teacher summary—strategies used, strategies missed, dates—before anyone asks in the meeting.

Behavior data collection for manifestation determination is not about winning a debate. It is about giving the IEP team a file that answers federal questions fairly—and giving D.K. a return plan that matches what the data said was missing.

---

Draft the narrative, not your Sunday. Manifestation weeks eat planning time; quarterly portals do not pause. If your session notes are done but the progress narrative box is still empty after D.K. returns, try IEP Progress free—paste de-identified weekly notes, get a first draft of the narrative in minutes, edit every line, then copy into Frontline, PowerSchool, or your LEA system. Free plan: three narratives a month, one student profile, initials only. No credit card.

FAQ

What is behavior data collection for manifestation determination?

It is the timed assembly of dated behavior evidence—implementation logs, goal-aligned counts, summarized ABC patterns, observations tied to present levels, and parent input—that the IEP team reviews when deciding whether conduct was related to disability or caused by failure to implement the IEP under §300.530(e).

How is manifestation data different from discipline incident reports?

Discipline reports describe rule violations and consequences. Manifestation data must also show IEP/BIP implementation, disability-linked patterns, and goal-aligned counts using the same definitions as the file—not referral codes alone.

How far back should teachers pull behavior data for a manifestation review?

There is no single federal day count. Practical teams use 4–6 weeks of goal/BIP monitoring before the incident, plus implementation logs for the days immediately surrounding conduct, and any parent information already shared. Summarize longer ABC work unless the team is still in active FBA.

What data best supports the implementation-failure question?

Dated fidelity logs: which BIP strategies were in place per setting, training dates, service minutes delivered, and honest notes when staff did not have the plan or tools. Question two is about district implementation, not student likability.

Should I bring raw ABC sheets to the manifestation meeting?

Bring summarized antecedent-consequence patterns tied to the incident context unless raw ABC is the named measure on a goal. A one-page pattern summary beats forty sticky notes in front of parents.

Who compiles the behavior packet for manifestation determination?

Case managers or compliance compile the file; teachers and related service providers supply setting-specific logs and observations. Teachers should not wait to be asked—send the one-page summary early when the clock starts.

Sources

• 34 CFR §300.530 — Discipline procedures (manifestation)
• IDEA — Discipline / manifestation (300.530)
• 34 CFR §300.322 — Parent participation
• Center on PBIS — team-based behavior support and data use

Rachel Kim is a special education teacher and case manager. Student examples use initials only (e.g., D.K.). Updated October 3, 2026. General guidance, not legal advice.