AI Disclosure Statement: Example & What to Include
Not a policy — the actual document you hand a client. Here's what belongs in it, a filled-out example, and a free tool that generates one in under a minute.
A disclosure policy is the internal rulebook — which tools are approved, when review is required. A disclosure statement is different: it's the one-page record you actually attach to a deliverable, so the client (or a future auditor, or you six months from now) can see exactly what happened on that specific piece of work. Most agencies have never written one because nobody's shown them what it should look like. Here it is.
What belongs in a disclosure statement
Six fields cover almost every situation:
Client and deliverable. What was made, for whom.
Which AI tool(s) were used. Named specifically — "AI" alone isn't a disclosure.
Involvement level. AI-generated, AI-assisted, or human-created/AI-reviewed — pick the tier that actually matches.
Reviewer. Who checked it before it shipped, and when.
Date of use. When the AI tool was actually applied, not just the delivery date.
A reference ID. So the statement can be looked up later if a client or a compliance question comes back to it.
A filled-out example
Here's what a real one looks like, in the format DisclosureTrail generates:
Client:Northwind Retail Co. Deliverable:Q3 email campaign copy (4 emails) AI tool(s) used:ChatGPT (drafting), Grammarly (editing pass) Involvement level:AI-assisted — human substantially edited and directed Reviewed by:J. Alvarez, Senior Copywriter — Aug 22, 2026 —————————————————————————————— Reference ID:AID-20260822-7F3K Generated via DisclosureTrail on Aug 22, 2026
That's the whole thing. No legal boilerplate, no paragraph nobody reads — just a factual record that answers the question before the client has to ask it.
Statement vs. policy — which do you need?
If you're setting internal rules for your whole team, that's a policy — see our guide to writing one, template included. If you need to hand a specific client a record for a specific deliverable right now, that's a statement — this page, or just use the generator below.
When to actually send one
You don't need a statement for every single deliverable to get the benefit. Three situations where it's worth the sixty seconds:
Any deliverable where AI did meaningful drafting work, not just spellcheck or research
Anything published under the client's name to their own audience (their disclosure exposure, not just yours)
Any time a client asks — and once one client asks, assume others are wondering too
Why this matters beyond "being nice"
Under the EU AI Act's Article 50, AI-generated content that's had genuine human review can be exempt from certain disclosure duties — but only if that review is documented. A dated statement with a named reviewer is exactly the kind of record that makes an exemption defensible instead of just asserted. See the plain-language Article 50 breakdown for specifics. This isn't legal advice — it's the practical reason "who reviewed it, and when" is worth writing down even where no law requires it yet.
Skip the copy-paste — generate one
DisclosureTrail fills in all six fields and gives you a downloadable statement with a reference ID, free, no login, nothing stored on our end.