CertSafari
    Anthropic Claude Certified Architect – Professional (CCAR-P) - December 7 onwards· Lessons

    Domain 1 · Lesson 1/39

    Delegating process steps between Claude and humans

    Task Delegation Between Claude and Humans

    15 min read
    3% of exam
    8 sources
    Published 18 Nov 2026
    Docs as of 18 Nov 2026

    What you will be able to do

    • Break a business process into steps and assign each one to Claude, a human, or both working together
    • Use reversibility to decide whether a human gate goes before an action or a review comes after it
    • Spot designs that look supervised but leave no accountable human owning each decision
    • Justify a collaborative split for high-stakes steps and reject confidence thresholds or AI auditors as a substitute for human sign-off

    Key concept

    Step-level delegation — Break the process into its steps first, then decide for each one whether Claude does it, a human does it, or the two share it. Each decision rests on three questions: can the step's effect be undone, what happens if it is wrong, and who has to answer for the outcome.

    1.Assign steps, not whole processes

    Delegation is the decision about what Claude handles and what stays with people. You make that decision step by step, never for a whole process at once. A claims workflow, a compliance review or a refund pipeline is a chain of separate steps, and those steps differ in kind. Reading a form and pulling out its fields is one kind of work. Deciding whether the company owes money is another. Moving the money is a third. A design that calls the whole process "automated" or "human-run" has skipped the analysis the decision depends on.

    Each step lands in one of three modes. In Automation, Claude does the work and a person checks it. In Augmentation, Claude and a person work the step together. In Agency, Claude operates with latitude inside boundaries a person has set. A fourth outcome, keeping the step entirely with a human, sits beside these three. It is the right answer more often than enthusiasm for automation suggests.

    Collaboration modes and the kind of step each fits
    ModeWho does whatFits a step that is…
    AutomationAI does it, you checkHigh volume, mechanical, and its errors show up in review
    AugmentationYou and AI work it togetherA judgement call where Claude can prepare the evidence and a person makes the decision
    AgencyAI operates with latitude inside boundaries you setEasy to reverse, with the boundary enforced outside the model
    Retained by a humanA person does itIrreversible, or a decision a named person must answer for

    Agency needs its boundary enforced outside the model because a model can misread or overstep an instruction, and a limit it is merely told about is only as reliable as its reading of it. Anthropic's incident log records an agent deleting remote git branches from a misinterpreted instruction. Anthropic's own guidance says a prompt block telling Claude to leave payments to a person "guides Claude and doesn't enforce anything", so a person must approve each call to a tool that can move money. A limit built into the surrounding system, such as a tool list with no delete action, holds because the model cannot attempt what is not there.

    Implementation and judgement split along a clear line. Handing Claude the production of an artefact is generally safe, because the artefact can be inspected before anyone relies on it. Handing Claude the judgement about what should happen is a different act. Claude is versatile and fast at scale, but it also has known failure modes: hallucination, stale knowledge and unreliable complex reasoning. The strongest designs pair Claude's speed and scale with human judgement and oversight, and step-level assignment is how you build that pairing.

    Checkpoint 1 of 7· Match them up

    A refund pipeline has been split into steps. Match each step to the mode it should be assigned.

    Tap a term, then the definition that fits it.

    Sources123456

    2.Reversibility decides where the human gate sits

    Whether an action's effects can be undone decides whether a human approves it beforehand or reviews it afterwards. If an action can be rolled back, corrected or recalled, review after the fact works: a mistake gets caught and undone. If it cannot be undone, review after the fact is just a record of the damage. Anthropic's own prompting guidance for agentic work makes this the first thing Claude itself should consider.

    Recommended system-prompt guidance: reversible local actions go ahead, hard-to-reverse or shared-system actions need confirmation firsttext
    Consider the reversibility and potential impact of your actions. You are encouraged to
    take local, reversible actions like editing files or running tests, but for actions that
    are hard to reverse, affect shared systems, or could be destructive, ask the user before
    proceeding.

    Claude Code's auto mode applies the same rule. File edits inside the project directory run with no approval step, because version control makes them reviewable and reversible. Shell commands, external integrations and operations outside the project go to a classifier first. Anthropic's incident log shows why that line matters. It records an agent deleting remote git branches after misreading an instruction, and another attempting migrations against a production database. In each case the model was overeager and took initiative the user did not intend. None of those mistakes could be fixed by an after-the-fact review.

    Some properties feel relevant but do not move the gate. A draft that passes formatting and schema checks is well-formed, which tells you nothing about whether its effect can be undone. High volume is a reason to hand Claude the preparation work, but the action itself stays exactly as reversible as it was. Running on a more capable model tier changes neither the stakes nor whether the effect can be undone. Model choice is a separate decision; see model tier selection.

    Checkpoint 2 of 7· Check yourself

    Your team's Claude agent sends about 4,000 supplier payment instructions a week to an external bank API. Every instruction passes schema validation, and the agent runs on the most capable model tier. A colleague wants to drop approval before sending and audit a weekly sample afterwards instead. Which question should decide whether that proposal is acceptable?

    Checkpoint 3 of 7· Exam question

    Which factor most directly determines whether a human approval gate should sit before a Claude-initiated action, rather than a review after it has run?

    Sources45

    3.Accountability attaches to each decision, not to the system

    Claude can do the work behind a decision, but it cannot be the one answerable for it. The person who ships or signs remains responsible for the result, whatever part AI played. "AI wrote it" explains nothing and excuses nothing. So when a regulation, contract or licence names a person as accountable for a decision, that person has to make each decision before it takes effect. Supervising the machinery that makes decisions does not meet that requirement.

    Several designs look like oversight but fail on this point:

    • Owning the log. Claude decides each case and records its reasoning, and a named officer owns the audit trail. The officer is accountable for the records, not for the decisions in them.
    • Owning the policy. The officer sets the scoring thresholds and reads a monthly summary. Claude still makes every individual decision, and the officer sees only aggregates.
    • Batch countersignature. Claude acts on cases, and the officer signs a weekly batch of actions that have already taken effect. The signature arrives after the decision is already out in the world.
    • Sampled audit. People check a sample of completed cases. Unsampled cases never get a human decision at all.

    A design that keeps accountability intact while still using Claude for volume looks different. Claude triages the incoming cases, puts aside the clearly routine ones for the accountable person to dispose of, and writes an evidence-based narrative for each case it escalates. The accountable person then makes and signs the decision on each of those cases. Claude takes on the reading and drafting load, and the decision stays with the person the rules name. That signature step is a human-in-the-loop checkpoint. The same ownership principle applies to code in accountability for AI-generated code.

    Checkpoint 4 of 7· Check yourself

    A lending regulation names the credit officer as accountable for each loan denial. The bank wants Claude to carry most of the review workload. Which design meets the regulation?

    Checkpoint 5 of 7· Exam question

    A bank uses Claude to screen transaction alerts for money-laundering indicators. Regulation requires that a named compliance officer be accountable for each decision to file or not file a suspicious-activity report. Alert volume is high and most alerts are benign. Which design keeps accountability intact while still using Claude for volume?

    Sources718

    4.Collaborative splits for high-stakes steps

    When a step is high-stakes, the usual answer is collaboration, not exclusion. Claude does the extraction and the first-pass analysis, and shows its sources so a reviewer can check them. A qualified person reviews that work against the original material, makes the decision, and carries out any irreversible action. Take a supplier-refund process. Claude reads the invoices and drafts a recommendation citing the contract terms. The finance officer checks the draft against the file and approves the transfer. Claude's speed goes into the preparation, and the decision and the transfer stay with the officer.

    Confidence gating fails because the cases it trusts are exactly the ones nobody looks at. A second Claude instance that audits the first one fails for a related reason. Pairing a doer agent with a verifier agent is a real and useful pattern. Good long-running agents verify their own work in several ways before a human sees it, and code tests and documentation rubrics serve the same purpose. But the verifier raises the quality of what reaches the human. It cannot be the accountable party, and it should not carry out an irreversible action. Giving the auditing agent less context, such as the policy text without the case file, makes it a weaker check still.

    Autonomy can grow over time, one task type at a time. Anthropic teams give agents autonomy in proportion to the reliability they have shown. They review agent work by hand at first, track which kinds of task each agent has earned autonomy on, and expand scope one task type at a time. In one backlog-triage effort, people first reviewed every agent decision. They then taught the agents to send decisions needing human input straight to a person, so that decisions with hard tradeoffs always had a human in the loop. Trust grows on the reversible, verifiable tasks. The hard-tradeoff decisions stay with people however reliable the agent becomes.

    Checkpoint 6 of 7· Check yourself

    An architect wants to speed up supplier refunds with a doer–verifier pair. One Claude agent drafts each refund decision from the invoices, a second Claude agent audits the draft, and any transfer the verifier approves is sent automatically. The finance officer is accountable for each refund. How should this design be judged?

    Checkpoint 7 of 7· Exam question

    A property insurer wants Claude (via the Messages API) in its claims process. The process has three steps: extract fields from submitted claim forms and photos, compare the claim with the policy wording to judge coverage, and release the payout. Payouts go out by bank transfer that cannot be recalled, and the insurer remains legally accountable for every coverage decision. Which assignment of the three steps is most defensible?

    Sources38

    Sources

    (8)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “Delegation means deciding what AI handles and what stays with you.”
      ↩︎ Assign steps, not whole processes
      “Diligence means owning the final result fully, regardless of AI’s role.”
      ↩︎ Accountability attaches to each decision, not to the system
    2. 2.
      “Automation (AI does it, you check), Augmentation (you and AI work it together), or Agency (AI operates with latitude inside boundaries you set)”
      ↩︎ Assign steps, not whole processes
      “Explain why delegating implementation is safe and delegating judgment is not”
      ↩︎ Assign steps, not whole processes
      “Delegation means decomposing the problem first, then deciding what AI handles at each step.”
      ↩︎ Key concept
    3. 3.
      “Current limits include knowledge cutoffs, hallucinations, and unreliable complex reasoning.”
      ↩︎ Assign steps, not whole processes
      “The best applications pair your judgment, creativity, and oversight with AI’s speed and scale.”
      ↩︎ Collaborative splits for high-stakes steps
      “Current limits include knowledge cutoffs, hallucinations, and unreliable complex reasoning.”
      ↩︎ Exam trap 1
      “Current limits include knowledge cutoffs, hallucinations, and unreliable complex reasoning.”
      ↩︎ Prediction
    4. 4.
      “The block guides Claude and doesn't enforce anything, so have a person approve each call to any tool that can move money.”
      ↩︎ Assign steps, not whole processes
      “might take actions that are difficult to reverse or affect shared systems, such as deleting files, force-pushing, or posting to external services”
      ↩︎ Reversibility decides where the human gate sits
      “Consider the reversibility and potential impact of your actions.”
      ↩︎ Exam trap 3
      “Consider the reversibility and potential impact of your actions.”
      ↩︎ Checkpoint
    5. 5.
      “deleting remote git branches from a misinterpreted instruction”
      ↩︎ Assign steps, not whole processes
      “in-project edits are reviewable via version control.”
      ↩︎ Reversibility decides where the human gate sits
      “Each of these was the result of the model being overeager, taking initiative in a way the user didn't intend.”
      ↩︎ Reversibility decides where the human gate sits
    6. 6.
      “It will never attempt an action that isn't in its tool list.”
      ↩︎ Assign steps, not whole processes
    7. 7.
      “You own the outcome, not the output.”
      ↩︎ Exam trap 4
      “You own the outcome, not the output. “AI wrote it” explains nothing and excuses nothing.”
      ↩︎ Checkpoint
    8. 8.
      “they hold the roles only humans can hold”
      ↩︎ Accountability attaches to each decision, not to the system
      “the best long-running agents have many different ways to verify their work before a human looks at it”
      ↩︎ Collaborative splits for high-stakes steps
      “Tracking which kinds of tasks each agent has earned autonomy on and expanding scope per task type after repeated successes”
      ↩︎ Collaborative splits for high-stakes steps
      “decisions with hard tradeoffs always had a human in the loop”
      ↩︎ Collaborative splits for high-stakes steps
      “the best long-running agents have many different ways to verify their work before a human looks at it”
      ↩︎ Exam trap 2
      “we’ve found that the best long-running agents have many different ways to verify their work before a human looks at it.”
      ↩︎ Checkpoint

    Ready to test yourself?

    Practise Anthropic Claude Certified Architect – Professional (CCAR-P) - December 7 onwards in quiz mode.

    Spotted a mistake, or was something unclear? Tell us.