You already know the answer. The hard part is writing it down, and most people write it soft. That’s where a refusal goes wrong: softened until the reader can’t tell what the answer was. So they work it out a day later, or a week later, and by then you’ve paid for it. A second email, a slot somebody held for you, and a harder conversation two weeks on.
The repair is small. Put the answer where the reader lands first. Give one true reason. Name a door only if you’d walk back through it. Then stop. Most of what people add to soften a refusal is the same thing that makes it read as negotiable.
- The reader is hunting for the decision, not for your tone. Put it in the first two sentences, or they’ll pick the reading they prefer.
- A refusal framed as an inability invites somebody to remove the inability. A refusal framed as a practice stands.
- The discomfort you feel writing it is a poor guide to how it lands. That’s been measured, and the error runs one way.
- The expensive part is rarely the answer. It’s the door you left open and didn’t mean.
This piece is about the refusal itself. Tone is its own subject, and courtesy in email is better measured by how little work you hand over than by how warm the wording is, which is worked out in the polite reminder email. A second attempt at a request somebody left alone is a different message with a different job, and it’s in the follow-up email that gets answered.
Why a soft no costs more
Out loud, a refusal arrives before the words do. There’s a pause. The pitch drops. Somebody says “ah, look”, and the other person has already heard it. The rest is courtesy, and both people know it.
A mailbox carries the paragraph and nothing else. A hedged paragraph is genuinely ambiguous. “This might be tricky for us in the current quarter” reads two ways to a reasonable person acting in good faith. They take the reading they were hoping for, and that’s sensible of them. They have their own week to plan, and a maybe is more useful to them than a no.
So the softening you added out of kindness buys three things you’d rather skip. A second message, which they write and you answer. Their arrangements, because somebody holding a maybe stops looking, holds a date, and sometimes tells their own client. And two weeks of carrying an answer you’d already reached.
Then the plain version lands. By now it’s a refusal plus a broken expectation, and the broken expectation is the part people remember. Being turned down costs you very little. Having somebody build a month around an answer you’d already made, and hadn’t said, costs you plenty.
There’s a check that takes four seconds. Cover your draft except the first two sentences. Ask whether somebody who knows none of the background could report the answer correctly. The answer, not the reasoning.
The fear is bigger than the fallout
People soften because of a forecast. You’re predicting what the other person will do when the answer arrives, and that forecast has been tested more than once.
Jingyi Lu, Qingwen Fang and Tian Qiu, at East China Normal University, ran seven studies with 2,132 participants. Four supplementary studies added a further 1,470. The work was published in the Journal of Experimental Psychology, Applied in 2023. Their finding was that “rejecters overestimated these negative consequences”, and that the overestimation “persisted in hypothetical (Studies 1 and 3), real-life (Study 2), and incentivized (Study 4) settings”. People turning down a request expected to be badmouthed, judged unhelpful and not helped in return. They expected it more than the evidence warranted.
Julian Givi and Colleen Kirk reached the same place from the other side, in the Journal of Personality and Social Psychology in 2024. Studying people declining social invitations, they found that “invitees have exaggerated concerns about how much the decline will anger the inviter, signal that the invitee does not care about the inviter, make the inviter unlikely to offer another invitation in the future, and so forth”. Their pilot holds the line worth keeping: “77% of respondents had accepted an invitation to a social activity that they did not want to attend because they were concerned about the negative ramifications that would have emerged had they declined”.
The mechanism they name is the useful part. The person declining watches their own decision and replays the deliberation behind it. The person receiving it watches their own week. You’re grading an essay nobody else read.
Take the direction and leave the numbers. One line of work is about favors. The other is about museum trips with friends. A consulting proposal is a third thing, carrying money and obligation that a lunch invitation never carries, and these samples are somebody else’s clients. The direction still holds, and the direction is what makes people write worse email. Softening is a response to discomfort rather than to a risk you weighed, and it stops the discomfort for about as long as it takes to hit send. That’s a poor instrument. It should buy neither three days of delay nor four paragraphs of cushioning.
Why I don’t beats I can’t
One wording change carries more evidence than anything else in this piece, and it turns on a single word.
Vanessa Patrick and Henrik Hagtvedt tested two refusal frames in the International Journal of Research in Marketing in 2012. In their first study, 44 undergraduates in a professional selling class were given about three minutes each to sell an annual newspaper subscription. The prospective customers were trained confederates working from a script. The script refused in one of two ways: “I don’t make spontaneous decisions about money”, or “I can’t make spontaneous decisions about money”. Everything else about the encounter was the same.
Afterwards the salespeople rated the refusal: how convinced they were by it, how effective it had been, and how far they respected it. The “don’t” version scored 7.05 on a nine-point scale, against 5.80 for “can’t”. On the conviction behind it, 7.06 against 5.52. The authors’ account is simple. “I don’t” reads as identity, something the person is. “I can’t” reads as an impediment, and an impediment is something the other side can offer to remove.
Forty-four students role-playing a sale is a small study, spoken rather than written, in one domain. Your own sent folder shows you the same mechanism for free. “I can’t do it this month” comes back as “what about next month”. “I can’t do it at that price” comes back as a different price. Every inability you name is a puzzle you’ve handed somebody, and some of the people you write to are good at puzzles.
So where the true thing is a practice, write it as one.
- “I can’t do it for that budget” becomes “we don’t take projects under twenty thousand.”
- “I can’t get to it before the 30th” becomes “we don’t start work we can’t finish, and nothing about this finishes by the 30th.”
- “I can’t really do free consultations” becomes “I don’t do unpaid scoping calls.”
One caution, worth writing down. Quote a policy you actually have. A rule you made up in the four seconds before sending is checkable, the same person quotes it back to you next year, and something you did for somebody else contradicts it. Where the truth really is a temporary constraint, say the constraint and then close the negotiation yourself. Name what would have to change, and say plainly whether it’s going to.
The order that keeps it from reopening
Four moves, and the order does most of the work.
One line of acknowledgment, if you have one that’s true. This is the one thing that earns a place ahead of the answer, and it earns it by doing real work. It tells the other person the ask was reasonable, which is what they’re quietly asking. One line does it. “Thank you for thinking of us on this” is a complete line. Then stop, because a second line of warmth starts to read as a run-up.
The answer, in the second sentence at the latest, in the words you’d use out loud. “We’re not going to take this one on.” “I’m going to pass.” “No, not this year.” On the page it looks harsher to you than it does to them, and the section above is why. Most refusals are replies, and a reply belongs on the existing thread, where the ask sits underneath and speaks for itself.
One reason, and only one. What goes in it is the next section.
A close that settles it. People miss this move most often. A refusal ending “let me know your thoughts” or “does that work for you” reopens what it just closed. A question is an instruction to reply, and the reply you’ve invited is an argument. End on a statement instead. “I’ll leave it there.” “Nothing needed in reply.” “I hope it goes well.”
A word on apologies, since a refusal is where they multiply. One is plenty, and zero is often better. “Sorry, we can’t take it” costs you nothing. “I am so sorry, I feel terrible about this, I really wish I could” turns your decision into something the other person now has to manage. It asks them to reassure you about a choice that was yours.
The reason, and how much to give
Three reasons read as a case, and a case invites a rebuttal. One reason reads as a fact. When the word “also” turns up in your refusal, the paragraph has started arguing instead of answering.
Keep the reason on your side of the table. “This is not work we take on” is a fact about you. “Your timeline is not realistic” is a judgment about them, and they’ll answer the judgment instead of the decision.
Name only a condition you’d be happy to have tested. “We’re full through March” means April is coming. “The budget is the problem” means a bigger number is coming. Where the extra month or the extra money would leave your answer where it is, keep both out of the message.
And give a true reason every time. This is the one shortcut in business email that reliably costs more than it saves. A false reason gets repeated back to you, it’s checkable, and it teaches somebody the wrong way to get a yes out of you. Tell a prospect you’re booked until the fall and you’ve scheduled your own September problem.
Some refusals carry no reason at all, and they’re complete as they stand. A cold pitch takes “no thanks, not something we’re looking at” and stops there. A favor declined to a peer takes “I’m going to sit this one out”. A reason handed to a friend is something to discuss, and the friendship was never about the discussion. Where the honest reason is about the person rather than the request, leaving it out is the kind move.
Others earn more. Somebody who did real work to get the ask in front of you is owed the reason, whether that’s a written proposal, an application, or a pitch you invited. The reason is the only part of your message with any value to them. Two specific sentences about what you went with and why beat a page of regret. A long-standing client turned down on something is owed enough that the refusal reads as one decision inside a relationship that carries on, which usually means one line about what stays the same.
Whether the door is a real one
There are three doors, and one rule covering all of them.
A later date. A different scope. A different person.
Name a door only if you’d honor it today, on the terms you just wrote. Any other door is a maybe in a refusal’s clothes, and it comes back. The check-in in six weeks. The “you mentioned the new year”. The proposal you decline a second time, with less grace than the first.
“Keep us in mind for the future” is the most common fake door in professional email, and it’s harmless precisely because everyone reads it as the formality it is. The doors that do damage are the specific ones you didn’t mean. “Come back to me in the spring” is a commitment, and somebody will put it on the calendar. Where spring is a refusal too, say today what you mean today.
The third door is the strongest and the least used. Name somebody who does take this work and your refusal becomes the most useful message that person gets all week, at a cost of one line. Two conditions on it. Name people whose work you’d stand behind. And where the volume is real, ask them first.
Closing the door properly is the kind option. “This is not something we do, so I’d rather not leave you waiting on us” reads better than an open ending, because it gives back the thing the other person actually needs, which is their own time.
Eleven you can send today
Each of these is shorter than the message it answers, and most sit on the existing thread.
One. An inquiry that’s a poor fit. The referral is the whole value of the message.
Hi Nadia,
Thank you for the detail, that was a clear brief.
This one is not for us. We only do annual reporting, and you’re describing a brand system built from scratch.
Two studios who do this properly are Ardent and Fieldwork, and I’d start with Ardent. Use my name if it helps.
Good luck with it.
Two. Below your price floor. The number is the reason, and stating it ends the negotiation rather than opening one.
Hi Tom,
No from us on this, and the reason is simple. We don’t take projects under twenty thousand, and this scopes at about half that.
That’s a floor rather than an opening position, so I’d rather say it today than spend your week writing a proposal around it.
If the scope grows later, write to me and we’ll look again.
Three. A discount request from a client you want to keep. The rate holds, and what stays the same is named at the end rather than defended at the start.
Hi Rachel,
The rate is the rate, and I’d rather tell you that straight than take a week over it.
What I can change is what’s inside it. Moving the monthly report to quarterly takes about eight hundred off, and nothing you have ever said you cared about is in that report.
Say the word and the revised scope comes over today. Otherwise the current one stands and we carry on as we are, which is working.
Four. Extra work a client believes was included.
Hi Marcus,
The migration is not in the current statement of work. I’ve gone back and checked, and I’d have said yes to it in March if it had been raised then.
It’s about six days. If you want it, a change order comes over today and it lands two weeks behind the main build.
If you’d rather leave it, we go live on the 14th as planned. Either is genuinely fine. What I can’t do is fit it inside the current number.
Five. A no to how, rather than to what. Refusing the approach while accepting the work is a real answer, and people rarely write it down.
Hi Elena,
I’m not going to build the questionnaire as it’s written, and I’d rather say why than quietly deliver a worse version of it.
Twenty-two questions with a five-point scale on each is a long survey, and the people who stay to the end of a long survey do not look like your customers.
Nine questions gets you the same four decisions. They’re drafted and attached.
If you want the long one anyway, say so and I’ll build it. I’d be doing it against my own advice, and I’d rather you knew that than found out in the data.
Six. A meeting you can skip.
Hi Dan,
I’m going to skip Thursday’s call. It’s a scoping conversation and the scope is settled at my end.
Send me the notes and I’ll read them the same day. If something lands that needs me, put it on the list and you’ll have an answer in writing by Friday.
Nothing needed in reply.
Seven. Free advice, asked for warmly. The reason is a practice rather than an inability, and there’s a real alternative attached.
Hi Chris,
Good to hear from you, and thank you for thinking of me.
I don’t do unpaid scoping calls any more. It got to about four hours a week and it was crowding out the work that pays for the week.
Most of what I’d have said on that call is written up here and it’s free: [link]
If you’d rather have it properly, an hour is $350 and there’s space next Wednesday.
Eight. An introduction you’d rather not make. The reason is about the writer’s own budget of goodwill, and it says so.
Hi Sofia,
I’m going to pass on introducing you to Dev. That is not a judgment on you at all. I’ve spent what I’d ask of him this year and I’d rather not spend it twice.
If it’s useful, he’s active on the industry Slack and answers direct messages there, which is how I met him.
Nine. A cold pitch. Two sentences, sent the day it arrives.
No thanks, not something we’re looking at. Please take us off the list.
Ten. A speaking or podcast invitation. The door here is real, which is why it can be named.
Hi Marcus,
Thank you for the invitation, and it’s a no from me on this one. I’m not taking anything on outside client work before the new year.
That’s a no rather than a not yet, so please fill the slot without waiting on me.
If you’re still running these in the spring, ask me again and you’ll have a straight answer inside a day.
Eleven. A candidate you interviewed. The specific reason is the only thing in this message worth anything to them.
Hi Jordan,
We’re not going to make you an offer, and I wanted you to hear it today rather than work it out from silence.
We went with somebody who has run a close at a firm of our size before. That was the whole of it, and your written exercise was the strongest of the four.
If you want twenty minutes on what I’d work on before the next one, write to me and I’ll make the time. That offer is real and it stays open.
Read across the eleven and three things hold every time. The answer arrives in the first or second sentence. Each one carries a single reason. And where a door is named, it’s a door the writer would open that afternoon.
The phrases that reopen the question
Every one of these was written by somebody trying to be gentle, and every one costs the sender another round.
“Unfortunately,” carrying the whole message. The word is fine. The trouble is the message that carries the regret and leaves the decision out, which happens more often than anyone would guess.
“At this time,” “right now,” “currently.” Each one hands the reader a calendar and invites them to pick a date. Where a later date would genuinely change your answer, name the date yourself. Otherwise take the words out.
“I don’t think we’d be the right fit.” You’ve decided it. The hedge reads as an opinion still forming, which is an invitation to change it. “We are not the right fit for this” is the same sentence with the invitation removed.
“Let me see what I can do.” A refusal rescheduled, usually to a worse moment for both of you.
“I’d love to, but.” The second half deletes the first half, and the first half is often decoration anyway. Where you genuinely would have loved to, put it in the last line. In front of the answer it works as a warning.
“Does that work for you?” at the end of a refusal. A question is an instruction to reply, and you’ve just invited the one reply you’d rather avoid.
The second apology. One acknowledgment of the inconvenience is courtesy. Two is a request for reassurance, and it puts the other person to work on your feelings about a decision that was yours to make.
The long explanation. Length reads as guilt, and guilt reads as negotiable. Where your reason runs past two sentences, the extra ones are usually there to make you feel better rather than to tell the reader anything.
The invented third party. The partner you’d have to check with. The policy that turns out to be you. The committee nobody has ever met. These work exactly once. After that you’re somebody whose refusals have a hidden appeal process, and every future one gets appealed.
When no is not an email
Five refusals worth saying out loud first, and one that people put off writing when they should simply send it.
You’re taking back a yes. A withdrawn agreement in writing lands as a decision announced rather than a difficulty shared, and the reader is left holding the question forming in their head. Call, say it, then send the email that confirms what you agreed. The call is the delivery. The email is the record.
The no ends something. Declining a renewal. Closing an engagement. Telling a long client that this is the last piece of work. The message is bigger than email can carry, and the person will remember for years how they found out.
It’s really a negotiation. Where a version of this exists that you’d say yes to, you’re writing the opening of a conversation about scope or price. Email takes six rounds to find that version. A call takes ten minutes, and the summary goes out afterwards.
It’s a no to somebody’s work rather than to their request. Criticism arrives colder in writing than you meant it. The reader supplies a tone of their own, and it’s rarely a generous one. Say it out loud, where you can hear how it’s landing.
The answer belongs to somebody else. Declining for a person who hasn’t been asked helps nobody. Say who decides, and pass it there.
The case people get backwards is the small one. Routine, low-stakes, high-volume refusals are exactly what email is for. The cold pitch, the meeting invitation, the small ask from somebody you barely know: a same-day two-line answer is the whole job. Saving those up to “do properly later” is how a hundred of them come to sit in a mailbox, each carrying a little weight. Where what’s outstanding is a date rather than a decision, the shuttling has a repair of its own, in scheduling without the email chain.
What a written no leaves behind
A spoken refusal evaporates. A written one gets forwarded, pasted into a group chat, and sits in two mailboxes for as long as either party keeps mail, which for most firms is years.
So write the version you’d be comfortable having read aloud. In practice that’s also the version that reads best today. One true reason, on your side of the table, and it stays off the other person’s competence, finances or character.
Two places make the record a matter of rules rather than awkwardness, and both catch small firms by surprise.
The first is who you decline as a customer. Title III of the Americans with Disabilities Act defines a place of public accommodation broadly. The list at 42 U.S.C. 12181(7)(F) expressly includes the “office of an accountant or lawyer” alongside a bank, an insurance office and a travel service. The general rule at 42 U.S.C. 12182(a) is that “no individual shall be discriminated against on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation”. Turning away work you’d rather leave is ordinary and lawful. Naming a person’s disability, their health, or an accommodation they asked for as the reason is a different act, and you’ve put it in writing yourself. Whatever your reason actually is, that’s the one to write down.
The second is turning down a job applicant when you ran a background check. 15 U.S.C. 1681b(b)(3)(A) governs the order. Before you take any adverse action for employment purposes “based in whole or in part on the report”, the applicant gets two things from you. One is “a copy of the report”. The other is “a description in writing of the rights of the consumer under this subchapter, as prescribed by the Bureau”. So the pre-adverse-action notice is the first message in that sequence, and the rejection email comes after it.
Almost every refusal you write this month sits outside both of these, and ordinary business stays ordinary business. These are the two spots where the record you’re creating has rules attached, and both are cheap to get right once you know they’re there.
Point and the refusal that sat
The refusals that do damage are usually the ones that sat. Nine days in a mailbox, because answering was unpleasant and the inbox let it slide.
The mailbox itself can take some of this off you. Point is an email client for an account you already have on Gmail or Microsoft 365, and the job Point takes here is the noticing.
A message waiting on a decision is its own animal, and Point sorts it that way. It holds its place in the feed while the rest of the day moves past. Leave it long enough and Point raises it again. That covers the delay, which is the expensive half of a bad refusal.
The wording is the other half. Put the decision into a short instruction on the thread, “no to the extra scope, offer a change order, keep it warm”, and what comes back is a draft in your own phrasing with the conversation still sitting beneath it. How far Point goes with something like that is a per-action choice you make, and every kind of action ships on review, so a refusal Point has drafted waits for you until you say otherwise. The three positions and what each one means in practice are on the autonomy dial. Whatever Point did is recorded step by step, and undo runs against that record. One thing stays out of reach, and it’s a message already sitting on somebody else’s server. What else a mailbox picks up from all this is listed under benefits.
Common questions
How do you politely say no in an email?
Put the answer in the first or second sentence, in the words you’d use out loud. Give one true reason. Then stop. The politeness lives in the clarity. A reader who knows the answer immediately can act on it immediately, while a reader who has to infer it spends a week on a maybe you never meant. One line of acknowledgment before the answer is worth having. A second line starts to read as a run-up, and by the third the message has become something the reader has to decode.
Should I give a reason when I say no?
One, and make it true. Keep it off any condition you’d rather leave untested. Three reasons read as a case being built, and a case invites a rebuttal. Some refusals carry none at all. A cold pitch, or a favor declined to a friend, takes “no thanks” as a complete message. Others earn more. Anybody who did real work to put the ask in front of you is owed the specific reason, whether that’s a proposal, an application or an invited pitch. It’s the only part of your message that has any value to them.
What actually damages a relationship when I turn something down?
Usually the delay in front of the answer, and the expectation somebody built while you were delaying. The research on refusal suggests people overestimate the fallout from the answer itself, so they spend a week softening it, and the week is the part that costs. Being turned down on Monday costs almost nothing. Being turned down on the 20th, after two weeks of encouraging vagueness, costs a great deal, because the other person made plans in the gap.
A client wants a discount. What do I write?
Say that the rate holds, in about that many words, and then change what’s inside the scope rather than what it costs. “The rate is the rate” is a fact. “I can’t really go lower” is an inability, and an inability is something the other side will try to argue you out of. Offering to take something out for a smaller number keeps you in a conversation about value rather than about price, and it tells you quickly whether the budget was ever the real issue.
Is it rude to say no by email rather than on a call?
For most refusals, email is the considerate choice. It’s fast, it arrives without an ambush, and it lets the reader absorb an unwelcome answer in private. Five kinds are worth saying out loud first, and each is a case where the reader will have a question your message can’t answer. Taking back a yes. Ending a relationship. A refusal that’s really a negotiation. Criticism of somebody’s work. And any refusal where the honest reason is about the person.
What if I already said yes and now have to say no?
Do it out loud, the day you know, and follow it with an email confirming what you agreed. This is the one case where the call is the delivery and the email is the record, because a withdrawn agreement lands as a decision announced and leaves the other person holding the obvious question. The follow-up email owes them three things. The new fact. What you’ll do to limit the damage. And the date you’ll do it by. One apology covers the courtesy; a second and a third convert your mistake into something they have to manage.
How long should a no email be?
Shorter than you want it to be. A refusal has four parts. An optional line of acknowledgment, the answer, one reason, and a close that settles it. All four fit in under a hundred words for nearly everything you’ll ever decline. Length in a refusal reads as guilt, and guilt reads as negotiable. Where yours has run long, the extra words are usually working on your discomfort rather than on the reader’s understanding.
The short version
A refusal works when the reader can tell it was one. Everything you add to soften it makes the answer harder to find: the run-up, the second apology, the “at this time”, the open-ended future. And an answer that’s hard to find gets read as the answer the reader would prefer. So answer early, answer plainly, and let the courtesy sit in the speed and the clarity rather than in the padding.
Then the four small decisions. One reason, true, on your side of the table, and safe to have tested. A frame that describes what you do, since an inability is a problem the other side will try to solve for you. A door only where you’d open it today, plus a name to send them to if you have one, which is the single most useful line a refusal can carry. And a close that’s a statement, since a question at the end reopens what the rest of the message just settled.
The rest is timing, and timing is where the real damage lives. You’re almost certainly overestimating what the answer costs, and underestimating what the silence in front of it costs.
What you’re declining changes the emphasis. An accounting practice refusing a position a client wants taken on a return writes the one kind of refusal where the reason is the entire message and earns its length. A design studio turning down a project at the wrong number gives the floor and stops there, since any judgment on the brief invites a defense of the brief. A coaching practice declining a client who is not ready owes them the thing that would have to be true instead, which is the only version they can use. Whichever line of work you’re in, one sentence does most of the job. Say it early, say it once, and mean the part you leave open.