A checklist for running a focused pilot that tells you what teachers actually need before you commit to a district-wide rollout. Structure it in four phases: pick one use case, name the roles, set success criteria up front, and review data quality and feedback at a real checkpoint before scaling.

Phase 1: choose one primary use case

Do not try to solve everything at once. Pick a single main workflow for the pilot: daily behavior charts, IEP progress monitoring, FBA and BIP documentation, or parent communication. A pilot with one clear job produces feedback you can act on. One that tries to cover all four usually produces noise.

Phase 2: name the roles

Write down who does each part: who creates students, who creates charts, who logs daily, who reviews reports, and who fields parent communication questions. Ambiguity here is the quiet killer of pilots, because work that belongs to nobody simply does not happen. Naming the daily logger in particular matters most, since the whole pilot rests on consistent logging.

Phase 3: define success before kickoff

Agree on a small set of success signals before the pilot starts, not after. Reasonable ones are teachers logging consistently, reports that hold up in a meeting, and families able to access updates. Writing these down up front keeps the post-pilot conversation about evidence rather than impressions, and keeps everyone honest about what the pilot was meant to prove.

Phase 4: review at a checkpoint, then decide

Many teams learn enough from a focused two-to-six-week pilot, timed around their meeting cycles. At the checkpoint, review whether logging held up, whether the reports were useful, and what should change before expansion. If parent communication is part of the use case, confirm the family-sharing plan worked before you scale it across more classrooms.