An email can be grammatically correct and still difficult to answer. Three paragraphs of history may bury a simple decision. Rewriting changes the emphasis and order; proofreading is the narrower task of correcting errors in wording you want to keep.
Decide what the reader needs to answer
Consider an invented internal email from an event coordinator:
Hi Ren, following all the discussions about the welcome desk and the earlier version of the rota, I wanted to come back to the question of Saturday because we have the room change to think about as well. We still need someone at the desk from 9 to 10 a.m. You mentioned you might be able to do it, but I know you were waiting to hear about transport. Could you let me know by Thursday at noon whether you can cover that hour? If not, I will ask someone else. Thanks, Alex.
The request is whether Ren can cover Saturday's 9–10 a.m. desk shift, with a reply needed Thursday at noon. Transport is unresolved. Ren has not accepted the shift.
A shorter authored revision is:
Subject: Can you cover Saturday's 9–10 a.m. welcome desk?
Hi Ren,
Could you confirm by Thursday at noon whether you can cover the welcome desk on Saturday from 9 to 10 a.m.? I know your transport plans are still uncertain. If you cannot cover it, I will ask someone else.
Thanks, Alex
This revision is a worked editorial example, not a live ChatGPT result. It removes the rota history because Ren does not need it to answer this request. If the room change affects where Ren should go, add the confirmed location before sending; do not assume the rewrite can resolve that missing detail.
Give ChatGPT the relationship and the request
“Make this professional” can produce an unnecessarily formal message. Describe the relationship and desired tone more plainly: a colleague you know well, a customer awaiting a decision, or a supplier receiving a first inquiry.
Rewrite the email below for [RECIPIENT AND RELATIONSHIP].
The one action I need from them is: [ACTION].
They need to reply by: [DATE/TIME/TIME ZONE, OR NO DEADLINE].
Tone: [E.G., FRIENDLY AND DIRECT, WITHOUT FORMAL BOILERPLATE].
Put the request near the beginning. Keep only the background needed
to answer it. Preserve the facts and distinguish a request from an
agreement. Do not add offers, apologies, guarantees, attachments,
deadlines, or prior conversations that I did not supply.
Return one subject line and a ready-to-review email. Below it,
identify any missing detail I should resolve before sending.
Do not send the email.
Original email: [PASTE]
OpenAI's prompting documentation, checked October 24, 2026, supports stating the audience, intended result, and boundaries. You do not need a special email-writing mode for a short rewrite in a conversation.
Choose the tone without changing the negotiation
For the desk-shift example, “Thanks for agreeing to cover Saturday” would turn a question into an agreement. “No problem if you cannot make it” might be friendly, but it should not remove the reply deadline Alex needs to arrange cover.
If the first version sounds too abrupt, request a focused revision:
Make the greeting and request warmer. Keep this as a request for
confirmation, not an accepted shift. Keep the Thursday-noon reply
deadline and the Saturday 9–10 a.m. shift. Do not add pressure or
suggest that Ren has already committed.
Read the full version after the change. Tone adjustments can spread beyond the greeting, so check the actual request rather than approving the response based only on how pleasant it sounds.
Send only after checking the message in your email app
Compare the recipient, dates, requested action, and any commitments with the original facts. Remove placeholders and confirm whether a mentioned attachment is actually attached. If a reply depends on a time zone or location that is missing, resolve it before sending.
Paste the approved subject and body into your email app. Check the To and CC fields there; an accurate draft cannot choose the right recipients for you. For the example, send a question Ren can answer with yes or no, and keep the rota unchanged until Ren confirms.