Saying no to a project feels harder than it should. There’s the guilt of letting someone down, the worry that you’re closing a door for good, and the worst part: not knowing if you should have just taken the work. A clean decline solves all three. It respects the client, preserves the relationship, and sometimes turns the no into a yes later.
Declining well is mostly a problem of speed and structure. Take too long and you signal the answer is yes. Write too much and the no gets lost. Be vague and you damage trust. Here’s the template that solves all three, and the situations where it gets used.
Why you should decline fast
The longer you take to decline, the worse the outcome. Two reasons.
First, the client starts planning around you. If you take a week to say no, you’ve cost them a week of their decision timeline. They were holding the project for you, and now they’re behind.
Second, your “no” starts to feel like a “yes I keep avoiding.” The client builds up an expectation that the answer will be positive, and the no lands harder when it finally arrives.
The rule: decide within 24-48 hours. Send within 48 hours. If you can’t decide that fast, the answer is no anyway (a real yes is usually obvious within a day).
The clean decline template
Five lines. That’s the entire structure.
Subject: Re: [project name]
Hi [Name],
Thanks for sending this over and for thinking of me. After looking it through, I’m going to pass on this one, [brief honest reason].
If it would help, I can introduce you to [name], who handles this kind of work well. Otherwise, definitely keep me in mind for future projects, and I’ll do the same for you.
All the best, [Your name]
Read it back. Notice what’s missing:
- No three-paragraph apology
- No “I really wish I could but…”
- No detailed explanation of your current workload
- No backdoor reopening (“…unless you can be flexible on…”)
Just thanks, no, reason, alternative, door open. That’s the whole thing. Eight lines including the close.
The honest reasons that work
A brief honest reason makes the decline land cleanly. The reasons that work:
- Capacity: “I’m fully booked through [month]”, most common, easy to accept
- Scope mismatch: “This falls outside the main work I’m taking on right now”
- Timing mismatch: “The launch timeline is tighter than what I can responsibly commit to”
- Fit: “I don’t think I’m the right fit for this specific project, but I want to make sure you find someone who is”
- Direction: “I’m moving away from this kind of work over the next quarter”
The reasons that don’t work:
- Fabricated excuses the client can disprove with a 30-second LinkedIn check
- Vague language that makes them think they could change your mind
- Negative comments about their project, brief, or budget
- Pricing comparisons that sound like you’re fishing for a counter
Honest is short. Dishonest is long. If your decline email is more than 8 lines, you’re probably hiding something.
When to suggest a referral
Suggest a referral when:
- You know someone good who does this kind of work
- The project is well-defined and reasonable (not a problem you’d send to your enemies)
- The client seems easy to work with
- You actually have an active relationship with the person you’re recommending
Don’t suggest a referral when:
- The project has red flags (scope chaos, bad budget fit, difficult vibe)
- You don’t actually know anyone who’d do it well
- You’re using “let me introduce you to…” as a way to soften the no without meaning it
A bad referral hurts everyone: the client gets handed to someone who doesn’t fit, the freelancer you sent gets a project they should have refused, and you become the source of a mess.
If you don’t have a referral, skip that line. Just say “I’m happy to keep an eye out if I think of someone who’d fit.” That’s enough.
The version for past clients
When a past client comes back and you have to decline, the decline needs more warmth because the relationship is real.
Hi [Name],
Great to hear from you, and thanks for thinking of me again for [project type]. I want to be straight with you, I’m not going to be able to take this one on (capacity through end of Q3), but I really don’t want to leave you hanging.
Two options: I can introduce you to [name], who’s done similar work and is currently taking on new clients. Or if your timeline is flexible into Q4, we could chat about a version of this that fits a later start.
Either way, want to stay in touch, happy to do a coffee or quick call in the next few weeks if there’s anything else on your mind. Don’t be a stranger.
[Your name]
The differences:
- Warmer opening (you have a relationship)
- More effort to solve the problem (referral plus delayed option)
- Suggestion to stay connected outside of the work (coffee, call)
- Personal close (“don’t be a stranger”)
Past clients who get the warm decline often come back 6-12 months later with the same project, or a different one. The freelancers who decline past clients curtly lose them permanently.
The version for prospects you don’t know well
For a cold or warm inbound lead, the decline can be shorter and slightly more formal.
Hi [Name],
Thanks for reaching out about [project]. After reviewing, I’m going to pass on this one, the scope falls outside the main work I’m focused on right now.
If you’d like, I’m happy to recommend a couple of freelancers who’d be a stronger fit. Just let me know.
Best, [Your name]
Short, clean, professional. No relationship to warm up, so no need to over-personalize.
What to do when they push back on the no
Sometimes the client replies to your decline with “wait, what if we [change something]?” Don’t reverse course on a polite re-ask.
If you said no for capacity, the capacity hasn’t changed in 24 hours. If you said no for fit, the fit hasn’t changed either. Reversing your no makes you look like you were never sure to begin with, and the project starts with the client knowing you can be talked into things.
A clean response:
“Appreciate you coming back on this. Capacity-wise it’s still going to be tough through [month], I don’t want to commit and then deliver something rushed. If timing on your side can flex to [later date], happy to revisit. Otherwise I’d rather connect you with [name] now so you’re not stuck waiting.”
You held the no, gave one path to revisit (if you genuinely meant it), and re-offered the referral. That’s the polite firm response that protects both the project and the relationship.
The yearly impact of declining well
A freelancer who handles declines well typically sees, over a year:
- 20-40% of past-client declines turn into future engagements within 12 months
- 5-10% of declines result in introductions to other clients via the original prospect
- A referral network that compounds, because the freelancers you send work to send work back
- Almost no burned bridges, even from major declines
A freelancer who handles declines poorly (slow, vague, ghosting) loses most of those upside scenarios and gains a small reputation problem in their network.
Declining well doesn’t show up as revenue in the month you do it. It shows up 6-12 months later, when the past client comes back, or the referred prospect mentions your name in another room.
Build the template once. Use it every time. Speed and honesty do most of the work.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
