Learn how Turnitin's AI detection algorithm works and what triggers detection.
Universities — including KNUST — use Turnitin for both plagiarism and AI writing detection. Understanding how the detector works, rather than guessing, tells you exactly why some perfectly human essays get flagged and why some AI-heavy ones slip through. It also helps you use AI responsibly: as a tool, not a substitute for your own thinking.
This lesson is organized into 3 tiers so you only pay for the depth you need:
Turnitin's AI detection works by analyzing two key statistical properties of text: perplexity and burstiness. Understanding these concepts helps you understand why AI-generated text gets flagged.
Perplexity measures how predictable a piece of text is. AI models are trained to produce the most probable next word, which makes their output highly predictable (low perplexity). Human writing is more varied and surprising (higher perplexity).
Low perplexity (AI-like): "The results of the study indicate that the
data suggest a significant relationship between the two variables."
Higher perplexity (human-like): "We ran the numbers twice. The data
told a slightly different story the second time."Burstiness measures the variation in sentence length and structure. Humans naturally write with a mix of short and long sentences. AI tends to produce sentences of similar length (low burstiness).
Students often blur these. They are separate scores, separate rules, and separate consequences:
| Plagiarism (Similarity) | AI Writing | |
|---|---|---|
| What it checks | Copied text matched against a database | Machine-like text patterns |
| What it finds | Verbatim copying, poor paraphrasing | AI-generated rhythm |
| Score meaning | % of text matching published work | % of text likely machine-written |
| Typical response | Citation warnings, resubmission | Interview about your work |
| Defence | Proper citation practice | Draft history + knowing your material |
Turnitin gives a percentage score (0–100%) indicating how much of the text it believes was AI-generated. Most institutions set thresholds at:
Here are two paragraphs on the same idea. Only one trips the detector. Spot the difference:
PARAGRAPH A (flagged):
"Furthermore, the adoption of mobile payment systems has significantly
transformed financial transactions in developing economies. Moreover,
these systems provide enhanced accessibility for unbanked populations.
In addition, they reduce the cost of financial services. Consequently,
regulatory frameworks must evolve to accommodate this growth."
PARAGRAPH B (not flagged):
"We watched it happen on the street. A trader in Kumasi sells her
maize with a Momo code on a tin — no bank account, no card, no queue.
Mobile money didn't just change payments here; it made banking
invisible. And that, honestly, is the harder thing for regulators:
the old rules simply don't see the transaction happening."Every detector has hard limits. Knowing them keeps you realistic — about both evasion and false alarms:
Understanding the enforcement side helps you calibrate risk:
One glance at this card answers the three questions that come up most:
| Question | Answer |
|---|---|
| What does the AI % mean? | Share of text statistically likely machine-written — not a verdict |
| What raises a score? | Uniform sentence length, stock transitions, flat formality, no specifics |
| What lowers a score? | Varied rhythm, personal voice, real data, genuine citations |
| Where do I look first? | The highlighted sentences, not the headline number |
The core science: perplexity and burstiness, the 5 detection triggers, what Turnitin ignores, and how to read the 0–100% score.
Most students misread the report. The key facts to understand:
How to read a report:
1. Open the AI writing report icon on the right of the document
2. Look at highlighted sentences, not the overall % first
3. Cross-check which detector type was used (AI writing vs AI paraphrasing)
4. Note the sentence count flagged vs total sentences| Tool | Strengths | Weaknesses |
|---|---|---|
| Turnitin | Integrated with Moodle/Canvas; per-sentence highlights | False positives for non-native English; no public API |
| GPTZero | Fast, free tier, per-paragraph breakdown | Less accurate on heavily edited text |
| Copyleaks | High accuracy, detects GPT-4 and Claude | Paid; over-flags short texts |
| Originality.ai | Build for content creators; plagiarism + AI | Commercial focus, not student-oriented |
Under the hood, Turnitin runs the model over the document and produces a per-sentence likelihood. Understanding the mechanics explains a lot of "weird" results:
Interpreting a 40% score on a 10-sentence paragraph:
= 4 sentences above the machine-likelihood threshold
Find the 4 highlights → those are what a supervisor will challengeKnowing the human behind the tool removes most of the fear:
Many students are surprised to learn Turnitin checks two things at once:
Paraphrasing detection catches text that was originally human but machine-reworded, and text reworded by AI from a cited source. Rewriting the words does not reset the signal — the sentence rhythm usually survives the rewrite.
Everything in Basic + how to read the report sentence-by-sentence, the full false-positive list, a detector comparison table, and 2026 model coverage.
If you genuinely wrote the work and were flagged, use this structure when requesting a review:
Subject: Request for review of AI-detection flag — [COURSE] — [YOUR NAME]
Dear [LECTURER / DEPARTMENT HEAD],
My submission "[ASSIGNMENT]" received an AI-detection score of [X]%.
I am writing to request a manual review because I authored this work.
Evidence I can provide:
1. Google Docs / Word version history showing the document built up
over [DATES] — timestamps predate any AI session
2. My hand-written research notes and drafts ([describe])
3. Specific data/observations in the essay that only I could know
(e.g. [ONE EXAMPLE])
I understand the score is a statistical tool and welcome the
opportunity to discuss my work in person.
Regards,
[YOUR NAME] | [STUDENT ID]Pre-check your own draft before submission, then apply the writing-style fixes from our related lesson to any flagged passages.
Watch these tutorials to go deeper, and keep these resources handy for the full workflow:
Everything in Basic + Advanced + the 10-point pre-submission checklist, the full troubleshooting FAQ, and extra video resources.
Payments are processed securely by Paystack. Your card details never reach our servers.
Lesson access unlocked. Check your email for confirmation.