You already wrote the email.
That matters.
The most useful way to bring AI into email isn’t as a ghostwriter. It’s as an editor. This AI email editing workflow has five steps: Start with your rough draft, give the AI a specific editing Job, add only the Context it needs, say what Output you want back, and Check the result before you send it.
That keeps the important parts human: the meaning, the relationship, the decision, and the final responsibility for what leaves your inbox.
The five steps at a glance

- Start — hand over the rough draft you actually wrote.
- Job — say what kind of edit you need.
- Context — give the minimum the AI needs to keep your meaning.
- Output — say what you want back.
- Check — read it before it goes out under your name.
1. Start with the rough draft
Your first draft doesn’t need to be elegant.
It can be too long, too blunt, too stiff, repetitive, or written in the special dialect known as “I typed this while three other things were on fire.”
That’s fine. Don’t polish it before asking for help. The whole point is that it’s rough.
Here’s a fictional example:
Hi Jordan, just following up on the timeline thing from last week. So the supplier pushed back delivery on the components, which honestly I didn’t see coming, and so I’m not totally sure we can still do Friday like we said. I really don’t want to promise Friday and then miss it, that would be worse. I was thinking maybe Tuesday might be more realistic? But I don’t want to just change it without checking with you first in case it messes something up on your end. Anyway the supplier thing is the main issue, they pushed the delivery. Let me know if Tuesday works or if it causes problems, or if we should talk about it. Thanks, Alex
It’s long, it says the supplier thing twice, and the actual question is buried near the end.
But look at what’s already there: the facts, the concern, and the proposed next step. The AI doesn’t have to invent the message. It only has to help make it clearer.
2. Give the AI a job
“Fix this email” is better than nothing, but it still leaves the AI to decide what “fix” means.
Tell it the editing job instead:
- make this shorter without sounding abrupt
- make this clearer and more professional
- make this warmer without becoming gushy
- remove repetition
- make the request obvious
- rewrite this in plain language
- keep my tone but clean up the structure
Those are editing instructions, not magic prompts. You’re telling the AI what problem to solve.
For the Jordan email, the job is: make it shorter, make the Tuesday question easy to spot, and keep it tentative.
3. Add only the context it needs
The AI doesn’t need your life story. It does need enough context to understand the relationship and the purpose of the message.
Useful context might include:
- who the recipient is
- whether the relationship is formal or casual
- what outcome you need
- what must not change
- whether a decision has already been made
- whether the message is sensitive
For example:
This is going to a long-term client. We have a good relationship, but I don’t want to sound casual about the delay. I’m asking whether Tuesday creates a problem, not announcing Tuesday as the new deadline.
That single paragraph prevents a lot of accidental nonsense.
Without it, the AI may confidently rewrite your tentative question as a firm announcement, because machines are very good at producing clean sentences and somewhat less talented at reading the invisible politics of your Tuesday afternoon.
Context is also where you decide what not to share. The AI only needs the information required to do the editing job. If it doesn’t need the account number, customer ID, private medical detail, or confidential attachment, leave it out. If the email involves money, contracts, personnel issues, health information, or private customer information, be more careful about what you put into an AI service in the first place. (See [What Not to Put Into ChatGPT or Another AI Tool].)
4. Say what you want back
You can also specify the form of the answer:
- one polished version
- two versions with different levels of formality
- a shorter version under 100 words
- a subject line plus body
- the revised email followed by a short note on what changed
For everyday work, ask for one revised version first. Too many options create a new problem: now you’re comparing six perfectly acceptable emails when you were trying to save time.
5. Check before you hit Send
This is the step people skip, because the output looks polished.
Polished isn’t the same as correct.
Compare the revised email with what you meant to say, and check five things:
- Did any fact change?
- Did a possibility become a promise?
- Did the AI add an apology, commitment, deadline, or offer you didn’t authorize?
- Does the tone fit the actual relationship?
- Does this still sound like something you’re willing to send under your own name?
If something’s off, don’t start over. Tell the AI what’s wrong: “This is too formal. Keep my original conversational tone and only fix clarity and structure.” You’re allowed to edit the editor.
Before and after
Here’s the Jordan email after one pass with the job and context above.
Before (about 125 words):
Hi Jordan, just following up on the timeline thing from last week. So the supplier pushed back delivery on the components, which honestly I didn’t see coming, and so I’m not totally sure we can still do Friday like we said. I really don’t want to promise Friday and then miss it, that would be worse. I was thinking maybe Tuesday might be more realistic? But I don’t want to just change it without checking with you first in case it messes something up on your end. Anyway the supplier thing is the main issue, they pushed the delivery. Let me know if Tuesday works or if it causes problems, or if we should talk about it. Thanks, Alex
After (about 60 words):
Hi Jordan,
Following up on our timeline. Our supplier has pushed back the component delivery, so I’m not confident we can still hit Friday, and I’d rather not promise a date we might miss.
Would moving to Tuesday cause any problems on your end? If so, I’m happy to talk it through before we change anything.
Thanks,
Alex
Half the length, one mention of the supplier, and the question now stands on its own line.
Notice what the AI didn’t need to do.
It didn’t invent a reason for the supplier delay.
It didn’t apologize on your behalf.
It didn’t offer a discount.
It didn’t turn Tuesday into a final decision.
Those would be business decisions, not editing.
A copy-and-use instruction
Here’s a practical starting point:
Revise the rough email below.
Job: Make it clearer, shorter, and easier to act on.
Context: [Who this is for and what they need to know.]
Keep unchanged: [Facts, commitments, dates, or wording that must stay accurate.]
Tone: [Professional / friendly / direct / warm / neutral.]
Output: Return one revised version only.
Check rule: Do not invent facts, commitments, deadlines, apologies, or offers that are not in my draft. If something is unclear, flag it instead of guessing.
Rough draft:
[Paste your draft here.]
It isn’t a sacred formula. Change the labels if you want. The point is to stop making the AI guess what kind of editing you need.
When this works, and when it doesn’t
This works well for ordinary messages:
- client follow-ups
- scheduling emails
- internal updates
- requests for information
- short project recaps
- polite declines
- messages that got too long while you were thinking them through
It’s less useful when the hard part isn’t the wording. If you don’t know what decision to make, what you’re allowed to promise, or how to handle a serious conflict, rewriting the email isn’t the real problem.
A beautifully edited bad decision remains a bad decision. It merely arrives with cleaner punctuation.
The point
AI is genuinely useful in the gap between “I know what I mean” and “this is ready to send.”
You provide the meaning. You provide the context. You decide what the message is supposed to accomplish. Then let the AI do some of the boring cleanup.
And before it goes out under your name, read the thing.
Frequently Asked Questions
Is it safe to paste work emails into ChatGPT or another AI tool?
It depends on what’s in the email and on your organization’s rules. Share only what the editing job requires, and leave out account numbers, customer IDs, health details, and confidential attachments. Often a short summary plus your draft is enough. (See [What Not to Put Into ChatGPT or Another AI Tool].)
Which AI tool is best for editing emails?
Most general-purpose AI chat assistants can help edit an email. A clear job, enough context, and a human review usually make the results more useful than a vague request. Different tools can still produce different results.
Will the recipient be able to tell AI edited it?
You can’t reliably determine from the wording alone whether AI edited an email. Generic, overly polished phrasing may raise questions, but it isn’t proof. Use the Check step to make sure the message still sounds like you.
What if the edited email no longer sounds like me?
Tell the AI what changed. For example: “This is too formal. Keep my original conversational tone and only improve clarity and structure.”
Should I ask AI to write the email from scratch?
You can, but starting from your own rough draft gives the AI more of your actual intent and leaves less for it to invent. A human-written starting point is also easier to review.




