GPTZero flagged your writing? What to send and say

TL;DR: A GPTZero result is a score, not a ruling. Send your dated drafts and version history, ask for a person to review them instead of running the score again, and use the short reply below.

Writers: keep a record of your sessions for next time. Free at drawdog.art/download.

A GPTZero flag is a score, not a ruling. Send whoever flagged you your dated drafts and version history, then ask for a person to review that record instead of running the score again. By the end of this post you'll have a note you can paste and a list of what to attach.

Don't rewrite the piece to sound more human

This is the first instinct and the worst move. If you rewrite the text to beat the score, you create a new version with a new date, and the original timeline gets harder to show. A second flag on the rewrite looks worse than the first one on the original.

Leave the flagged file exactly as it is. Make a copy if you want to experiment.

Treat the score as one reading, because the tool says so

GPTZero's own results come with a note that they are not guaranteed to be right, according to Kanaries' explainer on the tool. The same explainer says the scoring leans on two measures, perplexity and burstiness, which in plain words means how predictable your word choices are and how much your sentence rhythm varies. Smooth, even writing scores as more machine-like, whether or not a machine wrote it.

That is why the argument "the number says AI" is weaker than it feels. Working Educators makes the same point for teachers: a detection score is one input that can start a conversation, not a verdict on its own. A Gigazine test from 2023 flagged one of three human-written texts as AI. Three texts is a tiny sample, so don't quote it as an accuracy rate. It is enough to show that a false flag happens.

That leads to the rule for the whole reply: lead with your drafts, not with statistics about the tool. Accuracy figures vary by test, and the person reading will pick the number that agrees with them. A dated draft can't be argued with the same way.

Send things in this order

Keep the whole message under 150 words so it gets read. Put the items in this order:

1. One line saying you wrote it yourself.
2. Your dated drafts, earliest first.
3. Your outline and research notes.
4. The version history from the app you wrote in.
5. An offer to write a short passage on the same topic while they watch.

Your attachment checklist

• Earliest draft, with its date visible
• Latest draft before you sent it
• Outline or notes, even if they are messy
• Version history exported or screenshotted, with dates
• Any messages where you discussed the piece with someone
• A list of every tool you used, including grammar or editing tools

The last item matters more than it looks. If you ran the text through a grammar checker, say so in the note. Leaving it out turns a small, ordinary disclosure into a credibility problem if someone finds it later.

Use this reply, word for word

Pick the version that matches who flagged you.

For a school, publisher or anyone with a formal process:

Thank you for telling me about the GPTZero result. I wrote this piece myself, and I would like it reviewed on the evidence of how it was made. I am attaching: (1) the earliest draft with its date, (2) my outline and notes, (3) the version history from [Word / Google Docs / Pages / Scrivener]. Could you tell me who reviews this, what they will look at, and by what date I will hear back? I am also willing to write a short passage on this topic while you watch.

The last question is the important one. Ask in writing for the process, the person who decides and the deadline. Then answer inside that deadline. Formal processes often have a response window, and a missed window can end the review before anyone opens your drafts.

For a client:

I understand why the report worried you. It is a score from a tool, and I can show you how this piece was written. Here are my dated drafts and notes. If it helps, I can write a 200 word section on the same topic on a call so you can see it happen. Tell me which you would prefer.

Don't offer a refund or a free redo in this message. Let them look at the record first. Offering to pay back work you did yourself signals that you doubt it.

Match the reply to who flagged you

If the flag came from	Do this first	Skip this
A school with a formal process	Ask for the process, the decider and the deadline, in writing	Arguing about the score in a hallway or by phone
A publisher or editor	Send dated drafts and ask for a human read	Rewriting the manuscript before they respond
A client	Offer a live 200 word sample and send drafts	Offering a refund or redo before they look
A platform form	Reply inside its window with the same attachments	Deleting or reorganizing your files

Name the style you wrote in

GPTZero can misfire on human writing that is naturally smooth and uniform. Working Educators lists technical documentation, formulaic or template-driven text, and content that follows a strict style guide. CASRAI adds that the best-documented weakness is a higher false-positive rate on writing by non-native English speakers, whose text tends to use more predictable vocabulary and more formulaic sentences.

So add one sentence to your note that names your situation:

• "This is a technical report written to a house style guide, which produces very even sentences."
• "English is my second language, and I would like the score weighed alongside my drafts."

Say it once, calmly. It is context for the reviewer, not an excuse.

If you wrote in Google Docs, the evidence is already there

GPTZero sells its own way to show a writing process. Its Chrome extension produces a Writing Report that includes a replay of how a Google Docs document was written, edited and pasted, along with typing analysis covering typing patterns, edits, deletions and copy-pasting, according to GPTZero's support page. It can also split credit between multiple editors as percentages.

That gives you a useful line for your reply: "My draft is in Google Docs, so the full edit history is available. If your process uses a writing replay, I am happy to share the document so you can watch how it was written."

A few rules when you do:

• Share with view access only, so the document can't change during the review.
• Tell the reviewer exactly what to open.
• State which parts, if any, were edited by someone else.
• Label large pasted sections (quotes, your own notes) and say where they came from.
• Call the replay evidence for them to weigh, not proof. It records how text was entered and edited.

A replay of a document that was pasted in from another app starts at the paste, so it can look like the text appeared all at once. If that is your situation, send the earlier drafts from the other app too.

If you wrote in Word, Pages or Scrivener, the Docs replay doesn't apply. Send the saved draft files with their dates and the app's own version history.

If you have no drafts, say so and offer a live sample

Don't invent a history. Write: "I don't have earlier drafts saved. I can write a short passage on this topic while you watch." A live sample isn't perfect evidence, but it is honest, it can be done in 15 minutes, and it shows your actual voice.

If you wrote the whole piece in one sitting with little editing, say that up front as well. A clean single pass looks different from a messy multi-day draft, and explaining it first avoids a surprise.

Four mistakes that cost you the review

• Arguing from the score alone. It turns into your word against a number.
• Deleting drafts or history after the flag. That removes the one thing that could clear you.
• Running the text through other tools until one says "human." You end up with mixed scores and nothing a reader can verify.
• Replying emotionally or late. Wait an hour, then write the calm version above.

Start the record before the next flag

A record has to exist before the accusation. If you write for clients, publishers or a school regularly, keep every dated draft, turn version history on in whatever app you use, and keep your notes in one folder.

If you want that done in the background, DrawDog is built for it. It is a menu bar or system tray app for Mac and Windows that runs while you work, and it works with writing apps including Word, Pages, Scrivener, Ulysses and Obsidian. It doesn't score your writing. It records process as it happens, and when you finish, it produces a certificate page showing time spent and the percentage of session time that involved AI tools, which the reviewer can open without an account. It never records file contents, file names, keystrokes or screen contents. A certificate gives the reviewer a record to weigh. It is not a ruling, and it can't prove someone didn't generate text elsewhere and retype it by hand.

Your next ten minutes

1. Open the flagged file and find its version history. Check that it shows dates.
2. Copy the file somewhere safe. Don't edit the original.
3. Fill in the checklist above.
4. Paste the reply that fits who flagged you, and swap in your app name.
5. Send it inside any deadline they gave you.

Keep the record from the start next time

The fix for this problem isn't a better argument after the flag. It is a record that already exists when the question comes. DrawDog's free tier gives you three certificates a month with no credit card, which is enough to try it on your next delivery. Download DrawDog and start recording the next piece.

See a sample record: drawdog.art/c/sample.