234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-230
Higher education and research · United Kingdom · 2025 · In two published cases, universities penalised students for suspected AI use after AI-detection software flagged their work, without sharing the evidence beforehand or properly considering the student's own evidence

UK Ombudsman Upheld Two Student Complaints Over AI-Detection Misconduct Procedures

By Ellie Harris · Filed Complaints decided before July 2025

Alleged: Universities in England and Wales (not named by the ombudsman) developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

UK Ombudsman Upheld Two Student Complaints Over AI-Detection Misconduct Procedures

What happened

Two university students received zero marks after being accused of using AI in their coursework. Both challenged how their universities handled the accusations, and both complaints were found justified.

The cases were reported on 15 July 2025 by the Office of the Independent Adjudicator for Higher Education (OIA), which handles student complaints against universities in England and Wales.

The OIA published six cases involving AI and academic misconduct. It raised concerns about universities failing to explain why they believed students had used AI improperly and whether students had been given a fair chance to defend their work.

What an auditable version would have shown

In the first case, an autistic student was accused of including AI-generated content in an essay.

According to the OIA, the student explained that the detection software had previously flagged another essay incorrectly. The student also provided evidence showing how they had planned and prepared their work.

The university’s panel examined the essay but did not properly consider the student’s explanation or supporting evidence. It found misconduct and gave the student a zero mark, with a capped reassessment.

The OIA found the complaint justified. When the university reconsidered the case, it found no academic misconduct.

In the second case, Turnitin flagged substantial AI-generated content in an international student’s coursework. The student was called to a viva, found to have committed misconduct and given a zero mark.

It was reported that the OIA found the complaint justified because the university had not shared any of the evidence it relied on before the viva. The student had been asked to defend their work without first seeing that evidence.

Where the gap was

The OIA recommended that the universities reconsider the cases and improve their procedures. Students needed to know what offence they were accused of, why they were being investigated and what evidence was being used. They also needed an opportunity to respond and present mitigating evidence.

Of the six cases published, two complaints were justified, one partly justified, two not justified and one settled.

In the partly justified case, the OIA found that the university had not explained what evidence supported its conclusion about AI use. It had also failed to consider whether Turnitin might be less reliable for students whose first language was not English.

In one complaint found not justified, the student had not declared their use of AI or referenced the AI-generated material. In another, a student used an AI detector to claim that a marker’s feedback was AI-generated. The OIA said these tools could be unreliable and found it reasonable for the university to give more weight to the staff member’s account.

The universities were not named.

A VerificationGate is designed to check an output against a trusted reference before it is acted on, such as treating a detection score as a prompt to review the work and the student’s own evidence.

A ConductRecord keeps what evidence was used in each case, when it was shared with the student and how the student’s response was weighed.

VerificationGate and ConductRecord are Headlights designs.

What governance should have looked like

The OIA’s casework note reported concerns about how universities investigated suspected AI use, particularly when students were not shown the evidence or given a proper chance to explain their work.

The OIA expects universities to follow its recommendations fully and on time, although its decisions are not binding on students.

When software flags a student’s work as potentially AI-generated, best practice would be to share the evidence before any hearing, consider the student’s drafts and notes, and explain the reasons for the final decision.

Failure Pattern: according to the higher education ombudsman, in two published cases universities penalised students for suspected AI use after AI-detection flags, through procedures that did not share the evidence or properly weigh the student’s own.

Governance Principle: a flag from AI-detection software should be treated as a reason to look closer, with the evidence shared and the student heard, not as proof on its own.

The reference implementation of VerificationGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Universities in England and Wales (not named by the ombudsman) could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

Last reviewed October 2026. This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →