Sometimes a practitioner is not refusing to cooperate. They are refusing to pretend. They may see that the plan does not match the student’s needs, that implementation has drifted, or that a support is being reduced for the wrong reason. If the system does not want to hear that, clinical judgment can get mislabeled as…
A decision rationale is the reason a team made a decision. In plain language, it answers: Why are we doing this, and why does it make sense for this student?
This checklist helps review whether an important decision has been documented clearly enough to survive memory, staff changes, and next Tuesday.
Documentation does not have to sound like a legal grenade. A good record can be calm, factual, and useful: what was discussed, what was decided, why, who is responsible, and what happens next. The goal is not to win a fight. The goal is to keep the team from needing a séance to remember the…
One meeting. Four memories. None of them malicious. All of them incomplete. That is why important decisions need documentation. Not because everyone is untrustworthy, but because humans are humans and school systems are busy. The record should make it possible to reconstruct the decision without asking everyone to replay the meeting from memory.
People forget. Staff change. Meetings blur. Good intentions evaporate under Monday morning. Documentation is the institution’s memory. If the team cannot reconstruct what was decided, why it was decided, who owned it, and what happens next, the system is running on memory and vibes. That is not a plan. That is a hope chest.
Implementation drift is what happens when daily practice slowly moves away from the written plan. It may start small: a skipped support, an informal substitution, a vague handoff, or a routine everyone assumes someone else owns.
This checklist helps compare the written plan with the actual school day. Because drift rarely announces itself with a tiny clipboard and a name tag.
Implementation drift shows up in small mismatches. The plan says one thing, the day looks slightly different, and everyone hopes it is fine. The fix is not panic. The fix is early comparison: written plan, actual routine, responsible person, observed gap, and next correction.
Implementation drift is sneaky because each individual shortcut can look small. One day the support happens a little differently. Another day the assigned person is unavailable. Another day the equipment is in the wrong place. Nobody means to rewrite the plan. But after enough drift, the child is no longer receiving what the team wrote…