Turn Rough Notes Into a Professional Email: One Ask, the Right Tone
Most work emails are born not from a well-formed idea but from a messy impulse; you cram three things that popped into your head into one email, and the recipient gets confused about which one to answer, or answers the least important one and misses your real ask. Tone is its own trap: the firmness you'd use with a supplier reads as rudeness to an investor, and the formality you'd use with an investor reads as coldness to a close colleague. The common mistake is telling the AI to just 'clean up' the note; the AI polishes the sentences but leaves the structural problem (multiple asks, a vague subject line) untouched. This prompt reads your note against the recipient and the purpose first, reduces it to one clear ask, finds the right tone, and if needed gives you two tone variants of the same note; you decide which one fits the context better.
You are a business-writing editor and tone advisor. Your job is to turn the user's messy draft note into a clear, single-ask professional email that fits the recipient and the purpose. If the note contains more than one ask, you separate them and recommend which one should stay in the main email. Set the tone based on the real level of the relationship with the recipient, and don't default to overformality. An email's strength is not in its length but in its clarity; after reading it, the recipient should know exactly what they need to do. Use the information below: - Draft note (messy, as-is): [paste here] - Who the recipient is: [name/title, e.g. supplier, investor, client, colleague] - Level of relationship with the recipient: [just met / worked together a long time / formal and distant / casual] - The purpose of this email (in one sentence): [e.g. remind about payment, propose a meeting] - Do you want two tone variants: [yes/no] - Expected action (if any): [what you want the recipient to do, e.g. approve, pick a date, make a payment] RETURN THE OUTPUT IN THIS EXACT ORDER, WITH THESE EXACT HEADERS: === SINGLE ASK CHECK === Detect whether the draft note contains more than one ask or topic. If it does, recommend which one stays in this email and which should be left for a separate follow-up email, and briefly explain why. If there's a single ask, note briefly that 'the note is already single-topic' and move on. === SUBJECT LINE === Suggest a clear, short subject line (max 8 words) that lets the recipient grasp the purpose the moment they open the email. Avoid vague or generic subject lines (e.g. 'hello', 'a quick question'). === EMAIL (main variant) === Write the full, ready-to-send email: greeting, body, a clear action sentence, closing. Carry the single ask from the note clearly, without padding. The recipient should know exactly what to do by the final paragraph. === SECOND TONE VARIANT (if requested) === If the user asked for two variants, rewrite the same content at a different tone level (e.g. one more formal, one warmer). If not requested, note briefly 'Second variant not requested' and move on. === CLOSING AND SIGNATURE SUGGESTION === Suggest a closing line and signature format that fit the recipient relationship (e.g. the difference between 'Best regards' and 'Cheers', and which is more appropriate at this relationship level). === BEFORE YOU SEND CHECK === List the 2-3 things the user should check before sending (e.g. missing date, missing attachment, recipient name correct, expected action clearly stated). RULES: - Do not invent a name, date, amount, or any information not in the draft note; if something is missing, leave a placeholder in square brackets. - If the email has more than one main ask, always separate them; don't dissolve them all into one email. - Adjust the tone to the recipient relationship; don't write every email as formal by default. - Write short and tight; don't pad the email with an unnecessary opening line or filler pleasantries.
How to use it
- Dump what's in your head exactly as it is, unedited: who you're writing to, why you're writing, and any multiple asks, all in one note. Clarity isn't your job here, it's this prompt's job.
- Run the prompt. Look at the 'Single Ask Check' section; if your note had more than one ask, see whether the AI separated them and which one it kept in the main email. If needed, leave the second ask for a separate follow-up email.
- If you asked for two tone variants, read both and pick one based on the real level of your relationship with the recipient; before sending any of them as-is, make sure the subject line reflects your actual purpose.
Example / tip
A freelance consultant wants to both remind a client about an overdue payment and pitch a new project, and has written both into one messy note. The prompt detects that this contains more than one ask and suggests: send the payment reminder as its own clear, short, single-topic email; put the new project pitch in a separate, warmer second email, sent after the payment matter is settled. For the payment email it suggests a clear subject line (for example, About the October Invoice) and a polite but firm closing; it offers two tone variants, one more formal and one more casual, and the user picks the casual one based on the level of their relationship with the client.
Usage example
Copy the prompt as is, fill in the bracketed fields for your own business, and paste it into ChatGPT or Claude. The more concrete your input, the more useful the output. Take the first draft, ask for a one-sentence fix on whatever you don't like, then give it a final pass in your own voice.
When not to use it
For crisis communication or formal correspondence that could carry legal consequences (a termination notice, a formal objection, a legal warning), don't use this prompt on its own; it suggests tone and structure, but situations that require legally binding language demand review by the relevant expert or a legal advisor.
Output quality checklist
- Was the email genuinely reduced to a single clear ask, or is more than one topic still tangled together?
- Does the subject line let the recipient understand the purpose the moment they open the email?
- Does the tone actually match the recipient-relationship information you gave, or was a default corporate tone used?
