all free tools

escalation threshold calculator

Most AI workflows give each case a confidence score and send the low ones to a person. Where you draw that line is a cost question: set it too low and errors get through, too high and people review cases the model already got right. Put in how your cases spread across confidence bands, how accurate the model is in each, and what an error and a review cost. You get the cheapest threshold and every alternative next to it.

free, no sign-up, runs in your browseropen source on GitHub
the volume
the confidence bands

For each band of model confidence: the share of cases that land there, and how often the model is right in it, measured on a labelled sample.

the costs

auto-complete at 0.95 confidence and above; send the other 45% to a person

$37,125total cost per month at that threshold
$3.71cost per case
55%auto-completed
127.5undetected errors per month
$17,875saved against reviewing everything
$75,600saved against reviewing nothing
Every threshold, per month. The cheapest is marked.
auto-completeautoreviewederrorsreview costerror costtotal
nothing0%10,000100$40,000$15,000$55,000
0.95 and above (cheapest)55%4,500127.5$18,000$19,125$37,125
0.90 and above75%2,500207.5$10,000$31,125$41,125
0.80 and above87%1,300339.5$5,200$50,925$56,125
0.60 and above95%500531.5$2,000$79,725$81,725
everything100%0751.5$0$112,725$112,725
bandaccuracyauto, per casereview, per casecheaper
0.95 and above98.5%$2.25$5.50auto
0.90 to 0.9595.0%$7.50$5.50review
0.80 to 0.9088.0%$18.00$5.50review
0.60 to 0.8075.0%$37.50$5.50review
below 0.6055.0%$67.50$5.50review

Break-even accuracy: 96.33%. A band the model gets right more often than that is cheaper to auto-complete than to review. A review costs $4.00 in time, and still lets through 1.0% of errors. Band accuracy is only as good as the sample behind it; check it with the accuracy proof calculator.

questions

how do i measure accuracy in each band?

Take a golden set: a few hundred recent cases a person has labelled carefully, including the hard ones. Run the model on them, group the cases by its confidence score, and count how often it was right in each group. Bands with few cases have wide error bars; the accuracy proof calculator shows how many cases you need.

why does calibration matter?

A threshold only works if higher confidence really means higher accuracy. Many models are overconfident: a score of 0.9 might be right 80% of the time. The calculator uses the accuracy you measured in each band, not the score itself, and warns you when accuracy does not fall as confidence falls. Re-measure after every model or prompt change, because calibration moves.

why isn't human review counted as error-free?

Because it isn't. Reviewers working through a queue miss errors, especially when the model is usually right and they stop looking closely. Measure it the same way as the model: give reviewers seeded cases with known answers. If review catches 99% of errors, 1% still get through, and that is part of what each review costs.

what if the law or a regulator requires a person to decide?

Then keep the person, whatever the numbers say. Credit, hiring, insurance, medical and other decisions with legal or similarly significant effects can require human involvement under GDPR Article 22 and human oversight under the EU AI Act. Use the calculator to size that review, not to remove it.

what should an error cost include?

What one undetected mistake costs once it reaches a customer or a ledger: the rework, refunds or credits, penalties, the support time, and a fair share of lost customers. If errors differ a lot in size, run the calculator once with the typical cost and once with the worst plausible one.

more free tools

Want the numbers checked against your own process? Book a 20-minute call.