Revise an existing email to make its purpose and next step clear. Adjust tone while retaining the facts and requests in your draft.
How to use
Sign in and paste the email. Choose a tone and explain the relationship with the recipient in context. Compare names, dates, and commitments with the original.
Example
Turn a long status email into a short update with the completed work, remaining issue, and question for the recipient.
FAQ
How is this different from the email writer?
Start here when you already have a draft. The email writer starts from your description of a message.
Related tools
A practical task
Keep the revised email's subject and first sentence aligned. If the purpose is approval, the reader should see what needs approval and by when before the background. Supply the actual deadline rather than letting a rewrite add one for urgency.
Another useful question
What if the rewrite sounds too formal?
Choose a friendlier tone and explain the relationship. Remove stock greetings or closings that do not fit how you normally write to that person.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Context and audience | The same fact needs different explanation for a specialist and a first time reader. State the audience, purpose, and terms they already know. Relevant context guides wording more effectively than broad requests to make a text impressive. |
| Tone and commitments | Tone changes the way a message sounds, not the obligations it contains. A friendly version must not invent permission, and a formal version must not invent a promise. Compare commitments as well as style. |
| Supplied facts | A writing request needs the facts the finished draft must preserve. Names, dates, quantities, and policies should come from your source. Missing information is a question to resolve rather than a blank to fill with a plausible invention. |
| A clear next action | A message should make the next action easy to identify: approve a choice, send a file, confirm a time, or answer a question. State the action directly and keep supporting background separate from the request. |
| The recipient's knowledge | A recipient cannot act on references they cannot identify. Replace an unexplained “that file” with a real document name and include the needed context. Omit background they already know when it does not help the decision. |
| Real deadlines | Give an exact date or time only when it is known and needed. Relative phrases such as next Friday can be ambiguous across timezones or a delayed reading. Keep the deadline consistent with the action the message requests. |
| Editorial review | Review facts, names, omissions, and implications before approving a draft. A smooth sentence can still change a condition or attribute a statement to the wrong person. Compare meaning with the source instead of judging fluency alone. |