BTEC AI Detection: How Assessors Check Coursework Fairly

BTEC coursework is one of the most exposed assessment formats when it comes to AI-generated writing. Long-form learning aims, reflective accounts, business proposals, and applied scenarios are exactly the kind of tasks that ChatGPT and Claude handle well. At Level 2 or Level 3, an assessor has to plan for some learners using these tools and decide how to assess fairly when they do.

Why BTEC Coursework Is Different from GCSE Essays

GCSE English essays sit inside a controlled question framework. BTEC tasks are different. A Level 3 Business unit might ask a learner to write a 1,500-word strategic recommendation. A Health and Social Care assignment might require a reflective account of a placement. An IT unit might want a written rationale for a database design. The marking criteria reward applied knowledge and structured writing - both of which a large language model can produce quickly.

That is what makes a suspicious BTEC submission hard to call. The writing can be fluent, the structure can hit every pass criterion, and the tone can stay consistent across thousands of words - and still the learner may struggle to explain a single sentence when you ask them about it.

The Vocational Portfolio Problem

Portfolio-based assessment makes detection harder for a second reason: portfolios are submitted in chunks over weeks or months. A learner might write some sections themselves and use AI for others. By the time the portfolio reaches you for final assessment, you are looking at a mix of human and machine writing, and the join is not always visible to the eye.

How Likelihood Scores Actually Work

Modern AI detection does not give you a yes/no answer. It gives you a likelihood score: an indicator of how far a piece of work sits from what you would expect, never proof. GradeOrbit's detection, on school accounts, returns a score from 0 to 100 that measures how far the new work departs from that learner's own earlier writing on file: a low score means it is consistent with their own writing, a high score means it differs from it in ways worth a closer look.

That probabilistic framing matters. A score of 87 does not prove a learner cheated. It tells you the writing - sentence rhythm, vocabulary, predictability of word choices - departs sharply from what this learner has produced before, in ways consistent with AI assistance. You then bring your knowledge of the learner, their previous work, and the assessment context to interpret what the score means.

Baseline-Aware Detection on School Accounts

On a GradeOrbit school account, unlimited AI detection is included in every teacher seat, with no per-check charge. Instead of a generic "does this read like AI" score, GradeOrbit compares the submitted work against that learner's own earlier work already marked in GradeOrbit, and each result comes with a Low, Medium or High confidence label, the signals it noticed and a plain-English reasoning paragraph. A learner with no earlier work on file is skipped, and you are told, rather than given a generic score. Individual teacher accounts do not include AI detection.

For BTEC, a sensible pattern is still to run detection across every learner's submission at the unit deadline, and then give the small number of pieces that flag highest the closer look - checking against the learner's track record, having the conversation, and applying your professional judgment.

What to Do When BTEC Work Scores High

A high likelihood score is the start of a conversation, not the end of it. Once a learner's work scores above your school's threshold, do not file an academic malpractice form before doing three things.

First, look at the learner's track record. Does this writing match the style and quality of work they have produced in class? BTEC assessors usually have months of evidence - written drafts, witness statements, observation notes - to compare against. A high detection score on work that is wildly out of line with everything else they have produced is much more concerning than a high score on work that matches their usual standard.

Second, talk to the learner. Ask them to explain a specific paragraph in their own words. Ask why they chose a particular case study or recommendation. A learner who wrote the work can usually explain their choices, even clumsily. Learners who have leaned heavily on AI often cannot - and that conversation, recorded in your assessor notes, is often more useful evidence than the score itself.

Third, apply your professional judgment. You are the assessor. The detection score is one data point. Your knowledge of the learner, the assignment brief, and the standards of the qualification matter more than any single number.

Building a Department Policy Around Likelihood Scores

If you lead BTEC delivery in your school or college, agree a shared threshold with your team before the next coursework deadline. Some departments use a score of 70 as the trigger for a verifier conversation; others use 85. The exact number matters less than the consistency - every learner is treated the same way, and every flagged piece goes through the same evidence-gathering process.

Document the policy. Tell learners at the start of the unit that AI detection is part of how you check submitted work. Learners who know the rules up front are less likely to stumble into a breach, and a policy announced in advance is easier to defend than one applied after the fact.

How GradeOrbit Handles Student Data

Because AI detection runs on a school account covered by a signed Data Processing Agreement (DPA), learners' work is held under that agreement with their real names, so each check can compare against that learner's 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), learner records follow your school's retention window, and everything is wiped at offboarding. Individual teacher accounts do not include detection; they cover marking, where uploaded student work is redacted client-side, never stored, and learners are referred to only as "Student 1", "Student 2", and so on. Across every tier, student work is never used to train AI models.

Before the Next Unit Deadline

Before submissions come in, settle three things: the score at which you look more closely, how learners are told their work will be checked, and who holds the follow-up conversations. If you use detection on GradeOrbit for Schools, it compares each submission with that learner's own earlier work, with checks included in every school teacher seat, and you can start with a free school trial.