Draft an email from your purpose, recipient, and facts. Set the tone and give the reader a clear next step.
How to use
Sign in and describe the message you need. Add names, dates, and the action you expect in context. Choose a tone, generate the email, and check every commitment.
Example
Request a meeting with a supplier on Tuesday at 10 AM. Ask for confirmation and leave the location unspecified.
FAQ
How do I avoid invented details?
List the facts to include and identify details that must remain blank, such as price or meeting location.
Related tools
A practical task
Give the email one clear purpose. A request for a delivery update needs the order reference, the information you need, and a reasonable response date. Background belongs only where it explains that request; avoid asking the draft to invent urgency.
Another useful question
What should the last sentence do?
State the action the recipient can take. A direct question is easier to answer than a vague request to share thoughts on several unrelated issues.
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. |