
My Client Said It Was a 'Rough Draft.' Here's How I Figured Out It Was ChatGPT.
Try WriteMask free
500 words/day. No credit card required. Paste AI text and see the difference.
Sara had been freelance editing for six years. She knew bad writing. She knew good writing. She thought she knew the difference between a rough first draft and a polished piece. Then a client sent her something that felt off.
The assignment was simple: take a "rough draft" on supply chain logistics and clean it up for publication. The client — a B2B consultant — said he'd been working on it for weeks. Sara opened the document and started reading.
Something was wrong immediately. She just couldn't name it yet.
What Tipped Her Off First
The writing wasn't bad. That was the strange part. Usually rough drafts are rough. This one was grammatically flawless, structured perfectly, and completely hollow. Every paragraph made sense. None of them said anything she could actually remember five seconds after reading it.
She started noticing specific patterns:
- Uniform sentence rhythm. Every paragraph had the same pacing — medium-length sentence, medium-length sentence, slightly shorter wrap-up. No long run-ons. No punchy one-liners. No variation.
- Zero personal voice. The client supposedly had 20 years in logistics. The draft had no personal opinions, no specific war stories, no "in my experience." Just general truths, stated smoothly.
- Suspiciously broad examples. When the draft used examples, they were things like "a major retailer" or "a global manufacturer." Nothing named. Nothing real.
- Hedging phrases everywhere. "It is worth noting," "it's important to consider," "in many cases." These fillers appeared constantly — a hallmark of AI trying to sound measured and balanced.
- No errors at all. Not one. Not a missing comma, not a repeated word, not a tense slip. Real humans make micro-errors even in polished work.
Each of these alone means nothing. All of them together? That's when Sara started running tests.
How Can You Tell If Something Is Written by AI?
The clearest signals are structural, not just stylistic. AI-generated text tends to be grammatically flawless, emotionally flat, and structurally predictable — it follows an intro-body-conclusion format almost every time, uses hedging language like "it's important to note," and avoids specific personal anecdotes or named examples. When you see all of these patterns together in a single document, it's a strong signal the text was machine-generated.
Sara ran the draft through WriteMask's free AI detector first. The result came back flagging the document as highly likely AI-generated. She cross-checked with a second tool to be sure. Both pointed the same direction.
But here's what most people don't know: how AI detectors work isn't magic. They're trained on statistical patterns — things like perplexity (how predictable word choices are) and burstiness (how much sentence length varies). AI text scores low on both. Human text scores high. Sara's client's draft scored low on both, across multiple tools.
The Signal That's Hardest to Fake
After running the tools, Sara went back and looked at the document manually. She now knew what to look for.
The biggest tell wasn't any single sentence. It was the complete absence of friction. Real writing has friction. Writers change their mind mid-paragraph. They overexplain something, then backtrack. They use a word that's almost right but not quite. They make choices that are slightly odd but feel human.
AI text is smooth in a way that real writing isn't. It's the difference between a highway and a path through the woods. Both get you somewhere. Only one shows evidence of a person having walked it.
She also noticed the document had metadata showing it had been created and last edited within a span of four minutes. A document "worked on for weeks" would show revision history spanning days. This wasn't proof on its own, but it fit the pattern.
What She Did With It
Sara didn't accuse the client directly. She sent a note saying the draft read as AI-generated based on her review and the detector results, and that she'd need original voice content to edit — she wasn't a ghostwriter for AI output. The client didn't respond.
She raised her rates after that. And she started running every new client submission through a detector before agreeing to take on the work.
If you're on the other side of this — worried your own structured writing style might get flagged unfairly — it's worth understanding that AI detection false positives are real. Formal academic prose, translated text, and highly technical writing can all trip detectors even when a human wrote every word.
How to Test Something Yourself
If you want to check a piece of text — yours or someone else's — here's a practical process:
- Run it through at least two detectors. One tool flagging it might be a fluke. Two tools agreeing is harder to dismiss.
- Look for the manual signals: uniform rhythm, no personal voice, broad vague examples, constant hedging fillers, zero errors.
- Apply the "so what?" test. Can you quote any specific, original thought from the piece? If every sentence is technically true but nothing is surprising or particular, that's a red flag.
- Try the AI or Human? game to train your own eye — it's surprisingly effective at teaching you what AI text actually feels like to read in practice.
Sara's experience is more common than people admit. Clients send AI content to editors. Students submit AI drafts to advisors. Colleagues email AI-written reports without disclosing it. Learning to recognize it — with tools and without — is a practical skill in 2026.
WriteMask works on both sides of this. Writers who use AI as a starting point can humanize their drafts until they pass detection — with a 93% pass rate across major detectors. Readers who need to verify text can use the free detector before deciding what to do next.
Either way, the first step is knowing what you're actually looking at.