Not every task is a good fit for Claude, and not every fit is the same kind of fit. Some tasks are appropriate because a person stays in control of the outcome and Claude is simply making that person faster or better-informed. Others are inappropriate specifically because a consequential decision about a real person's life — their job, their credit, their eligibility for something — gets made with no human ever reviewing it before it takes effect. Learning to tell these apart, quickly and confidently, is the core skill this domain of the exam tests.
The question to ask is rarely "is this task technical" or "does this sound risky." It's narrower and more mechanical: does a human with real authority to change the outcome review this before it takes effect on a person? When the answer is yes, Claude assisting — even with something substantial, like drafting a termination letter or scoring loan applications — is appropriate. When the answer is no, the use case is inappropriate regardless of how accurate or well-intentioned the system is.
The Human-in-the-Loop Test, Applied to Business Decisions
Consider two ways a company might use Claude in hiring. In the first, Claude reads resumes against a job description and produces a short summary and a list of clarifying questions for a recruiter, who then decides personally which candidates move forward. In the second, Claude scores every applicant and automatically rejects anyone below a threshold, with no recruiter ever looking at the rejected applications. The first is appropriate: Claude accelerates the recruiter's work, but a person with the authority to say "wait, that's wrong" makes the actual call before the candidate is affected. The second is inappropriate: a person's job prospects are decided by a system with no one positioned to catch an error, a blind spot, or an unfair pattern before it affects them.
The same test applies outside hiring. A financial services team that has Claude flag transactions as suspicious for a human analyst to approve, deny, or escalate is using Claude appropriately — the analyst has both the information and the authority to override Claude's flag. A team that lets Claude autonomously approve or deny loan applications end-to-end, with no analyst reviewing individual decisions before applicants are notified, has crossed into inappropriate territory: nothing stands between a flawed judgment and a real financial consequence for a real applicant.
One detail matters as much as the review step itself: review has to happen before the decision takes effect, not after. A supervisor who spot-checks 5% of already-sent approval or denial notices is doing quality assurance on a process that already ran autonomously — it doesn't put a human between the decision and the person it affects.
Ethical Implications: Fairness and Transparency
Adding a human reviewer doesn't automatically make a use case ethically sound on its own — it's necessary, but two more things matter once review is in place, and both come directly from the blueprint's "ethical implications of AI usage" bullet.
The first is fairness. Claude can reflect patterns in the data or instructions it's given, and an AI-assisted process applied at scale can quietly encode a bias that would have been caught, one case at a time, by a purely human process. A reviewer who's just rubber-stamping Claude's output — glancing at a summary and clicking approve without the context or authority to meaningfully disagree — isn't providing the kind of oversight that catches this. Real human-in-the-loop review means the reviewer has enough information and enough actual power to change the outcome, not just a formality that satisfies a checkbox.
The second is transparency with the people affected. If Claude helped draft the denial letter a customer receives, or generated the interview questions a candidate is asked, that's usually fine to not mention explicitly. But if AI involvement is material to how someone would understand or contest a decision about them — for example, an applicant's ability to know a scoring system was involved at all, so they can meaningfully appeal — concealing that involvement is itself an ethical problem, separate from whether the underlying decision was accurate. Being honest about where AI was involved, when it would matter to the person on the other end, is part of using Claude responsibly, not an optional extra.
Key Concept
Appropriate use rests on three things together: a human with real authority reviews the consequential decision before it takes effect, the review is substantive rather than a rubber stamp, and the AI's involvement isn't concealed from people it would matter to. Fully autonomous high-stakes decisions — autonomous hiring/firing calls, autonomous financial approvals with no human step — fail the first test regardless of how well they otherwise perform.
Common Exam Distractor
Watch for scenarios that technically include a human somewhere in the process but not in a way that provides real oversight: a spot-check after decisions have already gone out, a reviewer with no authority or context to overrule Claude, or "review" that happens after the affected person has already been notified. These read as appropriate on a quick skim but fail the actual test — human review, with real authority, before the decision takes effect.