Hi again,
The reports are in. And for one strange week in October, nothing is on fire.
You know the week I mean. Progress reports went home. The meetings that could ambush you this month haven't scheduled themselves yet. There's no stack due tonight. And in that quiet — the first quiet since July — you finally notice how tired you are.
Most of us spend this week catching up on grading. Fair enough. But I want to ask you for twenty minutes of it for something else. Not more work. The opposite of work, really. A debrief. The one nobody ever runs.
The one on yourself.
You do this for students every day. You've never once done it for you.
Think about how much reflection you run on your kids. Data points. Trend lines. What's working, what needs adjusting, who's climbing and who's stuck. You are, all day long, a machine for noticing patterns and changing course.
You have never once pointed that machinery at your own week.
Here's the reframe I keep coming back to: you just finished the first nine weeks. That is a data set. Nine weeks of your hours, your evenings, your Sundays. And you have all the information to ask the one question you never ask — where did the time actually go?
Not "was I busy." You were busy. Everybody's busy. The real question is which busy was worth it and which busy was a system you never got around to building.
The 20-minute reset
Step one takes ten minutes and a blank page. No AI yet. Just you, being honest.
Jot bullets. Not a journal, not paragraphs. The recurring stuff — not the one-off fires, the things that came back every single week:
The tasks that ate you. The ones that showed up every week and took a chunk each time.
The thing you built this quarter that actually worked. (You built something. Name it.)
The thing you kept doing by hand that a system should own.
The one thing you dreaded most, every week, before you even sat down to it.
Be blunt. This page is for you and nobody else. I'll tell you mine, since I'm asking you for yours: I still hand-build every study guide from scratch, and it costs me a night I never plan for. Wrote it down. There it is.
Then you hand those bullets to a coach. That's step two, and that's where the AI comes in.
The prompt
You are a practical coach for a special education teacher doing a first-quarter reset. Here are my honest notes about where my TIME went this quarter — tasks and workload only, nothing about any student: [paste your bullets, e.g., "progress report comments took two full evenings; the sub binder finally exists and saved me twice; I still hand-build every study guide; IEP meeting follow-ups keep slipping; the input form worked"]. Give me: (1) the 2–3 recurring time sinks worth building a system for before January, ranked by hours saved; (2) the one thing I should stop doing entirely and what to do instead; (3) a 30-minute plan for the first week of next quarter to set those systems up. Be blunt and practical, don't flatter me, and don't invent details I didn't give you.
What comes back is a reset plan. The two or three systems worth building before the new year, in order. The one thing to quit. And a thirty-minute first-week-back plan so the whole thing doesn't just live in your good intentions.
Keep the kids out of your own diary
Here's the thing about a debrief. Even your own can smuggle kids in.
Teacher venting has names in it. That's how we talk. "The Tuesday group" — fine, that's a block on a schedule. But "the kid who ran," "the mom who called four times," the initials you'd know in a heartbeat — that's a child, and a child does not belong in the prompt.
So de-identify your own diary. Write the debrief about tasks and hours, not people. If a line in your notes is really about a student, it doesn't go here at all — it goes in your data system, where the private details are supposed to live. Your district's AI policy is still the final word on any of this; check it.
Everything else you already know. But this one's a little different from the usual rule, because the temptation is coming from inside the house this time. This debrief is about you. Keep it that way.
It doesn't know your spring
The plan that comes back is a draft, same as everything the robot hands you. It doesn't know your building. It doesn't know what your caseload's spring looks like, or which of those "time sinks" is actually load-bearing for reasons no AI could guess.
So keep what rings true and cross out what doesn't. You'll know in about four seconds which suggestions are real and which ones are a coach who's never met your February. Trust the four seconds.
While you're in there, raid the archive
One more thing, and it's the nice part of a reset.
Since July, these issues have been building you systems one week at a time — the at-a-glance sheet, the data tracker, the teacher-input form, the para guide. The reset is where you notice which ones actually stuck to your week and which one you nodded at back in August and never went back to build. If a system keeps showing up in your "should own this by now" bullets, there's probably an issue in the archive already waiting to walk you through it. Go back and do that one for real.
(New here? That's the back catalog. It's all still good.)
You run a debrief on every kid in your caseload. This week, run the one nobody ever runs — the one on you.
The part nobody tells you
You can't get October's hours back. That night I lost to study guides is gone. So is your report-comment marathon. Done.
But here's what nobody tells you in September, when you're pouring yourself into it: Q2 has its own October coming. And that one doesn't have to cost the same.
The teachers who make it to May in one piece aren't the ones who worked the most heroic fall. I used to think they were. They're the ones who noticed which parts of the fall were actually optional — and quietly stopped doing them.
Because burnout mostly isn't one giant dramatic thing. It's the same seven small things, never once inspected, grinding on you every week from now until June. The reset is the inspection. Twenty minutes, once a quarter, to catch the small things before they add up to a spring you dread.
Try it this week
Ten minutes with a blank page and the honest bullets. Ten minutes with the prompt. Then do the one thing that makes this stick: put a single system-building block on your calendar for the first week back after the break. Thirty minutes. One block. That's the whole assignment.
Then go home on time, just once, this week. Doctor's orders. Well — teacher's orders.
Hit reply and tell me the task that ate your first quarter — the recurring one, the one that'll eat Q2 too if nothing changes. I'm building the next run of issues straight from your answers, so this is you helping plan them. Tell me what to build next.
Talk soon,
Shaun
P.S. Know a teacher limping toward fall break, running on empty? Forward them this one. Ten quiet minutes might be the best thing they do for themselves all week.
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.