Polite Decline Email Prompt: Say No Clearly

What this prompt does

A polite decline email prompt turns a request you've already decided to refuse — a project, a meeting, a discount, a favour, a speaking slot — into a short email that says no within its first two sentences, gives a reason only when it's one you'd stand behind, and offers the thing you'll follow through on instead. You supply the decision, the real reason, and what's on offer. The model supplies the wording, the order, and a note on what it left out. It doesn't decide for you, and it doesn't invent a reason you didn't give it.

Ask a chat window for "a polite way to say no to this" and you'll get 180 words, three apologies, and the answer somewhere in paragraph three. The recipient reads the first line in a notification, sees "Thank you so much for thinking of me," and assumes it's a yes until it isn't.

That's worse than a blunt no. They've now been let down twice.

This page starts from a blank reply box. The tone adjustment prompt is for the moment after — you've written the no, it came out cold, and you want the temperature changed without the content moving. The refund request response prompt owns the decline where money has already changed hands and a policy makes the call; send those there.

The prompt

Write a decline email from the inputs below. I've already decided. Your job is the wording, not the decision.

**What they asked, in their words:** [PASTE the request, or one sentence summarising it]
**Who they are to me:** [CLIENT / FORMER CLIENT / COLLEAGUE / STRANGER / A FRIEND OF A CLIENT — and roughly how long we've dealt with each other]
**What I'm saying no to:** [THE SPECIFIC THING — the whole request, or one part of it]
**The real reason:** [ONE LINE]
**Can the reason be said?** [YES, as written / YES, but softened / NO — write the no without a reason]
**What I can offer instead:** [SOMETHING I'LL FOLLOW THROUGH ON — a later date, a smaller version, a referral, an answer in writing — or "nothing"]
**Door position:** [CLOSED — don't invite them to ask again / AJAR — say what would change my answer / OPEN — ask again after DATE]
**Reply or new thread:** [REPLY / NEW — and write a subject line if new]
**Voice samples (optional):** [PASTE 2–3 emails the sender wrote themselves, so the no sounds like them]
**Length cap:** [DEFAULT 120 words]

Output:
1. The email. The no sits in the first or second sentence, and those two sentences together fit in a phone notification, which is all many people read before deciding whether to open it.
2. One thank-you at most and one apology at most. Use the reason exactly as I marked it: as written, softened, or absent. Add no other reasons.
3. Make any offer exactly what I typed. If I said "two names", the email says two names, not "happy to help however I can".
4. Close to match the door position: closed ends warmly with nothing to reply to; ajar states the condition in one sentence; open names the date.
5. After the email, two lines: "Left out:" (anything from my inputs you didn't use, and why) and "Before sending:" (anything the email commits me to that I should confirm).

Rules:
- Every sentence is about the decision, the reason, or the offer. Sentences about my feelings get cut.
- Write in first person as the sender. If voice samples are pasted, match their greeting, sign-off and sentence length; otherwise write plain, warm and direct.
- Keep the email shorter than the request it answers.
- If an input you need is missing, put a question in its place in square brackets rather than guessing.

How to use it

1. Decide before you prompt. The draft will show you if you haven't. Hedged verbs, a "probably not", a no that asks for their thoughts — those come from a decision that isn't finished, and no rewrite fixes them. If you're still weighing it, the pros and cons prompt is the page before this one.
2. Give a reason you'd let them repeat. The test is whether you'd be comfortable hearing the recipient quote it to someone else. "I'm booked through the 20th" passes. "The last project with you was a slog" doesn't, so mark it unsayable and the prompt writes the no without one. Julian Givi, whose research on declined invitations is cited below, told NPR that the bare "no thanks" he once got from his own mother was the reply that stung, and that citing a lack of money tends to get more understanding than citing a lack of time.
3. Offer only what you'd do this month. Givi's own habit is what he calls the "no, but": can't do this, would do that. It works while the "that" is real. An offer you won't honour is a second decline you'll be writing in November.
4. Read the first two lines as a notification. Cover everything after them and ask whether the person knows the answer. If they don't, send the draft back with "the no moves to sentence one."
5. Count the words against the request. A decline that runs longer than the ask reads as guilt. The default cap is 120, and a reply to a two-line message should be shorter still.

Example output (partial)

Inputs: writing as Priya, a freelance brand designer, replying to a former client (two projects in 2025, both pleasant) who asked for a 24-page product catalogue by 6 October at the flat fee she'd normally charge for an eight-page piece. Reason as typed: "booked through 20 October, and a 24-page catalogue is a three-week job at my rates" — sayable as written, though she asked that the fee not be negotiated in this email. Offer: two designers who take catalogue work at short notice, or the same job from 27 October quoted separately. Door: ajar. Reply in thread. Cap 120.

Re: Catalogue for the autumn range

Hi Daniel,

Thanks for thinking of me for the catalogue. I can't take it on for 6 October: I'm booked through the 20th, and a 24-page catalogue is a three-week job for me, so you'd be getting rushed work.

Two things that would work. I can send you two designers I've worked alongside who take catalogue jobs at short notice, or I can do it myself from 27 October, in which case I'd quote it separately at my usual rate. Tell me which, and you'll have names or a quote by Friday.

Priya

Left out: the fee gap. You marked it as not for this email, so the timing reason carries the no and the rate moves to the quote. Before sending: the 27 October start is now a commitment — confirm it's free.

The request was 140 words. The reply is 93, and the no is in its second sentence — a phone shows "Thanks for thinking of me for the catalogue. I can't take it on for 6 October" and nothing else needs opening.

Variations

Declining a meeting

Add "The request is for a call. Decline the call, not the topic: offer to answer their questions in writing by a named day." Most meeting requests are a question wearing a calendar invite. The meeting request email prompt is the other side of this exchange — what a request looks like when it's written well enough to say yes to.

Declining on someone else's behalf

Add "Write as [CLIENT NAME], first person. The reason must be one they've given me and the offer one they've approved; where either is missing, write [NEEDS APPROVAL] in its place instead of choosing for them." A virtual assistant declining as a client is the most common use of this page, and the reason that can't be said is usually the one the client said out loud. More on the client-inbox setup in prompts for virtual assistants.

Declining scope on a live project

Add "This is a request for extra work inside a project that's already running. The no is to the addition, not the project: name the line in the agreement it falls outside, offer to quote it as a separate piece, and keep the current deadline untouched." The out-of-scope section of your business proposal is the sentence to point at.

When the no needs a call

Some declines get taken personally whatever the wording — ending a five-year retainer, turning down a friend's business. Add "This email confirms a decision I'll deliver by phone first. Two sentences: what I've decided, and when we spoke." The call carries the reason, and the difficult conversation prep prompt is for the call.

Common pitfalls

• Don't bury the no. The tell is a decline you can't find by reading only the first two lines. Warmth goes around the no, never in front of it.
• Don't give a reason you'd have to defend. "I'm at capacity until January" ends the thread; "I'm not sure it's the right fit" opens a negotiation about fit.
• Don't apologise twice. A second sorry invites them to reassure you, and now you owe a reply to that.
• Don't offer what you won't do. The "no, but" only works while the "but" is true — make the offer small enough to be certain of.
• Don't let the model choose. If the draft comes back with "I'd love to, but I'm not sure I can," the input was a maybe. Decide, then re-run.

Who uses this prompt

• Virtual assistants writing as a client: the fourth decline before lunch, in a voice that isn't yours — the voice samples input exists for you. More in prompts for virtual assistants.
• Freelance writers and designers turning down work: the under-priced job and the rush job, which tend to arrive together. See prompts for freelance writers.
• Small business owners: the discount request, the sponsorship ask, the partnership pitch that would cost more than it brings. See prompts for small business owners.
• Consultants holding a scope: the extra workshop that "should only take an hour." See prompts for consultants.

77% of the participants in Julian Givi's research had accepted an invitation they didn't want to, and across five studies published in the Journal of Personality and Social Psychology the people declining overestimated how upset the inviter would be, per West Virginia University's summary of the work. His explanation is the useful part: inviters weren't hearing the no on its own — they were weighing the deliberation behind it. Those were social invitations, not client emails, so treat the carry-over as a hunch. It's still why the prompt spends one sentence on the reason and none on the feelings.

ChatGPT, Claude, and Gemini all run it unmodified. Anthropic's prompting best practices say to tell the model what to do instead of what not to do, and to be specific about output format and constraints — which is why the rules say "the no sits in the first or second sentence" rather than "don't bury the no", and why the length cap is a number. In the example, the sentence that did the work was "a 24-page catalogue is a three-week job for me": the one line of deliberation Givi's inviters were listening for.