How to Say No in an Email: 7 Templates That Keep the Relationship

The no is the email you rewrite the most. You type it, delete it, soften it, add a paragraph explaining yourself, delete that paragraph, start again. Twenty minutes for four sentences. And the version you finally send is usually worse than the one you wrote first, because every round of softening pushed the answer further down the page. Here is the shape that fixes it and seven templates for the nos that actually turn up.

Nobody minds a no

This is the part most advice gets backwards. People assume the difficulty is the answer and spend their effort disguising it. In practice the answer is rarely the problem. Almost everyone has been turned down before and survived it.

What people do mind is hunting for the answer. They mind reading four paragraphs of warmth and then discovering, somewhere near the bottom, that the warmth was cushioning. They mind a maybe that was always going to be a no, because a maybe costs them a week of planning around something that was never happening. And they mind the follow-up round of guessing, where they cannot tell whether you have said no, said not yet or said convince me.

Clarity is the kindness here. Softening is what feels kind to the person writing.

The shape of a good no

Four parts, in this order. Then you stop.

• The answer, in the first line. Not the third paragraph. If someone has to scroll to find out whether you are doing the thing, the email has failed regardless of how nicely it is written.
• One reason. Exactly one. This is the rule people break most. Three reasons do not sound three times more justified, they sound like excuses. Each one hands the other person something separate to argue with. Give the real reason and stop.
• What you can do, if anything. An alternative turns a closed door into a redirection. Only offer one you actually mean. A fake alternative is worse than none, because now you have to decline twice.
• The door, left open. One warm line. Then stop writing. Every extra apology after the decision makes the decision sound negotiable.

That last point deserves its own sentence, because it is the difference between a no that holds and a no that gets tested. Over-apologising reads as an invitation. If you say sorry four times, you have signalled that you feel bad enough to be talked round. A reasonable person will try. Apologise once if you have genuinely caused inconvenience. Otherwise do not apologise at all. Declining work you cannot take is not a wrong you have committed.

Seven templates for saying no

Why the same words matter on the second no

Template seven is the one people get wrong. The mistake is subtle. When someone pushes back, the instinct is to find a better reason, a more convincing one, something that will finally land. It is a trap. Producing a new justification tells the other person that your first reason was not the real one, which means this one probably is not either, which means it is worth pushing a third time.

Repeating yourself feels blunt. It is actually the most respectful option available, because it treats the first answer as having been true.

Three things that quietly wreck a no

• "Unfortunately." It is a signal word. Readers see it and brace, then stop reading properly. Say the thing instead.
• "At this time" and "right now." These turn a no into a not-yet whether you meant that or not. If you do mean not-yet, say when. If you mean no, delete the qualifier.
• Blaming a policy you control. "Our policy does not allow it" is fine when a policy genuinely exists. When it is really your decision, hiding behind a rule is transparent and slightly insulting. Own it.

The part that actually costs you the afternoon

None of this is hard to understand. It is hard to execute at four in the afternoon on the fourth awkward email of the day, when the person you are declining is someone you like and want to keep. That is when the softening creeps back in, the apologies multiply and the answer drifts down the page again.

That gap is what ReciteMail is for. You give it the decision in one line, something like tell them no on the extra round and offer a quote instead. It drafts the whole thing in your own voice, learned from emails you have already sent. Firm comes out firm rather than apologetic, because you are not writing it while feeling guilty. You read it, change anything you want and send it yourself. Nothing connects to your mailbox and nothing sends without you.

Agencies use this most for scope conversations. The same shape does the work when you are chasing a late invoice or declining a refund request. If you are building a proper library of these, the guide on templates that do not sound like templates pairs with this one.

Common questions

How do you politely say no in an email?

Put the answer in the first line, give one plain reason, offer an alternative if you genuinely have one, then leave the door open and stop writing. Politeness comes from clarity and warmth rather than from softening. A no buried in paragraph four reads as evasive, not kind.

Should I apologise when declining a request?

Once at most and only if you have actually caused inconvenience. Repeated apologising signals that the decision is negotiable and invites a second attempt. You can be warm without being sorry. Saying no to work you cannot take is not something that requires an apology.

Do I have to give a reason for saying no?

One line helps, because a bare no feels abrupt and leaves people guessing at something worse. Do not give three. Every additional reason is another thing the other person can argue with. A stack of justifications reads as an excuse rather than a decision.

What do I do if they ask again after I said no?

Repeat the same answer in the same words rather than inventing new reasons. Changing your explanation suggests the first one was not the real one. Acknowledge that you have heard them, restate the decision plainly and say what would need to change for the answer to be different, if anything would.

← Back to the blog