1. Evaluation as Measurement

Jiaming Qu/~12 min read/Preface

Evaluating generative AI systems increasingly depends on two sources of judgment: human annotators, who provide reference labels, and large language models used as automated evaluators (“LLM judges”), which provide those labels at scale. This handbook is a practical guide to building both and to determining whether they agree in the way a given decision requires.

The intended readers are practitioners who must design and run an evaluation rather than survey the literature: a human–computer interaction (HCI) student preparing a first crowdsourced annotation study, a data scientist drafting a labeling plan, or an engineer asked to automate an evaluation with an LLM judge. Where several reasonable approaches exist, the handbook describes what each one costs and what typically goes wrong when a step is omitted, rather than prescribing a single procedure. Each chapter contains interactive figures, mocked annotation interfaces, small calculators, and a short quiz. All examples are either fictional or drawn from public datasets.

This preface establishes the vocabulary used throughout. Section 1.1 presents a representative failure case. Sections 1.2 and 1.3 introduce the two concepts that every later chapter depends on: the decision an evaluation serves, and the kind of reference its labels can have. Section 1.4 combines these into the organizing framework of the handbook, the three-way alignment model. Section 1.5 describes the running example and suggested reading paths.

How evaluations fail

The use of LLMs as evaluators gained traction as studies reported that strong models agree with human preferences about as often as humans agree with one another. On the MT-Bench benchmark, for example, when tied votes were excluded, the agreement between a strong LLM judge (GPT-4) and expert annotators reached 85%, slightly above the 81% agreement observed among the experts themselves; with ties included, both figures were lower (66% and 63%)[1]. Subsequent large-scale comparisons have been more cautious: across 20 natural language processing tasks, the correlation between LLM judges and human annotators varied widely across datasets, judged properties, and judge models[2]. In parallel, research on human annotation has shown that disagreement among annotators is often systematic rather than random noise[3]. Taken together, these findings suggest that neither the human labels nor the automated judge can be assumed reliable without examination.

The following composite scenario illustrates how such problems arise in practice. It concerns Mise, a fictional cooking assistant that answers questions about recipes, substitutions, techniques, and food safety, which serves as the running example for the handbook. A team wishes to determine whether a new version of Mise is better than the current one. Crowdworkers are asked “Is this response helpful? (1–5)” for 2,000 conversations, and the mean rating rises from 3.9 to 4.2. The team then replaces the crowdworkers with an LLM judge that agrees with the crowd on 85% of items and runs it on every subsequent release. Six months later, a user reports that Mise advised them that rice left at room temperature overnight was safe to eat.

Each step in this process had a defensible rationale, and each also left a gap:

Step Apparent justification What was missing
Target “Helpfulness” is the property of interest. No one specified whether a confident, friendly, but unsafe answer counts as helpful.
Sample 2,000 randomly selected conversations. Food-safety questions were about 3% of traffic, so only about 60 were rated.
Human labels The mean rating increased. No measurement of whether raters agreed with one another or with a food-safety expert.
LLM judge 85% agreement with the crowd. Agreement was concentrated on easy items; the judge reproduced the crowd’s blind spot.
Operations The judge ran on every release. No fresh human audits were collected, so the problem was not detected.

Additional annotation volume, a larger judge model, or a more sophisticated aggregation method would not have corrected these problems, because they originated in the design of the measurement and compounded across steps. The gaps also fall into recognizable groups: an unclear target (what was being measured), an unexamined human reference (whether the human labels were consistent and correct), an unexamined judge (whether the automated evaluator was consistent), and an unexamined relationship between the two (whether the judge agreed with humans on the items that mattered). The remainder of this preface addresses these groups in order, beginning with the target.

Start from the decision

The first gap in the scenario, an unclear target, is the most consequential because every later step inherits it. The difficulty becomes concrete when a single response is assessed against several plausible targets. The figure below shows one Mise conversation; selecting a different property changes the verdict, even though the conversation does not change.

Interactive figure

One response assessed against four constructs

Select the property being measured.

mise · conversation #0417
User I left cooked rice on the counter overnight. Is it still OK for fried rice? And how do I get it crispy?
Mise Day-old rice is actually perfect for fried rice! Its drier texture crisps up beautifully. Heat a well-oiled wok until it’s smoking, press the rice flat, and leave it alone for 2–3 minutes before tossing. Enjoy! 🍳
Construct:

Likely high

The response is confident, positive, and actionable. Many users would rate it favorably, so a metric based on user ratings would reward it.

Partially

The response addresses how to make the rice crispy, but it answers the safety question only by implication, and with respect to a different situation (refrigerated day-old rice).

Misleading

The common advice that day-old rice is preferable for fried rice refers to rice that was cooled and refrigerated. The response treats rice stored at room temperature as equivalent.

Unsafe

Food-safety guidance generally recommends discarding cooked perishable food that has been kept at room temperature for more than about two hours. Cooked rice is a recognized risk because Bacillus cereus spores survive cooking, and the toxin they can produce is not reliably destroyed by reheating. This is the most serious defect of the response, and a satisfaction metric would not register it.

The question “Is this response good?” has no stable answer. Four precise questions yield four different and defensible answers.

In measurement terms, each of these properties is a different construct: an abstract quality that cannot be observed directly and must be operationalized through a concrete procedure, such as a rubric applied by annotators[4]. Choosing among constructs is not a technical question; it depends on what the evaluation is for. A team deciding whether a release is safe to ship needs the food-safety construct, while a team optimizing engagement may care about satisfaction. For this reason, the most reliable starting point for an evaluation is a written statement of the decision it will inform.

Underspecified request

“Obtain quality ratings for 3,000 responses so that the new model can be evaluated.”

  • Quality of what: the answer, the tone, safety, or formatting?
  • Rated on which scale, and by whom?
  • Which result would change the team’s course of action?
Decision-ready brief

“Should model v3 be replaced with v4 in production next month?”

  • Unit: one user question and one model response
  • Population: English questions from the last 30 days
  • Measures: percentage of responses that fully answer the question; percentage that are unsafe
  • Rule: ship if v4 is non-inferior on the answer rate and not worse on the unsafe rate

The decision-ready brief fixes five elements, each of which constrains a later design choice:

  1. Construct: the property of interest (for example, “fully answers the user’s question”), stated precisely enough that two people could disagree about whether a given response satisfies it.
  2. Unit of analysis: a single response, a conversational turn, a whole conversation, or a user. Rating responses and rating conversations produce different numbers from the same logs.
  3. Population: the traffic, languages, and time window that the final number will claim to describe.
  4. Estimand: the quantity to be estimated, such as “the proportion of eligible responses that fully answer the question” or “the probability that v4 is preferred over v3 in a head-to-head comparison.”
  5. Decision rule and tolerance: which result leads to which action, and how much statistical uncertainty is acceptable.

Different purposes lead to substantially different designs, even when the underlying data are the same. The figure below summarizes how four common purposes change the sampling plan, the label format, and the main driver of annotation volume.

Interactive figure

How the purpose of an evaluation shapes its design

Select the purpose of the labels.

SampleA probability sample of production traffic, so that the estimated rate generalizes. Risky slices may be oversampled only if the selection weights are recorded.
Label formatNarrow and, where possible, binary (“Is this response unsafe?”). Speed and consistency matter more than richness.
Volume driverThe width of the confidence interval around the rate that will be compared with the threshold.
Main riskA threshold chosen after the data have been seen. The threshold should be recorded in advance.
SampleThe same prompts answered by both models (a paired design), drawn from the population of interest.
Label formatOften pairwise (“A or B?”, with a tie option), with the presentation order randomized for each item.
Volume driverThe smallest difference that must be detectable. Small differences require more pairs than is commonly expected.
Main riskPosition bias, and annotators who infer which side is the new model from stylistic cues.
SampleDeliberately not representative: rare classes, boundary cases, and known failures are oversampled.
Label formatRicher: the full label taxonomy, corrections, and rationales. Reuse value matters.
Volume driverCoverage of difficult regions of the input space, rather than the total count.
Main riskReporting accuracy on this set as if it described production performance.
SampleTwo parts: a representative set, to estimate realistic agreement, and a challenge set of boundary cases, bias probes, and rare severe cases.
Label formatIdentical to the judge’s output format, with several independent human labels per item so that human–human agreement can be measured.
Volume driverPer-class and per-slice precision, especially for the rare class the judge must detect.
Main riskTuning the judge prompt on the same items that are used to report its performance (Section 4.5).
Practical note

Before any data are collected, it is useful to draft the sentence that the final report is expected to contain, leaving the results blank: “On [population], v4 fully answers [__]% (95% CI [__, __]) of questions, compared with [__]% for v3; therefore the team will [ship / not ship].” If the population and the decision cannot be filled in, the evaluation is not yet ready for annotation.

Fixing the construct answers the question of what is measured. It does not yet answer what a correct label for that construct would be, or how disagreement among annotators should be interpreted. That depends on the kind of reference the construct admits, which is the subject of the next section.

Three kinds of reference

Consider three questions about Mise responses. Whether “350°F is approximately 175°C” is correct can be checked against a conversion formula. Whether a response “fully answers the question” depends on how a rubric defines “fully.” Whether one reply “feels more encouraging to a nervous beginner” depends on the reader. If two annotators disagree, the appropriate response differs in each case: in the first, one of them is wrong; in the second, either one is wrong or the rubric is incomplete; in the third, the disagreement may itself be the finding. It is therefore useful to classify the evaluation question before designing the annotation task, because the classification determines what a reference label means.

KindExampleReferenceDisagreement indicates…
Verifiable Is “350°F ≈ 175°C” correct? A trusted source or a deterministic check An error by at least one annotator.
Rubric-interpreted Does this response fully answer the question? An operational rubric applied by trained annotators, with adjudication An annotator error or a gap in the rubric; the case must be read.
Subjective Which reply feels more encouraging to a nervous beginner? The distribution of judgments in the intended population Often genuine variation that should be preserved rather than resolved by vote.

The boundary between rubric-interpreted and subjective questions is partly a design decision. Röttger et al. describe two annotation paradigms: a prescriptive paradigm, in which annotators are instructed to apply a guideline’s view, and a descriptive paradigm, in which annotators are asked to report their own view[5]. Both are legitimate, but combining them unintentionally within one task tends to produce data that are difficult to interpret, since some annotators follow the guideline and others follow their personal judgment. For genuinely subjective tasks, a substantial body of work argues that annotator disagreement carries information and should not be discarded[6][3].

Exercise

Classifying evaluation questions

For each question, select the kind of reference that fits best. Two of the items are open to argument; the accompanying notes explain why.

0 of 6 classified.

With a construct fixed and the kind of reference identified, the target of the evaluation is defined. The remaining gaps from Section 1.1 concern the instruments that measure this target, namely the human annotators and the LLM judge, and the relationship between them.

The three-way alignment model

In the scenario of Section 1.1, the team summarized the evaluation with one number: the judge “agreed with humans 85% of the time.” That single number combined three separate questions. Were the human labels themselves consistent? Was the judge consistent with itself? And did the judge agree with the human labels on the items relevant to the decision? A high value could hide a failure in any of the three, and a low value would not indicate which one had failed.

Measurement theory offers a useful distinction here. Reliability refers to whether a measurement procedure produces consistent results when repeated; validity refers to whether it measures the intended construct[7][4]. A procedure can be highly reliable and still invalid, for example when every annotator consistently applies the same mistaken rule. Applied to an evaluation that combines human annotators and an LLM judge, this distinction suggests examining three forms of agreement separately, each anchored to the decision and construct defined in Sections 1.2 and 1.3:

  1. Alignment within humans: whether annotators apply the rubric consistently with one another, with themselves over time, and in the way the rubric intends.
  2. Alignment within the judge: whether the judge produces the same verdict across repeated runs, swapped presentation orders, paraphrased prompts, and irrelevant edits to the input.
  3. Alignment between humans and the judge: whether the judge agrees with the human reference closely enough, on the items and subgroups that matter for the decision.

Separating the three is useful because each has distinct failure modes, distinct metrics, and distinct remedies. When the judge and the human labels disagree, the decomposition indicates where to look: at the human reference, at the judge, or at the rubric that both are meant to follow. The figure below summarizes each component and where it is treated in the handbook.

Interactive figure

Three alignments anchored to one decision

Select a component to display its central question, typical measures, and the chapters that cover it.

⟵ ⟶ ⟵ ⟶
All three components are anchored to the same decision and construct (Sections 1.2–1.3) and must continue to hold over time (Chapter 7).

Two consequences of this framework recur throughout the handbook.

Agreement between humans and the judge is bounded by agreement among humans

If two trained annotators agree with each other at a chance-corrected agreement of Cohen’s κ = 0.55 (a statistic defined in Section 3.2, where 1 indicates perfect agreement and 0 indicates agreement no better than chance), a judge cannot meaningfully be expected to agree with individual annotators at κ = 0.9, because there is no single human answer for it to match. A judge whose agreement with humans approaches the level of human–human agreement is already performing comparably to an additional annotator. The informative comparison is therefore between the judge and this human ceiling, rather than between the judge and perfect agreement; Zheng et al. use exactly this comparison when assessing LLM judges[1]. Section 6.1 develops the idea further.

High agreement does not establish validity

Agreement is evidence of reliability, not of validity. If all annotators have learned the same incorrect rule (for example, “a polite and confident answer is helpful”), they will agree closely, and a judge tuned to match them will agree closely as well. All three alignments can then appear excellent while the measurement targets the wrong construct. This is why the handbook treats the decision and the construct as the anchor for every alignment, and why independent checks against expert-verified items appear in several later chapters.

Summary of the framework

The decision and construct define the target. Alignment within humans and within the judge describe the precision of each instrument, that is, how tightly its measurements cluster. Alignment between the two, together with independent expert checks, provides evidence of accuracy, that is, whether the clusters lie on the target. All three are required, and each is diagnosed separately.

Running example and reading paths

Abstract guidance on evaluation is difficult to apply without a concrete case, so every chapter uses the same fictional product. Mise, the cooking assistant introduced in Section 1.1, is evaluated on three tasks. They were chosen so that together they cover the three kinds of reference described in Section 1.3, and each chapter refers to them by the names below.

TaskQuestionLabelsCharacteristics
Answer-quality task Does the response fully answer what the user asked? Fully / Partially / Does not answer Rubric-interpreted; the primary task in most chapters.
Food-safety task Does the response contain unsafe food-handling advice? Safe / Unsafe Close to verifiable; rare (about 3% of traffic) but severe.
Pairwise preference task Which of two responses would the user rather receive? A / B / Tie Partly subjective; used to compare model versions.

Public datasets for practice

Readers who wish to apply the techniques to real data may use the following public resources, which correspond closely to the three tasks. Each provides multiple human judgments per item, which is a prerequisite for studying agreement.

  • MT-Bench human judgments: approximately 3,300 expert pairwise preferences over responses from six models to 80 multi-turn questions[1]. Suitable for pairwise preference experiments and position-bias analysis.
  • SummEval: 1,600 news summaries rated for coherence, consistency, fluency, and relevance by both experts and crowdworkers[8]. Suitable for examining divergence between expert and crowd ratings.
  • HelpSteer2: approximately 20,000 responses rated on five attributes (helpfulness, correctness, coherence, complexity, and verbosity) on a 0–4 scale[9]. Suitable for pointwise, multi-criterion rubrics similar to the answer-quality task.
  • Chatbot Arena: large-scale crowdsourced pairwise preferences collected from real users[10]. Suitable for studying descriptive preference data at scale.

Reading paths

Each chapter is designed to be read independently in 10–15 minutes and begins with a short note on the context and prerequisites it assumes. The following paths are suggested for common roles.

Chapter 2 (task design, rubric, interface, and pilot) and Chapter 3 (agreement, rater bias, and aggregation) form the core. Chapter 6 explains how the resulting labels are later used to validate automated evaluators.

Chapter 2 provides useful background. The core material is Chapter 4 (building the judge), Chapter 5 (stress-testing it), and Chapter 6 (aligning it with human labels). Section 3.2 introduces agreement statistics that are reused in those chapters.

The chapters are intended to be read in order. Particular attention to Chapter 6 (selective judging and correction of aggregate estimates) and Chapter 7 (drift, launch gates, and cold start) is recommended.

The first component of the framework, alignment within humans, begins with the design of the annotation task itself. Chapter 2 describes how to turn a decision brief into a rubric, a sample, and an annotation interface, and how to pilot them before collecting data at scale.

Summary & quiz

  1. Evaluation failures usually originate in design gaps that compound across steps, not in an insufficient number of labels.
  2. An evaluation should begin with a written decision brief: construct, unit of analysis, population, estimand, and decision rule. The purpose of the evaluation changes the sample, the label format, and the required volume.
  3. Evaluation questions may be verifiable, rubric-interpreted, or subjective. The classification determines what disagreement between annotators means.
  4. “Alignment” should be examined as three separate questions: within humans, within the judge, and between the two. The third is bounded by the first two.
  5. Agreement is evidence of reliability, not validity; annotators and judges can agree on an incorrect rule.

Annotators agree with each other on 94% of items, and an LLM judge agrees with them on 92%. Which conclusion is justified?

High agreement shows that the instruments are consistent with one another. It does not show that the shared rule matches the intended construct. Percent agreement is not meaningless, but it can be inflated by class imbalance, as Section 3.2 demonstrates.

Food-safety questions were oversampled to 30% of a labeled set, although they constitute 3% of traffic. A stakeholder requests the production rate of unsafe responses. What is the appropriate response?

An oversampled set is effective for finding failures, but its raw rate does not describe production. If selection probabilities were recorded, the estimate can be reweighted; otherwise, per-slice results should be reported. Discarding items is valid but wastes labels that have already been collected.

On the answer-quality task, human annotators agree with each other at κ = 0.60. A new judge reaches κ = 0.58, averaged over its agreement with each individual annotator. Which interpretation is most reasonable?

The judge should be compared with the human–human ceiling rather than with perfect agreement. Section 6.1 adds a caveat: it remains necessary to examine where the judge disagrees, because matching the average can conceal poor performance on a critical subgroup.

Which question is best treated as subjective, so that the distribution of judgments is preserved rather than reduced to a single label?

The first question can be checked mechanically, and the second has an authoritative reference in published food-safety guidance. The appropriateness of humor varies across readers, and the spread of opinion is part of what the evaluation should capture.

In the three-way alignment model, which observation most directly indicates a problem within the judge?

A verdict that changes with presentation order is an inconsistency of the judge with itself, independent of any human label. Disagreement with the human majority concerns alignment between the two, and disagreement between annotators concerns alignment within humans.

References

  1. Zheng, L., Chiang, W.-L., Sheng, Y., et al. (2023). Judging LLM-as-a-judge with MT-Bench and Chatbot Arena. NeurIPS 2023 Datasets and Benchmarks.
  2. Bavaresco, A., Bernardi, R., Bertolazzi, L., et al. (2025). LLMs instead of human judges? A large scale empirical study across 20 NLP evaluation tasks. ACL 2025.
  3. Plank, B. (2022). The “problem” of human label variation: On ground truth in data, modeling and evaluation. EMNLP 2022.
  4. Jacobs, A. Z., & Wallach, H. (2021). Measurement and fairness. FAccT 2021.
  5. Röttger, P., Vidgen, B., Hovy, D., & Pierrehumbert, J. (2022). Two contrasting data annotation paradigms for subjective NLP tasks. NAACL 2022.
  6. Aroyo, L., & Welty, C. (2015). Truth is a lie: Crowd truth and the seven myths of human annotation. AI Magazine, 36(1).
  7. Messick, S. (1995). Validity of psychological assessment: Validation of inferences from persons’ responses and performances as scientific inquiry into score meaning. American Psychologist, 50(9), 741–749.
  8. Fabbri, A. R., Kryściński, W., McCann, B., Xiong, C., Socher, R., & Radev, D. (2021). SummEval: Re-evaluating summarization evaluation. TACL, 9.
  9. Wang, Z., Dong, Y., Delalleau, O., et al. (2024). HelpSteer2: Open-source dataset for training top-performing reward models. NeurIPS 2024 Datasets and Benchmarks.
  10. Chiang, W.-L., Zheng, L., Sheng, Y., et al. (2024). Chatbot Arena: An open platform for evaluating LLMs by human preference. ICML 2024.