When to Disclose AI Use on a Client Deliverable

When to Disclose AI Use on a Client Deliverable

Clients care about trust and claims, not your tool stack. When to disclose AI drafting vs a humanizer QA pass, sample contract language, and when silence becomes a problem.

3 min read
disclose ai writing to clientai content ethics freelanceclient deliverablefreelanceai humanizer

Clients do not buy your prompt library. They buy work they can put their name on. Disclosure is about trust and liability, not about sounding pure.

Academic ethics live here: Checklist for Ethical AI Use in Academia. Who a humanizer is for: AI Humanizer Use Cases. This post is the client deliverable version: freelance and agency.

When silence is a problem

SituationDisclose?
Brief or MSA bans AIDo not use it, or get a written exception
You invent testimonials, metrics, or citations with a modelAlways a problem; delete, then tell them if it shipped
You outline in ChatGPT, write the argument yourself, humanize onceTell them if they ask, or if the SOW requires any AI note
Grammar pass on your own draftRarely material; still answer honestly if asked
Regulated claims (health, finance, legal)Counsel + explicit approval; tools are not a defense

If you would be embarrassed to explain the workflow on a Zoom, fix the workflow before you fix the wording.

Humanizer as QA vs ghostwriting

RoleWhat happenedHow to describe it
GhostwriteModel produced the substance“AI-drafted; I edited” (if allowed)
AssistModel helped outline; you wrote claims“AI-assisted outline; human draft”
QA / humanizeYour draft; rhythm pass“Edited with an AI writing tool for clarity”

Human Writes sits in the QA row when you already locked facts. It does not invent a case study. If you used it to polish empty ChatGPT marketing, you are closer to ghostwrite. Be honest about which row you are in.

Sample language (edit with counsel)

Allowed in SOW:

Contractor may use AI tools for outlining, grammar, and clarity editing. Contractor will not invent facts, quotes, or metrics. Final claims remain Contractor’s responsibility. On request, Contractor will disclose which tools touched the deliverable.

Banned:

No generative AI may be used to draft client-facing copy without prior written approval.

Delivery note (when they want visibility):

Drafted by [Name]. Outline assistance: ChatGPT on [date]. Clarity pass: Human Writes on [date]. All product claims taken from your brief dated [date].

Keep a one-line log per job. You will need it when an account manager changes.

Detectors and clients

Some buyers add “must pass Originality.” That is a QA SLA, not a substitute for disclosure. See detectors for agencies. A green score does not fix a fake customer quote.

What not to do

  • Do not hide AI after they asked a direct question.
  • Do not put their unreleased strategy into a consumer chatbot.
  • Do not promise undetectable delivery as a service line.
  • Do not treat disclosure as a confession of incompetence. Treat it as scope control.

Bottom line

Disclose when the contract requires it, when substance came from a model, or when trust would break if they learned later. Human Writes is a clarity pass after the work is yours. It does not send the email for you.

Lock the claims, run one pass on Human Writes if the account allows it, and keep the log.