NHS prioritisation interview questions and answers
Explain competing demands, your judgement and the communication that helped others understand the agreed plan.
Applies to: UK-wide
Explain how you reached a priority decision
A prioritisation interview answer should show how you understood the work, recognised competing demands and communicated a realistic plan. Saying that you make a list gives the panel little information about your judgement. Choose one event and explain what mattered in that situation, what you could decide and when another person needed to agree the priority.
NHS Professionals recommends preparing evidence for the competencies in the actual vacancy. The National Careers Service describes STAR as a way to explain a specific event, action, result and learning. These sources support structured preparation. They do not provide one NHS-wide task order, timing formula or scoring key. All worked examples below are original fictional editorial exercises.
Prepare examples for the advertised competencies and explain your own contribution. Its employer-specific model is not a universal NHS framework; source model answers are not copied.
A structure for a specific situation, responsibility, action, outcome and learning. All worked examples here are original fictional editorial material rather than source examples.
Applies to: UK-wide: Adapt the evidence to the actual NHS or HSC employer, profession and responsibility. This guide concerns recruitment preparation. Its administrative and project examples are not clinical triage, staffing-allocation, emergency-response or treatment instructions.
Clarify what the question is asking
“How do you prioritise your workload?” may invite an explanation of your approach and a short example. “Tell us about a time priorities changed” asks for an event. A scenario question may provide specific facts you need to consider. Listen to the wording and answer its emphasis rather than delivering the same memorised paragraph for every version.
For a real example, identify the competing demands precisely. Two tasks may appear similar but serve different purposes or depend on different information. A deadline may be fixed, provisional or misunderstood. Explain what you checked before deciding how to organise your own work. Avoid implying that the loudest request or most senior person automatically determines the right order.
Use a practical evidence map
| Question to consider | Evidence to explain | A useful boundary |
|---|---|---|
| What was actually needed? | The purpose, deadline and required output of each request. | Do not assume similar wording means the same task. |
| What depended on another person? | The information, review or decision still required. | Tracking a dependency is different from owning the decision. |
| What could you complete? | Your responsibility, capacity and relevant learning. | Do not promise a task you are not competent or authorised to undertake. |
| Who needed to know? | How you explained the plan, obstacle or changed position. | An uncommunicated delay can leave colleagues working from a false assumption. |
| What changed afterwards? | The result, remaining issue and learning. | Do not invent a perfect outcome or numerical saving. |
The table helps you describe evidence, not run a healthcare service. In a professional or technical interview, use the actual competence and responsibilities the vacancy requires. A clinical scenario needs relevant professional reasoning and current applicable guidance; an administrative example cannot stand in for that expertise. Be clear about the limits of the example you choose.
Example for an entry or support role
“In an invented community venue, I was preparing a room when a colleague asked me to help with another activity. I checked when each activity needed the space and explained the work I still had to complete. One request depended on the coordinator confirming a booking, so I asked them to agree the immediate priority rather than assume both tasks could be finished together. I completed my agreed preparation and told the colleague which question was still open. The team had a clearer view of what was ready. I learnt to clarify the need and communicate a limit before making a promise.”
- The applicant and event are fictional, with no actual NHS task or operating procedure.
- The candidate explains the competing work and the coordinator’s authority to agree the priority.
- The result is accurate shared information, not an unsupported claim that everything was completed without difficulty.
For your own support-role example, a modest event may be sufficient if it clearly demonstrates the criterion. Explain what you personally noticed and did. Do not invent a healthcare setting if the experience came from hospitality, study or volunteering. State what transfers and keep any essential specialist requirement separate.
Example for administration or coordination
“In a fictional administration role, two teams requested documents for the same afternoon. I checked what each reader needed and found that one document required an approved factual summary, while the other was an early draft for discussion. I confirmed the review dependency and explained my available drafting time to the manager. We agreed which completed section I would prepare first and when I would update the other team. I made the remaining review point clear instead of presenting a draft as final. The learning was to compare the actual output and dependencies rather than prioritise solely by arrival time.”
- This is original fictional preparation material, not an actual service or staff record.
- The candidate distinguishes purpose, review and their own capacity.
- The manager’s agreement is visible, and no staffing, financial or clinical decision is implied.
Example about changing an initial plan
“In an invented project office, I initially treated a routine update as the first task because I thought its deadline was fixed. A colleague explained that another contribution was needed for a review sooner than I had understood. I checked both requirements, acknowledged my assumption and discussed the effect with the project lead. I changed the order of my own work and told the people affected what would be available. One non-essential section moved to the next agreed update. I learnt to confirm the reason behind a deadline and make the trade-off visible, rather than quietly change the plan.”
- The project and applicant are invented. The example does not describe a real missed clinical or statutory deadline.
- The candidate acknowledges a specific misunderstanding and the action taken to correct it.
- The result includes an agreed limitation, showing reflection without claiming perfect performance.
A development example can be credible when it explains a genuine change in understanding. You do not need to manufacture a failure or confess something unrelated to the role. Choose an event you can discuss honestly, including who knew about the changed plan and what you would check earlier next time.
Example for Band 7 or another senior responsibility
“In a fictional service-improvement project, several teams wanted different additions to the next review pack. I was coordinating the work, so I asked the sponsor to confirm the decisions the review needed to inform. I compared the requests against those questions and identified which contributions were ready, which needed further review and which were outside the agreed purpose. I presented the choices and dependencies to the sponsor, then confirmed the agreed plan with contributors. Some background material was deferred. I learnt that senior coordination includes making the basis and limits of a plan understandable, rather than saying yes to every request.”
- The applicant, project and outcome are fictional. This is not a clinical workload, budget or staffing-allocation method.
- The coordinator explains their responsibility and the sponsor’s decision authority.
- A real senior candidate should add the scale, accountability and evidence appropriate to the actual vacancy.
Show communication as part of prioritisation
Explain who needed an update and what they needed to know. A useful message distinguishes the confirmed plan from an open question, identifies the effect of a change and avoids promising an outcome outside your control. Your example should show how another person could continue their work using that information.
Do not describe communication as a final apology after a hidden delay if the event actually required earlier discussion. Equally, avoid claiming that you can always prevent changes or complete every request. The evidence should show realistic judgement, appropriate responsibility and a truthful account of the result. Keep private patient, staff or service details out of the answer.
Practise follow-up questions
- What information did you check before deciding the order?
- Why was the chosen priority relevant to the actual purpose and responsibility?
- Who agreed a change that was outside your authority?
- What did you tell the people affected, and what remained unresolved?
- What would you check or communicate earlier if the situation happened again?
Prepare key points and a fuller account rather than one long script. Follow the actual employer’s invitation and instructions on permitted preparation. If the panel changes the question, choose the evidence that fits. A prioritisation answer should make your reasoning understandable, not recite a slogan about working well under pressure.
Prioritisation interview questions answered
A useful answer explains the actual competing demands, what you checked, your authority, the action agreed and the result or learning. Match the evidence to the role and the question rather than giving one universal task order.
Explain how urgency was understood in the actual event and what other dependencies or responsibilities mattered. A label alone gives little evidence. Clinical and technical scenarios require the relevant professional competence and current applicable arrangements.
Yes, where it genuinely demonstrates the criterion and the employer accepts that evidence. Name the real setting and explain the transferable behaviour without replacing a specialist requirement.
No. Describe what happened truthfully, including an agreed limitation, changed plan or learning. Do not invent a saving, praise or successful result to complete a template.
Show the actual scale, responsibility and decision route, including how you made choices and dependencies understandable to others. Band alone does not define one suitable story across professions.