Manuel B. Garcia

Manuel B. Garcia serves as the Senior Director for Educational Technology and Digital Learning at FEU Institute of Technology, Manila, Philippines. Read More

Contact Info

1607, FEU Tech Building,
P. Paredes St, Sampaloc,
Manila, Philippines
mbgarcia@feutech.edu.ph

Follow Me

Why Should Researchers Never Treat an AI-Detection Score as Proof?

An AI-detection percentage may look precise, but it cannot establish who wrote an academic manuscript. Understand the statistical and evidentiary limitations of detector scores and why researchers should distinguish automated predictions from proof.

560
Why AI-Detection Scores Are Not Proof Guide 560 of 1196
01 · The Question

What Does an AI-Detection Score Actually Prove?

A researcher submits a manuscript to an AI-text detector and receives a score of 87%. The report highlights several passages and indicates that the writing resembles AI-generated text.

Does 87% mean there is an 87% probability that the researcher used AI? Does it mean that 87% of the manuscript was generated by a language model? More importantly, could the score justify an allegation of academic misconduct?

These interpretations are tempting because numerical results often appear more objective than subjective judgments about writing style. Yet the apparent precision of a percentage can conceal considerable uncertainty about what was measured and how the result should be interpreted.

For researchers, editors, and institutions, the essential question is whether a statistical classification can establish the historical fact of who produced a manuscript.

02 · The Short Answer

An AI-Detection Score Is a Prediction, Not Proof of Authorship

In Brief

Researchers should never treat an AI-detection score as proof that academic writing was generated by AI because the score represents a tool-specific classification or estimate, not direct verification of the writing process. AI detectors can incorrectly flag human-written text and fail to identify genuinely AI-generated material.

The meaning of a reported percentage varies among systems, and its evidentiary value depends on validation, error rates, and the circumstances of use. A misconduct finding additionally requires evidence of a specific policy violation and compliance with applicable investigative procedures.

A score may provide information about how a detector classified a passage. It cannot, by itself, establish what a researcher actually did while preparing the manuscript.

03 · What You Need to Know

Why AI-Detection Percentages Cannot Establish Academic Authorship

What Does an AI-Detection Percentage Represent?

There is no universal definition of an AI-detection percentage.

Different systems may report a classification confidence score, an estimate of the proportion of text identified as AI-generated, or a proprietary indicator derived from statistical features.

These quantities are not interchangeable.

For example, Turnitin describes its AI writing percentage as the proportion of qualifying text in a submission that its model identifies as likely AI-generated or AI-generated and subsequently paraphrased, according to the product's applicable reporting categories.

That percentage is not presented as the probability that the author used AI. Nor is it a direct measurement of how much writing was actually produced by a language model.

Other detectors may use different definitions. Researchers must therefore consult the specific provider's documentation rather than assuming that all displayed percentages have the same meaning.

Why Is a Classification Score Different From a Probability of Authorship?

A detector may calculate a score indicating how strongly a passage resembles examples of AI-generated writing.

That score does not necessarily represent a calibrated probability that the passage was actually generated by AI.

Calibration concerns whether predictions assigned a particular probability correspond to observed frequencies in an appropriately defined population.

For example, if a well-calibrated system assigns a 70% probability to many comparable cases, approximately 70% of those cases should belong to the predicted category over repeated evaluation.

However, even a calibrated probability would not constitute certainty about an individual manuscript. It would remain conditional on the model, reference population, and available information.

A proprietary score labeled 70% may not even have that probabilistic interpretation.

Detector score A numerical output generated according to a particular system's classification and reporting procedures.
Probability of actual AI use A probabilistic claim about whether AI was involved in producing the text, requiring appropriate statistical justification and contextual information.

Confusing these quantities is one of the most consequential mistakes in interpreting AI-detection reports.

Why Can a High Score Still Be Wrong?

Most general-purpose detectors analyze characteristics of the finished text rather than observing its creation.

Human-written academic prose can contain predictable terminology, standardized methodological descriptions, and conventional sentence structures that resemble generated writing.

Consequently, a detector may assign a high AI-likelihood classification to text that was written entirely by a human.

Published evaluations have documented this problem. Weber-Wulff and colleagues examined 14 AI-text detection tools and reported important limitations in their accuracy and reliability.

Liang and colleagues demonstrated substantial false-positive disparities in a particular evaluation of essays written by non-native English speakers.

These findings support the existence of classification errors without establishing the current error rate of every commercial system.

The possibility of false-positive AI classifications means that a high score cannot independently establish machine generation.

Why Can a Low Score Also Be Misleading?

A detector may fail to identify text that was genuinely generated by AI.

Such a result is a false negative when the evaluation defines the text as AI-generated but the system classifies it as human-written.

Research has demonstrated that paraphrasing and other text transformations can reduce detection effectiveness under particular conditions.

Moreover, a detector may perform differently when evaluating text from a language model that was not adequately represented in its training or validation data.

A low score therefore cannot establish that a manuscript was written without AI assistance.

This is why passing an AI detector does not prove human authorship.

Why Do False-Positive Rates Matter More Than a Headline Accuracy Claim?

Overall accuracy measures the proportion of correct classifications across an evaluation dataset.

However, accuracy alone does not reveal how frequently human-written material is incorrectly flagged or how often AI-generated text escapes detection.

A detector might perform well on a balanced benchmark while producing numerous incorrect positive classifications in a population where AI-generated writing is relatively uncommon.

The false-positive rate is especially important when a positive result may trigger an allegation against a researcher.

Yet even a low false-positive rate does not establish that an individual flagged manuscript is AI-generated.

To interpret a positive result, the prevalence of AI-generated material in the relevant population must also be considered.

How Does the Base-Rate Problem Affect AI-Detection Scores?

The base-rate problem arises when people interpret a positive test result without considering how common the condition being tested actually is.

In AI detection, the relevant prevalence is the proportion of texts that genuinely belong to the AI-generated category under the evaluation's definition.

Consider a hypothetical detector with 90% sensitivity and 95% specificity.

If only 5% of manuscripts in a population are genuinely AI-generated, the detector will correctly flag many generated manuscripts but may also incorrectly flag a substantial number of human-written ones.

Positive Predictive Value
PPV = (Sensitivity × Prevalence) / [(Sensitivity × Prevalence) + (False-positive rate × (1 − Prevalence))]
Sensitivity is the proportion of genuinely AI-generated texts correctly identified. Prevalence is the proportion of AI-generated texts in the population. The false-positive rate is the proportion of human-written texts incorrectly flagged.
Using sensitivity of 90%, specificity of 95%, and prevalence of 5%: PPV = (0.90 × 0.05) / [(0.90 × 0.05) + (0.05 × 0.95)] = 0.045 / 0.0925 ≈ 48.6%. In this hypothetical population, fewer than half of the flagged manuscripts would actually be AI-generated.

The calculation demonstrates that a detector can have seemingly strong sensitivity and specificity while producing a positive result that is correct less than half the time in a particular population.

These figures are illustrative, not estimates of any commercial detector's performance.

The result also does not mean that every manuscript assigned a high proprietary detection percentage has a 48.6% probability of being AI-generated. Positive predictive value concerns a defined group of positive classifications under specified conditions.

Why Does the Writing Population Affect Interpretation?

Detector performance may vary across academic disciplines, writing styles, text lengths, and linguistic backgrounds.

Liang and colleagues found that seven evaluated GPT detectors disproportionately misclassified a collection of essays written by non-native English speakers.

Their findings demonstrate that overall performance statistics may conceal unequal error rates across populations.

For research institutions, this raises questions about whether a detector validated on one type of writing can be applied fairly to manuscripts produced under different conditions.

It also highlights the need to examine language-related differences in AI-detection errors before using scores in consequential decisions.

Why Does Agreement Among Multiple Detectors Not Establish Proof?

Several detectors may classify the same manuscript as AI-generated. Their agreement may appear persuasive, but it does not automatically provide independent confirmation.

Detectors may share training data, statistical features, model architectures, or assumptions about generated writing.

If their errors are correlated, agreement may reflect a common limitation rather than independent evidence of authorship.

Combining detector results requires evidence that the combination improves performance under relevant conditions.

Simply counting how many systems flag a passage does not establish that the classification is correct.

Why Is a Score Insufficient to Establish Research Misconduct?

Even if AI assistance were independently confirmed, investigators would still need to determine whether the assistance violated an applicable rule.

Policies differ across universities, journals, publishers, and research activities.

Some forms of AI-assisted language editing may be permitted, while substantive drafting or analysis may require disclosure or be subject to restrictions.

A detector cannot independently establish which tools were used, whether the researcher disclosed them, or whether the relevant policy was violated.

Formal research misconduct also has specific definitions in some jurisdictions. For example, US Public Health Service regulations address fabrication, falsification, and plagiarism, rather than treating every undisclosed use of AI as research misconduct.

Therefore, a detection score cannot substitute for identifying the alleged conduct, establishing the relevant facts, and applying the governing policy.

What Evidence Is More Directly Relevant Than a Detection Score?

Evidence about the actual development of a manuscript may be more informative than a statistical classification.

Depending on the allegation, relevant records may include dated drafts, revision histories, research notes, authenticated AI interactions, and correspondence concerning manuscript preparation.

Such evidence is not automatically conclusive. Its authenticity, completeness, and relevance must be evaluated.

For example, a saved AI conversation may establish that a researcher requested generated text without proving that the output was incorporated into the manuscript.

Conversely, a document history may demonstrate extensive human revision without proving that no AI-generated material was used earlier.

The evaluation of documentary evidence of suspected undisclosed AI use should focus on what each record can genuinely establish.

04 · A Practical Example

Why an 85% AI-Detection Score Is Not an 85% Probability of Misconduct

Hypothetical Example

A Manuscript Receives a High AI Score

A journal editor receives a manuscript whose introduction is assigned an 85% AI-detection score by a commercial tool.

The editor initially interprets the result as meaning there is an 85% probability that the author used AI to write the introduction.

However, the detector's documentation defines the percentage as an estimate of the proportion of qualifying text classified as likely AI-generated, not as a probability of actual AI use.

Interpret the score correctly. The reported percentage concerns the detector's classification of qualifying text, not a verified probability of authorship.
Consider classification uncertainty. The detector may produce false positives, and its performance may vary across academic writing populations.
Identify the actual concern. The editor determines whether the issue involves prohibited drafting, missing disclosure, or another specific policy requirement.
Examine relevant evidence. If a justified concern remains, the editor requests clarification and considers appropriate manuscript records.
Reach an editorial decision. The editor evaluates the available evidence and applicable policy rather than treating the score as a finding.

In this scenario, the 85% score cannot establish an 85% probability of AI use, much less an 85% probability of misconduct.

It is a numerical representation of the detector's assessment under its own reporting rules.

The distinction illustrates why statistical terminology must be interpreted according to its actual definition rather than the apparent precision of the number.

05 · What Researchers Often Get Wrong

Misconceptions About AI-Detection Percentages and Proof

Misconception

An 80% AI Score Means an 80% Probability That AI Wrote the Text

Not necessarily. Many systems report proprietary scores or estimated proportions of qualifying text rather than calibrated probabilities of authorship. The provider's score definition must be consulted.

Misconception

A High Score Is Strong Evidence Because It Is Numerical

Numerical precision does not establish scientific validity. A score's evidentiary value depends on what it measures, how reliably it measures it, and whether it is relevant to the question being investigated.

Misconception

A Detector With High Accuracy Cannot Make Serious Individual Errors

Overall accuracy can conceal false positives, false negatives, and subgroup disparities. Even a detector with favorable benchmark results can misclassify individual manuscripts.

Misconception

Several High AI Scores Are Equivalent to Independent Proof

Different detectors may share systematic limitations. Agreement does not guarantee independence or establish the actual writing history.

Misconception

A Zero-Percent Score Proves That No AI Was Used

A low or zero score is a negative classification under the tool's method. It cannot independently verify the absence of AI assistance.

Misconception

A High Score Automatically Establishes a Disclosure Violation

A detector does not determine what assistance occurred or whether disclosure was required. A policy violation must be established through relevant evidence and the applicable rules.

06 · What This Means for You

How Should Researchers, Editors, and Institutions Interpret AI-Detection Scores?

The most important practical step is to separate the detector's numerical output from the conclusion someone wants to draw from it.

A Practical Interpretation Framework

If your own manuscript receives a high AI score
Do not assume the classification establishes AI use. Review the tool's limitations and preserve relevant evidence of your writing process.
If your manuscript receives a low or zero score
Do not treat the result as certification of human authorship or exemption from applicable AI-disclosure requirements.
If you are an editor considering a detection report
Verify what the score represents and whether credible independent concerns justify further examination.
If you are an institutional investigator
Identify the alleged policy violation, assess relevant evidence, and follow the governing burden and standard of proof.

For researchers, accurate documentation and transparent disclosure are more useful than repeatedly testing manuscripts until they obtain a preferred score.

For institutions, fair procedures for AI-related investigations should ensure that numerical classifications are not mistaken for findings of fact.

Watch Out

Do not describe a detector's reported percentage as the probability of misconduct unless that interpretation is explicitly supported by appropriate validation. A score can look mathematically precise while remaining evidentially uncertain.

The defensible question is not how impressive the score appears, but whether the available evidence can support the specific conclusion being considered.

07 · A Quick Checklist

What to Verify Before Treating an AI-Detection Score as Evidence

Before interpreting a detector percentage, check:
Read the provider's definition of the reported score or percentage.
Determine whether the output is a classification, estimated text proportion, or calibrated probability.
Examine independent validation evidence for comparable academic writing.
Review false-positive and false-negative rates rather than relying only on overall accuracy.
Consider whether the prevalence of AI-generated writing affects the interpretation of positive results.
Account for relevant language, discipline, editing, and text-length limitations.
Identify the specific claim the detector report is being used to support.
Seek appropriate documentary evidence before drawing conclusions about authorship or policy compliance.
Avoid describing an automated score as proof of AI use or misconduct.
08 · Frequently Asked Questions

Frequently Asked Questions About AI-Detection Scores

Does an 80% AI-detection score mean 80% of a research paper was written by AI?

Not necessarily. Some systems report an estimated proportion of qualifying text classified as AI-generated, while others use different scoring methods. Neither interpretation independently establishes the actual proportion written by AI.

Is a 100% AI-detection score proof that a manuscript was generated by AI?

No. A maximum score remains an output of the detector's classification procedure. False positives and other limitations mean that even an extreme result should not be treated as conclusive evidence of authorship.

Does a zero-percent AI score prove that the manuscript is human-written?

No. A negative result does not establish that AI assistance was absent. AI-generated material can escape detection, and scoring conventions vary among tools.

Why do different AI detectors give different percentages for the same text?

Detectors may use different models, training datasets, linguistic features, thresholds, and score definitions. Their numerical outputs are not necessarily directly comparable.

Can a Turnitin AI percentage be used as proof of academic misconduct?

No. Turnitin cautions that its AI writing detection results should not be used as the sole basis for adverse action. A misconduct finding requires appropriate evidence and application of the institution's governing procedures.

Is a high AI-detection score statistically significant evidence?

A high proprietary score is not automatically a statistical significance test or a calibrated probability. Its meaning depends on the system's design and validation. Statistical terminology should not be inferred from the numerical format alone.

Can several matching AI-detection scores establish authorship?

Agreement may provide additional information, but detectors can have correlated errors. Multiple matching classifications do not independently establish how the manuscript was written.

What should investigators rely on instead of AI-detection percentages?

Investigators should consider authentic manuscript drafts, revision histories, relevant AI interactions, research records, and explanations connected to the specific allegation. Evidence must be evaluated under the applicable policy and procedural standards.

09 · The Bottom Line

A Numerical Prediction Cannot Substitute for Evidence of Authorship

The Bottom Line

Researchers should never treat an AI-detection score as proof because it is a tool-specific statistical classification, not direct evidence of who wrote a manuscript or whether an academic policy was violated.

High scores can be incorrect, low scores can miss AI-generated material, and numerical percentages may not represent probabilities of authorship. Consequential decisions require relevant corroborating evidence, accurate interpretation of the tool, and fair procedures.

10 · Sources and Further Reading

Research and Official Guidance on Interpreting AI-Detection Scores

11 · Cite this Guide

How to Cite This Guide

This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.

Has the Field Guide helped your research?

If a guide helped clarify a question, inform a research decision, or move your work forward, I would love to hear about your experience. Your story may also help other researchers discover the Field Guide.

Share Your Experience
Takes only a few minutes