Skip to main content
Back to Blog

Handwritten AI Detector: Can AI Check Handwritten Work?

George Burgess·Founder
6 min read

Most teachers who hear the phrase "AI detection" immediately picture typed text - a paragraph pasted into a website, a score returned, a decision to be made. But the reality of UK secondary school assessment is that the vast majority of student work is handwritten. Exercise book responses, mock exam scripts, timed essays, end-of-unit assessments - none of these arrive as a neatly formatted digital document. They arrive as a pile of books or a folder of papers, and that physical reality has historically made AI detection tools almost entirely useless for the contexts where teachers spend most of their time.

GradeOrbit's school AI detection accepts handwritten work as well as typed work. This guide covers how a handwritten script is checked, how to get it into GradeOrbit, and how to read the score that comes back.

Why Handwriting Makes AI Detection Harder

Most AI detection tools analyse typed text. They compare the structure, rhythm, and vocabulary of a submission against the known patterns of AI-generated output. A photograph of a handwritten page gives them nothing to work with, which is why most AI detection tools simply do not offer a pathway for handwritten work at all.

GradeOrbit's check uses an AI model that reads the page images directly, in the same way GradeOrbit's marking does. There is no separate step where the handwriting is typed up and then analysed, so there is no transcript to check before the result appears.

Legibility still matters. The model copes with the usual range of classroom handwriting - cursive, print, and mixed styles - but a page it cannot read well gives it less to judge. Flat, well-lit scans give the most dependable result, and every result carries a Low, Medium or High confidence label, so a weak comparison is marked as one.

How to Submit Handwritten Work for Detection in GradeOrbit

On a school account, you run a check from a pupil's profile (one pupil) or on a whole class at once, and the results appear on each pupil's profile. There are two ways to get a handwritten document into GradeOrbit for AI detection.

Uploading a Scanned Image

If you have access to a scanner - or a scanning app on your phone - you can scan the student's work and upload the resulting image file directly into GradeOrbit. JPEG, PNG, WebP and PDF files are all accepted. For a whole class set, bulk upload splits the pages by the number of pages per student, and GradeOrbit reads the name on each cover page and matches it to the class list; where a match isn't clear, you pick the pupil. This is the most straightforward route for teachers who already have a scanning workflow for assessment.

Using the QR Code Camera Feature

GradeOrbit includes a QR code feature that lets you use your mobile phone as a camera without needing a separate scanning app. On the upload step, GradeOrbit shows a QR code that links your phone's browser to your desktop session. You then use your phone to photograph the handwritten pages, and the images are sent directly to your GradeOrbit session on the desktop. This is a practical option for teachers who do not have access to a scanner but want to photograph physical work quickly.

How GradeOrbit Handles Student Data on School and Individual Accounts

A common concern when submitting student work to any AI tool is data privacy, and how GradeOrbit handles data depends on which account type you use. Because teacher AI detection compares a new script against a pupil's earlier writing on file, it runs on GradeOrbit school accounts under a signed Data Processing Agreement (DPA): pupils' work is held under that agreement with their real names, so each check can compare against their earlier work on file. Uploaded scans are removed when a run archives (after 90 days by default, and the school can set anything from 7 to 365 days), pupil records follow your school's retention window, and everything is wiped at offboarding.

That is why teacher AI detection is only available on school accounts. An individual teacher account, where no school DPA is in place, offers marking only: you redact identifying information - typically a student's name written at the top of the page - client-side in your browser before marking runs, and on those accounts the uploaded student work is not kept (it is analysed and then discarded). Across all tiers, student work is never used to train AI models.

Understanding the Likelihood Score for Handwritten Work

GradeOrbit returns a score between 0% and 100% with a confidence label. The score measures how far the new script departs from the pupil's own earlier writing: a low score reads as consistent with their own writing, and a higher score means it differs from it in ways worth a closer look.

There is an important nuance for handwritten submissions specifically: the act of handwriting something does not make it less likely to trigger a high AI detection score if the original composition was AI-generated. Students who generate text using ChatGPT or Claude and then copy it out by hand are still submitting AI-generated content, and that content will still carry the linguistic patterns that detection tools look for. Handwriting is not a bypass.

Conversely, a student who writes fluently - with clear structure, confident vocabulary, and well-organised argument - may also produce text that scores higher than their peers, simply because well-crafted human writing shares some characteristics with AI output. This is why the likelihood score is best treated as one input to your professional judgement, not a standalone verdict. Our guide on how to interpret AI detection scores covers this in detail and offers a practical framework for what to do when a score is high.

How School Detection Checks Are Included

On a GradeOrbit school account, unlimited AI detection is included in every teacher seat - handwritten or typed - with no per-check charge and no settings to choose between. The check works by comparing the new script against that same pupil's own earlier work already on file, which is a more useful signal for handwritten coursework than a generic "does this read like AI" score would be. A pupil with no earlier work on file is skipped rather than given a generic score.

That baseline comparison suits handwritten work particularly well: judging the script against the pupil's established voice - rather than an abstract standard of "AI-sounding" prose - gives you a steadier signal to work from, whatever the stakes of the piece.

What AI Detection Cannot Tell You About Handwritten Work

It is worth being explicit about what the detection workflow cannot do, even when it works well. A high likelihood score on a piece of handwritten work does not prove that the student used AI. It tells you that the writing differs from the pupil's earlier work in ways that are consistent with AI-generated text. That resemblance might reflect AI use. It might also reflect a highly proficient student, a student who drafted digitally and wrote by hand, or a student who received substantial editing support that changed the register of their writing.

A low likelihood score does not prove the work is authentic either. A student who heavily edits AI-generated text - restructuring sentences, adding personal voice, inserting subject-specific examples - can produce output that scores much lower than the original AI draft.

Detection is most useful as a flag that prompts further investigation, not as a mechanism that makes decisions. The most productive follow-up to a high score is a direct conversation with the student: ask them to talk through their argument, explain their evidence, or write a short response to the same question in class. A student who wrote the work genuinely will be able to engage with it. A student who submitted AI-generated content will often struggle to defend it in their own words.

Putting It Together

For handwritten work, the order matters: get a clean scan, note the confidence label, then read the score against the pupil's own earlier writing and your knowledge of them. In GradeOrbit for Schools, detection sits in the same school dashboard used for marking, and accepts scanned essays, phone photographs of paper scripts and typed work exported to PDF.

More on this topic

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
13 June 20267 min read

How Teachers Detect AI in A-Level History Coursework

A-Level History coursework is one of the highest AI-risk pieces a student submits. A practical guide for teachers on reading likelihood scores, fair process, and moderation.

George BurgessRead guide
9 June 20267 min read

How Teachers Detect AI in GCSE PE Written Papers

GCSE PE written components are an overlooked AI detection risk. A guide for teachers on reading likelihood scores, fair process, and aligning with school policy.

George BurgessRead guide

Ready to save time on marking?

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