
Blog Post
Why AI Text Detectors Fail and What to Use Instead
October 27, 2026
Somebody in the organization will eventually propose running documents through an AI text detector. The instinct is reasonable and the method is the one approach the published evidence rules out, for reasons a security or risk function should understand before the policy gets written.
The organization that built the most widely used language model tried this and withdrew its own tool after six months. Its reason was accuracy, and the figures it published before withdrawing explain why.
What Did the Vendor's Own Detector Achieve?
Less than a coin flip in the direction that matters.
The Published Figures
When OpenAI launched its text classifier in early 2023 it published its own accuracy figures. The tool correctly identified twenty-six percent of AI-written text while incorrectly labeling human-written text as AI-written nine percent of the time.
What Those Two Numbers Mean Together
Three quarters of machine-written text passed as human, and roughly one in eleven human writers was flagged. The company also noted that human text would sometimes be confidently mislabeled, and that AI text could be edited to evade the tool.
The Withdrawal
In July 2023 the classifier was discontinued, with OpenAI stating it was no longer available because of its low rate of accuracy. The tool built by the organization with the most direct knowledge of how the text was produced could not do the job.
Who Gets Falsely Accused?
Not randomly, which is what turns an unreliable tool into a discrimination problem.

The Stanford Finding
Researchers at Stanford tested seven widely used detectors against writing samples from native and non-native English writers, publishing the results in the journal Patterns. Essays written by non-native speakers drew an average false positive rate above sixty-one percent, while essays by native-speaking American students were classified close to correctly.
Why It Happens
Detectors key on linguistic predictability, and writing with a narrower range of vocabulary and construction reads as more predictable. The method penalizes constrained expression rather than machine authorship, and those are not the same thing.
The Part That Closes the Argument
The same study found that prompting for greater linguistic variety removed the bias and let generated text pass undetected. A detector therefore flags writers whose English is their second language while anybody deliberately using AI evades it with one extra instruction.
What Is the Organization Asking?
Usually one of three questions, none of which a detector answers.
- Did confidential material leave the organization? A security question, answerable from records of what was sent where.
- Is the work correct? A review question, answerable by checking the claims against their sources.
- Did this person do the thinking? A management question, answerable by asking them about it.
Why Separating Them Matters
Each has a reliable method and none of the three needs authorship attribution. Naming the question being asked usually reveals that the detector was never the right instrument for it.
The Question Nobody Should Need to Ask
Whether a tool was used at all, in an organization where using one is permitted. Where policy allows assistants, the use is not the concern and the handling of material is.
What Does Usage Monitoring Answer Instead?
Observed activity rather than inferred authorship, which is a different kind of evidence entirely.
What the Record Contains
Which identity reached which assistant, under which account, at what time, and what category of content went with it. Usage monitoring produces that from systems operating rather than from a judgment about prose.
Why It Is Fairer
A record of an event either exists or does not. It carries no view about a person's writing style and cannot be biased by their vocabulary, so the finding survives a challenge in a way a probability score does not.
What It Does Not Tell You
Whether a specific document was drafted with assistance. It tells you which tools a person uses and what they send to them, and that is usually the governable fact rather than the authorship of any single paragraph.
Where Does the Real Exposure Sit?
In the material that went out rather than in the text that came back.
The Asymmetry
A report drafted with an assistant and reviewed properly carries little risk. A customer list pasted into an unmanaged account carries a great deal, and the second leaves a record while the first does not. What employees share with assistants covers which categories are detectable and how.
Which Tools Are in Use
An assistant nobody approved is the one carrying material nobody is monitoring. Shadow AI detection establishes the population before any question about a document arises, and unsanctioned use is where the governable exposure concentrates.
What Should Be Done Instead?
Three things, and none involves pasting prose into a tool.
Set a Disclosure Expectation
State plainly whether assistance should be declared and in what form. Most disputes over generated work trace back to nobody having said, which makes the ambiguity a management failure rather than an individual one.
Review the Work on Its Merits
Check the claims, the sources and the reasoning. Generated text that survives that review is acceptable work, and human text that fails it is not, which is the standard that applied before any of this existed.
Never Act on a Detector Score
The Stanford authors cautioned explicitly against using these tools in evaluative settings. An accusation resting on a probability from a method with a documented bias is one the organization cannot defend if challenged.
Watch the Activity, Not the Prose
OpenAI's own classifier caught twenty-six percent of generated text while falsely flagging nine percent of human writing, and was withdrawn in July 2023 for low accuracy. Stanford researchers testing seven detectors found a false positive rate above sixty-one percent on writing by non-native English speakers against near-correct classification of native-speaker essays, because the method penalizes constrained expression rather than machine authorship. The same work showed that one additional prompt both removes the bias and defeats detection, so the tools penalize candor and reward evasion simultaneously. The questions behind the request concern whether confidential material left the organization, whether the work is correct, and whether the person understands it, and each has a reliable method that attribution does not.
To see which assistants your teams use and what they send to them, book a demo mapped to your own estate.
AI Text Detector FAQs
Speak to an ExpertCan AI text detectors reliably identify AI-written reports?
No, and the strongest evidence comes from the vendors themselves. When OpenAI launched its text classifier in early 2023 it published its own figures, showing the tool correctly identified twenty-six percent of AI-written text while incorrectly labeling human-written text as AI-written nine percent of the time. The classifier was discontinued in July 2023, with OpenAI stating it was no longer available because of its low rate of accuracy.
Are AI detectors biased against non-native English speakers?
Yes, substantially. Stanford researchers tested seven widely used detectors and published the results in the journal Patterns, finding an average false positive rate above sixty-one percent on essays written by non-native English speakers while essays by native-speaking American students were classified close to correctly. Detectors key on linguistic predictability, so they penalize constrained expression rather than machine authorship.
Can someone evade an AI text detector?
Easily, and the same research demonstrates it. Prompting for greater linguistic variety both removed the measured bias against non-native writers and allowed generated text to pass undetected. The practical consequence is that detectors flag writers whose English is a second language while anybody deliberately using AI evades them with one additional instruction, so the tools penalize candor and reward evasion at the same time.
What is the organization trying to find out?
Usually one of three things, and none requires authorship attribution. Whether confidential material left the organization, which is a security question answerable from records of what was sent where. Whether the work is correct, which is a review question answerable by checking claims against sources. Or whether the person did the thinking, which is a management question answerable by asking them about it.
What does AI usage monitoring show that a detector cannot?
Observed activity rather than inferred authorship. The record covers which identity reached which assistant, under which account, at what time, and what category of content went with it. An event either happened or did not, so the record carries no view about a person's writing style and cannot be biased by their vocabulary, which makes the finding defensible in a way a probability score is not.
Should a detector result be acted on?
No. The Stanford authors cautioned explicitly against using these tools in evaluative settings, and an accusation resting on a probability from a method with a documented bias is one an organization cannot defend if challenged. The more useful responses are setting an explicit disclosure expectation, reviewing work on its merits, and monitoring which assistants are used and what is sent to them.

.png)


