CertSafari
    Anthropic Claude Certified Associate – Foundations (CCAO-F) - December 7 onwards· Lessons

    Domain 4 · Lesson 12/21

    Delegating workflow steps: AI-executed, human-retained or human-reviewed

    Delegation and Workflow Redesign

    15 min read
    4.5% of exam
    11 sources
    Published 18 Nov 2026
    Docs as of 18 Nov 2026

    What you will be able to do

    • Break an existing business workflow into separate steps and record what happens when each step goes wrong
    • Rate each step on reversibility, stakes, need for human judgment or empathy, and accountability
    • Label each step AI-executed, human-retained or human-reviewed, and say why the label fits
    • Put a redesigned workflow in an order where human decisions and checks come before anything that depends on them
    • Recognize the signs that a workflow has been over-delegated

    Key concept

    Delegation — The decision, made one step at a time, about which parts of a piece of work AI carries out and which stay with a person. It starts with breaking the work into steps, not with the question of whether to use AI at all.

    1.Delegation is decided step by step

    Delegation is about where AI fits inside a workflow. Whether to use AI at all is the wrong question. Delegation is one of the four AI Fluency competencies, and its job is deciding what AI handles and what stays with you. That decision makes sense only at the level of a single step. A refund dispute, a donor thank-you campaign or a quarterly report each holds several steps. Some of them suit Claude well, and some must never leave a person's hands.

    Delegation therefore starts by breaking the work into steps. How to split work into parts is covered in task decomposition. Here, decomposition is the first move of a redesign: once a workflow is split apart, each step can get its own owner. A team that labels the whole workflow "AI-assisted" has made no delegation decision. It has only stopped looking.

    Each step gets one of three labels:

    • AI-executed: Claude does the step, and the result moves on without a person approving that specific output.
    • Human-reviewed: Claude produces the output, and a named person checks it before anything downstream relies on it.
    • Human-retained: a person does the step, and AI may at most supply inputs to it.

    These labels are not ranked, and a good redesign usually uses all three. One illustrator's workflow shows why. Applying the same delegation analysis led to different outcomes for different pieces of work. The goal is never to maximise the AI-executed column. Each label has to be one you could defend to a peer who challenged it.

    Checkpoint 1 of 8· Check yourself

    A support team redesigning its refund-dispute workflow reports that "the whole process is now AI-assisted." What should the team have done to make a real delegation decision?

    Sources1234

    2.Four criteria that decide the label

    Four properties of a step decide its label. Effort, length and boredom are not among them. A label that follows from how unpleasant a task is will put the wrong steps with Claude.

    Reversibility comes first. If a step's mistake can be caught and undone before it matters, the cost of an AI error is a quick edit. A draft that colleagues can freely rewrite before anyone outside the team sees it is fully reversible. A step that sends money, makes a commitment to a customer or deletes a record is not. Even guidance for highly capable agents keeps this line: retain your own confirmation step for risky or irreversible actions.

    Stakes are the size of the harm if the step goes wrong. Stakes decide how hard a human-reviewed output gets checked, and the rule is to verify in proportion to the stakes. How deep that review goes is covered in review depth and escalation. For delegation, the point is simpler: when stakes are high, at least review, and often retention.

    Need for human judgment or empathy covers steps where the right answer depends on values, relationships or reading a person in the moment. Comforting a distressed customer and reading their emotional state as a live conversation unfolds is the clearest case. Teachers drafting their own AI commitments land in the same place, refusing to delegate final judgment, relational feedback and high-stakes evaluation.

    Accountability asks who answers for the step's result. If a named person must stand behind a decision, that person has to actually make it. Owning the outcome regardless of AI's role is the competency called diligence, covered in policy, ethics and diligence. In delegation terms, a step where someone must answer for an irreversible decision is the strongest case for human-retained.

    How each criterion pushes a step's label
    CriterionPoints toward AI-executedPoints toward human-retained
    ReversibilityOutput can be edited or discarded before anyone relies on itCommits the organisation to something that cannot be undone
    StakesAn error costs a quick correctionAn error harms a customer, a donor or the organisation
    Judgment or empathyFollows a fixed checklist applied the same way every timeRequires weighing values or reading a person's emotional state
    AccountabilityNo one has to answer personally for the outputA named person must answer for the decision

    Steps in the middle of the table, which are reversible but still consequential, usually become human-reviewed. A fixed checklist that has been applied the same way for years needs no fresh judgment, so it leans toward AI-executed. A long, repetitive step leans the same way.

    Checkpoint 2 of 8· Check yourself

    In a charity's donor thank-you workflow, which of these steps has the strongest case for being labelled human-retained?

    Checkpoint 3 of 8· Exam question

    Which TWO characteristics of a workflow step most strongly justify keeping it human-retained? Choose two.(Select 2)

    0 of 2 selected

    Sources56781

    3.Redesigning a workflow in the right order

    A redesign runs as a chain in which each stage uses the output of the one before it. Understand each step before you judge it, judge it before you assign an owner, and test the design before you rely on it. Running a stage early leaves it with nothing to work from.

    The five stages, in order:

    1. Inventory. List every step of the current workflow separately, including what happens if that step goes wrong. The failure consequence is the raw material for the reversibility and stakes ratings.
    2. Rate. Score each step on reversibility, stakes, need for judgment or empathy, and accountability.
    3. Label. From those ratings, mark each step AI-executed, human-reviewed or human-retained.
    4. Assign owners. Name one accountable person for every human-retained and human-reviewed step. Until the labels exist, you do not know which steps need an owner.
    5. Pilot. Run the redesign on a small batch, check the results against a written definition of done, and confirm that reviewers actually catch problems. Move any step that proves over-delegated back toward human control.

    The pilot is where a design on paper meets real work. Piloting cautiously is a sensible default whenever a team is unsure an AI use is appropriate. Concrete acceptance statements give the pilot something to measure against. A pass or fail that a stranger could judge beats "the workflow feels smoother." The aim is a repeatable AI-assisted workflow with appropriate human review. Making that workflow reusable across a team is the subject of repeatable workflow design.

    Checkpoint 4 of 8· Put it in order

    An operations lead is redesigning the team's monthly vendor-invoice workflow so Claude can take on part of it. Put the redesign stages in the order they should run.

    1. 1.Mark each step AI-executed, human-reviewed or human-retained based on those scores
    2. 2.List every step of the current workflow separately, noting what happens if each one goes wrong
    3. 3.Run the design on a small batch, check the results against a written definition of done, and move over-delegated steps back toward human control
    4. 4.Score each step on reversibility, stakes, need for judgment or empathy, and accountability
    5. 5.Name one accountable person for every human-retained and human-reviewed step

    Checkpoint 5 of 8· Exam question

    A team is redesigning an existing workflow using delegation criteria to decide which parts Claude executes and which people keep. Which sequence should the team follow?

    Sources289

    4.Worked example: a refund-dispute workflow

    A support team redesigns its refund-dispute handling under two stated rules. The agent makes the remedy decision before any reply is drafted, and nothing reaches the customer until the agent has approved it. Both rules come straight from the criteria. A remedy commits the company and the agent answers for it, so it is human-retained. The customer reply is consequential but editable before sending, so it is human-reviewed.

    Ordering follows one principle: evaluate what AI gives back before acting on it. Each human check sits right after the AI output it checks and before anything that relies on it. The remedy decision depends on the facts of the complaint, so a verified summary must come before the decision. The reply must reflect the remedy, so the decision must come before the draft.

    The redesigned refund-dispute workflow, in the order it runs
    OrderStepLabel
    1Claude summarizes the complaint thread into the customer's main claims and datesHuman-reviewed (output checked in step 2)
    2The agent compares the summary against the original thread to confirm it is accurateHuman check
    3The agent decides the remedy, such as a refund, credit or replacementHuman-retained
    4Claude drafts a reply that reflects the remedy the agent choseHuman-reviewed (output checked in step 5)
    5The agent edits the draft, approves it and sends it to the customerHuman check and send

    Two orderings that look efficient both break the rules. If Claude drafts the reply before the agent decides, the draft quietly suggests a remedy, and the agent ends up approving a decision instead of making one. If the agent decides from an unchecked summary, a misread date or a missing claim feeds straight into an irreversible commitment.

    Checkpoint 6 of 8· Check yourself

    To speed up refund disputes, a manager suggests changing the order of the redesigned workflow. Which sequence still keeps the remedy human-retained and every human check in the right place?

    Checkpoint 7 of 8· Exam question

    A support team redesigns its refund-dispute workflow. The remedy decision stays with the agent and is made before any reply is drafted. Nothing reaches the customer until the agent has approved it. Which sequence of steps follows these rules?

    Sources110

    5.Recognizing over-delegation

    Over-delegation means a step that meets the criteria for human control has drifted to AI, or a human check has become a formality. It rarely announces itself. It shows up months later in how people work, so the useful skill is knowing the observable signs.

    Signs that a workflow has been over-delegated:

    • Skill atrophy. Staff can no longer do a step without Claude, so nobody could take it back or judge Claude's output well.
    • Convergence. Outputs that should be distinctive, such as appeals, proposals or customer replies, have started to sound alike.
    • Reaching for AI before knowing what you want. People open Claude to work out what a step should produce, so the judgment that belonged in the step never happens.
    • No one who answers for the result. When something goes wrong, nobody can say who owned the decision.
    • "AI wrote it" as an explanation. That phrase explains nothing and excuses nothing, and hearing it means accountability has slipped out of the workflow.

    The remedy is to re-run the criteria, not to ban AI. The creative-practice version of the method makes this concrete: start from no AI and let the analysis decide whether and how to opt in. A step pulled back to human-retained can move forward again once the reason for pulling it back is gone. That only happens if someone revisits the labels. A delegation policy without revision triggers goes stale silently.

    Checkpoint 8 of 8· Check yourself

    Six months after a fundraising team handed appeal drafting to Claude, the director audits the workflow. Which finding is evidence that the work has been over-delegated?

    Sources4113

    Sources

    (11)

    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.”
      ↩︎ Delegation is decided step by step
      “Diligence means owning the final result fully, regardless of AI’s role.”
      ↩︎ Four criteria that decide the label
      “Discernment means evaluating what AI gives back before acting on it.”
      ↩︎ Worked example: a refund-dispute workflow
      “Discernment means evaluating what AI gives back before acting on it.”
      ↩︎ Exam trap 2
    2. 2.
      “Delegation means decomposing the problem first, then deciding what AI handles at each step.”
      ↩︎ Delegation is decided step by step
      “Write acceptance tests before code. They give you and AI a shared definition of done.”
      ↩︎ Redesigning a workflow in the right order
      “Delegation means decomposing the problem first, then deciding what AI handles at each step.”
      ↩︎ Key concept
      “Delegation means decomposing the problem first, then deciding what AI handles at each step.”
      ↩︎ Exam trap 3
      “Delegation means decomposing the problem first, then deciding what AI handles at each step.”
      ↩︎ Checkpoint
    3. 3.
      “There is no single position on AI usage; it is decided at the level of mode and task.”
      ↩︎ Delegation is decided step by step
      “A policy without revision triggers goes stale silently.”
      ↩︎ Recognizing over-delegation
    4. 4.
      “If a peer challenged a Delegation call, could you defend it?”
      ↩︎ Delegation is decided step by step
      “Convergence and skill atrophy are the long-term pitfalls; reaching for AI when you do not know what you want is the immediate one.”
      ↩︎ Recognizing over-delegation
      “The starting position is no AI; the analysis determines whether and how you opt in.”
      ↩︎ Recognizing over-delegation
    5. 6.
      “Delegate implementation freely. Keep empathy, judgment, and shipping in your hands.”
      ↩︎ Four criteria that decide the label
      “Delegate implementation freely. Keep empathy, judgment, and shipping in your hands.”
      ↩︎ Exam trap 1
    6. 8.
      “I will not delegate decisions related to: (e.g., final judgment, relational feedback, high-stakes evaluation)”
      ↩︎ Four criteria that decide the label
      “pause, consult a colleague, review district guidance, pilot cautiously”
      ↩︎ Redesigning a workflow in the right order
    7. 9.
      “design a repeatable AI-assisted workflow with appropriate human review”
      ↩︎ Redesigning a workflow in the right order
    8. 10.
      “Humans often work in the same threads the agents do, but they hold the roles only humans can hold.”
      ↩︎ Worked example: a refund-dispute workflow
    9. 11.
      “You own the outcome, not the output. “AI wrote it” explains nothing and excuses nothing.”
      ↩︎ Recognizing over-delegation
      “You own the outcome, not the output. “AI wrote it” explains nothing and excuses nothing.”
      ↩︎ Exam trap 4
      “You own the outcome, not the output. “AI wrote it” explains nothing and excuses nothing.”
      ↩︎ Checkpoint

    Ready to test yourself?

    Practise Anthropic Claude Certified Associate – Foundations (CCAO-F) - December 7 onwards in quiz mode.

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