Draft history is decisive
Google Docs version history and Word track-changes both timestamp every revision. This is the single highest-leverage piece of evidence in any false-flag conversation.
For students · Appeals
AI detectors make mistakes. If you wrote the essay yourself and your teacher or school has flagged it, this is the evidence to collect and the conversation to have.
AI detectors are not courts. They produce a probability score, and the score is sometimes wrong, especially on careful academic writing, non-native English, autistic writing, and heavily revised prose. If you wrote your essay yourself and it has been flagged, you have a problem to solve, but you are not in trouble yet.
The key thing to hold onto: a detector flag is a signal, not a verdict. Every reasonable academic-integrity process, including the ones we recommend teachers adopt on /for-teachers/ai-policy-templates, treats the flag as the start of a conversation, not the end.
If a teacher flagged you using aiessaydetector.ai, the same principles apply. We publish the false-positive rate of our detector on /transparency, it is not zero. A score is a signal; the evidence is your draft history.
Google Docs version history and Word track-changes both timestamp every revision. This is the single highest-leverage piece of evidence in any false-flag conversation.
Every reasonable academic-integrity process treats a detector score as one signal alongside draft history, writing baseline, and a short oral check-in.
Most schools have a formal escalation path beyond the teacher. Ask what it is in writing, most false flags resolve in the teacher conversation, but knowing the next step keeps you grounded.
Read /methodology so you understand what the detector actually measured.
Read /methodology