Your client, your work,
your record.

Is this the same as a student getting accused at school?

No. A student faces a misconduct tribunal that can mark a transcript. You're in a dispute over money owed for work you already delivered. Different rooms. Different rules.

Notice what your burden is not. You don't have to talk anyone out of a suspicion about your character. The client has to justify keeping money for delivered work. You answer that with the record of building it — not a denial. → The cases — coming soon

Can a client refuse to pay because a tool flagged the work as "AI"?

No. A tool that reads writing for AI returns a guess. A guess is not a reason to keep money owed for delivered work.

• The companies that make these tools say the output should not be the sole basis for a decision.
• Independent peer review found the leading tools "neither accurate nor reliable" — all landing below 80% accuracy.
• Run on 91 human-written essays by non-native English writers, seven of these tools wrongly called 61.22% of them "AI" — on average. The same tools flagged native-speaker essays at an average of about 5% (5.19%). Feed the same essays through one richer-vocabulary prompt, and the false-flag rate fell to 11.77%. That tells you what the tool actually reacts to: vocabulary, not authorship (Liang et al., Patterns, 2023 · arXiv:2304.02819).

The em dash is the trap. The polish a client pays a professional for — clean syntax, varied punctuation, a formal register, tidy transitions — is exactly the pattern these tools read as "AI." Doing the job well is what makes you look suspect to a tool that mistakes craft for a machine. That is the tool's defect, not yours. The fuller reason these tools can't reliably tell a polished human from a model → Why a tool's "AI" reading isn't reliable →

A client just said your work is AI — what do you actually do?

It depends which of three moments you're in. The confrontation. A contract with no AI clause. Or outright non-payment. Each is won with a different move.

When the client confronts you — answer with receipts, not protest

Reply in writing, with the record of how the work was built. And ask the client to put their own claim in writing too. Send the drafts, the version history, the edit trail. The conversation moves off feelings ("is this AI?") and onto a document anyone can check — the work, taking shape over days. Then ask one precise question: which tool did you run it through, and what exactly did it return? That does two things at once. It pins a vague accusation to a named tool you can later show is unreliable. And it puts the work of explaining back on the side that raised the claim. What each piece is worth as evidence → What evidence actually holds up →

The catch: don't over-explain, and don't admit to anything you didn't do. A long, emotional defense becomes part of the record — it can be turned around on you. "I'd never use AI, I swear, my whole career—" reads as someone rattled, not someone with receipts. Keep it short. Keep it factual. Attach the evidence. Quiet about your character, loud about the record.

The reply — adapt this, don't paste it blind:

Hi [Name] — thanks for flagging this. I wrote this project myself, and I'm glad to walk you through how it came together. So I can respond precisely: which tool did you run it through, and what exactly did it return? On my side, I've attached the draft history and edit trail showing the work taking shape across [dates]. Separately, the invoice for [project], dated [date], is still outstanding and due under our agreement — I'd like to get this resolved quickly.

Four moves, no apology. Acknowledge it. Pin the claim to a named tool. Attach the record. Restate the invoice. Notice it never says "I'd never use AI." It shows — it doesn't plead.

Pulling your record (Google Docs): File → Version history → See version history. Export or screenshot the meaningful saves across the days you worked. Add your outline and any messages about the brief. Keep the real thing. A thin or one-sitting history is weaker dressed up, not stronger — show what's actually there.

When the contract has no AI clause — the gap is the client's, not yours

A missing AI clause doesn't put you in breach. There was no AI term to breach. So the dispute reverts to the only thing that was agreed: deliver the work, get paid. A client invoking "AI" on a contract that never mentioned it is trying to add a term after the fact. Silence on AI is not a promise you made and broke. Anchor everything to what the contract does say — the deliverable, the scope, the acceptance terms — and to the fact that you met it.

The catch, and why this is △ rather than ✅: it cuts cleanly only when the scope is specific. A vague scope line — "high-quality original content," "professional writing" — is exactly the language a client can stretch into "and obviously not AI-assisted." The looser your statement of work, the more room the client has to argue the deliverable wasn't what they bought. Tight scope: strong. Loose scope: weak. That conditional is the whole reason for the △.

When the client just won't pay — build the evidence packet

Stop arguing about AI. Assemble the packet a small-claims judge actually weighs: the written agreement, the brief, the invoice, confirmation you delivered, and your work record. Non-payment is a contract problem, not an authorship problem. The tool's "AI" reading isn't even an element of the case. The forum asks three things. Was there an agreement? Did you perform? Were you paid? Your drafts and version history sit in the packet as the answer if the client raises AI — not as the center of your claim.

The catch: small-claims dollar limits vary by state, and filing costs time and money. The tool's number is no defense to non-payment — but you still need the contract and the work record to win. A handshake deal with no written terms is the weak spot. That's exactly the gap the laws below were written to close.

When it's a platform dispute (Upwork and the like) — file into their process

Submit your work record into the platform's own dispute flow — logged hours, milestones, the work diary, version history. The platform decides on its evidence, not a court's. What a judge would weigh and what Upwork weighs are not the same thing. Your logged activity inside the platform often carries more weight there than drafts kept outside it, because the platform trusts its own logs.

The catch: the platform controls both the evidence and the clock. Dispute and refund windows are short, and they change. Miss the window and even the strongest record won't be looked at. Confirm the current timeline on the platform's support pages before you rely on any date — don't trust a number you remember from last year. And clients do raise exactly this claim on platforms — a refund demand built on a tool's "AI" reading. Answer it with the work record, not a protest.

What not to do — don't manufacture an edit history after the fact

Building a "natural-looking" edit history after the accusation is the one move that turns a payment dispute into a credibility problem. Auto-typers that replay text into a document to fake a writing history do exist. But a reconstructed record is fakeable, the people running a dispute know the tells, and getting caught manufacturing evidence is far worse than the original "AI" claim ever was. Use your real record, however thin. A genuine incomplete history beats a fabricated complete one. Every time. → The cases — coming soon

What laws actually back me when a client won't pay?

Several — and the newest were written specifically for freelancers. A missing AI clause strips none of them. They turn "the client won't pay" into a claim with teeth.

The law gives you a forum — and in two places, real penalties. But none of it supplies the one thing the client is counting on you not having: the record of how the work was made. That, you bring.

How do you make sure this never becomes a dispute again?

Stop reconstructing the record after the accusation. Keep it while you work. A record that already exists when the client objects beats one rebuilt under pressure. Every time.

You're reading this after a dispute. Look at the position that puts you in. Weeks later. The client already angry. You, reassembling how you wrote something from whatever happened to survive. That's the weak side of the table. The record that already existed when the objection landed — that's the strong side. One widely shared freelance-contract guide says it outright: an AI dispute should be settled by version-history review, not a tool's automated output (TextPolish). That moves you from defending-after to documenting-during. And the documenting has to already be done by the time anyone asks.