Track 05 · EvalsLesson 03 of 10
LLM judges and rubrics you can trust
Scale review with a judge model, calibrated against people.
- The FDE path · Stage 5 of 6
- 45 min read
- 60 min hands-on
- Pro
What you'll be able to do
01- Decide when a judge model is the right grader, and when code or a human should grade instead.
- Choose between pointwise, pairwise and reference-based grading for a given criterion and decision.
- Design a rubric of decomposed binary criteria with definitions, examples and an applicability rule.
- Write a judge prompt that reasons before its verdict, returns structured output and treats the graded text as data.
- Diagnose judge biases and calibrate a judge against SME labels with a confusion matrix, Cohen's kappa and a position-swap check.
- Control judge cost and drift with versioning, canary items, cascades and sampling.
Before you start
- From requirements to eval criteria: a judge grades a criterion; the criterion comes first.
- Golden datasets and the metrics that matter: calibration labels, splits and labelling guidelines.
- Typed output: schemas, validation and tool calls: judge verdicts should be schema-constrained.
- Reasoning models and what thinking costs: reasoning judges cost more; decide when it pays.
The short version
An LLM judge is a model that grades another model's output against a rubric. It is how you grade faithfulness, tone and adequacy across thousands of cases when code cannot decide and SMEs cannot read them all. It is also an instrument that can be biased, lenient or inconsistent, so it is not valid until you have compared it with human labels. Use judges only where code cannot grade. Write rubrics as small, binary, decomposed criteria with definitions and examples, not as a 1–10 scale. Ask for reasoning before the verdict, constrain the output to a schema, and treat the graded text as data. Calibrate on a held-out set of SME labels and report the confusion matrix and Cohen's kappa, not raw agreement. Check position bias in pairwise judges by swapping the order. Version the judge like any release, re-calibrate when anything in it changes, and never change the judge and the system in the same comparison.
- A judge is an instrument; calibrate it before you trust it.
- Binary, decomposed criteria beat unanchored numeric scales for agreement, calibration and action.
- Kappa, not raw agreement. On an imbalanced set, a judge that always says "pass" can agree 95% of the time and be worthless.
- Known biases are predictable. Position, verbosity and self-preference have documented mitigations.
- Judges drift when their model or prompt changes. Pin, version, re-calibrate, and run canary items every time.
Pro lesson
The rest of this lesson is in Pro.
The mental model, worked example, field note, failure table, exercise and self-check, with the voice tutor.
Pro opens this stage
Stage 5 · Prove it and pass review- 7 lessons, with the voice tutor
- Lab · Clean a golden set before you trust it, graded here
- Halden week 4 · First slice due
- Halden week 6 · Instructions hidden in an invoice
- The lab kit, to run Halden weeks on your machine
Also in Pro
- Every stage and specialisation, in full
- Every lab and every role project
- Halden weeks 2–10, on your record
- Every drill, live in the playground
- All solutions, plus the server judge
- Lab Assistant and every Teach with AI