A model can be accurate and still mislead you about how sure it is. Accuracy measures how often the model's call turns out to be correct. Calibration measures something the accuracy figure never shows: whether the model's stated probability matches reality, so that the cases it labels "70 percent" actually come true about 70 percent of the time. Whenever a number is going to drive a decision, calibration is the property that makes it safe to act on, because the choice usually turns on the size of the risk, not on whether the model happened to be right in a single yes-or-no sense.
Think of it as a weather forecast, not a coin flip#
The clearest way to separate the two ideas is a familiar one. A forecaster who says "70 percent chance of rain" is not making a yes-or-no bet. Over a long run of days that were called 70 percent, it should rain on roughly seven of every ten. That property is calibration. Whether any single day's forecast turned out "right" is a separate and much cruder question.
Accuracy asks that cruder question. The model predicted an event; did the event happen? Count the correct calls, divide by the total, and you get one tidy percentage. Calibration asks the subtler one: among every case the model rated at 30 percent, did close to 30 in 100 actually go on to have the event? One number grades the verdict. The other grades the honesty of the odds.
This is not a technicality, because people almost never act on a bare verdict. A clinician weighing a preventive medication is not asking "will this happen, yes or no." The real question is how likely the event is, and whether that likelihood is high enough to justify the treatment and its downsides. If the probability is mispriced, a technically correct verdict does nothing to protect the patient from the wrong choice.
How a model can be accurate yet dangerously overconfident#
The pairing surprises people, so two concrete failures make it stick.
Picture a condition that affects 5 in 100 people in a clinic. A lazy model that simply announces "no event" for everyone is right 95 percent of the time. Its accuracy looks superb, yet it is useless: it never produces a probability anyone could act on, and it misses every single person who actually has the condition. High accuracy, zero value.
Now flip the failure. Imagine a model that ranks patients sensibly and is right reasonably often, but quotes everyone a risk that runs about double the truth. It tells a group whose real ten-year risk is 15 percent that they sit at 30 percent. Its accuracy on the yes-or-no call might be perfectly respectable, but its calibration is broken, and the consequence is a stream of people convinced their danger is twice what it is, agreeing to treatment they did not need.
Neither failure shows up in a headline accuracy figure. The first hides behind a rare outcome; the second hides behind decent ranking. You only catch them by checking the probabilities against what actually happened.
The probability, not the verdict, is what the decision rests on#
A probability is a kind of promise. When a model says 20 percent, it is promising that, across many cases like this one, the event turns up about a fifth of the time. Calibration is simply whether that promise is kept.
Real decisions are built on thresholds, and thresholds are built on trusted probabilities. Guidelines often read "consider treatment above this level of risk." That line only protects anyone if the model's 7.5 percent is a genuine 7.5 percent. A model that systematically inflates risk shoves people across the threshold who should have stayed below it; one that deflates risk leaves people untreated who needed the conversation. The ranking of patients can be flawless in either case. The harm comes entirely from the number being mispriced.
The stakes climb as the decision gets weightier. A real clinical choice weighs a real benefit against a real cost, and that arithmetic is sensitive to the size of the risk. Move a quoted probability from 12 percent to 25 percent and you may have flipped whether a reasonable person says yes.
Reading a calibration plot#
Because calibration is invisible in a single accuracy figure, it has to be measured deliberately, and the standard instrument is a calibration plot. You sort cases into bins by their predicted risk, compute for each bin the fraction that truly had the event, and plot predicted against observed. A perfectly calibrated model traces the diagonal, where 10 means 10 and 50 means 50. A curve that sags below the line signals overconfidence: the model is telling people they are in more danger than they are. The shape reveals both the direction and the size of the error, which a lone summary number never can.
The JAMA Users' Guides framework (2017) makes the same point at the level of study appraisal: a prediction model should be judged on both discrimination (can it separate higher-risk from lower-risk people) and calibration, and reporting the first while staying silent on the second leaves the more decision-relevant property unchecked. A 2019 analysis in BMC Medicine put it bluntly, calling calibration the "Achilles heel" of predictive analytics precisely because it is so often the piece left out.
Calibration is not permanent, and that is fixable#
Two cautions keep the picture honest.
First, calibration can drift. A model tuned on one population can misprice another, because the underlying rate of the condition differs from place to place. A model trained at a referral center where the disease is common will tend to overstate risk when it is used in a neighborhood clinic where the disease is rare. A probability calibrated for one setting is not automatically true in the next, which is why local checking matters before a tool is trusted on new patients.
Second, and more reassuring, calibration can often be repaired without rebuilding the model. Recalibrating the outputs to the local population, a routine step covered in the JAMIA 2020 tutorial on calibration methods, can bring a drifted model back into line. The fix is usually a correction to the numbers the model reports, not a teardown of the model itself.
Why accuracy gets the spotlight and calibration gets skipped#
Accuracy is one intuitive number that sounds like the bottom line, and its cousin, the area under the curve, is nearly as tidy. Calibration is a curve; it needs enough cases in each bin to mean anything, and it tends to slip out of true when a model meets new patients. Every incentive points toward reporting the satisfying figure and staying silent on the awkward one.
So when a tool arrives described by a single number, that number is almost always accuracy or the area under the curve, and the missing calibration plot is the tell. None of this is a knock on the people building these systems; the work is genuinely hard. But patients live downstream of the probability, not the headline, and the probability has to be true for them.
The mental model worth keeping is small and durable. Accuracy tells you how often the model is right. Calibration tells you whether you can believe its odds. You act on the odds, so before trusting a number enough to change what you do, ask a simple question: has its confidence ever been checked against reality?
Sources and further reading
Questions and answers
Can a model be highly accurate and still unsafe to act on?
Yes. A model can post a strong accuracy figure while quoting probabilities that are systematically too high or too low. Because decisions hinge on the size of the risk, a mispriced probability can push people toward the wrong choice even when the model's yes-or-no calls look good on paper.
What does a calibration plot actually show?
It groups predictions into bins, then plots the predicted risk in each bin against the fraction of cases that truly had the event. A well-calibrated model hugs the diagonal. A curve that drifts off the diagonal shows whether the model is overstating or understating risk, and by how much.
If a model is poorly calibrated, does it have to be scrapped?
Usually not. Calibration often drifts when a model meets a population different from the one it was built on, and it can frequently be repaired by recalibrating the outputs to the local setting rather than rebuilding the whole model.