This domain is 21% of the CCAO-F exam. Check Claude's work before it reaches a customer, a report or a decision.
Treat Claude's output as a draft
Claude writes fluently, which makes errors easy to miss. The core skill here is reviewing output with the same care you would give a capable but new colleague's work: plausible does not mean correct.
What to check
- Facts and figures — verify numbers, names, dates and quotes against the source. Claude can state something wrong with complete confidence.
- Completeness — did it answer every part of the request, or quietly skip the hard part?
- Faithfulness to the source — when summarising a document, does the summary say only what the document says?
- Fit for purpose — tone, audience, format and length for the actual use.
Validate against criteria
Write the acceptance criteria before you read the output: what must be true for this to be usable? Checking against a list is faster and more reliable than a general impression. Where possible, ask Claude to show its sources or reasoning so you have something to verify, then check the evidence yourself.
Match the checking effort to the risk
A brainstorm needs a skim; a customer-facing statement, a contract clause or a financial figure needs full verification and often a second person. Decide up front which outputs need human sign-off.
Common exam angles
- Choosing the best check for a given output (verify against a source versus ask Claude if it is sure — the former).
- Recognising hallucinated detail, such as invented references.
- Knowing when output is good enough to use and when it must go back for revision or human review.