Stop Building Rubrics From Scratch: 4 AI Prompts That Do It Properly
Every teacher knows a good rubric pays for itself. It makes marking faster, keeps you consistent across thirty scripts, and gives students something concrete to aim at instead of a vague grade. The problem is building one from scratch — turning a task and a curriculum level into clear, gradeable criteria takes real thinking time, and it's usually the first thing that gets skipped when the week gets busy.
This is a genuinely good use of AI, because a rubric is a structured document with a predictable shape. You still need to check every line against what you actually want from students — but the first draft, the part that takes the longest, is exactly what AI is fast at.
1. The task-to-rubric prompt
Start here, with the task itself:
"Here is a task I'm setting for [year level, subject]: [paste task]. Build a marking rubric with 4 performance levels (e.g. Not Yet Achieved, Achieving, Merit, Excellence). Base the criteria on [curriculum standard or learning objective, paste if you have one]. For each level, describe what the work looks like in specific, observable terms — not vague language like 'good understanding.'"
The "observable terms" instruction is the one that matters most. Without it, you get four rows that all say some version of "shows understanding," which is useless for actually sorting work into levels.
2. The NCEA-alignment prompt
If you're marking against an NCEA achievement standard, don't make AI guess at wording:
"Here is the achievement criteria for NCEA [standard name/number]: [paste from NZQA]. Turn this into a student-facing checklist that breaks 'Achieved,' 'Merit,' and 'Excellence' into plain-language, specific actions a Year [X] student can self-check against before submitting."
This is different from the official standard itself — you're not rewriting the assessment, you're translating it into something a fifteen-year-old can actually use to check their own work before handing it in.
3. The consistency-check prompt
Once you've got a draft rubric, stress-test it against real work before you use it on the whole class:
"Here is my rubric: [paste]. Here are two student responses to the same task: [paste both]. Mark each one against the rubric and explain your reasoning for each criterion. Flag anywhere the rubric is ambiguous or where two markers might reasonably disagree."
That last sentence is doing the real work. It surfaces the vague criteria before you're 15 scripts into marking and realise row three doesn't actually distinguish Merit from Excellence.
4. The student-friendly rewrite
Teacher-facing rubrics and student-facing success criteria aren't the same document, but you can generate both from one draft:
"Rewrite this rubric as student-friendly success criteria — first person, plain language, no jargon. Format it as a checklist students could use to self-assess before submitting: [paste rubric]."
Put this version on the task sheet or the slide. Students engage with "I have explained my reasoning using evidence from the text" far more than they engage with a grid of achievement-standard language.
The part AI can't do
A rubric encodes what you value in student work — and that's a judgement call, not a language task. Read every level of every criterion before it goes anywhere near a class, and don't be afraid to throw out a row that sounds right but doesn't match what you'd actually reward in practice. The prompt gets you 80% of the way there. Your subject knowledge closes the gap.
If you only build one thing from this list, make it the rubric-to-checklist rewrite in #4 — it's the fastest to produce and the one students actually read.
TeachSmarterAI helps New Zealand teachers use AI tools effectively. New posts every week.