In this guide
- Co-taught behavior data vs homeroom-only vs office referrals
- Start from the goal line and the co-teach model (not “whoever notices”)
- Who collects during co-teaching (and how to avoid double counts)
- Pick a method both teachers can run in under three minutes
- Co-plan the handoff: one sample row beats a BIP attachment alone
- Worked example: T.N., co-taught ELA workshop and transitions
- Paras, subs, and split co-teach schedules
- Common mistakes with behavior data collection in co-taught rooms
- What I’d do Monday
- FAQ
- Sources
T.N. had a behavior goal tied to co-taught seventh-grade ELA—independent writing after mini-lesson, not the resource block where I kept the rest of the file. Monday, my co-teacher texted from the copy room: “I’ll run the checklist during workshop if you take transitions. Which definition counts as ‘leaving the desk’ when I’m conferencing at the back table?”
Behavior data collection for co-taught classrooms is the layer where two licensed teachers share one room, one pacing guide, and often different ideas about who owns the clipboard. It is not a discipline referral. It is not “the sped teacher will handle behavior.” It is the named behavior, named co-taught setting, named method, and named adult per lesson phase so quarterly reporting can cite trends from the class parents actually see on the schedule—not a homeroom sheet that never follows the student.
Federal rules 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 the goal’s condition names co-taught ELA, science, or math, the data need to come from that paired classroom often enough to show a pattern. District forms, BIP attachments, and FERPA storage vary by LEA; confirm who may see weekly tallies with your special education office. I am a case manager and former co-teacher, not a lawyer.
This guide is for co-teaching pairs and case managers who need shared systems that survive a normal week with two rosters’ worth of interruptions. For standalone homeroom blocks without a co-teacher, see behavior data collection for general ed classrooms. For signed-plan language and BIP review packages, see behavior data collection for BIP. For turning tallies into quarterly paragraphs, see behavior data collection for progress reports. This page stays on co-taught execution—two teachers, one instructional block—not resource-only or self-contained layouts.
Co-taught behavior data vs homeroom-only vs office referrals
Three packets land in the same inbox and blur together.
| What it is | What it answers | Fits the IEP when the goal names co-taught… |
|---|---|---|
| Office / discipline referral | Rule broken, consequence applied | Only if the goal counts those incidents with the same definition |
| Whole-class management system | Climate for all learners | The goal names that tool and an individual criterion |
| Goal-aligned co-teach monitoring | Trend toward the annual criterion in the paired class | Always—for behavior goals in co-taught settings |
Progress monitoring is the loop you run between reporting windows. Progress reporting is the summary parents read. Co-teachers are not being asked to draft the narrative; they are being asked to produce rows the case manager can defend. If the only record is “workshop was rough,” see how to report progress on IEP goals without data for honest language—and fix the co-plan before next quarter.
Short answer for snippets: Behavior data collection in a co-taught classroom means using the operational definition, co-taught setting, and measurement method from the IEP (and BIP, if adopted)—on a form both teachers understand—and logging on a fixed schedule with one primary collector per lesson phase so counts do not double or vanish.
Start from the goal line and the co-teach model (not “whoever notices”)
Before you laminate a strip on T.N.’s desk, open the behavior goal beside your co-teaching schedule.
- Observable behavior — verbs both teachers use (call-out, leave desk without break card, start writing within two minutes).
- Setting — “during independent work in co-taught seventh-grade ELA,” not “language arts” or “middle school.”
- Measurement — frequency per block, opportunity checklist, partial-interval percent—one primary method.
- Lesson phases — who scores during mini-lesson, workshop, closure (match your building’s co-teach model: one teach/one assist, parallel, station, alternative).
Open the BIP or data attachment if one exists. The gen-ed co-teacher should see the same definition the goal uses. Behavior intervention plan goals shows how settings get named on the goal line; your job in the co-taught room is to match that language on the sheet header and in a five-minute huddle.
If the goal only says “teachers will monitor,” stop at common planning—not after six weeks of incompatible hash marks. Behavior intervention plan data collection is the case-manager checklist before anyone prints a form.
Who collects during co-teaching (and how to avoid double counts)
Co-teaching fails data collection when both adults tick the same opportunity or neither does because each thought the other had it.
| Co-teach phase | Typical data job | Pitfall |
|---|---|---|
| Whole-group mini-lesson | Usually no individual behavior log unless the goal names whole-group responding | Sped teacher scores while gen-ed teaches—students notice |
| Independent / workshop | Primary collector named on the plan (often gen-ed during conferring, sped during roving) | Double scoring the same 5 opportunities |
| Transitions within block | One adult per transition (door line, materials pickup) | Assuming “we’ll remember at lunch” |
| Parallel / stations | Collector follows T.N.’s station rotation on a printed roster | Para at another station logs a different definition |
Agree in writing: Primary collector, backup (para initials), turn-in day. A sticky on the teacher laptop beats a policy memo.
FERPA in a co-taught room: initials only on clipboards; no behavior counts on the public whiteboard where 28 other students read them. Store completed logs in a locked drawer or district-approved secure drive—not the shared cart everyone borrows.
Pick a method both teachers can run in under three minutes
Co-taught blocks are dense. Choose one primary collector per goal—not two different forms because each teacher has a favorite.
| Method | When the goal sounds like… | Co-teach friendly habit |
|---|---|---|
| Frequency / event log | “No more than X episodes per block” | End-of-workshop tick marks; see event recording data sheet examples |
| Opportunity checklist | “Replacement skill in 4 of 5 opportunities” | Laminated strip; scorer initials per row |
| Partial-interval sample | “80% on-task during 15-minute observations” | Scheduled looks—case manager or counselor twice weekly, not all day |
| Short rubric | “Level 3 or higher on the regulation scale” | One row at block end; same rater all week when possible |
Do not hand the pair an ABC narrative grid as the weekly turn-in unless the team documented ABC as the progress measure—which is rare in co-taught core classes. ABC belongs in FBA bursts; see ABC data sheet examples for special education when you need antecedent detail after a spike.
Co-plan the handoff: one sample row beats a BIP attachment alone
T.N.’s team agreed on a daily workshop checklist (replacement: start writing within two minutes using the taught cue) and a transition event log (defined leave-desk without card during materials pickup). My failure mode used to be emailing the full BIP and saying “let me know.” What worked was common planning with a filled sample row and a turn-in time.
Co-teach handoff package (one screen):
- Half-page PDF: student initials, co-taught ELA, date, behavior definition in one sentence.
- Completed example row in pen—not a blank grid.
- Phase map: “Gen-ed scores workshop M–Th; sped scores Friday closure + transition log.”
- Turn-in: Friday photo to secure inbox, or folder in case manager mailbox.
- Backup: named para when one co-teacher is at PLC—not “the office will figure it out.”
If strategies change mid-quarter, send a dated note on the sheet (“chunk prompt to one paragraph starting 10/21”) so reporting week is not archaeology. For how to walk co-teachers through the quarterly report once data exist, how to explain IEP progress reports to general ed teachers complements this collection piece without repeating it.
Worked example: T.N., co-taught ELA workshop and transitions
Context: Escape-maintained off-task during extended independent writing after mini-lesson; leaving the desk without using the break card during materials transitions. BIP strategies in co-taught ELA: chunked prompt, visible break card, pre-transition cue at the supply shelf. Goals tied to replacement writing start and reduction of defined leave-desk episodes in the co-taught block.
Co-taught data plan (what the pair actually does):
- Workshop (Mon–Thu): Opportunity checklist—did T.N. start the assigned starter within two minutes using the taught cue? Five opportunities scored; gen-ed co-teacher initials when conferring, sped co-teacher initials on the day gen-ed runs small group.
- Materials transition (daily): Event tally for defined leave-desk without card per BIP—not every stretch or bathroom pass.
- Partial-interval on-task goal: counselor samples two 10-minute probes on Wednesdays only (not both co-teachers guessing all period).
Sample transition log (excerpt):
| Date | Setting | Transition (BIP definition) | Incidents | Strategy visible | Initials |
|---|---|---|---|---|---|
| 10/7 | Co-taught ELA | Materials pickup | 0 | Pre-transition cue | M.H. |
| 10/8 | Co-taught ELA | Materials pickup | 1 | Cue missed | M.H. |
| 10/10 | Co-taught ELA | Return to seats | 0 | Card on desk | L.R. |
Sample workshop opportunity checklist (excerpt):
| Date | Block phase | Opportunities | Starter within 2 min (taught cue) | Prompts | Initials |
|---|---|---|---|---|---|
| 10/7 | Workshop | 5 | 4 | 1 gestural | L.R. |
| 10/9 | Workshop | 5 | 3 | 2 verbal | L.R. |
| 10/14 | Workshop | 5 | 5 | 0 | L.R. |
Friday, the sped co-teacher slid the folder into my mailbox. I graphed trends, compared to each goal’s criterion, and flagged 10/8 for a five-minute strategy check at common planning—not a guilt email. That is co-taught data doing its job without turning workshop into a clinic.
Paras, subs, and split co-teach schedules
Behavior goals do not pause when one co-teacher is at a district training.
- Para in co-taught room: One line on the data plan—scores only the opportunities the primary teacher assigned (usually workshop backup), same definition.
- Substitute folder: One-page summary—what to count, what not to debate, who to call for safety; both co-teachers’ names and extension.
- Alternate-day co-teaching: If T.N. sees you only on B days, the goal setting still says co-taught ELA—A-day collector must be named on the plan, not assumed.
When co-taught ELA and resource both carry goals, split clear ownership per goal line. Double counting inflates trends; gaps make sample IEP progress reports for behavior goals impossible to write.
Common mistakes with behavior data collection in co-taught rooms
- Resource-only tallies when the goal explicitly names the co-taught course on the master schedule.
- Both teachers scoring the same workshop opportunities without a primary collector.
- Different definitions on the sticky note, the BIP, and the portal goal line.
- Public tracking that singles out T.N. while 30 peers watch the board.
- Collecting nothing until reporting week, then asking the co-teacher to “remember October workshop.”
- Changing the form mid-quarter without telling the case manager when the criterion stayed the same.
When incidents spike, run a short ABC burst and reconvene per district crisis policy first—then ask whether BIP antecedent strategies were visible during workshop, not whether the co-teach pair “cared enough.”
What I’d do Monday
- Pull T.N.’s behavior goals and highlight every co-taught setting on the schedule.
- Map one primary collector per lesson phase on a half-page both teachers sign.
- Bring a sample completed row to common planning—not a blank grid.
- Calendar a 10-minute fidelity glance after two weeks of workshop logs.
- Store copies in the secure file; graph before the quarterly window opens.
Behavior data collection for co-taught classrooms should feel boring. Boring rows protect workshop time and make parent-facing language honest.
Reporting week does not get shorter because you co-teach—but the paragraph does not have to wait until the couch at 10 p.m. Once T.N.’s workshop rows and transition tallies are in your folder, I paste those notes during planning period and get a first draft of the progress narrative on screen before I open the LEA portal. Try three free narratives a month on IEP Progress; you still edit every line, initials only, then file in Frontline, PowerSchool, or your district system. Same portal; you skip the cold start.
FAQ
What is behavior data collection for co-taught classrooms?
It is goal-aligned measurement—using the IEP’s behavior definition, co-taught setting, and method—on forms both licensed teachers understand, with a named primary collector per lesson phase and a fixed turn-in schedule to the case manager.
How is co-taught behavior data different from general ed homeroom data?
Homeroom posts focus on standalone gen-ed blocks (one teacher, one room). Co-taught posts focus on paired instruction: shared pacing, split attention, and handoffs so counts are not doubled or missed. See behavior data collection for general ed classrooms for homeroom-specific habits.
Which co-teacher should collect behavior data?
The team decides at adoption—not mid-spiral. Usually the adult closest to the goal’s setting during the named phase (e.g., gen-ed during writing workshop, sped during transitions) with a documented backup.
Should co-teachers write the IEP progress narrative?
Usually no. Co-teachers collect rows; the case manager (or teacher of record) summarizes trend toward each criterion for the parent-facing report. See behavior data collection for progress reports.
What if the student has a BIP and a co-taught goal?
Use the operational definitions and forms named on the BIP attachment. Implementation in the co-taught block should match what the team signed; behavior data collection for BIP covers review packages and ongoing logs.
Can we use a classwide chart for one IEP student in co-taught class?
Only if the goal names that tool and an individual mastery line. Otherwise use a discreet individual log or checklist so the chart does not double as a public label.
Sources
- U.S. Department of Education, IDEA: IEP content and measurable goals
- 34 CFR §300.321 — IEP team (general education teacher when in gen ed)
- Council for Exceptional Children — co-teaching resources — models and collaboration (district implementation varies)
Marcus Hale is a special education teacher and case manager. Student examples use initials only (e.g., T.N.). Updated October 3, 2026. General guidance, not legal advice.
Keep reading
-
Behavior Data Collection for General Ed Classrooms
Behavior data collection for general ed classrooms—one-sheet probes, discreet tallies, and weekly handoffs so homeroom staff can log IEP behavior goals.
-
Behavior Data Collection for Inclusion Classrooms
Behavior data collection for inclusion classrooms—who logs during push-in blocks, para handoffs across gen-ed rooms.
-
Behavior Data Collection for Self-Contained Classrooms
Behavior data collection for self-contained classrooms—whole-day settings, para rotations, center blocks.
-
Behavior Data Collection for Administrators
Behavior data collection for administrators—office logs vs IEP rows, BIP return fidelity, and handoffs case managers can graph without duplicating discipline.
More in IEP Data Collection · All IEP guides