Flagged, but you wrote it yourself: preparing a response

For students in England and Wales, the Office of the Independent Adjudicator's July 2025 casework note states the principle directly: the responsibility is on the provider to prove what it alleges, not on the student to disprove it. The OIA also says providers should identify what part of the work caused suspicion and consider a range of evidence.

Turnitin's current guide approaches the tool from the same direction: its model can misidentify human and AI text and should not be the sole basis for adverse action. The report is an input. Whether a rule was breached must be decided by people applying the institution's policy to all the evidence.

The OIA principle applies to providers in its scheme. Elsewhere, read the academic-misconduct procedure before assuming the same burden, standard of proof or appeal route.

Even where the formal burden sits with the institution, process evidence is still worth providing. It does not transfer the burden to you; it gives the decision-maker concrete material that can test the allegation. Your first task is therefore procedural: obtain the allegation, evidence, policy, deadline and available support before drafting a long defence.

• Identify the exact alleged breach. "AI detected" is not a rule; the notice should point to the provision said to have been broken.
• Identify the decision standard. The policy may use balance of probabilities or another standard, and may distinguish investigation from a final finding.
• Identify the response route. A fact-finding meeting, viva, panel and appeal are different stages with different purposes and deadlines.
• Get support early. A students' union adviser, programme representative or accessibility service can help you understand the process and request adjustments.

The OIA has both upheld and rejected complaints in this area. That mixed record is more useful than a collection of success stories because it shows what fair decision-making looks like on both outcomes.

• Reasons and evidence must be specific. The OIA criticised decisions that did not explain what evidence led to the conclusion or why a particular penalty followed.
• Students must see and answer the case. In one justified complaint, relevant comparison evidence had not been shared and the panel had not properly considered the student's planning and preparation.
• A viva must test the right question fairly. Another justified complaint involved a delayed viva that tested subject knowledge but did not let the student explain how the assignment was produced.
• A fair process can still uphold misconduct. In a complaint the OIA found not justified, the provider considered the student's admission, notes and responses and applied a policy that clearly required disclosure.

The OIA note also tells providers to consider whether assumptions about AI use may be biased by writing style, disability, communication differences or English not being the student's first language. The published detector-bias study can support that context, but it does not automatically decide an individual case. The stronger argument joins the research to your actual report, writing history and the institution's duty to weigh relevant evidence.

A successful challenge is not "the detector is imperfect, therefore I win." It is "the decision must consider the detector's limits, the complete evidence and the required procedure."

Every piece of guidance converges here. Gather the record of how the document came to exist.

• Version history. Google Docs shows it under File → Version history → See version history. A normal DOCX or PDF download does not include that history, so preserve access and capture the relevant dated states in the manner your institution accepts. Word version history is available for files stored in OneDrive or SharePoint under File → Info → Version History.
• Drafts and outlines as separate files, with their original timestamps. Do not tidy the folder.
• Reading notes, annotated PDFs, citation-library records and database search records. These connect the submitted claims to sources you actually consulted.
• Feedback and communication that predates submission - supervisor comments, a peer's notes on a partial draft, or an email discussing a specific section.
• Your explanation of the work. Be ready to describe why the question was framed that way, how key sources were selected, what changed between drafts and what any permitted tool did.

Preserve what already exists. Do not alter timestamps, manufacture drafts or edit the submitted file; doubtful metadata can damage otherwise credible evidence.

No single artefact is perfect. A version history can show gradual composition without proving every source was used correctly; notes can be genuine but incomplete; prior writing can differ because the task, deadline or language support differed. Present the set as a coherent timeline rather than claiming one screenshot conclusively proves authorship.

Make a working copy for annotations and leave originals untouched. List each item with its date and what it demonstrates: outline establishes the planned structure; annotated paper supports a particular paragraph; supervisor feedback explains a later revision. That index helps a reviewer follow the evidence without searching an unlabelled folder.

You are entitled to understand the case. Three requests are reasonable and specific.

• The allegation and all evidence relied on. Ask for the full report, the passages at issue, comparison work, staff analysis and any other material the decision-maker will see.
• Which detector, which version, and when it was run. Vendors change models; Turnitin's reporting rules changed in July 2024, and numerical scores from 1% to 19% are now hidden. An older report is not necessarily equivalent to one generated today.
• What the institutional policy says the result means. Ask which AI uses were prohibited or required disclosure, what standard applies and whether a flag merely triggers review.
• How and when you may respond. Confirm the deadline, meeting format, right to submit documents, right to representation, appeal route and available disability or language adjustments.

If evidence is withheld for confidentiality or another stated reason, ask for enough detail to answer it fairly and for the policy authorising the restriction. Keep requests neutral and in writing. The goal is a complete record, not an argument by email before you know the case.

Keep it factual and short. Three things, in this order: what you are providing as provenance; what you are asking the panel to consider about the detector’s reliability; and a request that the decision state the specific evidence it rests on beyond the score.

• Open with the position. State plainly that you wrote the work and identify any permitted tools you did use; do not leave a legitimate grammar checker to emerge as a surprise.
• Give a dated account. Summarise research, outline, drafts, feedback and revision, with references to the attached evidence.
• Answer each flagged passage. Explain sources, conventional wording or revision history where relevant instead of making only a general denial.
• Address reliability narrowly. Cite the vendor warning and any population-specific concern that applies; avoid claiming all detection is worthless.
• Request a reasoned outcome. Ask the decision to identify the policy, evidence, standard and response to your key submissions.

Do not rewrite the essay to lower a number, and do not run it through a second detector hoping for a better verdict. Detectors disagree with each other constantly - in the Stanford corpus, 89 of 91 essays were flagged by at least one detector and only 18 by all seven - so a clean second opinion proves nothing and a second flag hands the panel another number.

Before submitting, remove speculation and accusations about staff motive. Check that every attachment mentioned is included, every date is accurate and any sensitive third-party information is redacted only in a way the procedure permits. Keep a copy of exactly what you send and proof of the deadline being met.

Prepare for a viva as an explanation of your own decisions, not a memory contest. Revisit the submitted version, assignment question, core sources and key analytical choices. Practise explaining why a paragraph exists, how a table was produced and what changed after feedback. If a long delay, disability, language needs or acute circumstances affect recall or communication, request reasonable adjustments early and link the request to the institution's procedure.

Be equally precise about permitted technology. Grammar checkers, translation tools, reference managers and coding assistants may be treated differently by the assignment. Name the tool, feature and purpose; preserve any settings or logs already available; and do not relabel a substantive rewrite as spelling correction. Candour about an allowed use makes the boundary around the disputed use clearer.

This page is general information, not legal advice. Procedures, privacy rules and appeal rights differ by country and institution. The OIA sources are directly relevant to providers in England and Wales; elsewhere they are useful examples of fair process, not binding rules.