Email Draft Assistant: four templates that cover your week
Follow-up, refusal, apology, request. Fill in the bracketed parts, follow the tone rules, and send in under five minutes.
Work emails fail for one reason: the ask is buried under filler. The templates below put the point in the first line and give the reader one clear thing to do.
Template 1 — Follow-up (no reply in 5 days)
Hi [Name],
Just bumping this to the top of your inbox.
Could you confirm [decision/document] by [date]?
Happy to jump on a quick call if that is easier.
Thanks, [You]Template 2 — Polite refusal
Hi [Name],
Thanks for thinking of me for [request].
Right now I cannot take this on because [current priority/deadline].
I would like to revisit it [timeframe].
Best, [You]Template 3 — Apology (you made a mistake)
Hi [Name],
You are right — [mistake] was on me.
The fix: [what you already did].
To stop it repeating: [process/step].
Sorry again, [You]Template 4 — Request (budget, approval, help)
Hi [Name],
I am asking for [X] to [goal].
What it buys: [concrete outcome].
Timeline: [by date].
If this does not work, my alternative is [Y].
Best, [You]The tone rules (apply to every template)
- Subject line under 6 words: Q3 budget / Follow-up: report.
- First line = purpose. No weather small talk.
- One paragraph per point. Wall-of-text emails get skimmed.
- One ask at the end. If you need two answers, send two emails.
Why templates beat freewriting: you stop deciding format at 9am and start solving the actual problem. Also, every email you send is a brand signal — consistent first-line purpose trains your readers to trust that your mail is worth opening. Readers who know your first line is the ask skim less.
Two edge cases worth memorizing. To a client, drop the template entirely after the first paragraph — they care about their own situation, not your structure. To your own manager, one extra sentence on the blocker earns the reply: short emails are not rude emails, they are efficient ones.
AI rewrite prompt for messy drafts
Rewrite this email so the ask is in the first line, the tone is friendly but direct, and it stays under 100 words. Keep the bracketed placeholders. Draft: [paste].
How it works
- Pick the template matching your situation: follow-up, refusal, apology, or request.
- Replace every bracketed part with your real details — never send a template with brackets left.
- If your draft feels clumsy, run the AI rewrite prompt once, then read it yourself before sending.
Match the thread. If replies are casual, write casually. Default safe level: one greeting sentence, then the point. Never write Dear Sir or To Whom It May Concern to someone you already work with — it reads as cold.
Send one last nudge after another five business days, and change the ask from open-ended to yes-or-no: Can you confirm by Friday? After that, stop. Silence is an answer, and repeated nudges cost you reputation.
Read it once before sending and check three things: names right, no weird formal phrasing, and the ask is the one you meant. AI drafts are a first draft, not a finished product — sending them unedited once is how you get strange emails.
No. One clean apology, the concrete fix, and the prevention step. Repeated apologies signal you do not believe in your own fix — and they make the recipient uncomfortable.
Under 120 words, four short paragraphs max. If your email needs more, it probably needs two emails, a call, or a meeting instead — most emails over 200 words get skimmed, not read.
Who this tool is for
This fits the recurring messages that fill a workweek: chasing a decision, declining a request, owning a mistake, asking for budget or help. Coordinators, assistants, project managers, support leads, freelancers and non-native English writers get the most use from it.
It is not for legal notices, disciplinary or investigation messages, contract changes or safety reports. Those need review and often a template from legal. High-volume sales sequences also need a different structure and consent rules.
How to read your result
The output is a short message built on a fixed skeleton. Judge it in this order.
- Subject line. Six words or fewer, naming the topic. Quick question tells the reader nothing.
- First line. State the purpose or the ask. If they stop after one line, they should still know why you wrote.
- Body. One point per paragraph, under 120 words, no backstory.
- Ask. Exactly one, with a date. Let me know is not an ask.
- Names. Spell the recipient and company correctly, and match the greeting to the relationship.
- Brackets. Search for a square bracket before sending. One left means it is still a draft.
- Tone. Friendly and direct. Apologise only if you erred, and avoid softening every sentence with just.
- Channel. If the answer needs discussion, ask for fifteen minutes instead of writing four paragraphs.
If a refusal also needs an apology, send the apology as its own short note first. Combining them makes the refusal look insincere.
A worked example
Sofia coordinates projects at a design agency. A print vendor must confirm a delivery date for a client workshop on 3 November.
First draft: Hi Marco, hope you are well. Things have been busy with the Q4 rebrand, and the client changed a few things, so I wanted to check in about the delivery and whether the schedule still works, because we may need to adjust...
Final, using the follow-up template: Subject: Delivery date — 3 Nov workshop. Hi Marco. Bumping this to the top of your inbox: we need the print delivery confirmed by Friday 30 October for the 3 November client workshop. Can you confirm today or tomorrow? If easier, I can call at 10:00 or 15:00. Thanks, Sofia.
That is fifty-two words, one ask and two call windows. The draft asked Marco to interpret a situation; the final asks him for a decision.
A second, shorter case uses the refusal template. Declining a weekly status call reads: thanks for including me; I cannot join this quarter because the onboarding project takes my mornings; I can send written updates each Thursday and rejoin in January. Three parts, no excuse-making, and a route back in.
The same skeleton holds when you ask for money or approval: say what you need, what it buys, the timeline, and your fallback. The fallback is what separates a request from a demand, and it gives the reader an easy way to say no without ending the conversation. Write that line before you write the justification; it keeps the message to one screen.
Common mistakes
- Leaving brackets or the previous recipient's name. This is the most common template failure.
- Two asks in one message. Split them or drop the weaker one.
- A long apology. Length makes it sound less credible, not more.
- Using the refusal template when you actually made the mistake. Start with the apology template.
- Copying a manager to apply pressure. That turns a request into an escalation.
- Hiding the ask at the bottom to be polite. The reader may never reach it.
- Pasting sensitive text into an AI tool. Client names, contract terms and internal threads stay out of public tools; strip identifiers or write those messages by hand.