Skip to content
AI.info

Mathematical foundations

Proper Scoring Rules, Calibration, and Decision Theory

Learn why proper scoring rules reward honest distributions, how calibration differs from discrimination, and how utilities convert forecasts into decisions.

By the end you can

A probabilistic forecast should be rewarded for honesty, not confidence alone

A scoring rule assigns a numerical loss to a predictive distribution after the outcome is observed. A proper scoring rule is minimized in expectation when the forecaster reports the distribution it actually believes. That is what ties probability estimation to incentives. Honest reporting is not asked for as a virtue. It is the strategy with the best expected score.

The split between calibration and sharpness is not a folk distinction. Gneiting and two colleagues set out the paradigm in 2007, in the Journal of the Royal Statistical Society. Calibration there is statistical consistency between the forecasts and the observations. Sharpness is the concentration of the predictive distributions. And the goal the paper proposes is “maximizing the sharpness of the predictive distributions subject to calibration”. The order of those two words is the whole content of the rule. Sharpness is what you maximize. Calibration is the constraint you may not spend to get it.

The principle outgrew probabilities. A 2020 paper by Marc-Oliver Pohle describes its own contribution as one that “generalizes the famous sharpness principle by Gneiting et al. (2007) from probabilistic to all types of forecasts”.

The measurement tradition is older still. Glenn W. Brier's paper on verifying forecasts expressed in terms of probability ran to three pages in Monthly Weather Review in January 1950. Log loss and Brier score are both proper under standard conditions, but they emphasize errors differently, and neither one is calibration. A forecast can be calibrated and uninformative. It can be sharp and systematically wrong.

Sharpness is what you maximize; calibration is the constraint you may not spend to get it.

Analogy

A forecasting tournament that paid for honest distributions, and the ranking it produced

An odds maker reports probabilities and is settled up after outcomes occur. A proper scoring rule is what makes honest probabilities the best long-run strategy, rather than rewarding exaggerated confidence. That arrangement has been run at scale and scored in public.

Between 8 March 2021 and 7 March 2022 the European COVID-19 Forecast Hub collected forecasts and ranked them with the weighted interval score. Sherratt and colleagues reported the outcome in eLife in 2023. The multi-model ensemble scored better on relative weighted interval score than 83% of case-forecast scores — N=886, from 23 models — and better than 91% of death-forecast scores, N=763 from 20 models. The combination beat almost every individual forecaster it was built from. The comparison means something only because the ranking instrument could not be gamed by confidence.

The WIS “is a strictly proper scoring rule”, and the consequence is the point: “As a consequence, the WIS encourages forecasters to report predictions representing their true belief about the future”. Bracher and three co-authors introduced the score in 2021 and showed it is proper for any set of nonnegative weights. So the propriety survives whatever weighting a hub chooses for its prediction intervals.

One caution the odds-maker picture carries over. Published odds move the people reading them, and in some settings a prediction alters the outcome it describes. Causal and game-theoretic effects then enter the design.

Probability quality and decision value are related but not identical.

Example

Two models with the same accuracy

Consider two binary classifiers that both classify 80 of 100 examples correctly.

  • Model A: Usually reports probabilities near 0.6 and 0.4.
  • Model B: Often reports probabilities near 0.99 and 0.01.
  • Accuracy: The hard decisions can be identical.
  • Log loss: Confident mistakes from Model B receive a much larger penalty.
  • Decision impact: Model B may trigger riskier actions if its confidence is trusted.

Key idea

Recalibration can repair probabilities without repairing ranking or data shift

Platt scaling, isotonic regression, and temperature scaling learn mappings from scores to probabilities. Temperature scaling is the smallest of them — “a single-parameter variant of Platt Scaling”. That is part of why it travels well: one number fitted on held-out data, and the ranking of cases left exactly where it was.

That is also its limit. Recalibration requires a held-out calibration sample representative of deployment, and it cannot recover information the model did not learn. It may make the probabilities read more honestly while leaving ranking errors, subgroup failures, and stale features unchanged. Nothing in a reliability curve tells you that the target variable was the wrong one. No temperature will fix a model that ranks the wrong people first.

A calibration layer is a fitted model in its own right. It must be versioned, monitored, and refitted when the population moves under it.

Probability repair is not model repair.

Case

Measured at ICML 2017: 16.53% expected calibration error, cut to 1.26% by one parameter

Deeper networks got more accurate and worse at saying how sure they were. Guo and three co-authors measured that at ICML in 2017, and their abstract states it flatly: “modern neural networks, unlike those from a decade ago, are poorly calibrated”. Depth, width, weight decay and Batch Normalization are named as the influential factors.

Table 1 puts numbers on it. Reporting expected calibration error with 15 bins, a 110-layer ResNet on CIFAR-100 came in at 16.53% uncalibrated, against 4.85% for a 5-layer LeNet on the same data. The deeper, more accurate network was the worse-calibrated one by more than a factor of three. Post-hoc repair then split sharply by method. Temperature scaling cut the ResNet's ECE to 1.26%. Matrix scaling, with far more parameters to fit, made it worse: 25.49%, above the uncalibrated number it was supposed to fix. The authors found temperature scaling “surprisingly effective” on most of their datasets. The matrix-scaling column is the reason to distrust the flexible option.

The result is also dated, and that is worth reading as a lesson about calibration findings generally. Minderer and seven co-authors re-ran the measurement on later architectures for NeurIPS 2021 and reached the opposite conclusion for a class of newer models: “We systematically relate model calibration and accuracy, and find that the most recent models, notably those not using convolutions, are among the best calibrated.” The 2017 trend was a property of the architectures then in front of the authors, not a law of scale.

Comparison

Log loss, Brier score, and zero-one loss

Different losses elicit different predictive objects, and the choice quietly decides what your evaluation is able to notice.

Log loss is the negative log probability assigned to the observed outcome. It is strictly proper for full categorical probabilities, it connects directly to likelihood and cross-entropy, and it punishes confident mistakes hard. That last part follows from its sensitivity to near-zero probabilities, where −log p grows without bound.

Brier score is the squared error of probabilistic predictions. It is proper for probabilities, bounded in binary classification, and supports the calibration decompositions Brier's own 1950 paper set in motion. It penalizes extremes less sharply than log loss. That makes it more forgiving of a single catastrophic overconfidence, and less useful for detecting one.

Zero-one loss counts whether the chosen class is wrong. It evaluates a hard decision, ignores probability quality entirely, is not a proper score for full distributions, and depends on the threshold you happened to set. Two models with identical zero-one loss can differ arbitrarily in everything a proper score measures. That is exactly the situation the 80-of-100 example above describes.

FigureComparison · 3 columns

Log loss

Negative log probability assigned to the observed outcome.

  • Strictly proper for full categorical probabilities
  • Strongly penalizes confident mistakes
  • Connects to likelihood and cross-entropy
  • Sensitive to near-zero probabilities

Brier score

Squared error of probabilistic predictions.

  • Proper for probabilities
  • Bounded in binary classification
  • Supports calibration decompositions
  • Penalizes extremes less sharply than log loss

Zero-one loss

Counts whether the chosen class is wrong.

  • Evaluates a hard decision
  • Ignores probability quality
  • Not a proper score for full distributions
  • Depends on the decision threshold

Visual

From probability forecast to decision, with every layer measured

A probability estimate passes through several layers before it becomes an action. First the predictive distribution. Then a calibration check, comparing stated probabilities with observed frequencies. Then a scoring rule, measuring distribution quality across cases. Then a utility or cost, translating outcomes and actions into decision value. Finally a decision rule, choosing an action, a threshold, or an abstention policy. Every layer can fail on its own, and a deployed system can fail at several at once without any of them raising an alarm.

The Epic Sepsis Model is the worked example, because it ran at hundreds of US hospitals before anyone outside the vendor scored it. Wong and colleagues validated it externally at Michigan Medicine, on 27,697 patients and 38,455 hospitalizations between 6 December 2018 and 20 October 2019. Sepsis occurred in 2,552 hospitalizations, 7% of the total. The model's hospitalization-level AUROC was 0.63 (95% CI, 0.62–0.64). Their conclusion in JAMA Internal Medicine names both failures at once: “This external validation cohort study suggests that the ESM has poor discrimination and calibration in predicting the onset of sepsis.”

The decision layer was measured separately, elsewhere, and failed on its own terms. A 2024 validation in JAMIA Open covered 145,885 emergency-department encounters at two Harris Health county hospitals. Within a 6-hour window it reported sensitivity of 14.7%, specificity of 95.3% and a positive predictive value of 7.6%. A specificity above ninety-five percent looks reassuring, and it is not the operative number. At that positive predictive value, most of what the alert fires on is not sepsis. At that sensitivity, most of the sepsis is not alerted on. Discrimination, calibration and the alerting decision were each measured. Each one failed.

FigureProcess · 5 steps
  1. 1

    Predictive distribution

    Model uncertainty over possible outcomes.

  2. 2

    Calibration check

    Compare stated probabilities with observed frequencies.

  3. 3

    Scoring rule

    Measure distribution quality across cases.

  4. 4

    Utility or cost

    Translate outcomes and actions into decision value.

  5. 5

    Decision rule

    Choose an action, threshold, or abstention policy.

Steps

Choose evaluation from the decision backward

A model output read as a probability calls for the sequence below. Define the event — outcome, horizon, population. Check probability semantics — confirm the model output can support a probabilistic interpretation at all. Select a proper score, matching its sensitivity to confident errors against operational needs. Assess calibration with reliability diagrams, calibration error, and slice checks. Add utility, translating probabilities into action-specific costs and benefits. Monitor after shift, rechecking base rates, calibration, and thresholds over time.

Step one carries more weight than its position suggests, because a score is silent about whether you scored the right event. A commercial risk algorithm applied to millions of patients ranked Black patients as equally risky as healthier White patients. Obermeyer and three co-authors published that in Science on 25 October 2019. The algorithm was not broken at the modeling layer. It was predicting a different quantity from the one the decision needed: “The bias arises because the algorithm predicts health care costs rather than illness, but unequal access to care means that we spend less money caring for Black patients than for White patients.”

The size of the gap between the scored event and the intended one is measurable. Correcting the target would have raised the share of Black patients auto-identified for extra help at the 97th-percentile threshold from 17.7% to 46.5%. Nothing in a proper score computed against predicted cost would have flagged that. Against predicted cost, the model was doing well.

The decision layer moved fast once the paper appeared. On the same day, New York's Superintendent of Financial Services Linda A. Lacewell and Health Commissioner Howard A. Zucker wrote jointly to UnitedHealth Group about Impact Pro. The model was accurate. The question was what it was accurate about.

FigureProcess · 6 steps
  1. 1. Define the event

    Specify outcome, horizon, and population.

  2. 2. Check probability semantics

    Confirm the model output can support a probabilistic interpretation.

  3. 3. Select a proper score

    Match sensitivity to confident errors and operational needs.

  4. 4. Assess calibration

    Use reliability diagrams, calibration error, and slice checks.

  5. 5. Add utility

    Translate probabilities into action-specific costs and benefits.

  6. 6. Monitor after shift

    Recheck base rates, calibration, and thresholds over time.

Calibration does not imply usefulness, and it does not travel across groups

A model that always predicts the base rate can be perfectly calibrated when evaluated on a stable population. It contains no case-specific discrimination. Sharpness describes how concentrated the predictive distributions are, and the 2007 paradigm is a demand for both: sharpness subject to calibration, not calibration alone.

Calibration is also group- and time-dependent, and a globally calibrated model may be miscalibrated in important slices. The sharper problem is that per-group calibration can be genuinely satisfied and still be incompatible with the fairness property people assume it delivers. ProPublica analyzed 7,214 Broward County defendants on 23 May 2016 and found that COMPAS's false-positive rate was 44.85% for Black defendants against 23.45% for White defendants. Northpointe maintained that the score was calibrated by group. Both positions can be correct at once.

That is a theorem, not a controversy. Alexandra Chouldechova proved it in 2017 and states it directly: “We demonstrate that the criteria cannot all be simultaneously satisfied when recidivism prevalence differs across groups.” Kleinberg and two co-authors reached the same wall independently that year, proving that outside highly constrained special cases no method satisfies all three fairness conditions simultaneously. When prevalence differs across groups, calibration is a choice made against other properties. It has to be argued for, not assumed.

Key takeaways