One judge call, several scores
Most real outputs are not pass/fail on a single dimension — they need to be correct AND complete AND on-tone AND safe. You can run four separate judge calls, but a well-designed multi-criteria prompt does it in one shot, returning a structured score for each axis.
Anatomy of a multi-criteria judge
- List the criteria explicitly at the top of the prompt with definitions.
- Provide examples per criterion if calibration matters.
- Require structured output — JSON with each criterion as a named field.
- Force the judge to reason per axis before scoring (rationale before verdict).
Why one call beats N calls
- Cheaper — one round-trip, one input cost.
- Consistent context — the judge sees all criteria at once, reducing variance.
- Easier to log — one structured object per case.
Why N calls sometimes wins anyway
- For very nuanced criteria, the judge may not distribute attention well across axes — one call diluted, four calls focused.
- Different criteria may need different judge models (a strong model for correctness, a fast cheap one for format).
- Per-axis prompts can be reused across products.
Principle: Default to one multi-criteria call. Split into per-axis calls only when calibration evidence shows the combined call is missing things.