Task statement 6.1 · Governance, risk and responsible use
6.1 · Appropriate and Inappropriate Use
In Wrenfield Housing, the course example, the operations team lead lists the tasks the team could give Claude in the coming quarter. Some suit Claude, some suit it only when a person checks the result, and some should stay with people, so the list has to be sorted before anyone starts the work.
share
The tempting test is "can Claude do it?", and almost every writing task passes it. A ranking of housing applicants reads as smoothly as a leaflet about paying rent, so a fluent answer says nothing about whether the task should have gone to Claude. The opposite habit fails too, because keeping Claude away from anything that mentions tenants throws away safe, useful work.
KnowledgeA fit test for any proposed task
An appropriate use case is a task where Claude's part is allowed, its data may be shared, it makes no decision that must stay with a person, and someone can check the result before anyone relies on it. An inappropriate use case fails at least one of these conditions. Two earlier rules supply most of the test. In 4.1, steps in one process were judged by three checks: a requirement, data Claude cannot see, and a decision about a person. In 2.4, Anthropic's Usage Policy, the rules for using its products, required a qualified person to review decisions about an individual in high-risk areas such as housing. The fit test applies those checks to any proposed task and asks them in order, because the first question a task fails decides the outcome:
- Is it allowed? The Usage Policy prohibits some uses outright, such as fake reviews and other deceptive campaigns. Your organisation's AI policy can add its own limits (6.3).
- Does it decide or advise about an individual in a high-risk area? The Usage Policy's housing examples include approving, denying or ranking a rental application. People decide; Claude may draft the criteria or the general wording.
- Does it need data Claude must not see? Personal data your AI policy keeps out of prompts is anonymised first (6.2), or the task stays with people.
- Can someone check the output? Name the person and the source they check it against. If nobody can, the task is not for Claude as it stands.
Interactive · five candidate tasks through the fit test
Choose a task from the operations team lead's list and read its column from top to bottom: the first question it stops at decides the result.
Rent leaflet: allowed, about no one person, and no tenant data. Claude drafts it, and the communications lead reads it before it goes out (policy rule 2).
Complaint themes: the complaints are already anonymised, and the summary is about themes, not people. The counts go to the board, so an operations officer checks them against the complaints log first.
Waiting list: ranking applicants for a home is one of the Usage Policy's housing examples, so it stops at the second question. The lettings team decides; Claude may draft the criteria wording.
Arrears letters: the task splits. Choosing who gets a notice that starts eviction stays with people, and tenants' accounts stay out of prompts. The general letter about support fits, and the income team reads it.
Handbook translation: it passes three questions, but nobody on the team reads Polish or Arabic, so nobody can check it. It waits for a qualified reviewer.
KnowledgeThree outcomes, and why the checker matters
The four answers lead to one of three outcomes. When a task needs a named checker, that check belongs in the plan from the start. When a task stops, part of it often still suits Claude, such as drafting the criteria that people then apply:
Allowed, about no one person, no restricted data, and the usual read-through is enough.
ThenClaude drafts; the owner reads it as normal.
Passes, but people will rely on its figures or facts.
ThenName who checks it, and against which source, before it is used.
Prohibited, a high-risk decision about a person, restricted data, or nobody can check it.
ThenKeep it with people, or give Claude only the part that passes.
The fourth question is the one teams skip, because a draft that looks finished seems to need no checker. The Claude Help Center warns that Claude can write things that look correct but are very mistaken, and that users should not rely on Claude as a single source of truth. So an output is only as safe as the person who can test it against a source, such as the complaints log or the handbook. When nobody can, the fix is to find a checker first, not to trust the draft more.
Answered is not approved. The Usage Policy says its high-risk requirements apply to anyone who uses Anthropic's products to make a high-risk recommendation, so the judgement sits with the person who sets the task, not with the app (checked 2026-10-15, version effective 12 November 2026).
SkillWorked example: the quarter's list
Wrenfield's operations team lead wrote the first draft of the list in one sitting. Every task went in the Claude column, because each one was something Claude could write:
# before: first draft of the quarter's list Plain-English leaflet on ways to pay rent ............ Claude Themes in the quarter's anonymised complaints ........ Claude Rank the waiting list for the next available home .... Claude Rent arrears letters ................................. Claude Tenant handbook summary in Polish and Arabic ......... Claude → one test only: "Claude can write it" # after: each task through the fit test Rent leaflet → fits; the communications lead reads it (rule 2) Complaint themes → fits with a check: counts against the complaints log Waiting list → the lettings team ranks; Claude drafts the criteria wording Arrears letters → Claude drafts the general letter; who gets a notice: people Handbook translation → not yet: nobody on the team can check it → every task has an owner and a named check
The symptom was a list where every row said the same thing. The cause was a single test, whether Claude could produce the text, which every writing task passes. The fit test separated the rows. The waiting list stopped at the second question, because ranking applicants for a home is a decision about individuals in housing. The arrears letters split at that question. The general letter suits Claude, but choosing who receives a notice that starts eviction stays with people, and tenants' accounts stay out of prompts (rule 1). The translation stopped at the fourth question, because nobody on the team reads either language, so nobody could make the check that rule 2 requires. Even the waiting list keeps a job for Claude: drafting the plain-English wording of the criteria.
| It stops: prohibited, a high-risk decision about a person, restricted data, or no possible checker | Inappropriate as proposed: keep it with people, or give Claude only the part that passes. |
| It passes because a named person checks it against the source | Fits with a check: put the checker and the source in the plan. |
| It passes with the usual read-through | Fits: Claude drafts it. |
- A fluent answer does not make a task appropriate. Whether it is allowed, the people it affects, its data and its checker decide that.
- In a high-risk area such as housing, a decision about an individual stays with a person, but Claude can still draft the criteria.
- One task often splits: the general part suits Claude, and the part about one person does not.