Hi again,
You sent it Monday. The polite little email to all seven of this student's teachers: "His annual is coming up — any concerns I should know about?" Reasonable. Professional. The thing every case manager sends in September.
It's Thursday now. You've gotten one reply.
"He's fine."
One teacher, out of seven. And the reply you got isn't input you can put in front of a team. The meeting's in two weeks, and right now your plan is the one every case manager falls back on: start walking the halls, catching people between bells, collecting opinions like it's a paper route. You'll get your input. You'll just get it the hard way, one hallway ambush at a time.
Here's the part worth sitting with before you blame anybody. The six who didn't answer aren't lazy, and they don't dislike your student. "Any concerns?" is an essay question. Open-ended, blank page, no word limit, due whenever. A teacher with 130 kids is not going to sit down and write you an essay in September. You wouldn't either.
The fix isn't chasing harder. It's asking smaller.
Instead of one big open question, five specific ones a teacher can answer without stopping to think. Does he start work without a prompt? Does he turn it in? Not "tell me about this child" — just check a box about what happens in the room. Three minutes. And AI can build the whole thing.
First, the blank form
The natural way to start this is exactly the way you shouldn't: opening your AI tool and typing what you already know about the student so it can "help you ask the right questions." Stop before the name. There's no student in this job at all.
What you're building is a blank template. A form with five or six good questions and some checkboxes, that works for any student on your caseload and every one you'll ever have. The student's name doesn't go in here. It goes in later, once, inside your district email, to the one teacher you're actually sending it to. The AI just makes the empty form.
That's the whole first half of the safety rule, and it's the easy half. Here's the half nobody warns you about.
Then, the part everybody misses
The form goes out. Answers start coming back. And now you're holding something completely different from what you sent.
What you sent was a blank template. What comes back is student data — real observations about a real kid, written by a teacher who watched him all week. Where he struggles. What helps. That information lives in your district systems now, the same place the IEP lives. And it never goes back into an AI tool. Not to "summarize the seven responses." Not to "clean up the wording" or "pull out the themes." The temptation will be real, because by then you'll have a stack of replies and a meeting bearing down on you. Don't.
The blank form is the robot's job. The filled-in form never sees the robot again.
The prompt
You are an experienced special education case manager building a reusable teacher-input form. No student information exists in this job — it's a blank template I'll reuse all year, so don't invent any names, details, or examples. Build me two things. First, a short input form for [describe the setting, e.g., high school general-education classes] with five or six specific, observable questions a teacher can answer in under three minutes — quick rating scales (for example, "consistently / sometimes / rarely") plus one optional comment line at the end. Phrase every question so it describes a classroom behavior, not a diagnosis: things like starting work without prompting, following directions the first time, turning in assignments, participating, and what seems to help most when the student is stuck. Second, a two-sentence request email that's warm, names a specific deadline, and makes it easy to say yes.
You'll get back a form built out of the right kind of questions — the ones a teacher can answer by remembering, not by composing. And an email that's short on purpose: two sentences of warmth, one real deadline, and the honest promise that this takes three minutes.
One heads-up: the form comes back as plain text, not a formatted page. Paste it into a doc or your district's form tool and it's ready. The wording is the part you couldn't have written between bells.
Now read it like the professional you are. Check the questions against what your meeting actually needs to decide, and against your district's required input forms. Some districts have an official input form already — if yours does, use theirs. Let this become the friendly "pre-ask" that gets the official one filled out instead of ignored. And your district's AI policy is the final word on the prompt side. Their rules win, every time.
"Any concerns?" is an essay question. A teacher with 130 kids doesn't answer essay questions in September.
The part nobody tells you
Specific questions don't just get you more answers. They get you better ones.
Here's why "he's fine" happens. You asked a teacher to recall — to search their memory for anything worth reporting about one kid out of a hundred and thirty. Recall is hard. The brain comes back with "nothing's on fire," which is what "he's fine" actually means. But when you ask "does he start work without a prompt?", you've switched them from recall to recognition. And recognition is easy. The teacher suddenly pictures Tuesday, third period, that kid still staring at a blank page after everyone else had started. Now you've got something real. You didn't collect an opinion. You jogged a memory.
There's a second win, and it lands in October. The input you gather in September doesn't expire when the meeting ends. It's sitting right there in your files when progress reports come due and the next round of meetings gets scheduled. September input is October gold. You did the asking once, at the calm moment, and it pays you back at the busy one.
Try it this week
Build the form one time. Save it where you'll find it again — this is a template you'll reuse all year, not a one-off.
Then send it for exactly one student: the one whose meeting is next on your calendar. Put the name in your district email only, set a Friday deadline, and let the three-minute promise do the work. See how many of the seven come back this time.
Bonus move: paste this whole issue into your AI and tell it, "Build my input form using these rules."
Then hit reply and tell me your record — how many times have you had to ask the same teacher for the same input before you got it? I'm collecting the collaboration headaches, and yours is somebody else's too.
Talk soon,
Shaun
P.S. If you know a case manager about to send that "any concerns?" email to seven teachers this week, forward this one along. It might save them a paper route.
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.