How to Tell Colleagues You Used AI to Draft
You used AI to get a draft started. Now you are staring at the send button wondering whether to mention it, and if so, how, without sounding like you cut a corner.
The instinct pulls both ways. Say nothing and it can feel like hiding something. Announce it and you risk making people doubt work that is genuinely yours. Neither the confession nor the silence is automatically right.
What resolves it is a simple question: does the reader need to know how this was made in order to trust or act on it? Sometimes yes, often no.
Disclosure Depends On What The Reader Is Relying On
Nobody expects you to disclose spellcheck, autocomplete, or a thesaurus. AI that polishes wording sits closer to those than to authorship. If you wrote the substance and used a tool to tighten the prose, there is usually nothing to disclose.
Disclosure starts to matter when the AI shaped the substance, or when the reader is relying on your independent judgment. Analysis, recommendations, anything that carries your professional assessment: if a model generated the reasoning, say so, because the reader is trusting a human mind they may not be getting.
Team norms and any workplace policy set the floor. When your organization has a rule, follow it. If you are trying to get a tool approved in the first place, our guide to asking your company to approve an AI tool covers that conversation.
Your Edit Matters More Than The Tool
The thing that actually protects trust is not the disclosure line. It is whether the work is correct, on point, and clearly reviewed by you. A carefully edited AI draft is more trustworthy than a sloppy hand-written one, and everyone knows it.
The disclosure trap runs both ways: disclose nothing and hide a real reliance, or disclose loudly to cover work you did not check. Our piece on the AI disclosure paradox at work digs into that tension. The way out of both is the same: own the output. If your name is on it, you vouch for it, tool or no tool.
Phrase It As A Fact, Not A Confession
When disclosure is warranted, keep it brief and neutral. You are stating how the work was produced, not apologizing. Plain, direct language beats a hedged, over-explained caveat every time; the principles at plainlanguage.gov apply here as much as anywhere.
A good disclosure names the tool’s role, confirms you reviewed the output, and moves on. It does not grovel, and it does not oversell the human effort to compensate.
Before:
Full disclosure, I want to be totally transparent that I used AI to help write this so please don’t hold it against me if anything is off, I did my best to check it but I’m not an expert.
After:
I drafted this with an AI assist and reviewed it for accuracy. Flag anything that looks off and I will correct it.
The second version reads as a competent professional accounting for their process; the first invites the reader to distrust the work before they have read a word of it.
Make The Draft Sound Like You Before You Worry About Disclosing
Half the anxiety about disclosure comes from AI text that does not sound like you. Even generic phrasing reads as machine-made, which is what makes people want to hedge. Fix the voice and the question of disclosure gets smaller.
Our guide to making AI-written emails sound like you covers the specifics. And remember that some messages should not be AI-drafted at all; our notes on when not to use AI for work messages mark those lines, from condolences to sensitive feedback.
Use this Wrivio Context to close the gap between the draft and your own voice:
Rewrite this so it sounds like me: plain, direct, and warm without being formal. Keep my sentence rhythm and vocabulary. Remove generic filler and any phrasing that reads as machine-generated. Keep every name, date, figure, and commitment exactly as written.
Press Ctrl+Shift+Space, paste the draft, run it, and check the word-level diff so you can see what changed before you send.
Common Questions
Do I always have to disclose that I used AI to draft something?
No. Disclose when the AI shaped the substance or when the reader is relying on your independent judgment; routine wording help, like polishing an email, sits alongside spellcheck and usually needs no disclosure, unless a workplace policy says otherwise.
How do I disclose without undermining trust in my work?
State it as a fact, not an apology: name the tool’s role, confirm you reviewed the output for accuracy, and stop, because a brief neutral note reads as competence while an over-hedged confession invites doubt.
Does using AI make my work less trustworthy?
Not on its own. What builds or breaks trust is whether the output is correct and clearly reviewed by you; a carefully edited AI draft beats a careless hand-written one, and your name on it means you vouch for it.
What if my company has an AI policy?
Follow it. A workplace policy sets the floor for disclosure, so meet its requirements first and apply your own judgment about substance and reliance on top of that.
Download Wrivio for Windows to make an AI draft sound like you before you decide whether to mention it at all.
Read Next
How to Flag an AI Mistake at Work
Spotted an error in AI-generated work? How to flag it clearly and usefully: name the specific mistake, the impact, and the fix, without blame.
How to Write a Slack Message That Gets a Fast Reply
A chat message that gets answered fast is built, not lucky. Put the ask first, make the reply easy, and stop making people decode what you need.
How to Write a Message Supporting a Decision You Argued Against
The gap between disagree and commit and quiet sabotage is what you write next. A structure for backing a decision in writing without erasing your objection.
How to Write a Status Update When There Is No News
Sometimes the honest status is 'nothing moved.' How to write that update so it still informs, keeps trust, and does not read as a stall or filler.
This article is filed underWorkplace Writing, which has 132 articles.