Hi again,
5:40 a.m. You're awake before the alarm, and you already know. The head, the throat, the bone-deep "not today." You are sick.
And here's what you do next, because you're a SPED teacher: you lie there running your classroom in your head for a stranger. Arrival — do they know to hand out the folders before the bell? The small groups rotate at 9:15, but only if the timer works. Fourth block gets loud when the schedule slips, and it will slip. Who tells the sub that? Who tells the sub any of it?
So you get up. You take something, you find your other shoe, and you drive in sick, because writing the sub plan felt harder than the flu. Every one of us has done this. We teach sick not because we're heroes but because the alternative — handing our room to someone who's never seen it, with nothing to go on — feels worse.
And the binder that would've fixed it? A few weeks into the year, it's not blank. It doesn't exist yet. The office wants it by Friday.
Let's build the thing that lets you stay home next time. Not the whole binder. The engine underneath it — the part that has nothing to do with any one of your kids.
What a stranger actually can't guess
A gen-ed sub walks into a room and mostly figures it out. Bell rings, kids sit, worksheet happens. Your room doesn't run on that. Your room runs on routines nobody can see and nobody would guess — the exact order of the morning, the transition that only works if it's announced twice, the rotation that falls apart if the groups swap tables.
Miss those and it isn't just a rough day. The kids who need the routine most get a day of chaos, and you don't pay for it once. You pay for it all week, rebuilding what one unpredictable day knocked over. That's the real cost of a bad sub day in a SPED room, and it's why we drive in sick.
The routines can be written down. The good news is that writing them down is exactly the kind of boring, structured job AI is good at.
The line that keeps this safe
Here's the trap, and it's a big one. The sub binder is the single document we're most tempted to load with the sensitive stuff. Behavior triggers. Medical needs. The de-escalation steps for the kid who has a hard 10:30. The quiet "watch out for..." notes we'd whisper to a trusted colleague.
None of that goes into an AI tool. Not one line of it. The sub needs to know your routines. The robot doesn't need to know your kids.
So we split the job clean down the middle. AI builds the generic machine of the room — the schedule shell, the scripts for each routine, a bank of any-day activities, a plan for when things break. Zero students in any of it. A stranger could be teaching any classroom in America. Then the student layer — the names, the specifics, the sensitive notes — gets added by your hand, in your own secure copy, in whatever format your district requires. That part never touches the tool.
One more warning, because it's the mistake people make: don't paste last year's sub plan in and ask AI to "update" it. Old plans are full of old names. The whole point is to build the shell fresh, empty, with nobody in it.
The prompt
You are an experienced special education teacher building an emergency sub-plan shell — a blank framework, no students in it. My day runs like this, in generic blocks with no student information: [describe your schedule — e.g., resource room, self-contained, or co-taught — as time blocks and activity types, no names or student details]. Build me four things. First, a fill-in-the-blank day schedule with a short script for each routine — arrival, transitions, small-group rotations, dismissal — written plainly enough that a stranger could run it without knowing my class. Second, a bank of five or six low-prep, any-day activities per subject block that a substitute can run with no training and no special materials. Third, a "when things go sideways" page: plain if/then scripts for the predictable snags — the schedule changes, a student refuses, the tech is dead — each with a blank line for who to call. Fourth, a checklist of the student-specific information I'll add by hand later in my secure copy, written only as blank labeled slots, never content. No student details exist in this job, so don't invent any.
That last line is doing real work. There are no students in this task, and you never want AI filling that vacuum with a made-up "Johnny" who does made-up things. Blank slots only. You fill them.
Read it like it's never met your room
What comes back is a draft, and it's a draft from something that has never set foot in your classroom. The scripts will be generic because you gave it generic blocks — that's correct, that's the safety working. Now make them yours. Rewrite the arrival script the way arrival actually goes. Fix the rotation so it matches your tables. You know the ten things about your room the shell can't, and this is where you put them in.
And before it goes anywhere: many districts have a required sub-plan format, and rules about what can sit visible on a desk all day versus what stays locked up. Your district's format wins over the AI's. Your case-management lead is the person who tells you where the sensitive layer lives and how it travels. Ask first. Their rules win, every time.
The part nobody tells you
A finished sub binder isn't paperwork. It's permission.
Permission to be sick and stay sick. Permission to take the personal day without a knot in your stomach. Permission to go to your own kid's field trip instead of watching from work. The teachers who never build one don't just have messier sub days — they teach sick all year, because staying home was never really an option.
(And quietly, the same shell is the best training doc a new para will ever get handed. But that's a whole issue for another week.)
A finished sub binder isn't paperwork. It's permission — permission to be sick.
Try it this week
Block one planning period. Describe your day in generic blocks — times and activity types, no students. Run the prompt. Print the shell. Then handwrite the student layer into your secure copy: names, the specifics, the sensitive notes, in your district's format. Put the binder wherever the office told you it goes.
Done before Friday. And the next 5:40 a.m. when your body says "not today," you get to actually listen to it.
Then hit reply and tell me the one thing a sub could never figure out about your room on their own. That routine, that unwritten rule — it's probably the thing half of us forget to write down, and I'm picking future issues from your answers.
Talk soon,
Shaun
P.S. You know the teacher who taught through the flu last year — dragged in gray and shaking because the sub plan was the bigger nightmare. Forward this one to them. It might be the reason they stay home next time.
A quick but important note: this newsletter is for general educational and informational purposes only. I'm a special education teacher sharing time-saving ideas. The views here are my own and don't represent any school district or employer. I'm not a lawyer, and nothing here is legal, compliance, or professional advice. Always follow your district's and state's policies, especially on AI use and student privacy, and check with the right person in your district before acting on anything significant. You are the professional: review and finalize everything yourself. And never put student names or identifying details into any AI tool.