Pull your version history
Google Docs (File → Version history) and Word both record your draft being written over hours or days. This is the single strongest piece of evidence you have, so retrieve it before anything else.
A detector score is not proof of authorship. Here is how to respond fairly if original writing is questioned, which evidence of process to keep, and how to review a result without treating it as a verdict.
If you have been accused, the order of these steps matters. Evidence that you built the draft over time is far more persuasive than arguing about the score itself.
Google Docs (File → Version history) and Word both record your draft being written over hours or days. This is the single strongest piece of evidence you have, so retrieve it before anything else.
Find out which specific sentences read as machine-like. A single overall percentage tells you nothing useful and gives you nothing to discuss.
Offer to talk through your argument, sources, and choices. A student who wrote the work can explain why they structured it that way; that discussion is usually more convincing than any tool.
AI detectors do not establish authorship. They produce a statistical estimate from text, using methods and thresholds that differ by tool and can change over time. A score can start a conversation or prompt a closer review, but it cannot show how a passage was created.
That limitation matters when an original draft is formal, concise, translated, or heavily edited. A reviewer should consider the writing itself alongside drafts, notes, sources, version history, and the writer's explanation. False positives and false negatives are both possible.
None of these mean you did anything wrong. They are simply habits that overlap with how models write, and most are things you were probably taught to do in academic writing.
Most detectors return one number for a whole document. If you are told your essay is "78% AI", you cannot tell whether that reflects one formulaic paragraph or the entire piece, and you have no way to respond to the accusation specifically.
A sentence-level view is more useful. Penlify scores each sentence separately and colour-codes them, so you can see that—for example—your introduction and conclusion read as formulaic while the analytical middle section reads as clearly human. That gives you something concrete to point at, and shows you which habits to vary in future drafts.
To be clear about what this does not do: no tool can guarantee a particular detector outcome, and no tool can prove authorship. What a sentence-level breakdown gives you is an explanation instead of a verdict.
Keep your outline, notes, sources, and version history. Make your evidence and examples specific because they help readers assess the work on its merits. If a score is questioned, ask for a review of that process and the actual draft rather than treating a percentage as a verdict.