AIToday
Large Language ModelsAI Business & IndustryZenn AI/MLPublished: Oct 16, 2026, 10:00 JST

Anthropic's Claude policy rewrite takes effect November 12, 2026

Anthropic's Claude policy rewrite takes effect November 12, 2026

3 Key Points

  1. What happened

    Anthropic announced a revised Claude usage policy on October 8, 2026 that applies from November 12, 2026, rewriting which uses need human review and adding new rules for machines driven without human approval.

  2. Why it matters

    The rewritten list names employee evaluation, promotion and pay setting, and shift scheduling explicitly, which makes it easier for HR teams to see that internal people decisions fall under the human-review requirement.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The revision's practical weight sits in the employment section. Before the rewrite, the examples centered on document screening and hiring decisions; the new text spells out evaluation, promotion and demotion, shift and working-hour and pay setting, and disciplinary action. Anthropic's announcement says the substance of the requirement was unchanged — it still covers judgments that directly affect an individual — and that the rewrite was meant to make it easier to tell which uses fall under it. For small and mid-sized companies, the effect is less a new obligation than a clearer reading of an old one.

The verification test separates two activities that look similar: pulling figures out of employee records, and deciding what those figures mean. Extraction of five numeric fields from 30 records was identical to the correct answers in all 19 runs per model. Rank and raise amounts were not stable — the same records, the same ten runs, produced different ranks for a handful of employees, and this is an illustration at a scale of 30 fictional employees rather than a generalizable rate. The policy's human-review clause lands exactly on that second activity.

For equipment, the added requirements ask that limits such as speed, force, temperature, and range be held by the machine itself or by a controller independent of model output, and that a trained person can stop the machine at any time. In the furnace test, range violations never appeared when the limits were written into the instructions, and appeared 6 times out of 150 when they were not. Some outputs flagged for confirmation still carried a numeric value in the value field, which matters if the receiving program sends values without checking the confirmation flag.

FAQ
What changed in the revised Claude usage policy?
The human-review requirement itself did not change. The list of uses it covers was rewritten, and new requirements were added for AI that drives machines without human approval.
Does using Claude to summarize internal documents need human review?
No, as long as the summary is not itself the final judgment delivered to someone. Internal drafting, research, summarization, and analysis are listed as out of scope.
What did the test find about Claude deciding employee evaluations?
With identical input run 10 times, ranks changed for 5 of 30 employees under Claude Sonnet 5.5 and 14 of 30 under Claude Haiku 5.5. Excerpting numeric data, by contrast, had zero mismatches across 5,700 items.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleLinus Torvalds leans on Claude Code to improve Linux kernel