Draft Professional Emails from Bullet Points

Workflow area: Writing & Email · Tier: Foundation · Hands-on time: ~20 minutes

The difference between a mediocre AI email and one you can send unedited is almost never the model — it is whether you told it who is reading, what you want them to do, and how the message should feel. That frame takes thirty seconds to write and saves ten rounds of "make it shorter, make it warmer."

When to use — and when not to

• Use it for structured asksrequests, follow-ups, status updates, scheduling, gentle escalations, and bad-news messages where wording matters and a blank page slows you down.
• Use it when the stakes are moderatethe email matters enough to be well-written, but not so sensitive that every clause needs a lawyer.
• Skip it for two-line replies"Thanks, confirmed for Tuesday" does not need a prompt. Typing it is faster than framing it.
• Skip it for genuinely personal messagescondolences, apologies for something you personally did, performance conversations. Readers can feel outsourced sincerity, and the relationship cost is not worth the saved minutes.
• Skip it when the content is restricteddisciplinary matters, legal disputes, unannounced financials. See the privacy note below and pb-12.

The recipe

1. 1.

   Write your bullets first, before opening any AI tool. Three to seven bullets: the facts, the ask, any dates or amounts. If you cannot write the bullets, the problem is that you don't yet know what you want — no model fixes that.

2. 2.

   Fill in the four-lock frame. Recipient, goal, tone, length. This is the whole trick. Paste this prompt into ChatGPT, Copilot, or Gemini:

   Copy

   Draft an email from these bullet points.
   
   Recipient: [WHO — role and your relationship, e.g. "my client's finance
   director; we've met twice, cordial but formal"]
   Goal: [WHAT THEY SHOULD DO after reading, e.g. "approve the revised
   quote by Friday"]
   Tone: [e.g. "professional, warm, not pushy"]
   Length: [e.g. "under 120 words, 2 short paragraphs"]
   
   Bullet points:
   - [POINT 1]
   - [POINT 2]
   - [POINT 3]
   
   Rules: Use only the facts in my bullets — do not invent details,
   commitments, or dates. Write a subject line. No em-dash-heavy or
   flowery phrasing. End with a single clear ask.
   

3. 3.

   Read the draft as the recipient, not the sender. Good output looks like this — short, specific, one ask:

   Copy

   Subject: Revised quote — approval needed by Friday
   
   Hi Meera,
   
   Following our call on Tuesday, I've attached the revised quote with
   the updated delivery schedule (now 6 weeks) and the 4% volume
   discount we discussed.
   
   Could you confirm approval by Friday the 14th so we can hold the
   production slot? Happy to jump on a quick call if anything needs
   clarifying.
   
   Best regards,
   Arjun
   

   If the draft buries the ask in paragraph three or invents a pleasantry that isn't true ("Hope the conference went well!" — which conference?), fix the frame, not the draft.

4. 4.

   Iterate with targeted edits, not "try again." "Make paragraph 2 one sentence." "Replace 'as per our discussion' with plain language." "The deadline is firm — remove 'if possible'." Each instruction should name what changes; regenerating from scratch loses what was already right.

5. 5.

   Do the final pass yourself. Check every name, date, and number against your bullets, then adjust one or two phrases into your own voice. A single sentence you actually wrote makes the whole email sound like you.

Make it yours

• M365 Copilot in Outlook: use Draft with Copilot directly in the compose window — paste the same four-lock frame into the instruction box. Copilot picks up the thread context automatically, so you can shorten the Recipient line to "reply to this thread." Use the built-in tone and length controls after generating instead of re-prompting.
• Gemini for Workspace in Gmail:Help me write accepts the same frame; keep it under ~150 words of instruction for best results. Gemini's Refine options (Formalize, Shorten, Elaborate) map to step 4 — use them for one-click adjustments before hand-editing.
• Batch scale: writing the same email to twelve people? Draft once with placeholders like [NAME] and [PROJECT], ask the model to keep placeholders intact, and fill them per recipient — or feed a small table of names and details and ask for all twelve variants in one pass. Read every variant; personalization is where models quietly recycle the wrong detail.

Quality check

• The ask is unmissablea reader skimming for five seconds knows what to do and by when.
• Every fact traces to your bulletsno invented dates, commitments, meetings, or pleasantries.
• Names and titles are exactly rightmisspelling the recipient's name undoes everything else.
• Tone survives the read-aloud testread it once out loud; anything you would never say, rewrite.
• Length matches the relationshipa 300-word email to someone who sends you two-liners signals "AI wrote this."