Writing prompt · Built for Apollo

Write a kind rejection email

Turns a blunt or over-apologetic rejection into a short, clear message that respects the reader's time without sounding cold.

The prompt

You are helping me rewrite a rejection message so it is kind but honest.

Here is my draft:
[PASTE YOUR DRAFT]

The person is: [WHO THEY ARE, e.g. a candidate we interviewed twice]
The real reason is: [THE ACTUAL REASON]
What I can and cannot say publicly: [ANY CONSTRAINTS]

Rewrite it so that:
- The decision is clear in the first two sentences, with no false hope.
- The reason given is true, even if it is less specific than the real one.
- There is no filler sympathy, no "we were so impressed", no promises of future contact I cannot keep.
- It is under 150 words.

Then list, separately, any sentence in my original draft that would give the reader false hope, and say why.
Try in Rekdan

Replace the outlined parts before running

  • [PASTE YOUR DRAFT]
  • [WHO THEY ARE, e.g. a candidate we interviewed twice]
  • [THE ACTUAL REASON]
  • [ANY CONSTRAINTS]

When to use this

Rejection emails fail in two directions. Written quickly they read as cold, and the reader spends a day deciding whether they did something wrong. Written carefully they fill up with softening — "we were so impressed", "please do stay in touch" — until the actual decision is buried and the reader comes away thinking a door is still open when it is not.

This prompt separates the two jobs. It rewrites the message so the decision lands early and the reason given is true, and then it reports back on the sentences in your draft that promise something you did not mean. That second half is the useful part: false hope is almost always accidental, and it is very hard to spot in your own writing.

How to use it

  1. Paste the draft you already wrote

    Do not clean it up first. The prompt is more useful when it can see the hedging you would have left in, because the second half of the answer is about exactly that.

  2. Tell it the real reason, even if it is blunt

    The real reason stays between you and the model — it is what lets the rewrite pick a true, sayable version instead of inventing a diplomatic one. If the real reason is budget, say budget.

  3. Name what you cannot say

    Legal constraints, an unannounced restructure, a decision that is not yours to explain. Without this the rewrite will sometimes be more specific than you are allowed to be.

  4. Read the false-hope list before the rewrite

    Whether or not you use the rewritten text, that list tells you what your own draft was accidentally promising.

Variations

For a vendor or supplier you may work with later

Rewrite this rejection so it is clear but leaves a genuine door open — only if the door really is open.

Draft: [PASTE YOUR DRAFT]
Why we chose someone else: [THE ACTUAL REASON]
Would we genuinely consider them again, and for what: [BE SPECIFIC, OR WRITE "NO"]

If the answer to the last question is "NO", do not soften the ending. Say the decision is final, politely.
Keep it under 120 words, then list any sentence that overstates the chance of future work.

For an internal candidate

Rewrite this rejection for someone who works here and will see me tomorrow.

Draft: [PASTE YOUR DRAFT]
Their role: [ROLE]
The real reason: [THE ACTUAL REASON]
What development would actually change the outcome: [BE CONCRETE, OR WRITE "NOTHING SHORT TERM"]

Requirements: the decision is unambiguous, the next conversation is offered as a real meeting rather than a vague "let's chat", and nothing implies the role may reopen unless I said it would.
Under 150 words. Then list anything in my draft that a colleague would reasonably read as a promise.

Where it falls short

  • When the decision is not actually finalThe prompt is built to remove hedging. If you are still deciding, it will make you sound more certain than you are — write that message yourself.
  • When the real reason cannot be paraphrased truthfullyIf every honest version of the reason is something you are not allowed to say, no rewrite fixes that. Say less and say it is confidential, rather than letting the model find a comfortable half-truth.
  • In jurisdictions with specific notification rulesSome hiring and procurement rejections have required wording or timelines. This prompt knows nothing about your local rules; check the output against them.