Behavior Data Collection for Administrators

M.T. left co-taught ELA after a loud refusal. My assistant principal walked him to the office, calmed the hallway, and called home before I finished my lunch duty. By 2 p.m. the discipline referral was complete: rule broken, consequence, parent notified. The case manager’s portal still needed goal-aligned rows—defined refusal episodes in ELA, break-card use during counseling check-ins, and whether the BIP return plan ran when he came back from the office. Two forms. Same kid. Reporting week was eleven days out. Nobody was trying to hide data. We had never written down what the office counts versus what teachers count after an admin-led cool-down.

Behavior data collection for administrators is how principals, assistant principals, and deans produce structured, goal-aligned facts when the IEP or BIP names office de-escalation, administrator contact, or return-to-class steps—without turning every referral into the legal progress record and without asking APs to score classroom goals they never see. Federal rules still require measurable annual goals and progress reporting at least as often as general education report cards (34 CFR §300.320(a)(2), 34 CFR §300.320(a)(3)(ii)). When behavior impedes learning, teams must consider positive behavioral interventions (34 CFR §300.324(a)(2)(i)). Who may access behavior logs, what belongs in education records versus confidential counseling notes, and how discipline data may be shared with special education staff vary by LEA—confirm with your special education director before you merge incident PDFs into IEP files. I am a case manager who briefs building leaders, not a lawyer.

This guide is for assistant principals, deans, case managers, and special education directors who share students like M.T. across classrooms and the main office. For teacher-run BIP logs, see behavior data collection for BIP. For turning tallies into quarterly paragraphs, see behavior data collection for progress reports. For post-crisis debrief rows, see behavior data collection for crisis intervention. For counseling check-ins that overlap office returns, see behavior data collection for counselors. For briefing leaders on finished narratives, see how to explain IEP progress reports to administrators. This page stays on administrator execution—definitions, office probes, handoffs—not full BIP authoring or manifestation hearings alone.

Administrator behavior data vs discipline referrals vs IEP goal logs

Three documents land in the same week and look like “behavior data” until the case manager tries to graph October.

Progress monitoring is the loop between report cards. Progress reporting is what parents read. Administrators are rarely the author of the full narrative, but your weekly rows should merge with teacher and counselor graphs without contradicting them.

Short answer for snippets: Behavior data collection for administrators means using the operational definition and measurement method on the signed goal or BIP—during office de-escalation, scheduled admin check-ins, or other named settings—on a form you can finish in under five minutes, with initials only, a fixed turn-in to the case manager, and no discipline jargon that does not match the goal line.

Start from the office calendar (not “handle it in admin”)

Before anyone prints a grid for M.T., pull the behavior goal, the BIP administrator section, and the master schedule of who covers the office during ELA blocks.

1. Observable behavior — same verbs as the portal line (verbal refusal, leave area without break card, defined aggressive contact).
2. Setting string — “during office cool-down after ELA referral,” “during scheduled administrator check-in,” “during return walk to class”—not “admin” alone.
3. Replacement skill — break-card request, taught exit script, agreed return steps—what the BIP says office staff model and score.
4. Primary measurement — brief frequency log per contact, opportunity checklist on return steps, yes/no on BIP return plan attempted—one lead method per goal line.
5. Collector map — AP owns office settings; teachers own instructional blocks; counselor owns named check-ins unless the team documented overlap.
6. Turn-in — same day or Friday folder to case manager; no surprise asks at 4 p.m. on due date.

Behavior intervention plan staff training is where definitions get read aloud—administrators should not discover “what counts” from a blank grid after a hard referral.

If the plan only says “administrator will monitor,” stop at team adoption with the case manager in the room—not after six weeks of incompatible hash marks between my office referral form and the ELA frequency log.

What administrators should score (and what stays in discipline files)

You see escalation up close. That does not make every office visit an IEP data point.

Double counting burned us early: the AP ticked “refused to return” in the office while the ELA teacher counted the same episode at the door. We split settings—teacher owns classroom refusal; office owns cool-down replacement steps and return plan attempted per the BIP. See behavior data collection for crisis intervention when the event crosses into safety review.

Pick a method that survives front-office Fridays

Office phones ring. Choose one primary form per goal—not a new grid every time a walk-in bumps a check-in.

Do not assign a full ABC narrative as your weekly turn-in unless the team documented ABC as the progress measure. ABC belongs in FBA bursts or spike troubleshooting—see behavior data collection for FBA and ABC data sheet examples for special education.

Handoff to the case manager: one sample row per office setting

M.T.’s team agreed on teacher frequency for defined refusal in co-taught ELA and administrator checklists for return steps after office cool-downs. My failure mode was forwarding discipline PDFs and calling it progress data.

Handoff package:

• Half-page per named setting: student initials, setting string from the goal, date, behavior definition in one sentence.
• Completed example row—including a contact where the return plan did run.
• Strategy column optional: “chunked return reviewed,” “case manager notified per BIP”—not a novel.
• Dated note when the return plan changes so reporting week is not archaeology.

Friday, the AP slid office rows into the case manager’s folder; she merged them with ELA graphs and counseling check-in rows before the quarterly window. That is administrator-backed data doing its job without turning M.T. into a hallway story with no numbers behind it.

Worked example: M.T., office cool-down and co-taught ELA

Context: Escape-maintained refusal during extended independent work in co-taught ELA; BIP includes office cool-down, break-card rehearsal with counselor, and a return walk with an administrator when needed. Teachers score defined refusal episodes in ELA; counselor scores replacement opportunities in scheduled check-ins; AP scores return-plan steps in the office—not duplicate refusal counts unless the team wrote one definition for both settings.

Administrator data plan (what we actually run):

• Office cool-down (as needed per BIP): Did M.T. use the taught break-card request before standing to leave the office, per the operational definition? Frequency or opportunity row; AP initials.
• Return follow-through: End-of-contact yes/no on completed return to ELA with teacher notified when the plan required it—binary row, not a discipline narrative.
• No duplicate ELA refusal tally in the office unless the BIP defines a separate “refusal during return walk” behavior.

Sample office return checklist (excerpt):

Sample BIP fidelity row (excerpt):

At the six-week review, we compared teacher refusal trend, counselor replacement trend, and office return fidelity separately—then asked whether chunking was visible in ELA before anyone blamed “admin just sent him back.”

FERPA, parent calls, and the main office counter

Behavior rows are education records when they document progress toward an IEP criterion. Discipline files may have different access rules.

• Initials only on forms that leave the locked admin file copy destined for special education.
• Do not read counts aloud at the front counter where other families wait.
• Agree with the case manager on what one sentence belongs in the progress narrative versus what stays in the discipline system.
• When a parent calls the main office first, use the script in how to explain IEP progress reports to administrators—trend and next step, not hallway impressions.

Building PBIS slides and IEP graphs can both look “fine” while definitions diverge. See behavior data collection for PBIS for schoolwide metrics—then keep M.T.’s office probes on the case manager’s intensive graph.

Common mistakes in administrator-led behavior data collection

1. Discipline referrals instead of rows—consequence language the case manager cannot graph toward a criterion.
2. Different definitions on the referral form, the BIP, and the portal goal line.
3. Scoring every office visit when the goal only named cool-down or return contacts tied to the plan.
4. Duplicating teacher counts for the same episode at the classroom door.
5. No turn-in day—admin collects until reporting week, then the case manager reconstructs October from memory.
6. Vague admin notes (“defiant,” “disrespectful”) without tying to the operational definition.

When incidents spike, run debrief per district crisis policy first—see behavior data collection for crisis intervention. Then ask whether M.T.’s return plan was trained or whether collectors were scoring different behaviors.

What I’d do Monday

1. Pull M.T.’s behavior goals and highlight every line that names administrator, office, or return settings.
2. Map one primary collector per goal per setting—AP vs teacher vs counselor—on a half-page the team signs.
3. Bring a sample completed row per office form to a five-minute huddle with the case manager.
4. Align discipline entry codes with goal language only when the team documented that overlap—do not assume they match.
5. Turn in rows on the agreed day; store copies in the secure file the special education team uses.

Behavior data collection for administrators should feel boring. Boring rows protect students in the hallway and make parent-facing language honest.

---

Draft the narrative, not your Sunday. If you already have office rows, teacher graphs, and debrief notes—and still dread the blank progress narrative box in the LEA portal—try IEP Progress free: paste de-identified notes, get a first draft of the progress narrative in a few minutes, edit every line, then copy into your district system. It does not write discipline referrals or replace the BIP. Free plan: 3 narratives a month, one student profile, initials only. No credit card.

FAQ

What is behavior data collection for administrators?

It is goal-aligned measurement—using the IEP’s behavior definition, named office or return setting, and method—on forms an administrator or dean can complete in under five minutes per contact, with one primary collector per setting, initials only, and a fixed turn-in to the case manager.

Should principals write the full IEP progress narrative?

Usually no. Building leaders produce rows for settings they own; the case manager or teacher of record summarizes trend toward each criterion for parents. See behavior data collection for progress reports.

How is administrator data different from discipline referrals?

Discipline referrals answer rule broken and consequence. IEP-aligned office data answers whether defined behaviors or replacement steps moved toward the annual criterion in settings named on the plan—using the same operational definition as teachers when episodes overlap.

Can office referral forms count as behavior data?

Only when the goal or BIP adopted the same definitions and settings as the referral fields—and your LEA allows those fields in the special education progress file. Otherwise admins supply structured rows on the BIP form, not forwarded PDFs alone.

What if the student only lands in the office after a crisis?

Follow district crisis documentation first. For IEP progress, collect on contacts named on the plan—cool-down, return walk, scheduled check-in—or convene the team to revise settings if crisis-only contacts are all you have.

How do administrators align with PBIS or MTSS building data?

Schoolwide metrics inform climate and Tier 2 decisions; IEP rows still follow individual goal definitions. See behavior data collection for PBIS and behavior data collection for MTSS—then keep M.T.’s office probes separate on the case manager’s graph.

Sources

• U.S. Department of Education, IDEA: IEP content and measurable goals
• 34 CFR §300.324 — Development, review, and revision of IEP (positive behavioral interventions)
• U.S. Department of Education: Family Educational Rights and Privacy Act (FERPA) (district policy still governs access and sharing)

Marcus Hale is a special education case manager who partners with building administrators on BIP implementation. Student examples use initials only (e.g., M.T.). Updated October 3, 2026. General guidance, not legal advice.