Skip to main content
Back to Blog

How Teachers Detect AI in Student Book Reviews and Reading Logs

George Burgess·Founder
6 min read

Detecting AI in book reviews and reading logs has become a quiet worry for English teachers, librarians and tutors running reading programmes. A review of a set text, or a weekly log reflecting on a chapter, is exactly the kind of task a student can hand to ChatGPT or Claude in seconds: name the book, ask for 300 words on the themes and characters, and a confident, tidy response appears. When a reluctant reader who barely finishes a page in class returns a polished review of a novel, you need a fair, consistent way to check before you record it or build on it in a lesson.

This guide looks at how teachers use AI likelihood scores to review reading tasks, why this genre produces so many false positives, and how to keep your own judgment at the centre of any conversation with a student.

Why Reading Tasks Are Easy to Fake

A book review draws on content a model already knows. Popular set texts - from GCSE novels to A-Level plays - have been summarised, analysed and discussed across the internet countless times, so a language model can produce a plausible reading response without the student having read a single page. A reading log is even easier: the reflective, "what I thought about this chapter" format has no facts to verify and no mark scheme pulling it in a particular direction, which is precisely the shape of writing models generate most fluently.

There is a real reason to care beyond honesty for its own sake. The point of a reading task is the reading - the student actually engaging with a text, forming a view, and finding the words for it. A review or log drafted by AI skips the only part that has any value, and it hides the very students who most need encouragement to read. Spotting that honestly is part of the job, and it starts with a clear read of what is genuinely theirs.

How AI Detection Actually Works

AI detection is probabilistic, not a verdict. GradeOrbit's detection, included on school accounts, compares a new piece of work with that student's own earlier work already on file and returns a score from 0 to 100 for how far it departs from their own writing, with a Low, Medium or High confidence label, the signals it noticed, and a plain-English explanation. It does not prove that a student used AI, and it should never be treated as an accusation on its own. A high score is a strong signal that a review is worth a proper conversation; it is not evidence of misconduct.

AI detection is unlimited and included in every school teacher seat, so running a whole class's reading logs through it costs nothing extra. It compares the submitted work against that student's own earlier writing on file, which is a stronger signal than a generic score for a genre this formulaic; a student with no earlier work on file is skipped rather than scored, and you are told. For a reading task, the score is most useful read alongside everything else you know: the student's classwork, the way they talk about the book, and what they say when you ask them about a specific moment in it. Our guide on how AI detection likelihood scores work explains the reasoning behind the number in more detail.

Where False Positives Hide

Reading tasks generate more false positives than most everyday classwork, and it is essential to understand why before you act on a score.

  • Shared vocabulary about a set text. A class taught the same themes and terminology will converge on the same phrases - "the writer uses imagery to convey", "explores the theme of" - flattening individual voice in a way that can read as machine-generated.
  • Formulaic review structures. Many schools teach a review scaffold: summary, favourite part, character, recommendation. Every student filling in the same template produces uniform, formal writing that mimics AI output.
  • EAL and very able students. A student writing in an additional language, or a strong reader who defaults to a formal, essay-like register, can score higher without any AI involvement at all.

This is exactly why a high score is a prompt to look, not a conclusion. The most reliable check you have is the student in front of you: a young person who can talk with specific, unscripted detail about a scene that stuck with them, a character they disliked, or a line they had to reread, is giving you far more than any percentage can.

Handling a High Score Fairly

When a review returns a high likelihood score, treat it as the start of a supportive conversation, not the end of an investigation. Ask the student to tell you about the book in their own words - what happened in the middle, which character changed, the bit they would skip. AI-generated reviews tend to be generic and interchangeable: accurate about the broad plot but empty of the small, personal detail that comes from actually turning the pages.

Frame it as helping them read and respond for themselves, because that is the thing the task exists to build. Keep a short, factual note of what you discussed and agreed.

Keeping Detection Data Protected

A reading log or review often carries the student's name and other identifying detail, so data protection matters. AI detection in GradeOrbit runs on school accounts, under a signed Data Processing Agreement. Because the check compares each piece with the student's own earlier writing, pupils' work is held with their real names for the school's chosen retention window. Scans are removed when a run archives (90 days by default, and the school can set anywhere from 7 to 365 days), pupil records are wiped at offboarding, and work is never used to train AI models. Individual teacher accounts don't include detection; there, work uploaded for marking is never saved and students are referred to anonymously as Student 1, Student 2, and so on.

Try GradeOrbit's AI Detection Tool

GradeOrbit gives UK schools a fair starting point for reviewing book reviews and reading logs - a 0 to 100 score showing how far a piece departs from the student's own earlier work, which you interpret with your own knowledge of the student and the text they wrote about. It is included in every school teacher seat, and it never replaces your judgment; it gives you evidence to apply it consistently and kindly.

See how AI detection works for schools and start a free school trial before your next set of reading tasks.

More on this topic

6 July 20266 min read

How Teachers Detect AI in UCAS Personal Statements

Sixth-form tutors are seeing more AI-drafted UCAS personal statements. Learn how to use likelihood scores to check drafts fairly while keeping your professional judgment in charge.

George BurgessRead guide
2 July 20266 min read

AI Detection for Criminology Coursework: A Teacher's Guide

WJEC Criminology controlled assessments ask learners to analyse and evaluate crime policy and campaigns, often after preparing away from the classroom. A fair process for reading likelihood scores and following up a high one.

George BurgessRead guide
20 June 20267 min read

How Teachers Detect AI in Online Homework Submissions

Homework set through Google Classroom and Teams is the easiest work for a student to generate with AI. A practical guide for teachers on running a fair detection check on online submissions without treating a score as a verdict.

George BurgessRead guide
19 June 20267 min read

How Teachers Spot AI in UCAS Personal Statement Drafts

Year 12 personal statement drafts land over the summer, and they are a high AI-risk piece. A practical guide for teachers on reading likelihood scores fairly and supporting students honestly.

George BurgessRead guide

Ready to save time on marking?

Join UK teachers using AI to provide better feedback in less time.