How to turn down a design project without burning the bridge
Not every project is a fit. Here is how to decide when to say no, what to say, and how to keep the door open for better work later.

Most freelance advice is about winning work. Far less of it covers the other half of running a healthy design business: saying no. Yet the projects you turn down shape your year as much as the ones you take. A bad-fit project eats the time you would have spent on better clients, drags down your portfolio, and often costs more in stress than it pays.
The trouble is that a clumsy no can cost you too. The person asking today might run a bigger company next year, or refer you to someone who does. This guide walks through how to decide when to decline, how to word it, and how to leave the relationship in better shape than you found it.
Know your reasons before the request arrives
Saying no is hardest when you are deciding on the spot. Write down your filters in advance, so a request either passes them or it doesn't. Good reasons to decline usually fall into a few groups:
- Fit: the work is outside what you do well, or outside what you want to be hired for next.
- Budget: the money is below your floor, and the scope can't shrink to match it.
- Timing: you can't give it proper attention without hurting current clients.
- Red flags: unclear decision makers, a request for free "test" work, or a story about how every previous designer failed them.
- Values: you are not comfortable with the product or how it treats people.
Keep this list where you write proposals. When you can point to a rule you set yourself, the decision feels less personal, and you are less likely to cave because a call went pleasantly.
Decide quickly
A slow no is worse than a fast one. If you sit on a request for a week and then decline, the client has lost a week they could have spent finding someone else. Aim to reply within one or two working days, even if the reply is just "Thanks, let me check my schedule and get back to you by Thursday."
If you are unsure, ask the one or two questions that would settle it: the budget range, the launch date, or who signs off on the design. Often the answer makes the decision for you.
Say no clearly, then be kind
The most common mistake is a vague reply that sounds like a maybe. "I'm pretty busy at the moment, but let's see" leaves the client waiting and invites a follow-up you will also have to dodge. Be direct in the first sentence, then add warmth.
A simple structure works for most situations:
- Thank them for thinking of you, and mention something specific about the project.
- State the decision plainly.
- Give a short, honest reason, without over-explaining.
- Offer something useful: a referral, a resource, or a future window.
Thanks for sending over the brief for the new booking flow. It's a clear problem and I can see why it matters to your team. I'm not able to take it on: my schedule is full until March and I don't want to give it half my attention. A designer I trust, who works on exactly this kind of product, may have space. Happy to introduce you if that helps.
Notice what is missing: no apology spiral, no long list of reasons for the client to argue with, no fake hope.
Match the reason to the situation
You don't owe every client your full reasoning, but the reason you give should be true. A few patterns:
When the budget is too low
Say what the budget would cover, or what your minimum is. "My projects of this size start at $8,000. If that's out of range, I'd suggest a well-chosen template and a few hours of customisation instead." This respects their constraints and sometimes turns into a smaller, well-scoped project.
When the timing doesn't work
Give a real date when you could start. Some clients will wait, and a booked project three months out is better than a rushed one now.
When it's not a fit
Be specific about what you do focus on. "I mostly design marketing sites for B2B software, so a mobile game UI isn't where I'd do my best work." That also teaches the person when to send work your way in future.
When something feels off
You don't need to list every red flag. "I don't think I'm the right designer for this one" is enough. Keep it short and polite, and don't get pulled into a debate.
Offer a useful alternative
The part of a no that people remember is whether you helped them anyway. Keep a short list of options ready:
- Two or three designers you trust, each with a different speciality or price point.
- Templates or tools that suit a smaller budget.
- A paid hour of advice, if they need direction more than delivery.
- A note about when your calendar opens, if they are happy to wait.
Referrals also build goodwill with other designers, and that tends to come back as referrals to you. Only recommend people whose work you know, and ask them first if they are taking on new projects.
Handle the push-back
Some clients will try to negotiate: "What if we doubled the timeline?" or "Could you just do the homepage?" Decide in advance whether a different scope would change your answer. If it would, say so and send a proper proposal. If it wouldn't, repeat your answer once, politely, without new reasons.
If they offer more money for a project you declined because of fit or values, the answer usually stays the same. Extra budget rarely fixes a bad match, and it makes it harder to walk away later.
Keep the door open
A declined project can still lead somewhere. Add the person to your contacts with a note about what they asked for and why you said no. If your situation changes, for example your schedule clears or your prices now match their budget, you have a natural reason to get in touch.
A short check-in a few months later also works: "I hope the booking flow launched well. I have some space opening in spring if you have anything else in the pipeline." It's low-pressure and shows you paid attention.
Conclusion
Turning work down is a skill, and like any skill it gets easier with a system. Set your filters before the request arrives, reply fast, say no in the first sentence, give one honest reason, and offer something useful on the way out. Done well, a no protects your time and still leaves the client thinking of you as someone they would like to work with, just not this time.


