Evaluation arrives at a budget meeting as a quote per cycle, and the quote is accurate. It is also about a tenth of what the thing costs. What the cycle consumes is a labelled set: items somebody wrote, labels somebody applied, a rubric somebody argued over and an adjudication record for the cases that were hard.
That set is an asset with a decay rate, not a phase with an end date. This paper prices one on illustrative inputs at $78,106 in year one and $28,939 a year to keep, and finds the validation sample worth far more than the line it sits on.
A plan that prices the run carries two of six cost lines. The four it leaves out are all tied to the set rather than to the suite, and that is where the growth lives. These three decide whether anybody can defend the number at the end of it.
The line cut first, on the reasoning that it buys no coverage. Take the sample from 200 items to 800, a fourfold swing nobody would concede in a planning meeting, and the year-one total moves $7,440, or 9.5% of it. That spend is what tells you whether $78,106 bought a measurement or a guess, and it halves the interval around every score while doing so.
The term that converts evaluation from a project into an operating cost. At a refresh share of a quarter the set turns over in four years, slower than most production distributions move, and it carries $13,539 a year in the worked example. Setting that share to zero is a decision about contamination, and somebody senior should be asked to sign it rather than inherit it.
A property of the rubric rather than of the raters, and the one input nobody writes down. An unclear rubric raises the adjudication line twice over, once through the volume of disputed items and once through the senior minutes each case takes to settle. When it climbs, rewrite the rubric instead of paying senior time to have the same argument item by item.
Items, labels, rubric and adjudication record belong to one accountable person with a refresh budget, not to whichever project last needed a number out of them.
A judge adopted without a held-out human sample converts a measurement into an assertion. Report kappa with position randomisation applied, and re-run it whenever the judge version changes.
Three raters on 1,200 items gives you an agreement figure you can defend. One rater on 3,600 items gives you none, and costs more to produce while giving it.
Decide what percentage rotates each year before the build project closes. A set with no rotation plan still has an expiry date, just an undeclared one nobody owns.
In the illustrative worked example, $78,106 for 2,400 items at three raters each. The eval run everybody quotes is $8,160 of that. The set build is $62,706 and judge validation $7,240, and steady state afterwards runs $28,939 a year.
The shape of the arithmetic is what transfers to your programme; none of the inputs does.
One of them. The kappa behind an 85% agreement rate, roughly 0.48, comes from UC Berkeley's 2026 work on 21 judges, run over MT-Bench, JudgeBench and RewardBench. Every cost input here is illustrative: 2,400 items, three raters, $62 a labeller hour, $95 a senior hour and 24 release cycles a year.
Defend both, but know what each one buys. Running the item count from 1,200 to 3,600 moves the year-one total 7.3 times as far as a fourfold swing in the validation sample does.
The validation sample is the small line that tells you whether everything above it measured anything at all.
It is the flattering way of saying moderate. In the Berkeley cohort the two statistics sit a mean of 38.6 points apart, which leaves an 85% headline standing on a kappa of about 0.48. Ask for the chance-corrected figure, with position randomisation applied, before any threshold is set on it.
No, and neither do the scores that judge produced. Each earlier validation describes a system that no longer exists. Most of the 21 judges Berkeley tested changed rank by at least four places when the benchmark changed, so treat a swap as a re-baselining event and budget validation per judge version.
No, it sits beside it. This paper puts a price on the apparatus: what a labelled set costs to build, to validate and to keep current. Benchmarking Model Evaluation grades the same apparatus and locates its weakest row.
One of them tells you what to fund, the other what to fix.
Two sets of them, held on opposite sides of the building. One holds the item count, the rubric and an honest view of how often two careful raters disagree. The other holds the loaded rates, the renewal cycle and the question of which budget a refresh is paid out of.
Drop your details and we'll send The Economics of Model Evaluation straight to your inbox - no spam, unsubscribe anytime.
Send us the eval set your release decisions already depend on, with your item count, your rater depth and your loaded rates. Our engineers will cost the asset, the refresh and the validation sample from your own numbers. SECTION 7 - FAQ - 5 to 8 questions
Cost your evaluation set