Single answer grading
The judge scores one answer against the rubric, alone.
- Works for monitoring live traffic
- Scores drift without anchors
- Prefer pass or fail to 1–10
A judge model reads an answer against written criteria and returns a verdict. It scales where people cannot — and it has biases you must measure before you trust it.
When an output is free text — a summary, an answer, a reply to a customer — no exact rule can grade it. Using an LLM as a judge means asking a second model to grade it against a rubric. This guide covers the three ways to set one up, what the research found about how often judges agree with people, the biases that skew them, and a step-by-step method for building a judge whose verdicts you can rely on.
Updated · 8 sources
LLM as a judge is an evaluation method in which a language model grades the output of another AI system against written criteria — scoring one answer, picking the better of two, or comparing an answer with a reference. It replaces slow human grading for open-ended text at scale. Research shows strong judges agree with human preferences about as often as people agree with each other, but they also favour the first answer shown, longer answers and text like their own, so a judge must be checked against human labels before it is trusted.
The MT-Bench paper that made the method mainstream used three set-ups. Each answers a different question and fails in a different way.
The judge scores one answer against the rubric, alone.
The judge sees two answers to the same input and picks the better one, or a tie.
The judge compares the answer with a known good one or with source passages.
Which set-up fits the question you are asking?
Agreement with people is high on average and uneven in the details. How ties are counted moves the headline figure by twenty points, and the same papers that showed judges work also catalogued how they go wrong.
The first four are measured in published work; the fifth is the property every model grader shares. None is a reason to stop using judges; each is a reason to design the judge call carefully and keep measuring it.
| Bias | What happens | Countermeasure |
|---|---|---|
| Position | The answer shown first, or second, wins more often regardless of quality. In MT-Bench, GPT-4 gave the same verdict after a swap in 65% of cases. | Run pairwise comparisons in both orders; count a split as a tie. |
| Verbosity | Longer answers score higher, even when the extra text adds nothing. Padding a list with rephrased items fooled GPT-3.5 and Claude-v1 91% of the time, GPT-4 9%. | Put length in the rubric; compare answers of similar length; grade claims, not prose. |
| Self-preference | A judge rates its own outputs above others’ that people judge equal; GPT-4 and Llama 2 can tell their own text apart. | Use a judge from a different family than the system under test, or a panel of several. |
| Weak reasoning | Judges miss errors in maths and reasoning — GPT-4 passed wrong answers to problems it could solve alone, misled by the answer it was shown. | Grade those with code: run the tests, check the sums. Use a reference answer. |
| Non-determinism | The same output can get a different verdict on another run, and verdicts shift when the judge model or prompt changes. | Binary verdicts; re-check against human labels after any change to the judge. |
A judge is a model, so it is evaluated like one. Anthropic’s guidance lists the weakness of model-based graders plainly: they are non-deterministic and need calibration against human graders. Treat the judge as one more system with its own golden dataset.
The steps are the same whether the judge grades summaries, support replies or extracted clauses. The order matters: a rubric nobody agreed on cannot be calibrated.
Split “good” into yes-or-no checks: states each key fact, makes no claim the source does not back, asks before acting.
The most capable model you can afford, from a different family than the system under test.
The judge explains against each criterion, then returns a structured verdict.
People grade a sample with the same rubric — 50 to 100 outputs is our rule of thumb, not a published figure — and you count how often the judge agrees.
Re-sample after any change to the rubric or the judge model, and read the disagreements.
You are grading an answer to a customer question.
Question: {question}
Source: {retrieved passages}
Key facts: {facts the answer must state}
Answer: {answer under test}
For each key fact: is it stated in the answer? (yes/no)
For each claim in the answer: is it supported
by the source? (yes/no)
Explain briefly, then return JSON:
{ "facts_stated": [...], "claims_without_support": [...],
"verdict": "pass" | "fail" }Graders sit on a scale from cheap and rigid to costly and nuanced. A good evaluation uses the cheapest grader that can see the failure, and reserves people for calibrating the rest.
Botminds uses a judge where rules cannot read — and keeps it honest: rules score everything they can, the judge answers yes or no, and the scorecard names the judge.
Every field a rule can score is scored by the rule.
The judge returns a binary verdict — supported or not.
Pick one from a different model family than the agent.
The scorecard names the judge, and shows a fallback as a fallback.
Verdicts feed a case-by-case comparison with a pinned baseline when an agent is published.
Does the answer state each fact the case expects?
Is each claim supported by the source documents?
Checked by rules on every turn: said what it must, avoided what it must not, asked before changing anything.
Read the full design in AI agent evaluation, and set up an evaluation in the Academy lesson crew and evaluations.
On average, strong judges agree with human preferences over 80% of the time — about as often as people agree with each other. That figure leaves out ties; counting them, GPT-4 and experts agreed 66% of the time and experts with each other 63%. Judges are weaker on maths and reasoning, and biased by answer order, length and their own outputs, so validate a judge against human labels for your task before trusting it.
Grading open-ended output that no exact rule can score: whether a summary is faithful, whether an answer covers the key facts, whether a reply follows tone and policy, and which of two versions of a system is better.
The written criteria the judge applies. Good rubrics break quality into specific yes-or-no checks — states each key fact, makes no claim the source does not back — rather than asking for an overall score.
The tendency to prefer the answer in a particular position when comparing two. In one study, changing only the order let a weaker model beat a stronger one on 66 of 80 questions. Running each comparison in both orders cancels it.
Yes, where you can. Judges rate their own outputs above others of equal quality; a judge from a different family, or a panel of several from different families, reduces that bias.
An LLM judge reads the output and returns a verdict. An agent judge can act: open files, run code and inspect intermediate steps, which suits grading an agent’s multi-step work. Research in 2024 found it as reliable as human evaluators on a benchmark of 55 AI development tasks.
Have people grade a sample of outputs with the same rubric, measure how often the judge agrees, read the disagreements, and repeat after any change to the rubric or the judge model.
For scoring at volume, largely yes — once calibrated. People remain the reference: they write the rubric, label the calibration sample and settle the cases where the judge and the rules disagree.
Bring one process and its documents. We’ll show you the agents, the controls and the record, running on your data.