How to Decline a Freelance Project: 5 Polite Email Templates

A new inquiry lands in your inbox. The client seems nice, but the budget is half what the work needs, or your calendar is already full, or the project is something you don't actually do. Saying yes feels safer. It usually isn't. The wrong project costs you the time you'd have spent on the right one, and a rushed or underpriced job rarely leads to a good testimonial.

A good email to decline a freelance project is short, kind and clear. It says no without a long excuse, leaves the door open when you mean it, and, when you can, points the client somewhere useful. This guide covers when to say no, five copy-ready decline emails for the most common reasons, and an AI workflow. ChatGPT or Claude can soften the wording. It should never invent reasons, referrals or future availability you didn't give it.

When saying no is the right call

Signal	What it usually means	Decline or negotiate?
You're booked for the next several weeks	You'd have to rush this or another client	Decline, or offer a later start date
The work is outside your skills	You'd be learning on the client's budget	Decline and refer
The budget is far below your quote	You'd resent the work by week two	Offer a smaller scope first, then decline
The scope is vague and the client won't define it	Scope creep is almost guaranteed	Ask once, then decline
Red flags on the call (rushed deadline, no decision maker, "it's easy")	Payment or approval trouble later	Decline politely

Your discovery call questions are where most of these signals show up. If you spot one, decide before you spend an evening on a proposal.

Template 1: Too busy right now

Subject: Re: [Project]

Hi [Name],

Thanks so much for thinking of me for [project]. It sounds like a
great project, but my schedule is full until [month], and I don't
want to take it on and give it less than full attention.

If your timeline can move to [month], I'd be glad to talk again
then. Otherwise, I hope it comes together well.

Best,
[Your name]

Only offer a later date if you'd actually take the work then. "Maybe later" that you don't mean just delays the same email.

Template 2: Not the right fit

Subject: Re: [Project]

Hi [Name],

Thank you for reaching out about [project]. After looking at what
you need, I don't think I'm the best fit. My work focuses on
[your specialty], and this project needs someone who does
[their need] every day.

I'd rather say that now than take it on and fall short.
Best of luck with it.

[Your name]

Naming your specialty keeps it about fit, not about the client. It also tells them what to send you next time.

Template 3: The budget doesn't work

Subject: Re: [Project] budget

Hi [Name],

Thanks for sharing the budget for [project]. To do the full scope
well, I'd need about [your number], so I can't take it on at
[their number].

If it helps, I could do a smaller version for your budget:
[one-line reduced scope]. If that doesn't work, no hard feelings,
and I hope you find the right person.

Best,
[Your name]

Offering a smaller scope is not discounting. You're changing what they get, not what your time is worth. If they accept, write it up properly with the one-page proposal template so the reduced scope is on paper.

Template 4: Scope is too open-ended

Subject: Re: [Project]

Hi [Name],

Thanks for the details on [project]. Before I could quote, I'd
need a clearer picture of [the specific missing piece, e.g. how
many pages, who approves the work, the launch date].

Since that's still being worked out on your side, I'll step back
for now. If you get it pinned down, I'm happy to take another look.

All the best,
[Your name]

Ask for clarity once. If the client can't or won't define the work, that's the answer.

Template 5: Decline with a referral

Subject: Re: [Project]

Hi [Name],

Thanks for thinking of me for [project]. I can't take it on
[right now / because it's outside what I do], but I know someone
who might be a great fit: [Referral name], who [one line on what
they do]. You can reach them at [contact].

I hope it goes well, and feel free to reach out for future
[your specialty] work.

[Your name]

Ask the other freelancer before you share their name. A good referral makes you look generous and often comes back around, the same way a referral request works in the other direction.

AI draft workflow: kind, short and accurate

AI is handy when you're tempted to over-explain or apologize five times. It also tends to add things: "I'll definitely have openings next month," a referral you didn't mention, or a discount you never offered. Give it only the facts, then check the draft. The same pattern runs through our ChatGPT workflows for freelancers.

Step 1: Draft prompt

Write a short email declining a freelance project, under 100
words. Use only the facts below. Do not invent availability,
referrals, prices, or reasons. One brief thank-you, one clear
"no", and an optional next step only if it's in the facts.
Warm, plain tone. No long apologies.

Facts:
"""
Client name and project:
Reason for declining:
Later date I'd actually take it (or "none"):
Smaller scope or price I'd offer (or "none"):
Referral I have permission to share (or "none"):
"""

Step 2: Check prompt

Compare this email to the facts. List every date, price, scope,
referral, and promise, and mark whether each one appears in the
facts. Flag any phrase that sounds like a maybe instead of a no.
Do not rewrite it.

Email:
"""
[paste draft]
"""

Facts:
"""
[paste facts]
"""

Step 3: Read it once as the client

Would you know, after one read, that the answer is no and what (if anything) to do next? If not, cut words until you would.

Declining a client you already work with

Turning down an extra request from a current client is different from turning down a new lead. If the request is new work inside an active project, treat it as a change order rather than a flat no. If you want to stop working with the client entirely, use a proper wrap-up instead: see how to end a client relationship professionally.

FAQ

Is it unprofessional to turn down freelance work? No. Declining clearly and quickly is more professional than accepting work you can't do well or leaving the client waiting.

Should I give a reason when I decline a project? A short one helps (too busy, not a fit, budget). You don't owe a long explanation, and a long one invites negotiation.

How quickly should I reply? Within a day or two of deciding. A fast no lets the client move on and leaves a better impression than silence.

Should I offer a discount instead of declining? Offer a smaller scope instead of a lower rate. Cutting your price for the same work sets the wrong expectation for every future project.

Can I use ChatGPT to write a decline email? Yes. Give it only real facts, keep it under 100 words, and run a check prompt so it doesn't promise availability, prices or referrals you didn't offer.

Bottom line

Decline projects that don't fit your schedule, skills, budget or process, and do it quickly. Thank the client, say no in one clear sentence, give a short reason, and offer a later date, a smaller scope or a referral only when you mean it. Let AI tighten the wording, then check that it didn't promise anything new.

Knowing when to say no starts before you quote. Run the free 40-point scope checklist on every inquiry, and the $9 Freelancer Proposal Autopilot Kit has prompts for scoping and pricing the projects you do say yes to.