A client has asked for something outside what you agreed to do. You’re on solid ground here. What a client remembers afterwards is three things: what you say, how fast you say it, and the tone it arrives in. The answer itself rarely makes that list.
- A decline almost always keeps the client. What loses them is four days of silence, a hope that it goes away, or the work done and then let slip.
- Most refusals are really questions. About sequencing, about who should do the work, or about which of two things the client wants more. Each of those has better words available than no.
- Keep the answer short. A long one reads as an uncomfortable one, and every extra clause is another thing to negotiate against.
- What decides the cost is what happens next: the work you did promise, arriving on the date you gave.
What a client actually minds
Nearly everyone writing this email believes the risk sits in the answer. It doesn’t, and that’s the one correction worth making here. Consulting relationships end over surprises, over invoices nobody expected, and over work that landed late. A declined request almost never ends one. Three things decide what your answer does to the relationship, and the word itself is barely among them.
How fast it arrives. A one line question sits for four days. During those four days your client told a colleague it was in hand, and possibly put it in a plan. Now your answer withdraws something they’d already counted on. That’s a much larger event than a decline.
Whether they can plan around it. An answer with a date, an alternative or a name attached is information, and information is what they pay you for. An answer that stops dead is a dead end, and dead ends are what people resent.
How it made them feel about having asked. Almost every request is reasonable from where the client is standing. A reply that leaves them feeling cheeky costs you a great deal to save half a day. A reply that leaves them feeling they asked a fair question and got a straight answer costs you nothing at all.
Three ways of avoiding the moment do more damage than the refusal itself.
Saying nothing. The most common and the worst. An unanswered request gets filed as agreed, and it comes back in six weeks as an expectation rather than a question. Threads that go quiet look identical to threads that are finished, which is why silence is such an expensive way to say no.
Doing it and mentioning it. You absorb the work. Then it surfaces, in a status update or a slightly weary sentence on a call. The mention is where the damage sits. It turns something you gave into something you’re owed, and the client agreed to owe you nothing. Worse still is the version where it first appears on an invoice.
Reaching for the document. As per the statement of work is the sentence that changes what you are. Ten seconds earlier you were an adviser whose judgment they bought. Now you’re a supplier managing a variation, and they’ll treat you as one for the rest of the engagement. It’s a weak move even when you’re entirely right. What gets remembered is that the contract came out.
One fact sits underneath all of this and is worth holding on to. Part of what a client buys is your view about what’s worth doing. The consultant who agrees to everything is selling an empty one, and clients work that out faster than most people expect. A no delivered well is the strongest evidence you have that your yes means something.
Work out what you are answering
The wording is the last decision. Before it, sort the request. It’s one of five things, and only one of them is actually a refusal. They sound quite different from each other.
It’s small and you’ll simply do it. Decide where that line sits in advance rather than in the moment. It has a guide of its own elsewhere on this site. The part that belongs here is the telling. Generosity the client hears about does a great deal for the relationship. One flat sentence names what you picked up and that it’s free, said once and left alone after that.
It has a price and the choice is theirs. Write it as what it is: a costed option, the same service you give on every other question they put to you. What that note contains, when to send it and how to record the answer is set out separately.
Not now. Honestly, most of them. The engagement has an order. The request is fine in itself and wrong in this particular month. Answering a sequencing question in the vocabulary of refusal is the single most common way a reasonable answer lands badly.
Not by you. It sits outside what you’re good at, or it belongs to their own team, or a different kind of firm does it better and cheaper.
Not at all. The smallest category, and it lives in the section on the ones money does not fix.
Two habits sit underneath the sort. The first separates the request from the solution attached to it. Almost every ask holds a problem you agree with and a proposed answer you can’t afford. Say yes to the problem. They want the model rebuilt for the second region, and the real driver is a board question about that region. A two page note answers the board, and the model stays as it is.
The second is a question to ask before you answer anything. Out loud if you’re in the room, in writing if you’re at your desk. What would that give you that the current plan does not? It’s the question a good adviser asks about any piece of work, so it reads as interest rather than delay. A useful share of requests dissolve in front of it. Most of the rest come back smaller and clearer than they went in.
The order the sentences go in
Most refusals are written back to front. Thanks, a paragraph of context, three reasons, an apology, and the answer in the last line. By then the reader has been braced for bad news for four hundred words. Turn it round.
Name what they asked for, in their words. Treat it as reasonable. That’s a clause each, rather than a paragraph. Give the answer plainly by the second or third sentence. Give one reason. Say what you can do instead, or when, or who could, with a date on it. Say what happens next and who moves. Then stop.
One reason, not three. Three reasons read as a case being assembled, and a case invites a rebuttal. They also hand the client a menu. Somebody stopped by the first reason moves to the second, and now you’re negotiating on ground you chose badly. Pick the truest one and let it stand alone.
Make the reason about the work rather than about you. Being stretched, having another client that week, the state of your margin: all true, and all yours to carry. The delivery date is a shared problem. A reason put in those terms is one they can actually think about.
Do not manufacture an impossibility. We cannot, when what you mean is I would rather not, gets found out eventually, usually because somebody else does the same thing for them next quarter. I would rather not do that inside the current plan is the stronger sentence, and it stands up.
Do not close on a question you do not want answered. Does that work for you? reopens the decision you just made. Hand them control a different way and you keep the politeness for free: if you would like the costed version, say so and I will send it today.
Keep it to two paragraphs. Length reads as discomfort, and discomfort reads as negotiability. The shortest refusals in consulting come from the people most confident they’ll still have the client next month. Readers pick that up straight away, though they’d struggle to say how.
The register is what they hear
The most common mistake is a change of temperature. People stiffen when they decline something, and the stiffening shows. Sentences get longer. The passive voice arrives. Words turn up that the correspondence has never carried before. Please note that. As previously advised. At this juncture. The client reads that as a relationship changing, which is a much bigger message than the one you meant to send.
Write the refusal in the voice of your last four emails to that person. If you sign off with a first initial, keep signing off with a first initial. That continuity does more work than any softening phrase.
Within that, a handful of specifics are worth getting right.
Apologize for a delay, never for the answer. Sorry this took a day to come back is fine, and often right. Sorry, I cannot do that treats your own judgment as a failing. A client told three times that your professional opinion is regrettable will eventually agree.
Use unfortunately once or not at all. All it carries is feeling. Twice in the same short email it reads as a plea. The same goes for I am afraid.
Hedges are not kindness. Probably not, that might be difficult, I think that would be a stretch. Each one costs the client a second ask to find out where they stand, and they’ll resent the trip. If the answer is no, the sentence says no.
Cut the diminishers. Just, a little, slightly, a bit tricky. They make a settled answer sound provisional, and they invite one more push.
Own the decision rather than hiding it in the passive. That was not included has no author, so the document is the only thing left to argue with. I would rather not add that inside the current plan has an author, and the conversation stays between two people who like each other.
Do not name the pattern. Any word that files the client’s question as a type turns a reasonable person defensive in a single sentence, including the word most consultants reach for first. Answer the request, and leave the pattern alone.
Do not borrow authority you cannot produce. A partner who will not approve it, a policy, a finance team. If they ask to speak to whoever it is, and they sometimes do, you’re left with one very awkward exit.
One construction is worth keeping. I would rather say that now than in three weeks does more for a refusal than any amount of cushioning. It tells the client the thing they most want to know. You’re the kind of person who says the awkward thing early.
Saying it in the room
On a call you’re working live, and the two failure modes sit opposite each other. You agree because agreeing is what the room wants. Or you refuse badly because it caught you out.
The holding sentence, with a time on it. Let me work out what that would take and come back to you today. It reads as care, because a number invented on the spot is one you’ll live with for the rest of the engagement. The time is what makes it honest. A hold with no hour attached is the slow no with better manners.
Do not hold something you already know you will refuse outright. If the answer is a plain no and it always was, three days of waiting only makes it a bigger no. Say it in the room, once, in an ordinary voice, and move the meeting on.
When they push back, repeat the answer in the same words. That’s the whole technique, and it’s easier than it sounds. Rephrasing reads as movement. A client who hears three different versions of your answer reasonably expects a fourth. Say the same sentence, warmly, then offer the alternative again.
Do not try to win. A meeting with their colleagues in it is a bad place to be right, and so is the email afterwards. If the exchange is turning into an argument, take it out of the room: I do not think we will settle this now, let me put something in front of you this afternoon.
Avoid refusing somebody for the first time in front of their whole team. The person who asked remembers it long after the substance is forgotten. When the request lands in a group setting and you have to answer there and then, make it a question of order rather than of permission. That is a genuinely different piece of work from what we are doing between now and the fourteenth, so it is a conversation about what moves.
Write it down the same day. One short paragraph in the thread: what was asked, what you said, what happens next. A spoken no with nothing behind it gets asked again in two weeks, by somebody who was elsewhere at the time. What an after-meeting note is for more generally, and why the first two hours matter, is taken separately in this collection. The one sentence this note has to carry is the sentence recording the answer.
When the person asking did not sign anything
A large share of scope requests come from somebody with no budget and no authority to change what was agreed. Refusing them personally goes wrong twice over. The decision belongs to somebody else, and you’ve made a person you work with every week feel told off.
Route it instead of refusing it. That sits outside what we agreed with Helen, and it is a fair thing to want. Do you want to put it to her, or shall I send you both what it would take?
Three things happen in that sentence. The request stays alive. The person stays right. And you’ve handed them a way to raise it that makes them look diligent rather than acquisitive, which is worth a great deal to somebody in the middle of a large company.
Do not go over their head to settle it. Adding a senior name to the thread reads as escalation whatever you meant by it. The version where you add somebody’s manager is the most common accidental insult in client email. If the decision genuinely has to go upward, tell the person first and let them take it. Which names belong on which line, and how a copy list is read, is a subject of its own in this collection.
A new stakeholder is simply arriving. Somebody turns up in month three, has read nothing, and asks for things the engagement never contained. That’s what arriving looks like. Get twenty minutes with them early, say the scope back in plain words, then use the same routing as everybody else. The wider question of what to do when the person who commissioned the work has gone is handled elsewhere.
When the sponsor is the one asking, the register changes. They can actually change the plan, so what they need from you is a choice. Include the trade, where something already in the plan comes out to make room. The note that carries those options, and what to do about the record afterwards, is set out separately.
The ones money does not fix
Pricing is the right move for most of this and the wrong move for some of it. Putting a number on the wrong request is its own mistake, because a price says you would do it if they paid.
Work outside what you’re good at. Decline it and name somebody who could do it. This is the refusal that most reliably raises your standing. Knowing the edge of your own competence is rare enough to get noticed.
Something you believe will not work. Separate whose decision it is from whose name is on it. If it’s theirs to decide, give your objection once, in terms of what it does to their outcome rather than to your plan. Then either do it with your view recorded in one sentence, or say plainly that you would rather not. The version that goes wrong is the objection given four times in four emails, which is how a professional disagreement turns into a personality problem.
A document to support a conclusion already reached. Refuse the framing and offer the work. I cannot write it as a recommendation when we have not tested it. I can write what we know, what we do not, and what it would take to find out.
A part in somebody’s internal argument. You can listen, and listening is usually right. Stop at listening. Where it goes once you become an instrument is well described in this collection’s piece on stakeholder threads.
Work that belongs to their own staff. A vacancy quietly becoming your job is recruitment, and naming it early is kinder to both of you.
Anything that puts you somewhere you should not be. One sentence, no reasons offered, no negotiation. Reasons invite the search for a version of the request with that particular reason removed.
And one that almost nobody counts. The scope with no deliverable in it. The daily standup you were added to, the extra weekly call, the group chat, the question at eight in the evening that’s easier to answer than to leave. It appears in no document, and on a long engagement it is often the larger overrun. Answer it the way you answer work, by naming the shape you can hold. I am not going to be able to make the daily. I will be on Monday’s call and reachable by mail in between, and if something is urgent, phone me. The related question of how much mail an engagement can carry before people stop reading any of it is taken up separately here.
Taking back a yes
Sometimes you agreed on a call because agreeing was the easy thing to do at that moment, and by the evening you know it was wrong. It happens to careful people, and it’s fixable.
Unwind it fast, inside a day if you can. The cost of taking a yes back roughly doubles every week it stands. The client is building around it the whole time. After two weeks you’re disrupting a plan rather than withdrawing an agreement.
Own it in the first line and only in the first line. I agreed to this too quickly on Tuesday, and I want to correct it before you build around it. That sentence is worth more than any amount of explanation. Keep the rest short: length reads as guilt, and guilt reads as an opening.
Name the specific piece rather than reopening everything, and bring something with you. A bare withdrawal is the version people resent. A withdrawal carrying a smaller shape, a later date or another name is a normal professional conversation.
If it’s genuinely too late to take back, do the work. Then say once, in the same flat tone you’d use for a date, what it actually took. Say it away from the invoice, and say it as the frame for the next one.
When the answer is not no at all
Some requests are a symptom, and answering the symptom politely wastes the signal.
The third request in the same area. That’s a scope drawn in the wrong place. Each individual refusal is a small argument you’ll keep having until somebody moves the line. Re-scoping is a legitimate commercial moment, and it has its own guide elsewhere.
A sudden run of asks from one person. Volume from a contact who was fine last month usually means something changed above them. The useful question is what. Ask it directly and kindly, once, rather than answering five times in a row.
The request that is really a renewal. A client who wants more of what you do is the best commercial news you’ll get in a quarter, and a flat no closes it. The answer is a conversation about the next piece, priced. Hold it now, rather than in the closing weeks when it’s too late to arrange anything.
Three refusals in a month with the same person. At that point the problem sits in the setup. How the engagement is arranged, or how you and that person work together, needs a call rather than another careful email.
And there’s the case for simply doing it. If it’s small, cheap and the goodwill is worth more than the hour, do it, say that you did, and let it go. Being difficult about trivia costs more than the trivia.
The two weeks afterwards
Do not explain it again. A second email adding reasons you thought of overnight reopens a settled matter, and it tells the client the first email was shaky.
Do not overcompensate. Extra warmth in the days after a refusal reads accurately, as guilt, and guilt suggests the answer was negotiable after all. Ordinary is the register you want.
Expect it back in a different shape. Reworded, or from a different person, or split into two smaller pieces. Answer it the same way, in the same words, with the same warmth. Inconsistency is what teaches a company to keep asking, usually inconsistency between a firm no in writing and a vague yes on a call.
Leave the answer where somebody can find it. In the thread the request arrived in, in the words a person would actually search for eleven months later. That means the name of the thing and the date, rather than the additional piece we discussed. The wider craft of keeping the record straight is covered elsewhere.
Put one line in the next update and then let it go. A decision taken is news, and news belongs in the update once, on its own, with the justification left off. Repeating it weekly is how a settled question starts looking unsettled. What an update should carry at all is a separate piece in this collection.
And the thing that actually decides it. Deliver what you did promise, on the date you gave, and be early with it if you can. A refusal followed by a delivery that lands on time is remembered as judgment. The same refusal followed by a slip is remembered as an excuse, and no amount of careful wording survives that.
The part of this that is not judgment
Everything above is yours. Whether to decline, what to charge for, how a particular client takes a particular sentence, when to stop writing and telephone somebody: that’s the job you’re paid for, and no mail client has a view on any of it. Two things round the edge are mechanical, and they’re where most of the damage in this guide actually comes from. The answer arriving late, and losing track of what you already agreed to.
The delay is the first and the larger one. A refusal that goes out the same day is a different event from the same words four days later. Those four days rarely come from indecision. They come from a request sitting in a full mailbox behind ninety other things. In Point the feed leads with what genuinely needs you today. Every thread carries a plain line saying what it’s about. So a request buried in the fourth paragraph of a message about something else surfaces while it’s still cheap to answer. Ninety messages become a few minutes of skimming rather than an afternoon, which is the difference between answering today and answering on Monday.
What you already promised is the second. When a client says this was always included, the whole conversation turns on what you yourself said in a thread three weeks ago. That’s the hardest fact in the room to check. Search in Point runs on meaning rather than on exact words, so the exchange about the second site comes back from whatever you happen to remember about it. A long chain opens at the position it has reached instead of at the top, which matters when the thing you need is one sentence somewhere in forty messages.
Commitments in both directions are the third. When a message commits you to something, it comes back as a dated item rather than sitting in a thread you’d have to remember to reopen. A request you made of the client is carried the same way, still dated. The costed option you sent and heard nothing about sits in the same register. Silence means the question is still open, and an open loop comes back before it goes cold rather than after. That register is also the honest record of what an engagement has absorbed. That’s the number you’ll want at renewal, and the one your invoices leave out.
Some of this is typing, and typing is fair game. A refusal is the email people rewrite five times and send at three times the length it needed. Point drafts new messages as well as replies, picking up your own habits of phrasing. Four rough lines come back as something to cut, rather than a blank window. Read that draft for the specific failure mode of this subject, which is padding. A model given a difficult message will add apology, hedges and a third reason, and all three are the things this guide spends its time removing. The sentence to check hardest is any sentence that commits you to work.
Four limits are worth stating in full.
Point holds no statement of work, so Point has no view on whether a request is inside the scope or outside it. That judgment is the guide, and it stays with you. Point has no opinion about how a client will take a sentence either, which is the other half of the subject.
How much Point does unaided is set for each type of action separately, and review is where every one of them starts out of the box. A message declining paid work is a good candidate for staying at review permanently, whatever you raise elsewhere. It’s a commercial statement to somebody who is paying you. What that dial actually controls is worth ten minutes before you move it.
Undo reaches what Point did, and it stops at your own mailbox. Once a refusal has arrived on the client’s server it belongs to them, and no mail client reaches that far. That’s one more argument for making the same-day answer a considered one rather than a hurried one.
And a scope conversation is largely commercial detail given to you in confidence. Where that material is permitted to go deserves a deliberate answer, rather than whichever chat window happened to be open. The questions to put to a vendor first are set out separately.
Your address stays exactly as it is. Point works on top of the Google or Microsoft account you run today, and the client goes on writing to you exactly where they always did. The full list of what Point does sits on benefits, the argument as it applies to advisory work is on Point for consultants, and Point is the product itself.
Common questions
How do I say no to a client without damaging the relationship?
Answer quickly, answer briefly, and make sure the client comes away feeling they asked a fair question. Name what they asked for in their own words. Treat it as reasonable, because it usually is. Give the answer by the second or third sentence. Give one reason, expressed in terms of the delivery rather than your workload. Say what you can do instead, or when. Then stop, because a long refusal reads as an uncomfortable one and every extra clause is something to argue with. What damages relationships is the four day silence before the answer, the version where you absorb the work and let it show, and the reply that produces the statement of work.
What do I say when a client asks for something outside the scope?
Decide what kind of answer it is before you decide on words, because only one of the possibilities is a refusal. Small enough to absorb, worth pricing so they can choose, fine but not in this particular month, better done by somebody else, or genuinely not happening. Most requests are the third, and they get answered badly because people reach for the language of refusal to answer a question about order. If it has a price, hand back a costed choice rather than a decision. Telling a client what something would take is the service they hired you for, and it refuses nothing.
How do I say no on a call when I am put on the spot?
Use a holding sentence with a time in it. Let me work out what that would take and come back to you today is honest. It buys you the hour you need, and it keeps you from inventing a number in front of an audience that you then live with for the rest of the engagement. The exception is the request you already know you will refuse outright. Answer that one in the room, in an ordinary voice, because waiting three days only makes it a larger no. If they push back, repeat your answer in the same words rather than rephrasing it, since three different versions of an answer sound like an answer that is still moving. Then write one paragraph into the thread the same day, recording what was asked and what you said.
The client says the extra work was always part of the deal. What now?
Treat it as a genuine difference of understanding rather than as a tactic, because most of the time that’s what it is, and answer it the day it appears. Go and find what was actually said and when, quote your own words rather than the document if you have them, and put the position back plainly. Use the tone you’d use for any other factual correction in the engagement, which means an even register and the contract left in the drawer. If the honest answer is that it was ambiguous, say so and price the difference from here. Arguing about a sentence written in March is expensive, and it rarely wins anything worth the cost.
Can I say no to the person who signs the invoices?
Yes, and it’s the mechanics that change rather than the answer. A sponsor can genuinely change the plan, so what they need is a set of options: what it would take, what it does to the end date, and what could come out of the current plan to make room for it. Give them the trade explicitly. A fixed budget with movable priorities is the ordinary situation, and a client who is only ever offered additions will simply keep adding. Where the request is one you would decline at any price, say that plainly and early, in one sentence, and expect the relationship to be better for it.
I already agreed to something I should not have. Can I take it back?
Yes, if you move quickly, and the cost of it roughly doubles every week you leave it. Own it once in the opening line, name the specific piece rather than reopening the whole agreement, and bring an alternative with you, because a bare withdrawal is the version people mind. Keep it short: a long explanation reads as guilt, and it invites a negotiation you’d rather skip. If it’s genuinely too late to withdraw, do the work. Then say once, in a flat tone and nowhere near an invoice, what it took, which sets the frame for the next request rather than settling this one.
The short version
The answer rarely costs you the client. The delay costs you, because four days is long enough for somebody to plan around a yes. Silence costs you, because an unanswered request gets filed as agreed. Absorbing the work and letting it show costs you, because it turns a gift into a debt. And producing the statement of work costs you, because it turns an adviser into a supplier in one sentence. So sort the request before you write anything. It’s one of five things, and only one of them is a refusal. Most are really about sequencing, or about who should do the work. Then put the answer near the top. Give one reason about the delivery rather than about your capacity. Offer what you can do instead, with a date on it. Finish inside two paragraphs. Keep the temperature of the email exactly where it has always been, because stiffening into the passive voice sends a bigger message than the refusal does. On a call, hold with an hour attached, repeat rather than rephrase when they push, and write the answer down the same day. Route requests from people who cannot decide instead of refusing them, and leave their manager off the thread. Decline outright, and without a price, the work outside your competence, the document written to a conclusion, the part in somebody’s internal argument, and the standing calls that quietly become an engagement of their own. If you said yes and should not have, take it back inside a day and bring something with you. And when the same request keeps arriving in the same area, stop refusing it and go and redraw the line, because that’s a scope drawn wrong rather than a client chancing it. The update that keeps a decision visible, the note after the meeting where it came up, and the question of who belongs on the thread are each taken separately in this collection.