- In short
- The stakes-based routing rule sends a decision to a human reviewer when it is low-confidence AND either irreversible or high-cost, while letting confident, reversible, low-cost decisions proceed automatically. When cost and reversibility disagree with confidence, weight cost and reversibility more heavily because they determine the consequence of a mistake, and use confidence to decide how much of the high-stakes volume can safely proceed. Routing on a single variable - confidence alone, or volume alone - misses the cases the rule exists to catch.
Combining three variables into one decision
Once reversibility, cost, and confidence are held in their proper roles, the CCAR-P exam asks you to combine them into an actual routing rule - an apply-level skill. The rule is compact: route a decision to a human when it is low-confidence AND either irreversible or high-cost, and let confident, reversible, low-cost decisions proceed automatically. Human review is a budget of finite attention, and the rule's job is to spend that budget on the decisions that actually warrant it.
The structure of the rule is what makes it work. It is not "route the uncertain ones" and it is not "route the important ones" - it is the conjunction. A decision earns human review when it is both likely to be wrong (low confidence) and consequential if it is (high-cost or irreversible). That intersection is where a mistake is both plausible and damaging, which is exactly where a person's judgement is worth its latency.
- The stakes-based routing rule
- Route a decision to human review when it is low-confidence AND either irreversible or high-cost; let confident, reversible, low-cost decisions proceed automatically. When the stakes variables and confidence disagree, cost and reversibility carry more weight because they set the consequence of a mistake, and confidence governs how much high-stakes volume can safely proceed.
The two clear cases and the conflicted middle
Two cases are unambiguous. A confident, easily reversed, low-cost decision can usually run without a human - the mistake is unlikely and, if it happens, cheap and recoverable, so spending review attention on it wastes the budget. A low-confidence, irreversible, high-cost decision almost always needs human review - the mistake is both plausible and damaging with no way to undo it, which is the textbook case for a person in the loop.
The decisions that actually consume your review budget are the ones where the variables disagree. A case can be high cost but easily reversed, or low confidence on something trivial to undo. The rule for these conflicts is explicit: when cost and reversibility disagree with confidence, give greater weight to cost and reversibility, because they determine the consequences of a mistake. Confidence then decides how much of that high-stakes volume you can safely let through unreviewed - it tunes the throttle, but the stakes decide whether the throttle exists at all.
Why single-variable routing fails
The tempting simplifications both break. Routing everything below a confidence threshold ignores reversibility and cost entirely: it floods the queue with low-stakes uncertain decisions that never needed a human, and worse, it can wave through a high-confidence decision that is nonetheless irreversible and high-cost - precisely the kind you most want a person to catch when the confidence turns out miscalibrated. Routing on volume alone is no better, sending items to review by throughput rather than by whether they warrant attention.
There is one assumption the rule quietly depends on: the confidence signal must be calibrated for the rule to hold. If confidence is miscalibrated, "low-confidence" and "high-confidence" stop meaning what the rule needs them to mean, so confirming calibration is a task of its own. But even a perfectly calibrated confidence signal does not rescue a rule that routes on confidence alone - the stakes variables still have to be in the conjunction.
What the CCAR-P exam trips candidates on
The first trap is choosing "route everything below a high confidence threshold" as the rule, ignoring reversibility and cost entirely. The scenario offers this as a clean, simple policy; the credited reading rejects it because it both over-routes low-stakes uncertain items and under-protects high-confidence, high-stakes ones. The rule must include the stakes variables, not just confidence.
The second trap is applying the rule with an uncalibrated confidence signal and assuming the routing decisions are still trustworthy. A scenario uses a confidence score of unknown calibration and treats the routing output as reliable; the credited reading flags that the rule depends on calibration and that confirming it is a separate task. The exam rewards candidates who both use the conjunctive rule and check the assumption it rests on.
Worked example
A team routes every decision whose confidence is below 90% to human review, regardless of anything else, and lets everything at or above 90% run automatically. Reviewers are swamped with trivial low-confidence cases, and a high-confidence but irreversible, high-cost decision recently ran unreviewed and caused harm. Fix the routing rule.
The rule is single-variable and it fails in both directions the exam warns about. Below the threshold, it floods the queue with low-confidence decisions that are trivial to undo and cheap when wrong - attention spent where no mistake would matter. Above the threshold, it auto-ran a decision that was irreversible and high-cost simply because the confidence number was high, and when that confidence proved miscalibrated, there was no stakes check to catch it. Routing on confidence alone ignored the two variables that actually set the stakes.
The corrected rule is the conjunction. Route to a human when a decision is low-confidence AND either irreversible or high-cost; let confident, reversible, low-cost decisions proceed automatically. That immediately drains the queue of the trivial low-confidence items - they are reversible and low-cost, so they proceed - and it captures the irreversible, high-cost decision for review whenever confidence is low. For the conflicted case where confidence is high but the action is irreversible and costly, weight the stakes: such decisions warrant a gate, with confidence tuning how much of that high-stakes volume proceeds rather than deciding on its own.
Finally, confirm the confidence signal is calibrated, since the whole rule leans on "low" and "high" confidence meaning what they claim. The fix is not a better threshold on one variable; it is combining all three and validating the one the rule trusts.
Common misreadings to avoid
Misconception
Routing every decision below a high confidence threshold is a sound review policy.
What's actually true
Misconception
If the routing rule uses confidence, the routing decisions are trustworthy.
What's actually true
How this shows up on the exam
Domain 5 items give you a routing policy or a decision and ask whether it should go to a human. The reliable method is to apply the conjunction - low confidence AND (irreversible OR high-cost) routes to a person; confident, reversible, low-cost proceeds - and to weight the stakes when they conflict with confidence. Reject any single-variable rule, and flag any use of an uncalibrated confidence signal.
This rule combines the three variables that set decision stakes into an operational policy. Once a decision is routed, review placement trade-offs decides where the human sits, and what the reviewer's screen must show decides what they see. Getting the rule wrong in the over-routing direction leads directly to consent fatigue and over-routing.
A team routes every decision below 90% confidence to review and auto-runs everything above it. The queue is full of trivial cases and a high-confidence irreversible decision recently ran unreviewed and caused harm. Which rule best fixes this?
People also ask
What is the rule for routing decisions to a human?
Should I route on confidence alone?
What happens when cost and confidence disagree?
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
Official prep for this domain
Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.
References & primary sources
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.