Claude Gave You Something. Now Push Back.
This is the third post in a series about Claude and use in Primary schools - if you haven’t read about how to set up a Project head here first.
You’ve set up your Project. You’ve uploaded your documents. You type a prompt and Claude gives you something back.
It’s pretty good. Not perfect, but pretty good.
You copy it, tweak it a bit, use it. It works out fine.
Next time, you are after the same kind of task. Claude gives you something slightly different. It is also pretty good, but you spend longer editing it than you’d like. The week after, same thing. Sometimes great, sometimes mediocre. It starts to feel like luck.
With AI, it isn’t luck. It’s one thing, and it’s completely fixable. You’re treating Claude’s first response like a finished product. It’s a first draft.
The conversation most teachers aren’t having
When a colleague reads your lesson plan and says “the starter activity feels a bit flat” — you don’t tear up the whole plan and start again. You say “fair point” and fix the starter.
Claude works exactly the same way. When the output isn’t quite right, you don’t rewrite your prompt from scratch. You say what you’d change. In one sentence. Claude fixes it. Immediately.
Most teachers don’t know this. They assume that if the first response isn’t right, they asked wrong — and next time they try to write a longer, more complicated prompt to compensate. The prompt becomes an essay. The output gets broader and shallower. The editing takes longer.
The fix isn’t a better prompt. It’s a second message.
What pushing back actually looks like
Here’s a real example across three tasks.
Lesson planning
You ask for a Year 4 lesson on equivalent fractions. Claude gives you something solid — good structure, reasonable activities. But the starter is paper-based and your class needs to move.
You don’t rewrite the prompt. You say:
“The starter is too paper-based. Make it fully practical — no writing, pupils just handle fraction strips and call out what they notice.”
Claude rebuilds the starter. Everything else stays. Thirty seconds.
Then you notice the Group 1 scaffolding has six sentence starters. Too many for your SEND pupils.
“Group 1’s scaffold is too complex. Cut it to three sentence starters only, each under six words.”
Fixed. You now have a lesson plan that took two minutes of conversation to get right, not twenty minutes of editing.
Report comments
You give Claude your bullet-point notes on a pupil. It drafts a comment. It’s warm, accurate, the right length, but the last sentence sounds like it was written by a robot.
You don’t start again. You say:
“Just rewrite the last sentence. The rest is fine. Make it warmer and more specific to this pupil.”
One sentence changed. Everything else untouched.
Then you notice it uses the phrase “is beginning to,” which your school actively avoids in reports.
“We never use ‘is beginning to’ in our reports. Remove it and rewrite that line.”
Done. That’s a report comment you’d actually send home — and it took two pushbacks, not a rewrite.
Differentiation
You ask Claude to differentiate a writing task for three groups. Group 3’s challenge question isn’t actually challenging; it’s just the same task with a slightly harder word.
You say:
“Group 3’s challenge isn’t stretching them. Remove the scaffolding entirely and replace the challenge question with an open-ended creative extension — something with no single right answer.”
Claude rebuilds Group 3. Groups 1 and 2 stay exactly as they were.
This is the conversation most teachers aren’t having. And it’s the one that makes the biggest practical difference.
Why this feels unnatural at first
There’s a reason teachers don’t push back instinctively. Most people approach AI like a search engine. You type a query and you get a result. You accept it or you don’t. You would never have a conversation with a search engine, so why with AI?
But Claude isn’t a search engine. It’s closer to a very capable colleague who’s written a first draft and is waiting to hear what you think. The expectation, built into how it works, is that you’ll respond. You need to shape it and tell it what’s not right.
When you don’t, you get first drafts every time. When you do, you get something genuinely tailored to your class, your school, your situation.
The shift from “query and accept” to “draft and shape” is the single biggest change in how teachers use Claude effectively. Everything else follows from it.
The phrases worth keeping
You don’t need special language. These plain-English phrases work every time:
For tone:
“Too formal. Make it warmer.”
“That sounds AI-generated. Rewrite it in a more natural tone.”
“Good structure, wrong tone. Keep the structure, change the tone.”
For length:
“Cut this to four sentences.”
“Too long. What’s the one sentence that matters most? Start there.”
For scaffolding:
“Group 1’s scaffold is still too complex. Three items maximum.”
“Group 3 doesn’t need any scaffold at all. Remove it.”
For specific parts:
“Just rewrite the last sentence — the rest is fine.”
“The starter is good. The plenary isn’t. Redo just the plenary.”
For continuing the work:
“Good. Now do the same for Group 2.”
“That works. Apply the same approach to the next three pupils.”
None of these are complicated. All of them work. The download below is a full reference card organised by task — lesson planning, reports, and differentiation — that you can keep on your desk until pushing back feels natural.
One thing to add to your Project Instructions
If you find yourself saying the same push back phrase repeatedly — “don’t use ‘is beginning to’”, “no worksheet format”, “keep it under five sentences” — that’s a sign it belongs in your NOT instructions, not your prompts.
Go to your Project Instructions. Add it there. Claude will apply it automatically to every conversation in the Project from that point on, without you having to say it again.
The rule of thumb: if you’ve pushed back on the same thing three times, it’s a NOT instruction waiting to be written.
What to do right now
Open your Project. Ask Claude to plan your next lesson or draft a report comment.
When it gives you something back, find the one thing you’d change. Say it out loud in the chat.
That’s the whole shift. It’s not a new skill or a new technique. It’s just the expectation that the first response is the beginning of the conversation, not the end of it.
The full guide can be found here.
Prompt Starter Pack — a full reference card of push back phrases organised by task, ready to print and keep at your desk — is available here.