Tell a Client Your Illustration Is Human Made
Put one honest sentence and a record link in your delivery message so clients never have to ask. Copy the three-line template and the pre-send check.
Published October 17, 2026. Last updated: October 17, 20267 min readDrawDog
Last updated: October 17, 2026
Put one plain sentence about how the piece was made in your delivery message, and link a record the client can check. Do it at handoff, before anyone asks, and by the end of this post you will have a three-line message you can paste into your next delivery.
Say it at delivery, not after the question
A reply written after a client voices doubt sounds defensive, however calm you are. The same sentence sent with the files sounds like part of how you work.
Freelance advice on AI disclosure says the same thing from the other side: tell clients when AI meaningfully shapes a deliverable, and explain the intended use before work starts. Your delivery message is the last point where you can do that cleanly. If you are also dealing with a client who already has doubts, A client thinks your art is AI. Here's what to say. covers that conversation.
Copy this delivery message
Keep the subject line normal: "Final illustrations for [project]". Then:
Hi [name], the final files for [project] are attached.
These illustrations were drawn by hand in [app]. No generative AI was used in the final art. Here is a record of the sessions that you can check: [link]
On that page you can see how long the work took and that the files you received match the recorded sessions. Tell me if you want any changes.
That is about 60 words. The first sentence of line two is the answer. The link carries the evidence, so the sentence does not need to argue.
Leave out the apology, the history of AI art and any "I know how it is these days" filler. A long explanation reads as a long defense.
Write the line before the project ends
Draft the sentence while you still remember what you did, not on delivery day. One writer advises preparing a single sentence in advance that you can say without hesitating, and being honest with yourself about where AI actually touched the work. A sentence built on a softened version of the truth falls apart at the first follow-up question.
Build it in this order:
- Write what you did yourself in plain verbs: drew, inked, colored.
- Name the tools that were or were not involved, by name.
- Read it once as the client would. Ask what the obvious follow-up question is.
- If you cannot answer that question in one sentence, rewrite the line.
- Save the final wording as a snippet so every delivery goes out the same way.
Pick the right line with this table
| What actually happened | What the delivery line says |
|---|---|
| No AI anywhere in the final art | "Drawn by hand in [app]. No generative AI was used in the final art. Record: [link]" |
| AI used for one small thing (a reference image, a color idea) | "I used [tool] for [one specific thing]. Everything in the final art was drawn by me. Record: [link]" |
| You are not sure about one step | Do not send the clean line. Name the step you are unsure about, or settle it first. |
| Your contract defines "AI-generated" | Repeat the contract's exact term in the line so both sides mean the same thing. |
| The client's industry asks about AI every time (publishing, agencies) | Include the line on every delivery, not only when asked. |
For the second row, Disclose Minor AI Use to a Client Without Losing the Job has the longer wording and what to expect from the reply.
On the contract row: a contract needs a shared vocabulary for "AI-generated". If you and the client mean different things by the term, the dispute starts at delivery. Use their word, not yours.
Name the specific part instead of writing something vague
Compare two lines:
- Vague: "AI helps with my workflow."
- Specific: "I used an image generator to look at lighting ideas. I drew every line and color in the final piece."
The vague one reads as a dodge and invites questions. The specific one answers them before they come. The same goes for a bare "yes" or "no" when a client asks directly: name the part that is yours and the part that is not.
The proposal stage works the same way. Disclose in the proposal which phases are expected to involve AI tools, and keep a log of which deliverables are human-created and which are AI-assisted. If you did that at the start, the delivery line just repeats it.
Do not rely on file credentials to say it for you
If you work in Adobe apps, you may assume the file itself will show that no AI was involved. It will not say that.
Adobe reports that Content Credentials are generally attached automatically when qualifying generative AI tools are used, including creating an image from a text prompt, Generative Fill and Generative Expand. So a file with no credential only means none was attached. It does not state that the piece was made by a person.
The reverse matters more. If you used Generative Fill on a background, a credential can travel with the file. A delivery line that says "no AI" would then contradict the file's own metadata, which is worse than disclosing.
Run this two-minute check before you write the line
- Open the final project and list every generative feature you touched on the piece.
- If the list is empty, the clean line is safe on that point.
- If the list has even one item, name it: "I used [feature] to [one specific thing]. The rest was drawn by hand."
- Export the deliverable, then send the line and the link in the same message.
Put the evidence behind a link, not inside the file
Metadata embedded in a file can be lost when someone re-saves it, converts it or uploads it to a platform. A link survives all of that. That is why the message carries a record link and not just a claim.
A sketch folder or a set of work-in-progress screenshots helps too, but the client has to trust you did not stage them. A record created while you worked is easier to believe than one you assembled afterward.
A DrawDog certificate is that kind of record. It shows time spent, stroke count, the AI tool percentage and whether the file the client received matches the recorded session. The client opens one link. No account, no install. DrawDog never records file contents, file names, folder paths, keystrokes, screen contents or browser tabs.
Five mistakes that make the line backfire
- Waiting until the client asks. The first message then sounds defensive. Send it with the files.
- Claiming "100% human" with nothing behind it. An unsupported claim is exactly what the link is for.
- Sending a link with no sentence of context. The client has to guess what it proves. Say what they will see.
- Softening the truth. If any part of "no AI" is shaky, the whole delivery gets doubted at the first follow-up.
- Promising more than the record shows. Say what the page shows and stop there.
What a badge does and does not do
Some illustrators mark finished work with a "Created With Human Intelligence" badge. It is a fine signal on a portfolio. It does not tell a client how to check anything. A badge is a claim. A sentence plus a link a client can open is a claim with something behind it. If you use both, put the badge on the portfolio and the sentence and link on the delivery.
See how it plays out on a delivery day
Example: say you are delivering three spot illustrations for a client's newsletter, drawn over about two weeks in Procreate, with no AI used in the final art. You finish the last file on a Thursday. Before sending, you run the two-minute check (nothing generative touched the files), paste the snippet from your notes, swap in the project name and the record link, and send it with the PNGs. The whole step takes about three minutes. If the client has a question, you answer in one sentence and point back to the link instead of re-explaining your process.
That reply habit matters. When a client does follow up, How to prove to a client you actually made the work has the longer playbook.
Your next ten minutes
Open your notes app and save the three-line delivery message above as a snippet, with your app name filled in. Then open your last delivered project and run the two-minute check, so you know what your line would have said. You will have a ready answer before the next client asks.
Send the record with your next delivery
The line only works when the link behind it holds up. DrawDog runs in the background on Mac or Windows while you work, then gives you one link for the client. The free tier covers three certificates per month with no credit card, which is enough to try it on your next few deliveries. Download DrawDog and put your first record behind your first sentence.
If you want proof that holds up before a client asks for it, read what a DrawDog certificate records or download DrawDog and seal your next piece as you make it.
Common questions
Should I tell a client I didn't use AI before they ask?
Yes, if your work is the kind clients now question. Put one plain sentence in the delivery message and link a record they can check. It reads as routine, not defensive.
Is a plain yes or no enough when a client asks if I used AI?
Usually not. Name the specific part: what you drew yourself and which tool, if any, you used for one defined thing. A bare answer invites follow-up questions.
Does a missing Adobe Content Credential prove my art is human made?
No. Adobe attaches credentials when qualifying generative tools are used, so no credential only means none was attached. State the human-made line yourself and link a record.
What if I used AI for reference only?
Say so in one sentence, naming the tool and the single thing it did, and state that the final art was drawn by you. Then link your record.
Do sketches and work in progress count as proof?
They show decisions and iteration, but the client has to trust you did not stage them. A record created while you worked is easier to check.
How long should the delivery message be?
Keep it under about 120 words. The human-made line is one or two sentences, and the link carries the evidence.
