LearnGrok
Prompts
PromptAdvancedWorkflows

Assessment moderation from marked samples

Compare marked work with rubrics and benchmark samples, then create a moderation record for subject leads and assessment teams.

4 min read

Use this pack to review whether marked work has been judged consistently against the same rubric and the same annotated standards. It is for teachers, heads of department and assessment leads who need an auditable moderation record, rather than a general summary of marking.

Remove names, email addresses and any other unnecessary personal information before pasting student work. Keep the anonymous student ID consistent across every prompt so that a proposed change can be traced back to the correct record.

Stop

Protect student information

Use anonymous IDs and paste only the work, marks and annotations needed for the moderation decision.

Run the prompts in order

  1. Start with Prepare the moderation evidence register. It exposes missing annotations, unclear marks and rubric labels that do not match. Do this before asking for a judgement. A neat-looking moderation record built on incomplete source material is still incomplete.
  2. Use Compare one marked response with benchmarks for cases flagged High priority, borderline responses, and a small sample from each marker. Keep the original annotations in the input. They show whether the written justification supports the awarded mark.
  3. Use Find inconsistent judgement across markers when you have a set of comparable responses. This separates a genuine difference in student performance from a different interpretation of the criterion.
  4. Finish with Produce the subject lead moderation record. Paste only findings that you have checked. The record distinguishes a proposed amendment from a decision that has actually been agreed.

Key point

Moderate the evidence, not the marker

Ask whether the response meets the descriptor and matches the standard, rather than whether one teacher is generally strict or lenient.

Set up the source material

Put the task brief, rubric and benchmarks beside the marked responses before starting. The task brief matters because a strong response to a different question is not evidence for this assessment. Benchmark annotations matter because the mark alone does not explain why the sample represents a particular standard.

Use the rubric exactly as issued. Do not simplify criterion names halfway through the review. If the rubric says Analysis and the teacher annotation says Evaluation, record that mismatch rather than silently treating them as the same thing.

For a large set, moderate a purposeful sample first:

  • Include work near each grade or mark boundary.
  • Include work from every marker.
  • Include responses with sparse annotations.
  • Include work already queried by a teacher or student.
  • Include a small number of apparently straightforward marks.

The model you are using may handle document formats and input sizes differently. Check the relevant handling guidance in the xAI documentation overview before using a large evidence set. Split the work by assessment and criterion if needed. Do not combine different tasks merely because they share a subject.

Check the output before changing any mark

The useful test is traceability. For every proposed change, you should be able to follow a short chain: student evidence, rubric descriptor, benchmark comparison, then proposed mark. If one link is absent, the finding should be Unresolved, not a confident recommendation.

Check

Test one proposed change

Read the quoted student evidence yourself, then locate the descriptor and benchmark reference. If either does not support the proposed mark, refer it for second moderation.

Use this table to deal with common results.

If you see Treat it as What to do
A changed mark with no quoted evidence Unsupported judgement Return to the individual comparison prompt with the full response.
Similar responses receiving different marks Possible inconsistency Check whether the same criterion and descriptor were applied.
A mark that fits the rubric but not the benchmark Standard-setting question Put it in Decisions for subject lead.
Different annotations and marks Audit weakness Keep the mark under review and request a clearer marker rationale.

Watch for false precision. A response may contain evidence for part of a descriptor but not all of it. The prompts should identify that gap. They should not fill it using assumptions about what the student meant, their prior attainment, or their effort.

Watch out

Benchmarks are evidence, not replacement rubrics

Do not award a mark because a response resembles a sample in one feature while missing a required criterion.

When the result does not work

Do not ask for a cleaner answer when the source evidence is unclear. Fix the input. Add the missing page, identify the mark scale, paste the relevant benchmark annotation, or ask the original marker to explain the criterion-level judgement.

If two reasonable readings of the rubric remain, record both in the subject lead decisions section. The subject lead should decide the interpretation, document it, and apply it consistently to affected work. Then rerun the final record prompt with that decision in Decisions already agreed.

Copy-ready prompts

4 prompts. Open one to read it, or take the whole pack.

1Prepare the moderation evidence registerUse this first when the rubric, marked work and benchmark samples arrive in different formats or use different mark labels.
Create a moderation evidence register from the materials below. Do not assess the student work yet.

Documents:
- Assessment task: [paste task brief]
- Rubric: [paste rubric, including criterion names, descriptors and available marks]
- Annotated benchmark samples: [paste samples, annotations and awarded marks]
- Marked student work: [paste anonymised student responses, teacher annotations and awarded marks]

Return one Markdown table with these columns: Student ID, criterion, awarded mark, stated teacher reason, relevant benchmark sample, benchmark evidence, evidence available in student work, missing or unclear evidence, and moderation priority.

Use only evidence present in the supplied materials. Preserve the rubric's original criterion names and mark scale. Set moderation priority to High where the annotation, awarded mark and rubric descriptor do not clearly align; Medium where evidence is incomplete; otherwise Low. If a document is missing, contradictory, illegible or does not identify a criterion, write `Unresolved` and explain the exact gap. Do not infer a mark or invent student evidence.
2Compare one marked response with benchmarksUse this for a close review of one student response where the original mark may need changing.
Moderate the marked student response against the assessment rubric and annotated benchmark samples below.

Assessment task: [paste task brief]
Rubric: [paste rubric]
Benchmark samples and annotations: [paste benchmark samples]
Student ID: [paste anonymous ID]
Student response: [paste response]
Original teacher annotations: [paste annotations]
Original marks by criterion: [paste marks]

Return a Markdown table with one row per rubric criterion and these columns: Criterion, original mark, relevant response evidence (quote or precise reference), matching rubric descriptor, closest benchmark comparison, proposed mark, change (Yes/No), confidence (High/Medium/Low), and reason.

Then provide `Overall recommendation:` with either `Confirm original marks`, `Refer for second moderation`, or `Amend marks as listed`. A proposed mark must be on the rubric scale and supported by both the response and a descriptor. If benchmark samples conflict, are not comparable, or evidence is too limited, retain `Unresolved` for that criterion and recommend second moderation. Do not comment on handwriting, personality, effort, background or unsupported assumptions.
3Find inconsistent judgement across markersUse this after several teachers have marked comparable responses and you need patterns, not just individual changes.
Review consistency of judgement across the marked responses below. Compare each decision with the rubric and annotated benchmark samples. This is a moderation review, not a rewording of teacher feedback.

Assessment task: [paste task brief]
Rubric: [paste rubric]
Benchmark samples: [paste annotated benchmark samples]
Marked response set: [paste anonymised records in the form Student ID | marker ID | response | annotations | marks by criterion]

Return:
1. A Markdown table with columns: Criterion, marker ID, Student ID, original mark, proposed mark, issue type, evidence, benchmark reference, and action.
2. A section headed `Marker patterns` listing only repeated patterns affecting two or more records.
3. A section headed `Subject lead decisions needed` with numbered decisions. For each, state the disputed interpretation, records affected, and the rubric or benchmark evidence needed to decide it.

Use `No inconsistency found` where appropriate. Issue type must be one of: severity difference, criterion misapplication, missing evidence, annotation mismatch, benchmark mismatch, or unresolved. Do not treat different marks as inconsistent if the response evidence differs. If the materials cannot establish comparability, say so and identify the additional sample or clarification required.
4Produce the subject lead moderation recordUse this last, once the review findings are ready for a formal record and subject lead decision.
Create a moderation record for the subject lead using the evidence below.

Assessment details: [paste subject, class or cohort, assessment title, assessment date, moderator and original marker]
Rubric: [paste rubric or criterion summary]
Benchmark references: [paste benchmark sample identifiers and key annotations]
Moderation findings: [paste criterion-level review findings]
Decisions already agreed: [paste agreed decisions, or write None]
Unresolved points: [paste unresolved points, or write None]

Return a Markdown document with exactly these sections:
## Assessment and evidence
## Records reviewed
## Inconsistent judgements identified
## Proposed mark changes
## Decisions for subject lead
## Agreed actions and ownership
## Audit note

In `Proposed mark changes`, use a table with columns: Student ID, criterion, original mark, proposed mark, evidence, benchmark reference, status. Status must be `Agreed`, `Awaiting subject lead`, or `No change`.

In `Decisions for subject lead`, number each decision and give the available options, evidence for each option, and the consequence for affected records. In `Audit note`, state what was supplied, what was not supplied, and all unresolved ambiguity. Do not present a proposed change as agreed unless it appears in Decisions already agreed.

Last checked against xAI’s own pages on 2026-08-21. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

More in Workflows

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →

Advertise on LearnGrok

$420.69one-time, for a 30-day run

Square works best. PNG, JPEG or WebP, up to 2 MB.

Stripe on the next step. Live once approved.