A client's AI detector flagged my human-written marketing copy. What can I send them as proof?
Send the process, not another score. A screen recording of your Google Docs version history playing from first draft to final, the brief, the call notes and the revision emails, with a one-paragraph note saying that detectors disagree with each other and that no published test has found them reliable enough to serve as evidence. That settles most of these.
Cite
Global 100 Forum, "A client's AI detector flagged my human-written marketing copy. What can I send them as proof?", https://global100.org/forum/q/a-clients-ai-detector-flagged-my-human-written-marketing-copy-what-can/, accessed 2026-11-10.Landing page copy. About 1,400 words. Wrote it myself over four days in Google Docs, off a brief and a 40-minute call with the client's product lead. Two rounds of revisions, both tracked in email.
Yesterday the marketing manager ran the final through a detector. It came back "92% likely AI". She has paused the invoice until I "prove it was written by a human".
I have tried the obvious. Ran the same copy through two other detectors. One said 12%. One said 60%. I sent her all three screenshots. Her reply: "So one of them says it is AI and one says it is mostly AI." Not the result I was going for.
I am not going to rewrite copy she already approved. I also cannot afford to lose this client over a number from a tool neither of us understands. What I need is a package I can send a non-technical marketing manager that she will accept, and that her boss will accept when she forwards it.
What have you sent in this situation that actually worked? And what did not?
Write something first.
Give people something to work with: at least 30 words on what happened and what you tried.
That is too long. Keep it under 6,000 characters.
Write the question as the title, 15 to 140 characters, no links.
Pick a category.
Add a name (2 to 40 characters, no links).
That email address does not look right.
That was quick. Read the thread, then try again.
The form expired. Reload the page and post again.
Something went wrong with the form. Reload and try again.
Please complete the check and post again.
Limit reached for now. Try again later.
This thread is closed to new replies.
This thread no longer accepts replies.
Something went wrong with the form. Reload and try again.
Post a reply or question first (name and email), then this browser can vote, edit and accept answers.
You cannot vote on your own post.
Only the author (within 30 days) or the forum team can do that.
That email already has an account. Use your sign-in link instead.
New accounts are paused for the moment. Try again later.
That was already posted.
9 answers
- Accepted answerMaya LindqvistStaffEdits the AI text detection and academic integrity sections ·
Send the process, not another score. A screen recording of your Google Docs version history playing from first draft to final, the brief, the call notes and the revision emails, with a one-paragraph note saying that detectors disagree with each other and that no published test has found them reliable enough to serve as evidence. That settles most of these.
Why version history first: it is the one artefact the client cannot read as opinion. Google's help page, "Find what's changed in a file", describes what it shows: who last updated the file and when, and a panel of earlier versions you can open one by one, with the option to name versions so they are not merged. Two practical notes from that page. Only people with edit permission can browse a document's history, so do not expect her to open it from a view-only link; record your screen instead, or share a copy with edit rights for a day. And start naming a version at the end of each working session, so the trail is legible later.
For the sentence on detectors, point her at the independent study rather than a blog post. Weber-Wulff and colleagues (2023) tested 12 public tools and two commercial systems and concluded that the available detection tools "are neither accurate nor reliable", with a bias toward calling text human and a sharp drop in performance once text is edited or paraphrased. Quote that line. It is the answer to "but the tool said 92%".
Two things to leave out. Do not send more detector screenshots; you have seen what that produced. And do not rewrite the approved copy. The false flag thread is written for students, but the shape of the response is the same: show the work, explain the instrument, ask what standard is being applied. For future contracts, a clause stating that acceptance is based on the brief and revisions, not on third-party detector output, saves this conversation entirely.
- Marco FerriMember ·
Treat it the way a photo desk treats a disputed picture: you do not argue about what the image looks like, you show where it came from. The proof is the provenance trail, not another score.
For text that means the document's own history. Google Docs keeps version history; it shows the file growing over your four days, with timestamps. Add the brief, the call notes, the two revision emails. Lay them out in date order on one page. A marketing manager understands a timeline. She does not understand a classifier, and neither does her boss.
- Tobias K.Member ·
From the other side of the table, Lena, what you describe is the evidence an integrity office accepts when a student is referred: work that visibly developed over time, consistency with the person's other writing, and the ability to discuss the choices made in it. It is also, in effect, what your client has initiated: an informal misconduct process, without a standard of proof, a right of reply, or an understanding of the instrument.
I would supply exactly what Marco lists, with one addition: a short cover note stating in two sentences what the attached material shows and what a detector score does and does not establish. Offer a fifteen-minute call in which you walk her through two or three deliberate choices in the copy and why you made them. In my experience that conversation ends most referrals faster than any document.
- Hana SatoMember ·
On why this happened, since it may help you write the cover note. Marketing copy is written to be predictable. Short declarative sentences, parallel structure, the product name repeated, a call to action in the same place every time. That is the craft. It is also a large part of what text classifiers score: how closely the next word matches what a language model would have chosen. Good copy and model output look alike on that axis, for different reasons.
The three scores you got are the tell. If the tools were measuring a property of the text, they would agree. They are each measuring their own training distribution, and your copy sits in a region where those disagree. The thread on why detectors give different scores covers the mechanics if she wants them.
- Ingrid V.Member ·
Thinking about this as a dispute rather than a technical question, because that is what it is. Your client has made a public-ish claim inside her company and now needs a way to reverse it without looking foolish to her boss. Give her that exit. A one-page PDF she can forward unchanged, with the timeline Marco describes on top, Maya's quoted sentence on detectors underneath, and your offer of a call at the bottom. Make it something she can send upward and say "I checked, here is the evidence".
If the engagement runs through a freelance marketplace, read its payment terms before anything else. On the platform I work for, a detector score alone is not grounds to withhold payment for delivered work, and the dispute team will say so in writing if asked. Yours may be similar. That letter is sometimes the whole argument.
- Dan OkaforMember ·
Teacher, not a copywriter, but the pattern is identical. When our indicator went on, the students who walked out of the meeting were the ones who could open a document and scroll back through a week of drafts. The ones who could not were the kids who wrote the whole thing in one sitting in a notes app and pasted it in. Same work, different evidence.
So whatever tool you write in, write in something that keeps history. It is a terrible reason to choose software. It is also, right now, the reason.
- Hana SatoMember ·
@Priya N. I would leave that out, and not only because it is extra work. A score that moves a lot after small edits shows the score is fragile, nothing more. It would move just as much for model output; that is the entire premise of the paraphrasing tools in the humanizer thread. So the demonstration proves nothing about who wrote it, and it hands the client a reason to distrust any future score in either direction. Fragility cuts both ways, and here it cuts against the point Lena wants to make.