List the requests, required timing and consequences of waiting. Ask the person responsible for the workload to confirm priority when you cannot decide it yourself. Communicate the resulting order and revise it when new information changes the conflict, rather than promising every request first place.
Several requests arrive marked urgent. You begin switching between them because each sender expects attention. The work moves slowly and the deadlines remain uncertain. You cannot give every request the first place in the queue at the same time.
List the tasks and the consequences of waiting. Ask the person responsible for the workload to confirm the order. Where different teams are involved, make the conflict visible rather than privately promising each team that their request comes first.
Communicate the chosen order
Tell affected people when their task is expected to begin or finish. If a new issue changes the order, repeat the check with the new facts. Avoid hiding the delay until the original deadline has passed.
Keep a note of the decision so you do not have to reconstruct it from separate messages. If competing urgency is common, discuss how requests are prioritised before the next busy period. A shared process can make the order clearer even when there is still more work than the available hours can hold.
Two teams expecting the same morning
An illustrative exampleImagine receiving a document correction and a schedule update from different teams, both marked urgent. Put the required outputs and relevant deadlines in one note, including the consequences of each delay. Ask the person who can prioritise the shared workload which should begin first. Tell the other team when its work is expected and what decision set that order. If a new issue changes the consequences, repeat the check with those facts. Keep the chosen order beside the tasks. Both teams can then plan around a visible queue, even when neither receives the speed it hoped for. Switching repeatedly without communicating would leave the timing uncertain for everyone involved.
Make competing urgency visible
Tick the steps as you work through them.
0 of 5 steps checked
When you receive contradictory priorities
Bring the conflict to the appropriate shared decision-maker with the relevant messages and consequences. Avoid privately assuring each sender their task comes first. If no immediate decision is available, state the temporary order you are using where your role allows that judgement, and flag what may be delayed. Recurring conflicts need an agreed intake or prioritisation process. A clear process cannot create more hours, but it can identify who chooses the trade-off and prevent the same request from repeatedly changing order without explanation.
Write the queue decision
Your notes stay in this page. Copy them before leaving; they are not saved or sent to us.
