Hiring Freelance Writers? A Fair Way to Check Submissions for AI Use

Quick Answer

Include your AI use rules in the project brief and ask for a draft history from the writer. Use any detector score as just one indicator to talk to the writer about it, not as definitive proof. There is no U.S. federal rule in 2025 requiring AI content labeling in journalism or advertising, so you’re setting the rules.

Key Points

• A 2026 WebCraft video review of GPTZero noted that it can give false positives for writing that is extremely formal, very structured, or written by a non-native speaker. So take any score as just one piece of evidence.
• Four of the open detectors (Desklib, Fakespot, Binoculars, and Fast-DetectGPT) didn’t flag any of the 223 held-out articles from one content pipeline (1% false positive rate).
• In 2025, the AP didn’t permit AI to write or rewrite any news stories that were to be published. You’ll need to set your own AI usage rules in the brief and ask for the draft history.

A draft history of a shared document will show you exactly how that piece was written, something a single detector score will not.

Big newsrooms have AI rules in writing. In her 2025 roundup, Elainna Ciaramella reported that the AP didn’t permit AI to draft or rewrite a publishable news story. Hearst only permitted AI to be used in the initial draft or outline stage for lifestyle and real estate content, and the stories had to be verified, rewritten, and approved by an editor. She put it down to the simplest of statements: “AI must not publish without human review.”

You may not have a standards desk, but you still need three things: clear rules in place prior to work commencing, a human review of the work after it’s submitted, and a method of detecting AI use which doesn’t unfairly blame the legitimate writer. I go on to explain why one score is not sufficient to determine authorship, how detectors can misread human writing, and how you can keep the process fair and the drafts private.

In 2023, monthly writing freelancer jobs on Upwork fell by 2% following the release of ChatGPT, and monthly earnings were down 5.2%. The higher the skill level of the writer, the greater the fall, which the researchers found to be quite significant. A false AI claim has an impact on people who are already in a precarious position.

Schools have reacted in their own way. On The Rough Draft (a 2024 writing podcast), the hosts were talking about teachers going back to the blue books and the in-class essay. One of the hosts thought the cat-and-mouse game of workarounds and detectors would continue. You can’t put a freelancer in a classroom, so your check has to work for writing that’s done elsewhere.

Questions this article answers

• Is an AI detector score enough to reject a freelance article?
• Why do AI detectors flag human writing?
• How do I check a writer’s work for AI fairly?

Why isn’t a detector score enough to judge a freelance submission?

In AEO Content’s own September 2026 evaluation, not an independent audit, its detector called 0 of 4,546 verified human documents AI. A calibrated score helps, but it cannot show how a piece was made.

I would settle four things before running any check:

1. Write your AI-use rules into the brief.
2. Ask for drafting in a shared document with edit history.
3. Pick one calibrated check and read which sentences it flags.
4. Talk to the writer before you decide anything.

That evaluation put the 95% upper bound at 0.08%, and the detector behind it is calibrated on more than 10,000 verified human documents with a 0.5% false-positive cap held in every writing register. The common assumption is that a number this low can stand alone. It cannot. A score reads finished text; it never sees the drafting. See how AI and human writing differ.

What you write in the brief is as important as who writes it. In practice, a brief which asks for specific first-hand material makes the subsequent checks much easier to understand.

You’re also paying for the specifics. The USCO states copyright “does not extend to names, titles, short phrases, ideas, methods, facts or systems” and only covers “specific creative expression”. Looking at four sources, the pattern is very clear indeed: authorship is in the details and the process. The first test for any submission is whether it contains expression which only this writer could have produced, and that’s where the single tool scores often diverge.

Where do AI detectors get human writing wrong?

Formal, neutral human prose is the usual casualty. In AEO Content’s internal evaluation (not an independent audit) of 2,868 pre-2021 Medium posts, 4 were called AI (0.14%), and the misses were neutral institutional prose.

A 2026 WebCraft video review of GPTZero describes the same pattern from outside: consistent reports of false positives on writing that is very formal, very structured, or written by non-native English speakers. The reviewer adds that different detectors can return completely different results on the same text. Experts, it says, treat a score as a supporting signal, never final proof.

The habits detectors key on are real. They are also style. AEO Content measured 12.9 dash-punctuation marks per 1,000 words in AI-drafted articles against 0.8 in a company’s pre-AI blog, and a dash budget cut its new articles to 1.69. A habit that strong is easy to spot. It is also easy to edit out.

That is why the company keeps two readings apart and never blends them: an origin reading (who wrote it) and a style reading (how generic it reads). A submission can fail the second and pass the first. Flat tone tells you about quality. It says little about authorship.

The whole ‘dashes’ argument is a good example of why you’d be mad to use punctuation as your sole reason frewriteng for rewriting. Punctuation is the easiest thing to change in a draft and therefore the weakest possible reason to accuse a writer. Use a generic style as a reason to rewrite, not as evidence of authorship. Save the authorship question for when you actually have evidence that can answer it. That’s where comparing a draft to your own chatbot output can actually get you into trouble.

How do you judge a submission fairly when AI might have helped?

Edited AI-assisted text can read human: four open detectors flagged 0 of 223 held-out articles from one content pipeline at a 1% false-positive rate. So judge the process, not the phrasing.

Those were AEO Content’s own articles. The detectors were Desklib, Fakespot, Binoculars, and Fast-DetectGPT, and at the same settings they still caught 13-80% of ordinary AI text. A score cannot tell a well-edited draft from a written one. Process can.

Wording overlap is even less convincing. Freelance writer John Hansen has had clients question the quality of his work after running the same piece through an AI tool and seeing it ‘use some of the same terms or wording’. His reply is straightforward: ‘AI is trained on human writing’. His clients are now in one of two camps: those who want absolutely no AI at all and those who want their AI draft (i.e., the draft produced by the AI) to be improved.

That split is the real decision, and you need to put it in writing prior to anything else. If you’re going to allow AI drafts, then you need to plan for the editing time (Hansen notes that editing one takes pretty much as long as writing it from scratch). Not doing so will lead to pricing disputes. Looking at four sources, the pattern is very clear: agree on the type of AI use, the drafting evidence, and the tool first so that any subsequent check is a check of fact rather than an accusation.

Privacy should be part of those same terms. Some of the checker vendors will tell you that pasted text is deleted after each scan and is never used to train any AI. Make sure you get that in writing before you share an unpublished client draft.

Final Thoughts: What should you do before the next submission lands?

Even a detector that flagged 222 of 223 held-out long-form AI articles only tells you where to look. Agreed rules, draft history,ry and a plain conversation decide what happened.

That figure comes from testing the AI detector I built to avoid flagging honest human writers, which also caught 144 of 146 AI articles published after its training cutoff. Its human test set took pre-2021 Medium posts with a different author on every post, drawn from 2,401 publications, and used them only to test, never to train. Before trusting any flag, ask the tool’s maker how its human sample was built. Then put your AI-use rules in the next brief. Do it before the first draft arrives.

Frequently Asked Questions

What else do people ask about checking freelance writing for AI?

Can a detector score cost a writer a client?

Yes. In a 2023 r/freelanceWriters thread, one writer had not lost any clients to AI but did lose one client who accused them of using it (based on an Originality.AI check). Decide in advance what a flag will trigger before you get your first assignment.

Should you ask writers to run their own AI check?

You can. In 2023, writers were already talking about clients asking for AI detection tests, and Grammarly now has an AI text check as part of its plagiarism check. You can also ask for the draft history (which is the edit history of a shared document).

Do some clients want writers to use AI?

Some clients do. In the same thread, a writer said their main client held a call to show them how to use AI for outlines and headings, then made its use optional. Another client might see that same workflow as a violation.