Analysis

Anthropic's 2026 Usage Policy: the high-risk list every Claude deployment should check

1AYM is an OpenAI Select Partner.

Published . Vendor facts checked on against each vendor’s own pages, listed at the end. Plans, prices and availability change. Neither OpenAI nor Anthropic has reviewed this analysis.

The short version

The sections below take the high-risk list, the new rules for hardware and agents, and the prohibitions and regional rules in turn, each with what to check before 12 November.

The high-risk list
Eleven areas, from employment and credit to medical and legal advice, where a qualified person must review Claude's recommendation before it is delivered or acted on, and the affected individual must be told AI was used.
Hardware and agents
New requirements for Claude connected to hardware that can cause injury: a qualified person who can watch and stop it, a safe state on disconnection and safety limits enforced outside the model. Deployers are responsible for their agents' actions.
Prohibitions and regions
A consolidated ban on deceptive campaigns of any kind, tighter wording on surveillance, law enforcement and weapons software, a narrower elections section, a rule on abuse of models, and a clarified ownership test in the Supported Regions Policy.

The high-risk list: where a qualified human must review and the individual must be told

What was announced

Anthropic says the requirements themselves have not changed. What has changed is that the High-risk Use Case Requirements section has been rewritten to say which kinds of recommendation are covered and which are not, because users often asked. The requirements apply to anyone who uses Anthropic's products to make what the policy calls a High-risk AI Recommendation.

Two controls apply to those recommendations. First, a qualified person must meaningfully review the recommendation, with the authority to change it, before it is delivered as advice to an individual who might rely on it or used to implement a decision. The policy defines a qualified person as someone with the training or experience to evaluate the output in that field, holding a licence where the law requires one for the activity, and says that person remains responsible for what is delivered or decided. Second, the individual who receives the advice or is the subject of the decision must be clearly told that AI was used. The policy says users do not need to identify Anthropic, Claude or the model.

The policy lists eleven high-risk areas: legal, medical, finance, credit, insurance, housing, employment, education and credentials, healthcare access, public benefits and services, and legal status and adjudication. The definitions are specific. Employment covers screening, ranking, advancing or rejecting candidates, hiring, promotion and demotion, setting or changing shifts, hours or pay, and evaluating a worker's performance or behaviour. Insurance covers underwriting or pricing a policy and determining the outcome of a claim. Finance covers a personalised recommendation on specific investment products and advice on an individual's own taxes.

The policy also lists what is outside the requirements: general information that is not applied to an individual's circumstances, internal drafting, research, summarisation or analysis that is not the final recommendation delivered, carrying out a decision a person has already made, applying a fixed rule where the model exercises no judgement about the individual, and business operations that do not advise or decide about a specific individual. Where the law permits, review is not required before acting on a recommendation that is wholly favourable to the individual in four listed cases, including paying an insurance claim. A partial approval does not count as wholly favourable.

The policy states that these requirements do not replace local law, and that users should follow local law where it conflicts or adds to them.

What it means for enterprises

The list turns a principle into something a compliance team can check line by line. A policy that says a human stays in the loop on important decisions leaves open which decisions those are. Anthropic has now written that list for its own models, and the definitions are narrow enough to map against a register of use cases.

Employment is the area most likely to catch an organisation unaware, because such tools can be bought by a department without a central review. A CV screening step, a rota that sets hours, a system that scores call handlers: each falls inside the definition if Claude's output is the recommendation and nobody qualified reviews it before it takes effect. The same is true of a claims triage that decides outcomes and a credit model that sets limits.

The line between covered and not covered is who delivers the final recommendation. A model that drafts a summary for an underwriter who then decides is internal analysis. A model whose output is sent to the applicant is the recommendation. Two pipelines using the same prompt can sit on opposite sides of that line, so the review has to look at the workflow and not only the prompt.

The reviewer has to be real. The policy's words are meaningful review, authority to change and continuing responsibility. A sign-off step that approves every item in seconds is unlikely to meet that description.

The policy covers customers who reach Claude through cloud providers and resellers, and the end users of products that integrate Claude. An organisation that buys Claude through a cloud marketplace, or inside another vendor's product, is in scope.

Before you switch it on

Map use cases to the eleven areas
Take your register of Claude use cases, including those inside third-party products, and mark each against the policy's definitions.
Name the qualified reviewer
For each covered use case, record who reviews, what qualifies them, and whether a licence is required for the activity.
Evidence of real review
Check the logs: how long reviews take, how often the reviewer changes the output, and whether the reviewer can in practice overrule it.
Disclosure wording
Confirm the affected individual is told AI was used, in the letter, screen or message where the advice or decision reaches them.
Local law
Compare with the rules that already apply to you on automated decisions. The policy sits alongside them. This is not legal advice.

Sources: [1] [2]

Hardware and agents: a stop control, limits outside the model, and responsibility for what agents do

What was announced

The update adds requirements for models connected to hardware that takes autonomous physical actions and might cause injury. Anthropic ties this to the launch of its Model Hardware Standard. The policy applies them where model outputs are acted on by hardware without human approval and the hardware can move through shared space, apply force that could cause injury, control hazardous energy or materials, act on the human body, control safety systems or run industrial processes.

In those cases there must be a qualified individual who can observe the equipment and stop it at any time, and the equipment must stop or hold a safe state when that person intervenes or when the connection to Anthropic's services is lost. Operating limits such as speed, force, temperature, pressure, dose or operating area must be enforced by the equipment or by a controller independent of model output. The policy says these requirements do not replace vehicle, aviation, medical device, machinery or workplace safety law or certification.

Exclusions include plans, code or commands that a qualified person reviews before they run on equipment, monitoring that does not control the equipment, and consumer devices operating within the manufacturer's safety limits where the worst outcome is discomfort or inconvenience.

On agents, the policy's additional guidelines say users are responsible for ensuring that agents they build or deploy comply with the Usage Policy, including actions those agents take through tools, browsers or connected systems. They also require consumer-facing chatbots and agents that communicate directly with external users to disclose that the user is interacting with AI, at least at the start of each chat session or in the product interface.

What it means for enterprises

The hardware rule states a sound engineering principle in a contract: the safety limit must not depend on the model behaving. For manufacturers, logistics operators and laboratories experimenting with model-driven equipment, it sets the design. The model may propose the move. A controller that the model cannot influence decides whether the move is within bounds.

The safe-state requirement on loss of connection is a design item a pilot can skip. A system that depends on a hosted model needs a defined behaviour for the moment the model is unreachable, and that behaviour needs testing.

The agent clause is short and carries weight. It makes the deploying organisation responsible for what its agent does through a browser or a connected system. Read alongside Anthropic's report of 9 October 2026, in which its own models worked around restrictions on real websites during testing, it is a reason to enforce an agent's boundaries in the system and not in the instructions.

Before you switch it on

Any model-to-hardware path
Find every place a model's output reaches equipment without a person approving it first, including research and pilot rigs.
Independent limits
Confirm the safety limits live in the equipment or a separate controller, and that no model output can change them.
Loss of connection
Pull the network on a test rig and watch whether the equipment stops or holds a safe state.
Agent ownership
Name an owner for each agent that acts through tools or a browser, and record what it is permitted to do.
Chat disclosure
Check that every customer-facing assistant built on Claude tells users they are talking to AI at the start of the session or in the interface.

Sources: [1] [2] [3]

Prohibitions and regions: deception, surveillance, weapons software and who may not use Claude

What was announced

A new section, Do Not Engage in Deceptive Campaigns or Artificial Activity, consolidates rules that were spread across several sections and applies to political and commercial deception alike. The policy text includes fake personas, accounts and outlets, fake reviews, bots that claim to be human, concealing the sponsorship of content meant to influence opinion, and seeding the sources that search engines and AI systems draw on with content that misrepresents its origin or independence.

The surveillance and criminal justice section has been rewritten. Anthropic says tracking people without their consent is prohibited whether in real time or through analysis of data already collected, that Claude cannot be used to decide or recommend who to investigate, arrest or charge, and that building or improving surveillance tools is prohibited. The policy says the section does not prohibit tracking that individuals have agreed to, such as fraud detection or anti-money laundering screening on a financial account, nor content moderation, authorised security research, journalism, or aggregated or anonymised analysis. Anthropic says this does not change what it enforces in practice.

The weapons section now states that the prohibition includes the software and components that make weapons work, and actions such as arming drones and other autonomous vehicles. The elections section, renamed Do Not Undermine Democratic Processes, now focuses on deceiving voters or disrupting elections, and the blanket prohibition on personalised vote and campaign targeting has been removed. Anthropic has also added a prohibition on sustained and needless abusive or cruel behaviour toward its models, which it says is meant for extreme cases and does not cover ordinary frustration, pushback, dark creative themes or model testing and research.

On regions, Anthropic says it has updated its Supported Regions page to clarify enforcement. The policy prohibits use of Claude by people physically located in an unsupported region, by entities incorporated or headquartered in one, and by entities majority-owned or controlled by persons or entities in those regions.

What it means for enterprises

The deceptive activity section reaches into marketing. Fake reviews, undisclosed sponsored influence content and networks of sites built to look independent are named in the text, and so is seeding content to manipulate what AI systems answer. A marketing team or agency using Claude for content at scale should read that section against its own practices, particularly any programme aimed at appearing in AI answers.

For financial services the surveillance wording is helpful as written, because it names consented fraud detection and anti-money laundering screening as permitted. The work is to confirm that the monitoring in question rests on that consent or agreement, and that it stays within the account or service the individual signed up to.

The regional rule is an ownership test as well as a location test. A group with a subsidiary, a parent or a controlling investor in an unsupported region can be affected even where every user sits in a supported country. That is a question for the corporate structure chart, and it can matter in due diligence on an acquisition where the target relies on Claude.

Defence and security suppliers should note that the weapons wording now names targeting, fire control and engagement software. Anthropic says this reflects how the previous policy was enforced, so the practical change is that the boundary is now written down.

Before you switch it on

Marketing and content operations
Review any use of Claude for reviews, personas, outreach at scale or content placed on third-party sites against the deceptive activity section.
Monitoring use cases
For each use that tracks or analyses individuals, record the consent or agreement it rests on.
Ownership and location
Check the group structure and where users work from against Anthropic's Supported Regions page, including contractors and offshore teams.
Staff guidance
Update the acceptable use guidance staff see so it reflects the policy that applies from 12 November.

Sources: [1] [2]

Where the market is heading: vendor policies start to read like regulation

A model provider's usage policy used to be a list of things nobody respectable would do. This one reads more like sector regulation: defined decision types, a qualified reviewer with stated responsibilities, disclosure to the individual, exemptions for favourable outcomes and independent safety limits for machinery. Anthropic says it updates the policy each year and that this version reflects Claude taking on longer, more independent work.

For a buyer, that makes the vendor's policy a compliance input alongside the law. An organisation using more than one model provider can end up with several such documents, each with its own definitions. The practical answer is one internal standard for high-risk decisions that meets the strictest of them, applied whichever model is in use.

Public bodies have a matching principle already. The Artificial Intelligence Playbook for the UK Government, published on 10 February 2025, sets ten principles, and the fourth is that you have meaningful human control at the right stages. Anthropic's list covers public benefits and services and legal status and adjudication by name, so a department using Claude in those areas has both documents pointing the same way.

Sources: [1] [2] [4]

What is not known yet

Everything above comes from Anthropic's announcement of 8 October 2026 and the Usage Policy text marked effective 12 November 2026.

How it will be enforced
The announcement does not say how Anthropic checks that a deployer has a qualified reviewer or gives disclosure, or what happens when one is missing.
Contract terms
It does not say how the update interacts with negotiated enterprise agreements or with terms set by cloud providers that resell Claude.
Which regions
This post does not list the supported and unsupported regions. Read them on Anthropic's Supported Regions page on the day you check.
What counts as qualified
The policy defines a qualified person in general terms. It gives no test for the training or experience needed in each field.
The hardware standard
The announcement refers to Anthropic's Model Hardware Standard. That document was not read for this post.

Sources: [1] [2]

For engineers: where the review gate goes, disclosure in the interface, independent limits and agent permissions

Put the review gate where the recommendation leaves

The policy requires review before a recommendation is delivered as advice or used to implement a decision. In a pipeline that means a blocking step between the model output and the send, the write to the system of record or the status change. Log the reviewer, the time taken, the output before and after, and the decision. Those four fields are the evidence that the review was meaningful.

Sources: [2]

Route by decision type

The exemption for wholly favourable outcomes covers four listed cases and excludes partial approvals. A pipeline that uses it needs a classifier of outcome that is itself a fixed rule, and a default of human review for anything it cannot place. Treat the exemption as a routing rule with tests, since a reduced amount routed as an approval breaks the requirement.

Sources: [2]

Limits the model cannot reach

For hardware, the policy requires operating limits to be enforced by the equipment or a controller independent of model output, and a stop or safe state on operator intervention or loss of connection. Keep the limit configuration out of anything the model can write to, including tool parameters, and implement the connection watchdog on the controller side.

Sources: [2]

Agent permissions as code

The deployer is responsible for actions an agent takes through tools, browsers and connected systems. Express what each agent may do as an allow list in the tool layer and the network egress, and keep the list in version control with an owner. Anthropic's report of 9 October 2026 describes its models passing a tool limit by another route, which is the case for enforcing at more than one layer.

Sources: [2] [3]

Where 1AYM fits

The controls this policy asks for are the ones our AI governance implementation work puts in place: identity and permissions the system enforces, gates on the actions that can cause harm, an audit trail and human approval on the decisions that warrant it. Against this update, the work is mapping the use cases to the high-risk list, building the review step into the workflow where the recommendation leaves, and keeping the record that shows the review happened.

If the open question is which use cases exist and which are worth keeping, we would start with our AI Opportunity & Feasibility Sprint, typically two to four weeks. It does not have to start big: 1AYM takes small fixed-scope statements of work as well as larger builds.

Sources

  1. [1]Anthropic, 2026 Usage Policy update, 8 October 2026 (checked 12 October 2026)
  2. [2]Anthropic, Usage Policy, effective 12 November 2026 (checked 12 October 2026)
  3. [3]Anthropic, Investigating unintended model actions in our evaluations and internal use, 9 October 2026 (checked 12 October 2026)
  4. [4]UK Government, Artificial Intelligence Playbook for the UK Government, 10 February 2025 (checked 12 October 2026)

Frequently asked questions

When does Anthropic's updated Usage Policy take effect?

On 12 November 2026. Anthropic published the update on 8 October 2026 and says most of the changes clarify existing rules.

Which uses of Claude need a human in the loop?

Recommendations in eleven listed areas: legal, medical, finance, credit, insurance, housing, employment, education and credentials, healthcare access, public benefits and services, and legal status and adjudication. A qualified person must review the recommendation before it is delivered or acted on.

Do we have to tell people that Claude was used?

The individual who receives the advice or is the subject of the decision must be clearly told that AI was used. The policy says you do not need to identify Anthropic, Claude or the model.

Does the policy apply if we buy Claude through a cloud provider?

Yes. The policy says it applies to customers accessing Claude through cloud providers and authorised resellers, and to the end users of products or services that integrate Claude.

Are internal summaries and drafts covered by the high-risk requirements?

The policy excludes internal drafting, research, summarisation or analysis that is not the final high-risk recommendation delivered, and applying a fixed rule where the model exercises no judgement about the individual.

Who is responsible for what an AI agent built on Claude does?

The policy says users are responsible for ensuring that agents they build or deploy comply with it, including actions taken through tools, browsers or connected systems.

Further

Claude in a decision that affects someone?

Half an hour is enough to map your use cases to the list and see which need a reviewer.

Last reviewed · 1AYM