ChatGPT Prompts for Everyday Work Emails

Most work emails aren't hard to write. They're hard to write well when you're busy, annoyed, or asking for something awkward. These 11 prompts cover the ones that come up every week: following up, saying no, pushing back on a deadline, owning a mistake, and turning messy notes or threads into something people will actually read.

Each one started as a draft from Promptimize, then was edited by hand. Invented details came out, paste-in slots went in, and every prompt keeps ChatGPT to your real names, dates, and facts. When something is missing, it marks the gap instead of guessing, so you never send a deadline or decision nobody agreed to.

Want to see how they hold up? Paste any of them into our free Prompt Grader for a score out of 100 and a breakdown of what's working.

They work in ChatGPT, Claude, and Gemini.

How to use these prompts

Copy a prompt. Paste in your details or the email you are replying to where marked. Read the draft once, fill any (ADD DETAIL) or (CONFIRM) spots, and make it sound like you before you send it.

Ask, follow up, and say no

Act as a friendly, experienced coworker who is good at getting replies without nagging. Help me write a follow-up email to a coworker who hasn't answered a request I sent.

Before you write, briefly note:
1. The one thing I need from them, restated as a single question they can answer quickly
2. Anything that might make it hard to reply (an unclear ask, the wrong person, too much on their plate), and how the email can make replying easier

Then write the email:
- Open with one friendly line that reminds them of the original request. Assume they're busy, not ignoring me.
- Restate the ask in one or two plain sentences.
- Say when I need an answer and why, only if I give you a date and a reason.
- Give them an easy out, like pointing me to the right person if this isn't theirs.
- Close with a short, warm sign-off.
- Under 100 words.

Rules:
- Use only the details I give you. Do not invent dates, deadlines, reasons, or project details. If something important is missing, write (ADD DETAIL) instead of guessing.
- No guilt or passive-aggressive phrases like "per my last email," "just circling back again," or "as I mentioned."
- Don't apologize for following up.

Also give me 2 short subject line options.

My original request (remove anything confidential first):
[paste your original email, or describe what you asked for]

When I sent it:
[the date, or roughly how long ago]

When I need an answer, and why (optional):
[the date and the reason, or leave blank]

Act as a supportive team lead who coaches people on asking their manager for help. Help me write an email to my manager about a task I'm stuck on.

Before you write, pick out the one question I most need answered. If I have more than two questions, list the extra ones for me separately so I can save them for later.

Then write the email:
- One sentence on the task and what it's for
- What I've already tried, in 2 or 3 short bullets
- Exactly where I'm stuck, in one or two sentences
- My suggested next step, if I have one, so my manager can just say yes or point me elsewhere
- End with one clear question and an offer of a quick call if that's easier
- Under 150 words. Confident and plain.

Rules:
- Use only what I tell you. Do not invent what I've tried, deadlines, or project details. If something is missing, write (ADD DETAIL).
- Don't open with an apology or put me down ("sorry to bother you," "this is probably a silly question").

Also give me a short subject line.

The task and what it's for:
[describe the task]

What I've tried so far:
[list what you've done]

Where I'm stuck:
[the exact problem, or the information or decision you're missing]

My suggested next step (optional):
[your best guess at the way forward, or leave blank]

Act as an experienced manager who coaches people on saying no at work without damaging trust. Help me reply to my boss, who has asked me to take on extra work I don't have room for.

Before you write, briefly list what would slip if I said yes, using only the current work I list below.

Then write the email:
- Thank them and show I understand the request, in one sentence
- Explain my constraint in one or two sentences, naming my current priorities
- Offer the options I list below as a short bulleted list
- End by asking which option they prefer, or offering a quick chat
- Under 150 words. Calm, respectful, and firm.

Rules:
- Use only the facts I give you. Do not invent workloads, dates, or reasons. If something is missing, write (ADD DETAIL).
- Only offer options I've listed. If I haven't listed any, ask me what I'm willing to offer before you write.
- No over-apologizing, no complaining, and no hinting that the request is unreasonable.

Also give me a short, neutral subject line.

What my boss asked for (remove anything confidential first):
[paste their email, or describe the request]

What I'm working on now:
[list your current priorities and their deadlines]

Options I'm willing to offer:
[for example, something you could pause, a later start date, or a smaller version of the task]

Act as an experienced project manager who is good at renegotiating deadlines without drama. Help me write an email asking to move a deadline I can't meet without hurting the quality of the work.

Before you write, briefly check:
1. What the person most needs by the original date, using only what I tell you
2. Whether a partial or smaller delivery by the original date could meet that need, using only the work I describe

Then write the email:
- Open by saying I'm committed to the work and the goal
- Say what's done and what's left, in one or two plain sentences
- Explain what would be at risk if we keep the current date, only if I tell you; otherwise write (ADD DETAIL)
- Offer the options as a short list: my proposed new date for the full work, plus a smaller version by the original date only if I say that's possible
- End by asking which option works for them
- Under 170 words. Confident and cooperative.

Rules:
- Use only the dates, tasks, and reasons I give you. Do not invent estimates, dates, or reasons. If something is missing, write (ADD DETAIL).
- Don't blame anyone or criticize how the deadline was set.
- Apologize once at most. Don't call the deadline "unrealistic."

Also give me a short subject line that names the proposed new date.

Who set the deadline, and the original date:
[their name or role, and the date]

What they most need by the original date, and what's at risk if it stays (optional):
[or leave blank]

What the work is:
[describe it]

What's done and what's left:
[list it]

My proposed new date:
[the date you can actually deliver]

Could a smaller version be ready by the original date? If so, what:
[yes and what it would include, or no]

Updates and tricky moments

Act as an organized chief of staff who knows managers skim status updates. Turn my rough notes into a short weekly status update email for my manager.

Steps:
1. Sort my notes into done, in progress, and blocked
2. Put the most important items first, not in the order I wrote them
3. Pull out anything I need my manager to decide or help with

Then write the email:
- Subject line: "Weekly update" plus the dates I give you
- One sentence on where things stand overall (on track, at risk, or blocked), based only on my notes
- Done this week: up to 3 bullets
- In progress: up to 3 bullets, with due dates only if they're in my notes
- Risks or blockers: up to 2 bullets, or "None"
- Need from you: one line, or "Nothing this week"
- Under 150 words. One line per bullet.

Rules:
- Use only what's in my notes. Do not invent progress, dates, numbers, or risks. If something is missing or unclear, write (ADD DETAIL).
- Don't bury or water down a risk or blocker.
- Leave out routine tasks that need no attention, and filler like "busy week."

Week this update covers:
[the dates]

My notes for the week (remove anything confidential first):
[paste your notes]

Act as a team lead known for clear, respectful handoffs. Help me write an email handing off a task to a coworker.

Before you write, check my details for:
1. What finished looks like, in things that can be checked
2. The deadline
If either is missing, ask me before you write.

Then write the email:
- Open with the request and why it matters, in one or two sentences
- What done looks like: 2 to 4 short bullets
- The deadline as an exact date (and time, if I give one), and how to hand the work over
- A check-in before the deadline, only if I give one
- What they can decide on their own, if I tell you
- Where to find what they need, and who to ask with questions
- End by asking them to reply to confirm they can take it on, or to tell me if the timing doesn't work
- Under 200 words. Friendly and direct. Don't tell them how to do every step.

Rules:
- Use only the details I give you. Do not invent deadlines, files, people, or requirements. If something is missing, write (ADD DETAIL).
- No vague timing like "ASAP" or "when you get a chance."

Also give me a subject line with the task name and the due date.

The task and why it matters:
[describe it]

What done looks like:
[what the finished work should include, its format, and where it goes]

Deadline:
[the date, and a time if it matters]

Check-in before the deadline (optional):
[a date, or leave blank]

What they can decide on their own (optional):
[or leave blank]

Resources and contacts:
[files, links, or people they can go to]

Act as a calm, experienced manager who helps people own mistakes in a way that builds trust. Help me write an email admitting a mistake I made at work and explaining how I'm fixing it.

Write the email in this order:
- What happened: own it plainly in the first one or two sentences, using "I"
- The impact: who or what was affected, stated factually. Don't make it sound bigger or smaller than it is.
- The fix: what's already done and what's left, as short bullets, with dates only if I give them
- Prevention: one sentence on what I'm changing so it doesn't happen again, only if I give you one
- Close by offering to talk it through, and ask for input only if I list some below
- Under 170 words. Calm and accountable. Apologize once, clearly.

Rules:
- Use only the facts I give you. Do not invent causes, impact, fixes, dates, or prevention steps. If something is missing, write (ADD DETAIL).
- No excuses, no blaming other people or tools, and no hiding phrases like "mistakes were made" or "an error occurred."
- Don't soften what went wrong. Don't grovel or apologize over and over.

Also give me 2 short, plain subject line options.

What happened:
[describe the mistake]

Who was affected, and how:
[the people or work it affected]

What I've done to fix it, and what's left:
[list it, with dates if you have them]

What I'm changing so it won't happen again (optional):
[or leave blank]

Who I'm sending this to:
[your manager, your team, or others]

Input I need from them (optional):
[or leave blank]

Act as a calm, experienced coworker who is good at cooling down tense emails. Help me reply to a frustrated or blunt email from a coworker.

First, if the email involves harassment, threats, or another serious conduct issue, don't draft a reply. Tell me to talk to my manager or HR instead of replying by email.

Otherwise, before you write, briefly tell me:
1. What they're actually concerned about and what they want
2. Which of their points are fair and which aren't, based only on the facts I give you

Then write the reply:
- Open by acknowledging the real issue in one sentence. Don't comment on their tone.
- Address the facts plainly. If something they said is wrong, correct it gently, without arguing.
- If I made a mistake, own it plainly. Don't apologize for things that weren't my fault.
- End with one concrete next step: a fix, a time, or an offer to talk in person or on a call
- Under 150 words. Steady and respectful.

Rules:
- Use only the facts I give you. Do not invent explanations, excuses, or promises. If something is missing, write (ADD DETAIL).
- Don't mirror their tone, get defensive, or blame anyone.
- Remove anything that could read as sarcastic or passive-aggressive.

After the reply, remind me in one line to wait a while before sending it.

The email I received (remove names and personal details first):
[paste their email]

What actually happened, from my side:
[the facts]

What I can offer or do next:
[a fix, a time to talk, or other next step]

Clean up your emails

Act as an experienced operations manager who handles a lot of email. Help me write one short reply to the email thread below that answers everything I was asked.

Steps:
1. Read the whole thread, including quoted replies, and list every question, request, or decision aimed at me or still open, with who asked it
2. Combine items that were asked more than once
3. Put decisions and deadlines first

Then write the reply:
- Answer each item directly, in one or two sentences. Use short bullets if there are more than three.
- Don't summarize the thread back to everyone or bring up new topics.
- End with the next step and who owns it, only if that's clear from the thread or my answers.
- Under 150 words.

Rules:
- Use only the thread and my answers below. Do not invent answers, dates, numbers, decisions, or commitments.
- If I haven't given you an answer for an item, write (ADD DETAIL) in its place. Don't guess what I'd say.
- Keep the existing subject line with "Re:" unless it's misleading.

Show me the list of items you found first, so I can check nothing was missed, then the reply.

The thread (remove confidential or personal information first):
[paste the thread]

My answers or notes on each point:
[what you want to say on each question]

Act as an organized project coordinator who writes clear meeting recaps. Turn my rough notes into a recap email for everyone who attended.

Steps:
1. Sort each line of my notes into: decision, action item, open question, or background
2. Combine repeated points and rewrite fragments as clear sentences without adding anything. If a fragment's meaning is unclear, keep it and mark it (CONFIRM).
3. Drop side discussion that didn't lead anywhere

Then write the email:
- Subject line: "Recap:" plus the meeting name and date I give you
- One sentence on what the meeting was for, only if it's clear from my notes; otherwise (ADD DETAIL)
- Decisions: one per line
- Next steps: each action with its owner and due date
- Open questions: anything still unresolved
- Close by asking attendees to reply with any corrections
- Under 250 words. Neutral and plain.

Rules:
- Only include decisions, owners, and dates that are clearly in my notes. Never add new ones.
- If an action has no owner or due date in my notes, write "Owner: (ADD DETAIL)" or "Due: (ADD DETAIL)".
- If it's unclear whether something was decided or just discussed, put it under Open questions and mark it (CONFIRM) so I can check.
- No opinions, commentary, or who said what, unless it's part of a decision.

Meeting name and date:
[the meeting and the date it happened]

Who attended:
[names or roles]

My notes (remove confidential or personal information first):
[paste your notes]

Act as a sharp business editor who makes work emails shorter and clearer. Edit my draft below before I send it.

Steps:
1. Say in one sentence what the email needs to do and what the reader should do next
2. Move the main point or request to the top
3. Cut repeated, off-topic, or over-hedged sentences ("just," "I think," "sorry to bother you")
4. Use bullets for any list of three or more items
5. Check that every name, date, number, and request from my draft is still there

Then give me:
- A clearer subject line
- The revised email, noticeably shorter than my draft
- 3 short bullets on the main changes you made

Rules:
- Keep my voice and level of formality. No buzzwords or exclamation points.
- Do not add new facts, dates, promises, or details. If something seems missing or unclear, tell me after the email instead of filling it in.
- Don't turn firm requests into vague suggestions, and don't make it sound harsher than I meant.

My draft (remove anything confidential first):
[paste your draft]

Who it's going to (optional):
[your boss, a coworker, or your team]

FAQ

More prompt packs