How can a hospital director say no to a team with a legitimate need?

When needs and resources do not align

When a team asks for another person on a shift, more time for consultations, or a safer distribution of work, the hospital director should first establish what problem lies behind the request. They can acknowledge the pressure they have observed before turning to staffing or financial constraints. After all, the absence of an available position does not mean the need for another nurse is unfounded. The conversation should separate two questions: whether the current way of working needs to change, and whether the requested resource is available now. That way, the refusal concerns a specific option, not the credibility of the staff. This distinction also creates room to ask how long the team can work under current conditions and which consequences need to be addressed immediately.

Understanding the staff’s perspective

Before delivering the refusal, the director can ask what is placing the greatest strain on staff: delayed consultations, the shift rota, or tasks completed at the expense of other duties. Asking for a specific account of the impact of the missing resource helps distinguish consequences that need immediate attention from those that can be discussed at the next review. A systematic review of 42 studies describes associations between leaders’ empathy and employees’ relationships, attitudes, and well-being, but the studies define and measure empathy differently. Nor do they consistently establish the effectiveness of particular behaviors. Asking about the team’s perspective is therefore a way to understand the problem better, not a technique that will secure acceptance of the refusal.

Fairness in a refusal has several dimensions

Staff may regard the outcome itself as unfavorable while judging separately how the decision was made and explained. A meta-analysis of 183 studies distinguishes fairness in allocation, procedures, treatment, and explanations; it does not, however, prove that any one way of conducting the conversation is effective. The director should therefore state a clear criterion for choosing between competing needs, rather than appeal to their own patience or expect trust without an explanation. Staff also need an opportunity to provide information that was missed in the assessment and to know how to challenge an overlooked fact. Respectful treatment does not replace these steps. When limited resources must be allocated, the team should understand both the reason for the refusal and how to correct a decision based on incomplete information.

How to explain what is missing

Saying “it can’t be done” leaves the team guessing. The director should identify the resource that is lacking and the period for which the constraint applies. Not having funds for another shift is different from not having available candidates, or from needing approval outside the hospital. It is worth explaining what can be changed locally and what must be referred to a higher authority for a decision. The director could say plainly: “I understand the need for an additional shift. Right now, we’re funding emergency department coverage; I’ll revisit this proposal during the budget review.” If amounts or dates are known, they should be given. The team then knows which constraint applies today and which decision would have to change.

What can be done despite the refusal

Refusing another staff position does not end the conversation about work that still needs to be done. The director can suggest a partial change to the rota or a short pilot of another approach, but should first check with the team whether it addresses the most pressing problem. They must also assess whether it would shift risk to patients or another group of staff. If there is no feasible alternative, it is more honest to agree on a reduced scope of tasks than to continue expecting the full workload after refusing the request. Any reduction in services also requires an assessment of its effects on patients. A statement of intent to improve matters is not enough: someone must be responsible for the next step, and the condition on which it depends must be clear.

When to revisit the request

At the end of the conversation, it is worth specifying when the request will be reassessed. This could be the date of a budget review or an event, such as a position becoming available. The director should also record what information will be needed then: staffing availability, the volume of additional tasks, or changes in workload. Staff will then know what they can submit instead of waiting for a vague “we’ll see.” The date of a discussion must, however, be clearly distinguished from a promise to approve the request. The review may uphold the refusal if the constraint still applies. Until then, the team should know who is collecting the data, who will make the decision, and how to report a change in circumstances that calls for an earlier response.

How to respond to dissatisfaction

Dissatisfaction after a refusal does not necessarily mean staff have failed to understand the explanation. The director should give the team space to describe its consequences without demanding immediate approval. It is useful to distinguish an emotional response from new information that may require a changed decision or urgent action to make the work safe. If staff identify a task that cannot be done safely with the resources available, the problem must be documented and someone assigned to address it. This does not require a promise to reverse the refusal. After a while, the director should check whether the agreed scope of work really matches available staffing. Returning to the team in this way reveals the cost of postponement, rather than treating the matter as closed after one conversation.

Declining a request for another staff position does not mean a director doubts that the team is overloaded. What matters is explaining the constraint, checking the effects of the decision, and agreeing when to revisit the request.

Using Empatyzer to prepare a refusal for a hospital team

A hospital director sees that the team is overloaded but has to refuse a request for another staff position. To prepare for the conversation, they can use Empatyzer: in a conversation with Em about themselves, they can draft a response that first acknowledges the staff’s need, then explains the current constraint and gives a date for reassessment. Their own profile may help them spot a tendency to ease dissatisfaction too quickly, for example by making a promise they cannot yet keep. In team mode, they can then consider staff members’ differing expectations around autonomy and fairness to prepare a clear explanation of the decision criteria. They can also practice with Em how to invite the team to assess feasible alternatives together and specify the information and timing needed to revisit the request. The aim is not to persuade everyone to agree, but to prepare a refusal that makes clear what happens next.