Last-Minute Surgery Cancellations: How Hospitals Analyse the Preventable Causes

What counts as a last-minute cancellation?

Before comparing departments, agree on the event you are measuring: a cancellation after the theatre list is approved, a cancellation on the day the patient attends, or a rescheduling identified earlier? Keep these categories separate and decide how to count a patient whose date changes more than once. The definition suggested here serves the improvement question and the organisation’s recording system; it is not a standard regulatory definition.

If definitions differ, one department can look better simply because it records postponements outside the cancellation log. Review a sample of original theatre lists against the final record rather than relying only on causes picked from a drop-down menu. Add when the barrier was found, who found it and what was known when the date was given.

Why do on-the-day cancellations deserve this attention?

NHS England’s guidance on theatre productivity describes cancellations as a major source of lost value in surgical pathways and says most are avoidable. ^[2] The early screening guide published by NHS England with the Centre for Perioperative Care and the Royal College of Anaesthetists notes that up to one third of on-the-day cancellations are for clinical reasons, such as the patient being unfit for surgery. ^[1]

These are figures from the English NHS and should not be presented as rates for Gulf hospitals. Their value is in framing the question: how many clinical causes could have been found and dealt with before the patient reached theatre?

Why is “patient not ready” not a good enough reason?

The early screening guide recommends screening and risk assessment as early as possible, when surgery is first considered or joining the waiting list is discussed, and at the latest soon after the patient is added to the list, followed by support to optimise their health before surgery. It also recommends that a patient who is not yet ready is not given a surgery date until readiness is confirmed, with a senior clinical decision-maker deciding whether they stay on the waiting list while being optimised. ^[1]

“Not ready” can mean a new change in health, an outstanding requirement, instructions the patient did not understand, or an issue that was not reviewed in time. These are different causes needing different interventions. So the review should ask: could the barrier have been found at booking? Was someone named to follow it up? Do not classify a case as preventable before reviewing its sequence of events.

How do you build a log that supports decisions?

Use a primary cause and, where needed, a contributing cause, with a short account of what happened. The template below separates clinical causes from patient preparation and operational capacity. An administrative category does not mean administrative staff decide whether a patient is fit for anaesthesia or surgery.

NHS England guidance recommends checking that a shortage of higher-acuity beds is not causing last-minute cancellations, and raising any concerns about intensive care or high-dependency capacity at the huddle the day before. It lists equipment availability, including business continuity plans with sterile services, among the process weaknesses that can lead to cancellations, many of which can be avoided through better operational management. ^[2] Planning should therefore check that the post-operative bed is available, not just the operating theatre.

Steps for reviewing a single cancellation

1. Rebuild the sequence: when the patient was listed, when the date was given, when the barrier appeared and who found it.
2. Identify the possible detection point: the earliest stage at which the information was available, such as booking, pre-operative assessment or the call before admission.
3. Ask about ownership: was following up this item assigned to a named person or team?
4. Classify after the review: preventable, not preventable, or undecided and needing a clinical opinion.
5. Link to action: what change would have revealed the barrier earlier, and who owns it?

Start with cases where the same cause recurs, as they point most clearly to a process failure rather than an individual case. Share the findings with the departments concerned without blaming individuals, because the aim is to improve the pathway.

What changes before the day of surgery?

NHS England guidance suggests contacting waiting patients at least every three months to confirm they still need surgery and that their health has not changed, contacting them three to five days before admission to confirm attendance, and having a late-cancellation procedure with a standby list to fill gaps at short notice. It links effective scheduling to a structured meeting attended by the right decision-makers. ^[2]

This can be turned into a local readiness checkpoint in which each item has an owner, evidence of completion and a way of handling exceptions.

The WHO Surgical Safety Checklist has its own place inside the operating theatre and cannot make up for a lack of early preparation. Its 2009 implementation manual lists early staff engagement, multidisciplinary involvement, training, local adaptation and ongoing feedback among the factors for successful implementation. ^[3]

Hypothetical example: “equipment shortage” hiding two problems

A hypothetical hospital reviewed its elective surgery cancellations and found that the label “equipment shortage” covered two different situations: an instrument that was not available at all when the list was drawn up, and one that arrived but was not ready for use when needed. Blaming the stores in both cases would solve neither.

The team proposed recording special case requirements at booking, a joint check between theatres and the team responsible for equipment before the day, documentation of exceptions, and an escalation point that allows the list to be changed or the barrier resolved early. No improvement figure is given here; the first step is to pilot the change and collect real data on its effects and any unintended consequences.

How do you avoid improving the measure at the patient’s expense?

Monitor rescheduling delays and patient experience alongside the cancellation rate. The figure can fall because complex cases stop being listed, or because postponement simply moves to an earlier stage without the barrier being addressed. The review team should be clear whether a rise in early postponements reflects better risk detection or a new build-up in waiting.

Give each measure an owner who reviews its data and presents it at the operational meeting, so the figure does not remain a report without a decision.

Keep a decision log showing why an intervention was chosen, who reviews its effectiveness and when it will be revisited. These are suggested improvement arrangements, not accreditation requirements, and decisions about individual patients remain with the treating clinical team.

What needs adapting in the Gulf?

Review the insurance pre-authorisation pathway where it applies, the availability of imported equipment, and the communication needs of patients travelling from other cities. Do not assume these factors apply everywhere; add them to the log when they appear in your data.

If the organisation contacts patients before admission, use a channel patients actually use and a language they understand, and record the outcome of the call in the same log that tracks cancellations, so the call can be linked to what happened on the day of surgery.

When drawing on NHS England’s experience, do not present British rebooking timeframes or patient entitlements as regulatory requirements in the Gulf. The reference point is the rules of each country’s health authority and the requirements of the accreditation body that applies to the facility.

Conclusion

A last-minute cancellation is often a sign of a barrier that could have been found days earlier. Standardise the definition, record when barriers are found and who owns them, and move checks to before the day of surgery, while protecting the decision to postpone when patient safety requires it.