Saying No With a Number
How to decline a claim in a way that survives the conversation, the four elements of a usable refusal, and why a refusal without a number is heard as an opinion.
A refusal without a number is heard as unwillingness. A refusal with one is heard as arithmetic, and arithmetic can be argued with, escalated or accepted — all of which are better outcomes than resentment.
The reconciliation in “Saying No With a Number” is strongest when assumptions and current work records can be examined separately. A team considering see the complete platform overview for attendance point system can add time and project context, with transparent settings, limited access and a clear correction route around consequential decisions.
The whole purpose of a capacity account, from the claimant's point of view, is that it makes a no into something they can do something about.
As a separate benchmark for “Saying No With a Number”, see Deloitte human-capital resources. Keep source data, calculation, override and decision visible as distinct steps.
The four elements
What exists. What is already promised. What this claim would need. And what would have to change for it to be possible.
Four sentences. They convert "we can't take that on" into a position that the claimant can test, which is the difference between a negotiation and a complaint.
Showing what is already promised
The part most often omitted and the most persuasive. A claimant who sees the other nine claims understands the situation immediately, and frequently proposes their own solution.
Visibility also moves the conversation from the planner to the portfolio: the claimant's quarrel, if they have one, is with the priority rather than with the person declining.
What would have to change
The fourth element is what distinguishes a refusal from a rejection. "This becomes possible if the regulatory return moves to the central team, or if it starts in April rather than February" gives the claimant two routes.
Offering them is not weakness. It is what makes the refusal a planning statement rather than a verdict.
Refusing in writing
Short, specific and sent the same day. The verbal version will be remembered differently by the two people in the room, and the difference surfaces when the work does not happen.
Three or four sentences in a message, copied to the book, is sufficient. Formality beyond that reads as defensive.
The refusal that should be escalated instead
Where the claim is contractual, regulatory or carries consequences the planner cannot weigh, the answer is not a refusal but an escalation with the arithmetic attached.
Knowing which is which is a matter of the priority bands: anything in the top band is not the planner's to decline.
What not to say
Not "we're very busy", which is unfalsifiable. Not "the team is at capacity", which invites the response that everybody is. And not a promise to fit it in if possible, which is absorption dressed as helpfulness.
The last is the most common and the most damaging, because it transfers the problem to whoever is doing the work without telling them.
The claimant who escalates
Expected and healthy. An escalation with the account attached goes to somebody who can see the whole book, which is exactly where a contested allocation should be decided.
Planners who regard escalation as failure end up absorbing claims to avoid it, which is how the account quietly stops being true.
Refusing consistently
The same arithmetic applied to everybody, including the claims it is awkward to decline. One exception made for seniority undoes a year of consistency, and everybody notices.
Where an exception is made, record it as one: "claim admitted above the line by decision of X, displacing claim Y". That line is uncomfortable and it is what keeps the rest of the book honest.
The number that makes a no stick
Not the shortfall. The specific figure this claim would need and what it would displace: "this needs 300 hours; the only uncommitted hours this quarter are 80; the rest would have to come from claim Y."
Displacement is what makes the cost visible. A refusal that only cites a shortage invites the belief that a bit more effort would cover it.
The four sentences, written out
We have 2,061 available hours this quarter. 1,840 are already committed to Project A and the regulatory return. Your claim needs about 300. It becomes possible if it starts in April, or if something currently committed moves — and that decision sits with the portfolio board rather than with me.
Five lines, sent the same day. It is a refusal, it is checkable, and it names who can overturn it.
The annual total of declined work
Worth publishing once a year: how many claims were declined, totalling how many hours, and what happened to them afterwards.
In most organisations a third of declined work was done anyway, somewhere, by somebody — which is either a capacity argument or an argument that the refusals were wrong, and both are worth knowing.
After the refusal
Keep the claim in the book, marked declined, with its date. Declined claims that vanish from the record reappear as new claims next quarter, and the organisation never learns how much it is turning away.
A year of declined claims, totalled, is a number worth taking to whoever decides the establishment.