The email you’ve been putting off, sent before lunch

Almost everyone has one waiting: the email that says no, tells a client a date will slip, answers a complaint or sets a limit with someone you’d rather not upset. The email itself is usually short. What drags on is the postponing: each day you reread the thread, compose two sentences in your head and move it to tomorrow, while the other person waits and the news gets no easier to give.

The method below splits the job in two. You decide what to say, bluntly, and an AI assistant handles how it sounds, under rules that stop it from watering your message down. It works the same in Claude, ChatGPT, Gemini or Copilot. By lunch, that email will be in your sent folder, and you’ll have two prompts saved for the next hard one.

Pick the email

Choose the one you’ve moved to tomorrow at least twice. If several qualify, take the one someone else is waiting on to get on with their work. It might be a project manager telling a sponsor the launch moves by a month, a teacher explaining to a parent why a grade stands, a nonprofit coordinator telling a partner the program won’t run next year, or a shop owner turning down a discount for a customer of ten years.

Write the blunt version in two minutes

Set a timer and write the email as if tone didn’t matter, the way you’d explain it to a colleague you trust: the facts, what you need from the reader, and by when. Skip the greeting and the apologies; typos can stay. If you can’t say what you need from them, you’ve found the real reason the email has waited this long, and no assistant can decide that for you.

If the email names a client or a colleague, write CLIENT or COLLEAGUE instead and put the real names back just before you send, at least until you know what your assistant does with what you paste. Before you upload a client document lists what to check.

Let the assistant fix the tone

With the facts and the decision on the page, what’s left is tone, and tone is the part an assistant handles well. Paste prompt 1 into a new conversation, fill in the brackets and add your draft at the end.

Below is a rough draft of an email I need to send. Rewrite it.

Rules:
- Keep every fact, number, date and request in my draft. Add no new facts, reasons or promises.
- Put what I need from the reader, with its date, in the first three lines.
- Write two versions, one firm and one warm, each under 150 words.
- Include at most one apology, and only for this: [WHAT YOU GENUINELY OWE AN APOLOGY FOR, or "nothing"].
- No filler such as "I hope this finds you well" or "Thank you for your patience."
- Suggest a subject line that says what the email is about.
- After the two versions, list every change you made to my facts or requests, and anything you left out. If there were none, say so.

The reader: [WHO THEY ARE AND HOW YOU WORK TOGETHER]

My draft:
[PASTE YOUR BLUNT VERSION]

If your draft is long because the facts are, raise the word limit. Then pick the version that sounds like you with that reader, or ask for “the firm one, with the warm one’s last paragraph.”

Answer the objections before they arrive

Prompt 2 goes in the same conversation:

Here is the version I'm going to send:

[PASTE THE VERSION YOU CHOSE, WITH YOUR EDITS]

Read it as the person receiving it. What are they most likely to push back on or ask about? List up to four points, most likely first. For each, write one sentence I could add to the email to answer it. Don't rewrite the email.

Add the one or two that matter, in your own words if the assistant’s sound stiff. If an objection has no good answer, leave it out of the email and think it through now, because that is what the reply will be about.

A worked example

For example, Dana, a made-up project manager, has to tell a client that a survey report due this Friday will be a week late. Two of the five regional data files arrived incomplete, and the new date depends on the client sending complete ones. Her two-minute version:

Report won't be ready Friday. North and Coastal data files came in incomplete, we found out Tuesday. Need complete files by Wednesday noon. Then new date is Friday the 20th. If not, it slips again. Other three regions done.

The firm version after both prompts, with one sentence she added from the second:

Subject: Survey report moves to Friday the 20th; two files needed by Wednesday

Hi Maria,

The survey report won't be ready this Friday. To deliver it on Friday the 20th, we need complete North and Coastal data files by noon on Wednesday.

The versions we received are incomplete; we found the gaps on Tuesday. The other three regions are finished and written up, and I can send you that part today if it helps your planning.

If the files arrive after Wednesday, the date will move again.

Best,
Dana

The request and its date sit in the first lines, and nothing from the blunt version is missing. The one addition, the offer to send the finished regions, answers the objection Dana expected most: Maria may have her own deadlines to meet.

What the assistant gets wrong, and a two-minute check

Assistants are good at tone and bad at holding a line. Left alone, they soften a request until it disappears (“whenever you have a moment, it would be wonderful if…”) and take the date with it. They add apologies you don’t owe, which make a week’s delay sound like a disaster. They pad with thanks for your patience and a closing paragraph that repeats the first. And they slip in promises you never made, such as “this won’t happen again.” The rules in prompt 1 hold most of this back; the check below catches what gets through.

Before you send, take two minutes:

1. Read only the subject line and the first three lines. Is the request there, with its date?
2. Put your blunt version next to the email and tick off every fact, number and date. The assistant’s list of changes points you to the likely spots, but it can miss its own edits.
3. Count the apologies. Cut any beyond the first, and that one too if the fault wasn’t yours.
4. Read it aloud. Would you say this to their face? Rewrite any sentence you wouldn’t.

When to pick up the phone instead

Some of these shouldn’t be emails at all. If someone is angry, or you are, a call clears up a misunderstanding on the spot instead of over several replies. The same goes for a relationship at real risk, such as a long-standing client, and for news that changes someone’s plans or income, since they’ll have questions you can’t predict. Write the blunt version anyway: it becomes your notes for the call. Afterward, a short email confirming what you agreed is a job this method handles well.

Try it today

1. Pick the email you’ve moved to tomorrow at least twice.
2. Set a timer for two minutes and write the blunt version.
3. Run prompt 1, choose a version, run prompt 2 and add what matters.
4. Do the two-minute check and send it.
5. Save both prompts where you’ll find them again; Keep your best prompts in one place shows a simple way.

Your finish line is that email in your sent folder before lunch, or before you leave today if lunch has already happened. Write down the time you started the blunt draft and the time you pressed send. The next hard email starts at step 2, because the prompts are already saved, and your own two timestamps tell you what it really costs, which makes it much harder to put off.

Where to go next

If your email asked for something by a date, you’re now the one waiting. A six-column tracker for everything you’re waiting on gives that reply a row and a day to nudge, along with every other answer you’re owed. If the same kind of hard email comes back every month, such as declining a request or announcing a delay, build a template from your sent folder and stop writing it from scratch. And if what you’ve been putting off is bigger than an email, such as a proposal or a report, let the assistant interview you before it writes a word.