The short answer
Before optimising the order of a waiting list, find out who on it still needs to be there. Lists accumulate people who moved away, were treated elsewhere, or no longer need the appointment.
Validation is unglamorous, it is often the single largest capacity gain available, and it makes every subsequent metric more meaningful.
What the system has to track
- When the clock started, by the definition your reporting uses
- Every pause and the reason for it
- Clinical priority, and who set it
- Contact attempts and their outcomes
- Offers made, and whether they were accepted or declined
- The reason for removal, whenever someone comes off the list
The last item is what makes a list auditable. Removals without recorded reasons are where confidence in a list breaks down.
Prioritisation has to be defensible
| Basis | Handling |
|---|---|
| Clinical priority | Set by a clinician, recorded |
| Time waited | Automatic, from a defined start |
| Capacity and skills available | Constraint, not a priority |
| Patient preference | Recorded, does not override clinical |
Any automated ordering must be explainable to a patient who asks why someone else was seen first. That means the rule is written down and the system can show which factors applied.
Offers and fairness
Short-notice offers fill cancellations and can be unfair if the same people are always asked. Rotate, track who has been offered what, and record declines with reasons.
Someone repeatedly declining short-notice offers may have a constraint worth recording rather than a lack of interest.
Report on stages, not just the total
An overall waiting time hides where the delay is. Reporting time spent at each stage, from referral to decision to appointment, shows which part to fix.
That breakdown is usually more actionable than the headline figure, and it is the thing most list systems do not provide.