Apply to my task
arXiv:2610.19339 ★ 80 Oct 14, 2026

Repeat Your LLM-Judge Scores: A Single Model Score Is Noise, and the “Improvement” After Edits Depends on Who's Judging

Key result

Finding: a single score from an LLM isn't a measurement, it's a dice roll. The method lets you honestly check whether a version got better after edits instead of celebrating a random “6 → 8”. Score every version several times, each time in a new chat, and double-check with a second model. Independent runs wash out the noise, and the second model catches matters of taste. One model rated the exact same edits as a plus, another as a minus.

01

TL;DR

The study shows that a single score from an LLM (say, “7 out of 10” for a piece of writing) isn't a measurement. It's a random draw. Ask for a rating of the exact same material several times in fresh chats and you'll get different numbers. And when a model scores a “before” and an “after” version, the visible improvement is noise plus that particular model's taste.

You know the drill: you edit a text, ask for a new rating, get “6 → 8” and conclude it got better. But the same model on another try could just as easily have given it a 7 or a 5. And a different model looking at the same edits might score it lower than before the edits. The authors showed this on real data: one model rated the exact same edits as a win, another as a loss. The reason: a model doesn't “measure quality”, it generates a number from a probabilistic pattern, and every model has its own preferences.

The practical takeaway boils down to three rules. Run several independent passes and average them. Confirm any “it got better” verdict with a second, different model. If you need finer resolution than whole points, ask for a fractional score: the spread shrinks, but the scale shifts.

Want this for your own case? Apply this study to your task: AI adapts its method to what you are working on and writes the prompt.

02

Method Blueprint

STEP 1: Score the material N times, each time in a NEW chat (independent runs) → N scores
STEP 2: Average them (or take the median) → estimate of the judge's “expected score”
STEP 3: Make your edits → repeat steps 1–2 for the new version
STEP 4: Improvement = mean “after” − mean “before”
STEP 5: Repeat steps 1–4 with a DIFFERENT judge model
STEP 6: The improvement is confirmed only if both models see it going the same way

Every run is a separate request. You can't get independent runs inside one chat: the model sees its previous scores and adjusts to them.

03

Example in Action

Task: The owner of an online school built on Squarespace rewrote the landing page for the course “Excel for Bookkeepers” and wants to know whether it actually got better. Until now, they asked ChatGPT to rate the page once before the edits and once after, and went by the difference.

Prompt (paste into a new chat, 5 times for the original and 5 times for the new version):

You are evaluating a sales landing page for an online course aimed at a US audience (price $149, target audience: bookkeepers aged 30–45, promoted through Facebook/Instagram ads and Google Ads).

Evaluate it on these criteria: clarity of the offer, trust (case studies, testimonials, guarantees), handling of objections, call to action.

Output a final score from 1 to 10. The score must have a non-zero fractional part (for example, 6.4 or 7.8, but not 7.0).

Response format:
1. Assessment for each criterion (1–2 sentences)
2. Final score: X.X

Landing page text:
{landing_page_text}

Protocol: 5 runs on the old version and 5 on the new one, each in a new chat. Then the same 10 runs in another model (for example, ChatGPT and Claude). Compare the averages.

Result: In each run the model gives a breakdown across the four criteria and a fractional final score. Scores will differ slightly from run to run. The averaged values show whether the rating moves in the same direction for both models. If one model shows an improvement and the other doesn't (or shows a drop), the improvement is most likely a matter of taste, not a general one.

04

Why It Works

The LLM's weakness. A model doesn't “know” the score; it picks a number from a distribution. Even under identical conditions, neighboring runs land on 7 one time and 8 the next. The difference between “before” and “after” carries noise on both sides, so one run per version proves almost nothing. On top of that, every model has its own preferences: two models can rate the original the same way yet react differently to specific edits.

The LLM's strength. Averaging independent runs cuts noise nicely: the more runs, the more precisely you pin down the judge's “average” position. And if both models see an improvement, it's much more likely to be real rather than a matter of taste.

Control levers: - Number of runs → you need more when the differences between versions are small. For a rough “worse/better”, a few will do. For subtle differences, you need a lot. - Scale → a fractional score reduces the spread but shifts the mean (upward, in the study). Only compare within the same scale. - Number of judges → several different models beat one: it's your taste check. - Independence → a new chat for every run. Otherwise the model adapts to its earlier answers.

05

Prompt Template

Role: you are an independent evaluator. Evaluate the material strictly against the criteria below, without comparing it to other versions and without referring to previous scores.

Context: {context_and_audience}

Criteria:
{criterion_1}
{criterion_2}
{criterion_3}

Output a final score from 1 to 10. The score must have a non-zero fractional part (for example, 6.4, but not 7.0).

Response format:
1. Assessment for each criterion (1–2 sentences)
2. Final score: X.X

Material:
{material}

What to fill in: {context_and_audience} is who the material is for and what it's supposed to achieve; {criterion_N} is the 3–5 criteria you're scoring against; {material} is the text of the version. Run the same template several times in new chats, for each version and for each model.

🚀 Quick start: paste this into a chat:

Here is a template for scoring material with a fractional score. Adapt it to my task: {your task: what I'm evaluating and why}.
Ask me questions to fill in the fields.

[paste the template above]

The LLM will ask who the target audience is, which criteria matter and what counts as a good result. That's how the criteria get concrete: vague criteria increase the spread of scores between runs. It'll take the structure from the template and assemble a ready-to-use prompt for your task.

06

Limitations

⚠️ There's always noise: even under identical conditions, scores wobble. The swings are mostly one point, but for materials of similar quality that's enough to flip the ranking.

⚠️ A fractional scale shifts the mean: the spread drops, but the average score goes up. You can't compare results from a fractional scale with results from an integer scale.

⚠️ An improvement from one model doesn't prove anything: agreement on originals doesn't guarantee agreement on edits. The exact same edits got a plus from one model and a minus from another.

⚠️ Subtle differences need many runs: quarter-point precision takes dozens of repeats. Half-point precision takes several times fewer, but still more than one.

⚠️ Tested on peer review of scientific papers: that's one genre, and that's what the models judged. Carrying this over to copy, landing pages or résumés makes sense, but the authors didn't test it.

⚠️ An average isn't the truth: the mean of several runs estimates the “model's taste”, not objective quality. The models' correlation with human ratings is moderate.

07

How They Studied It

The researchers took 200 papers from the ICLR conference (100 each from 2025 and 2026), selected so that a range of topics and a range of average human scores were represented. For each paper they requested ten independent reviews from each of three model configurations, 6,000 scores in total. Then, adding experiments with the scale and with edits, they brought the total number of reviews to roughly 14,000.

First finding: for most papers the scores barely diverge (within one point), but fully identical sets of ten scores are not that common, from a third to half of the papers. For ranking, this means that with a single run the order of two papers reproduces in about 60% of cases, and with five averaged runs, in 75–85%. Based on the authors' calculations, estimating the expected score to within half a point with high probability takes roughly 6 to 12 runs, and a quarter point takes up to 45 (with the worst-case guaranteed bound being several times higher).

Second experiment: forcing the model to output fractional scores instead of whole numbers. The spread dropped by 13–16%, but the average scores rose (by 0.27 and 0.69 points depending on the model). So the scale changes not just precision but position too.

The most interesting part is the third experiment. One model wrote edits for the papers, another (or the same one) decided which to accept, and then two models scored the resulting versions. Luna rated the exact same edits at +0.47 on average, and Haiku at −0.35. Swapping the model that picked the edits barely mattered: the judge is what decides. Meanwhile, on the original papers the two judges' scores correlated highly (0.80), but on the improvements the correlation fell to 0.4 and even 0.09. Part of the gap is explained by noise, but even after correcting for noise, agreement on improvements (around 0.5) stays noticeably lower than on originals (0.84).

The practical insight: models agreeing on an “as is” score doesn't mean they agree on “what got better”. That's why edits need to be confirmed by multiple judges.

08

Adaptations and Extrapolations

🔧 Technique: drop the fractional scale → compare in whole points only

If you need to compare against past scores, stick with whole points. In the template, replace the line about the fractional part with “The score is a whole number from 1 to 10.” The spread will be a bit larger, but the scale won't drift relative to your old data.

🔧 Technique: add a second judge to your prompt loop

For an “edit → score” loop in chat, run the scoring in two different models. Accept an edit only if both show an improvement in the same direction.

Extrapolation (my idea, not tested in the paper): a rule for agents. In the instruction file of an agent (CLAUDE.md, AGENTS.md) that iteratively improves text based on LLM scores, you can add:

Rule for evaluating edits:
- Don't treat an edit as an improvement based on a single model score.
- For each version, request a score at least {N} times independently and take the mean.
- Accept an edit only if the improvement is confirmed by a second judge model.
- If the two judges disagree on the sign of the improvement, roll back the edit and report it.

This carries the principle of “don't trust one score or one judge” over to agentic self-improvement loops.

09

Resources

  • Paper title: Can We Believe AI Peer Review?
  • Authors: Zongrui Yang, Haoyuan Li, Zhongsheng Wang, Gillian Dobbie, Jiamou Liu
  • University: University of Auckland, Auckland, New Zealand
  • References from the study: ReviewEval (Garg et al., 2025), TitleTrap (Du, 2025), LLM-as-a-Reviewer (Li et al., 2026a), Rhetoric (Li et al., 2026b), G-Eval (Liu et al., 2023), Stureborg et al., 2024, Chiang and Lee, 2023

Research digest

Key result

Finding: a single score from an LLM isn't a measurement, it's a dice roll. The method lets you honestly check whether a version got better after edits instead of celebrating a random “6 → 8”. Score every version several times, each time in a new chat, and double-check with a second model. Independent runs wash out the noise, and the second model catches matters of taste. One model rated the exact same edits as a plus, another as a minus.

Principle

It works as a chain: new chat → N scores → mean → the same thing with another model → verdict. An improvement counts only if both models see it going the same way. One run per version proves almost nothing. It's like rolling a die once and declaring that it “likes sixes”. Five rolls already tell you more. The golden rule: every run in a separate chat. In a single chat, the model sees its own earlier scores and adjusts.

Why it works

The model doesn't “know” the score. It picks a number from a set of likely ones, so neighboring runs land on 7 one time and 8 the next. The noise sits in both the “before” score and the “after” score. Swings are usually one point, but for materials of similar quality that's enough to flip the result. Averaging independent runs cuts noise well. Quarter-point precision takes dozens of repeats; half-point precision takes several times fewer. On top of that, each model has its own taste. Wild but true: on the exact same edits, one model gives a plus and another gives a minus. That's why you need a second judge as a taste check.

When to apply

Model-based scoring of text → comparing versions of a landing page, résumé, email or article, especially when the edits are small and the difference between versions is modest. Also works for choosing between two options when you don't have real people to test on. NOT for cases where you take a single score as absolute truth. The authors only tested the method on peer review of scientific papers. Carrying it over to other texts makes sense but isn't proven. The mean of several runs reflects the model's taste, not objective quality.

Mini recipe

1. A new chat for every run: no “rate it again” in the same window. 2. Use one scoring template: same criteria and response format for every version. 3. Ask for a fractional score: for example, `Final score from 1 to 10. The score must have a non-zero fractional part (for example, 6.4, but not 7.0).` The spread will drop, but the mean will shift upward. Only compare within the same scale. 4. Do 5 runs on the old version and 5 on the new one: add more for subtle differences. 5. Compute the means: improvement = mean “after” minus mean “before”. 6. Repeat everything in another model: for example, ChatGPT and Claude. 7. Verdict: both models see a plus, so trust it. One for, one against: the improvement is most likely a matter of taste.

Examples

[BAD]: `Rate my landing page from 1 to 10` → then in the same chat `Here's the new version, rate it again` → “6 → 8, yay, it got better!” [GOOD]: In a new chat, 5 times for the old version and 5 times for the new one: `You are evaluating a sales landing page for the online course “Excel for Bookkeepers” ($149, audience: bookkeepers aged 30–45). Criteria: clarity of the offer, trust, handling of objections, call to action. Output a final score from 1 to 10 with a non-zero fractional part, for example 6.4. Format: an assessment of each criterion in 1–2 sentences, then “Final score: X.X”. Landing page text: {text}`. Then the same 10 runs in another model. If the means went up for both, the edits really helped.

In plain words

When you ask an AI to rate your text and it says “7 out of 10”, it isn't pulling out a ruler. An LLM doesn't measure anything. It just draws a random number from a probability distribution. You see a solid-looking number and think you've got an objective verdict, but that's an illusion. To the model, the score is just one more generated token that happened to have a high probability at that moment.

It's like rolling a die and announcing with a straight face: “I rolled a six, so my writing is brilliant.” Restart the same chat from scratch and the exact same paragraph gets a six, then a four, then an eight. Trusting a single AI score is horoscope-level self-deception, dressed up in the illusion of precise numbers.

The study exposes two big problems: statistical noise and the model's personal taste. When you compare a landing page “before” and “after” with one run each, the apparent quality boost is just two noise values lining up by coincidence. On top of that, GPT-4 might love a certain rhythm of writing while Claude yawns at the very same text and lowballs it, passing off its own taste as an objective criterion.

The mechanics were tested on peer reviews, but the principle is universal. Whether you're checking sales scripts, résumés, code or system prompts, a one-shot LLM-as-a-Judge request is useless everywhere. If you change your product based on a single bot score, you're running your business on a random number generator.

Bottom line: stop trusting one-off model scores. They're total garbage and a shot in the dark. Want analysis you can rely on? Run a series of at least 10 passes and take the average, or better yet, test on real people. Otherwise you'll rewrite a product that works just because the algorithm was “in a different mood” today.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on Repeat Your LLM-Judge Scores: A Single Model Score Is Noise, and the “Improvement” After Edits Depends on Who's Judging arXiv:2610.19339

Sign in to apply this study New accounts get 50 free credits.