Saying no politely
Declining work, discounts and scope creep without a paragraph of apology. Filter by role or search for what you need to turn down.
10 templates · free · no sign-up
I'm a…
Sending it as…
Quick and clear. A slow no wastes their time as well as yours.
Subject: Re: [project]
Hi [Name], Thanks for thinking of me for [project]. I'm going to pass on this one — [short honest reason: capacity, fit, timing]. [Name] does excellent work in this area and might have room: [contact]. Happy to make the introduction. Do keep me in mind for [what you do want]. [Your name]
Hold the price, move the scope. Never just cave.
Subject: Re: budget
Hi [Name], I can't move on the rate — it reflects what the work takes, and discounting it would mean cutting corners I'm not willing to cut. What I can do is fit the work to your budget. For [their number] I'd deliver [reduced scope], which covers [the most valuable part]. Would that work? [Your name]
Polite, unapologetic, no lecture about exposure.
Subject: Re: [request]
Hi [Name], Thanks for the offer. I don't take on unpaid work — it's how I make my living, so I keep that line simple. My rate for something like this is [amount]. If the budget appears later, I'd be glad to talk. Best of luck with [project]. [Your name]
Yes to the request, no to it being free. That's the whole move.
Happy to do [request] — it sits outside what we scoped, so it'd be [amount] and add [duration] to delivery. Want me to go ahead, or park it for after [current deliverable]?
Offer the outcome without the meeting.
I'm going to skip this one — [reason: I'd add nothing / I'm heads-down on X]. If it's about [topic], my view is [your input] — feel free to use that in the room. Send me the notes and I'll follow up on anything that needs me.
Say what's actually possible rather than agreeing and failing.
Subject: Re: [project] timeline
Hi [Name], I can't do [full scope] by [their date] — not to a standard I'd put my name on. Two honest options: • Full scope by [realistic date] • A reduced version — [what's achievable] — by [their date] I'd rather tell you now than miss it later. Which suits? [Your name]
Honesty here buys you enormous trust.
Subject: Re: [project]
Hi [Name], I could take this on, but I'd be learning on your budget — [the part that's outside what I do] isn't my strength, and you'd get a better result from someone who does it daily. [Name] is genuinely good at this: [contact]. If [the part you are good at] ever comes up, I'd love to help. [Your name]
Offer proof of ability instead of free labour.
Subject: Re: [pitch request]
Hi [Name], Thanks for the invitation. I don't do speculative work — it means giving away the actual thinking, which is the part you'd be paying for. What I can do instead: walk you through [similar past project] in detail, including the reasoning, so you can judge whether I'm right for this. Usually more useful than a pitch anyway. Would that work? [Your name]
When 'quick favour' quietly became a standing commitment.
Subject: A change on [the thing]
Hi [Name], I've been picking up [the thing] for a while now, and it's grown past what I can absorb alongside everything else. From [date] I'll need to stop. Happy to [write it up / hand it over / train someone] before then so nothing drops. Sorry to change the arrangement — it's a capacity thing, nothing more. [Your name]
The no people remember warmly. Only refer people you'd vouch for.
Subject: Re: [request]
Hi [Name], This isn't one for me — [brief reason]. But it is squarely [person]'s thing. They've done [relevant work] and I'd trust them with it: [contact]. Want me to introduce you? [Your name]
Nothing matches that
Try a plainer word, or clear the filters above.
People delay declining because it feels rude, but the delay is the rude part. Someone waiting a week for a soft maybe cannot plan, and a colleague whose request you are quietly resenting has no idea anything is wrong.
Every template here is designed to be sent within a day. Brief, clear, no lengthy justification. A long explanation invites negotiation and suggests you are not certain, which is why over-explained refusals are the ones that get argued with. The discomfort of writing a short no is almost entirely yours; the recipient reads it in four seconds and updates their plan.
Capacity, fit or timing covers nearly every situation. Adding detail creates surface area for the other person to solve, and then you are declining twice.
If you say you are busy until March, a determined requester will offer to wait until March. A single, slightly general sentence closes the conversation kindly. This is not dishonesty — you do have limits and preferences, and the specifics are not information the other party needs. It is also worth remembering that an explanation is a courtesy rather than something you owe.
When budget is the obstacle, discounting teaches the other side that your price was never real. Reducing what is included keeps the rate intact and gives them a genuine choice.
For your budget I would deliver this smaller piece is constructive rather than a refusal. If you do discount, trade it for something concrete: payment up front, a longer commitment, a case study, or a flexible timeline. A discount given for nothing is a price cut with extra steps, and it sets the expectation for every future conversation.
The one-more-small-thing request is the most common and the most quietly damaging, because each instance is genuinely small and refusing feels disproportionate.
The move is not to refuse but to price it out loud, in the moment. Naming the cost and the effect on the deadline converts an assumption into a decision the other person gets to make. Half the time they decide it is not worth it, which tells you it was never important. What you must not do is absorb three silently and raise it as a grievance later.
A no that arrives with a good alternative is remembered as help. Referring work to someone you would genuinely vouch for costs nothing and turns an awkward message into a warm one.
It also comes back. People who refer generously tend to be referred to, and the effect is larger than the individual opportunity passed up. The only rule is that the recommendation must be real, because passing on a name you do not rate damages two relationships at once and the requester will associate the bad experience with you.
Some people treat a no as an opening position. The right response is to repeat the same answer in the same tone without new arguments, because fresh reasons invite fresh counter-arguments.
If they escalate — suggesting you are being difficult, or that this is how everyone else works — hold the line and stay warm. Someone who responds to a polite refusal with pressure is demonstrating exactly what the arrangement would have been like. It is also worth knowing that after a clear refusal and one restatement, further messages do not require an answer.
