Flagged by Turnitin's AI-writing report? How to respond
Turnitin's AI-writing report estimates whether parts of a submission resemble AI-generated text. It is one signal for an instructor to weigh, not a finding that you cheated: Turnitin itself says it does not make a determination of misconduct and that its false-positive rate is not zero. If your own work was flagged, the most useful steps are to stay calm, gather evidence of your writing process, and follow your school's procedure. HumaText is not affiliated with Turnitin, cannot see Turnitin reports, and cannot predict or change a Turnitin result.
Key points
- A detector report is a signal for review, not proof of authorship
- Drafts, notes, sources, and version history document your process
- Ask what the report showed and which policy applies before responding
- Keep the submitted file exactly as submitted instead of rewriting it
- HumaText does not access, predict, or change Turnitin results
What the report is, and what it isn't
Turnitin's AI-writing detection gives instructors an indication of how much of a submission its model considers likely to be AI-generated. It is a statistical model, not a record of how a document was written. In its own guidance on false positives, Turnitin says it does not make a determination of misconduct, that its false-positive rate is not zero, and that instructors need to apply professional judgment, knowledge of their students, and the context of the assignment.
Turnitin also changes its detection over time. In August 2025 it announced that its AI-writing detection now includes what it calls AI bypasser detection, aimed at text that may have been modified by humanizer tools. Because the model is proprietary and changes, no outside tool, including HumaText, can tell you what a Turnitin report will say.
If your own work was flagged
- Don't rush to reply. Ask your instructor what the report showed and which part of the course or school policy they are concerned about.
- Preserve the submitted file. Keep it exactly as you submitted it. Rewriting it now does not change the report you already received and can make your process harder to show.
- Gather process evidence. Collect version history, outlines, notes, research sources, earlier drafts, and timestamps. In Google Docs: File, then Version history, then See version history. In Word: File, then Info, then Version History.
- Be ready to talk through your work. Explain your argument, why you chose your sources, and how the draft developed. Being able to discuss your reasoning supports your account.
- Follow your school's academic-integrity process. Read the policy, meet its deadlines, and ask an academic advisor, ombudsperson, or student advocate for help if your school has one.
- Be honest about any tool use. If you used AI or editing tools, say so and explain how, in line with the course policy.
Before you submit next time
- Turn version history on and write in one document so the trail is continuous.
- Keep your notes, outline, and sources together with the draft.
- Read your course's AI policy and disclose tool use when it is required.
- If the policy is unclear, ask your instructor before using any AI-assisted tool on submitted work.
Where HumaText fits, and where it doesn't
HumaText is an editing tool for drafts you are allowed to revise, where your course or school policy permits it. It is not a way to respond to a Turnitin report, and it does not promise or predict any Turnitin outcome. Its writing-pattern score is a local heuristic, not a prediction of Turnitin or any other detector. If you use HumaText, review every change against your source, keep your version history on, and follow your policy.
Free to try
HumaText is free to try without an account: 250 words per rolling 24 hours, more with a free account. See pricing for paid plans.
A detector report can start a conversation; your drafts, notes, sources, and ability to explain your work are the evidence. Follow your school's process, and keep version history on for everything you write.
Try the Humanizer