Review Placement Trade-offs for the CCAR-P Exam

Once a decision is routed, where does the human sit

The routing rule decides which decisions a person should weigh in on; this knowledge point decides where that person sits relative to the action. The CCAR-P exam treats it as an analyse-level skill because each of the three placements makes a different safety-versus-throughput trade, and choosing the wrong one either grinds a high-volume workflow to a halt or lets an irreversible mistake take effect before anyone looks. The governing idea is that involving a human earlier is safer and slower.

There are three placements, and they are not interchangeable defaults. Pre-action approval, post-action audit, and sampled review each buy you something and cost you something, and the right choice for a given decision is dictated by that decision's stakes - the same reversibility and cost that drove the routing rule. Applying one placement everywhere, regardless of stakes, is the error the analysis is meant to prevent.

Pre-action approval: safest, slowest

Pre-action approval places the human before the action: the action cannot take effect until a person approves it. Its benefit is decisive - nothing irreversible happens unreviewed, so it is the safest placement and the right one for high-stakes, irreversible actions. Its cost is equally clear: it adds latency to every routed decision, and a person must be available to approve, so it does not scale to high volume. You pay in speed and staffing for the guarantee that no consequential action runs without a human first.

This is the placement the routing rule points to for its hardest case - a low-confidence, irreversible, high-cost decision. The whole reason to accept the latency is that the action cannot be undone, so catching the mistake afterward would be too late.

Post-action audit: high throughput, reversible only

Post-action audit places the human after the action: the action runs immediately, and a person reviews it afterward. Its benefit is throughput - nothing waits on a reviewer, so the workflow runs at full speed. Its cost is the flip side: by the time a wrong action is caught, it has already taken effect. That means post-action audit only fits reversible, lower-cost decisions, where a mistake found after the fact can be corrected without serious harm.

The exam's favourite failure is applying this placement to an irreversible action because it "worked fine" for a different, reversible workflow. Throughput is seductive, but for an action that cannot be undone, reviewing afterward reviews damage that is already done. Placement has to follow the stakes of this decision, not the convenience that suited another one.

Sampled review: monitors the system, not the outcome

Sampled review places the human over a fraction of decisions: it checks some proportion to monitor quality without gating each one. Its benefit is that it watches the system's overall health cheaply, without slowing the process. But its nature is crucial - it monitors aggregate quality rather than guarding individual outcomes. A bad decision can slip through simply by not being sampled, because sampled review never promised to look at any particular case.

This makes sampled review the wrong tool for protecting a specific flagged case. If a decision has been flagged as high-stakes, sampling gives it the same odds of being seen as any other item, which is not protection at all. Sampled review is for keeping an eye on the population; pre-action approval is for guarding the individual.

What the CCAR-P exam trips candidates on

The first trap is applying post-action audit to an irreversible, high-cost action because it worked for a different, reversible workflow. The scenario transplants a throughput-friendly placement onto an action that cannot be undone; the credited reading is that the stakes changed, so the placement must too - an irreversible action needs pre-action approval, not an after-the-fact audit of damage already done.

The second trap is assuming sampled review provides the same protection as pre-action approval for a specific flagged case. A scenario flags a particular high-stakes decision and offers sampled review as the control; the credited reading is that sampling only monitors aggregate quality and may never see that case, so it cannot guard it. The exam rewards matching each placement to what it actually guarantees.

Common misreadings to avoid

How this shows up on the exam

Domain 5 items describe a routed decision or a change of workflow and ask where the human should sit. The reliable method is to read the stakes - reversibility and cost - and match them to a placement: irreversible and high-cost demands pre-action approval; reversible and lower-cost can use post-action audit; system-wide quality monitoring uses sampled review. Reject any placement carried across a change in stakes, and never treat sampling as protection for a specific case.

This choice follows the stakes-based routing rule, which decides what gets routed, and rests on the three variables that set decision stakes. Whatever placement you choose, what the reviewer's screen must show determines whether the review is accurate, and over-using pre-action approval leads to consent fatigue and over-routing.