A self-paced session your team can run as a PLC to stop scattering ABC notes across documents and start producing summaries you can actually bring to a BIP meeting. Work through the recorded walkthrough and the agenda below over one block, and you leave with a shared behavior question, a logging standard everyone uses, and a plan for reviewing patterns together.
Before the session: gather one real case
Ask each participant to bring one student whose behavior data currently lives in a spreadsheet or a stack of incident slips. Working from a real case keeps the session concrete instead of theoretical. Open the fba-setup walkthrough together so everyone is looking at the same workflow when you start.
Part 1: write the behavior question as a team
Spend the first stretch agreeing on the practical question each case is trying to answer, such as what happens right before elopement during transitions. Have people read their questions aloud and tighten any that are too broad to log against. A clear question is what keeps every observer pointed at the same thing once data collection starts.
Part 2: agree on one ABC logging standard
Decide as a group how you will record antecedent, behavior, consequence, setting, and intervention, using one observable behavior definition per case. The goal is that two staff logging the same student produce comparable entries, not two different stories. Practice logging a few sample incidents in Evident as ABC notes tied to the student so the standard is muscle memory before you leave.
Part 3: read patterns and plan the review cadence
Walk through how to scan for repeated antecedents, times of day, and supports that worked before anyone drafts a plan. Set the date and owner for your next pattern review so the work does not stall after the session. Decide how you will export a summary for the BIP conversation rather than rebuilding the evidence by hand.
Run it as a PLC, not a one-time training
Treat this as the first meeting in a short cycle: collect for a defined window, then come back together to read the data and adjust. Logging the session and your shared standard somewhere the team can revisit gives new staff a way to onboard later. The point is a repeatable habit, not a single recorded talk.