Waiting well, the eight standards, and coming back afterwards

The waiting list measures how long. This is about what happens to the person during that time — being kept in touch with, offered help, and noticed if they get worse — the recovery the clock never covered, the referral and work-up that decide whether the wait should have started at all, the cancer clocks, and the eight national elective experience standards that make it something a board answers for.

1The problem, stated plainly

Every elective system in the world measures the wait as elapsed time and manages it as a queue position. Both are necessary. Neither tells you whether the person waiting heard from anybody, got worse, or was offered any help at all — and the measurement stops dead at the moment of treatment, which is roughly halfway through what the patient would call the episode.

Waiting well, as the King’s Fund frames it, is the idea that the time somebody spends waiting for planned care should be used well: a better, safer, more equitable wait rather than only a shorter one. This document is about the surfaces that make that a working practice instead of a sentiment — and, in section 6, about the eight national standards that turn it into something a board is answerable for.

2Keeping in touch — and the gate before the send

Each person carries a contact cadence, and going past it’s the trigger. What happens next is the part worth reading, because it’s where a well-meaning mail-merge does harm.

Three refusals are built into one send. Somebody marked do-not-contact is skipped before the message is composed. Somebody whose preferred channel is a letter gets a letter, and the column above shows the channel each message will take. And a row that can’t be resolved to a real patient is marked local-only and writes nothing, because a demonstration record has no business writing into a real person’s communications history. Everything that does send is written to the one communications record at /comms-crm, so the clinician who sees that person next can see they were contacted, when, and about what.

3Who you contact first

The default order of a waiting list is the date of listing. That’s fair in the sense of a queue and unfair in the sense that matters, because long waits don’t fall evenly.

Deprivation decile and the CORE20PLUS5 flag travel with the person, so the keep-in-touch list, the prehabilitation offer and the validation effort can be ranked by need as well as by date. Every tile above is clickable and lands on the tab listing exactly those people, filtered; a count you can’t open is a number nobody can act on. The ordering above is what this cohort says, and a production deployment computes it from whoever is on the list that day.

4The six surfaces

5Recovery, and why it belongs here

Splitting the wait from the recovery across two systems is how a person who was contacted every month for four months becomes invisible the week after their operation.

Ready for rehabilitation is recorded separately from discharged. They’re different facts, and conflating them is what produces a bedded rehabilitation place held by somebody who is waiting for a domiciliary care start and not for therapy. The length of stay runs against the target for the pathway, and where it is over, the row carries the reason.

6The eight elective experience standards

Published as PRN02340_ii on 3 July 2026, the standards set out what every elective patient should experience from referral to care-complete. They aren’t a separate programme: seven of the eight are clocks and formats over data the organisation already records, which is why they were reflected in the product quickly — and why embedding them cost no new data entry.

7Why this needed no data-collection programme

The reason a national standard could be reflected quickly isn’t heroics. It is that the standards ask for clocks and a format, not for new information.

8Getting the referral right, and catching cancer fast

The cheapest wait to fix is the one that should never have started. Everything above assumes the right person is on the right list, and that assumption is where a lot of elective time goes missing. This section is the front of the pathway: the referral, the work-up, the advice that avoids a referral, and the one set of clocks where a slow wait is a clinical harm instead of an experience problem.

The clock starts at the referral and stays with it. The referral hub carries the 18-week referral-to-treatment clock per referral: when it started, days elapsed, days remaining, and a status that turns amber at 14 weeks and red past 18. Privately funded referrals are lifted into a separate queue, because the 18-week rules apply to NHS-funded pathways and counting anything else in them flatters the return. The counters at the top of that page for referrals pending, accepted and at risk on RTT are read from the referral store, and the breach-risk scoring is a real call against it. The per-patient clock table underneath is seeded, and the page puts a banner across it saying so instead of letting a buyer find out later.

The optimiser is the part that saves a whole outpatient visit. Each pathway carries a protocol and a list of pre-consultation investigations. From the referral you batch-order that work-up in one action, so the person arrives at the first appointment with results already in. It’s protocol-gated: if the pathway’s mandatory criteria aren’t met the order is refused, and the only way past is to record a reason, which is written into the order and travels with it. Pathways, referrals, waiting times and the ordering itself are live API calls. So is advice and guidance — the referral you don’t make. A clinician asks a specialist a question, the specialist answers, and the request can be escalated when the answer needs to become a referral; requests, responses, escalations and the outstanding urgent count are all real.

The tracking list, ranked by need instead of only by date. The patient tracking list holds the 18-week position, breach and at-risk RAG, specialty breakdown and validation. Its equity lens re-ranks by clinical priority and deprivation decile, showing the uplift it applied to each row, so two people of equal clinical priority aren’t separated by their postcode; CORE20PLUS5 travels with the patient. The same tab counts what could come off the list at all — stable follow-ups suitable for patient-initiated follow-up, pathways with no activity for a year that need validating, duplicates, people already treated elsewhere. The waiting swarm draws the same list as several hundred dots ageing towards the 18 and 52-week lines, coloured by wait, priority or deprivation. All of that’s a demonstration list, and each page says so on its face.

Cancer runs on its own clocks and they’re the ones that matter clinically. The cancer surface tracks the two-week wait, the 28-day Faster Diagnosis Standard, the 62-day treatment standard, multidisciplinary team meetings and systemic anti-cancer therapy. The Faster Diagnosis view is the useful one, because it shows the chain of dates instead of a percentage: referral, first appointment, investigations ordered, investigations done, MDT, diagnosis. When a pathway breaches you can see which link took the time, which is the only version of that number anybody can act on. This surface is seeded throughout.

9Where each part lives

The hub is a coordination layer over modules that already exist. It integrates /comms-crm /waiting-list /rtt-ptl /smart-triage /pifu /social-prescribing /discharge-hub /virtual-ward /comm-needs /referral-hub /referral-optimisation /advice-guidance /cancer-pathways /rtt-swarm and /esign — and duplicates none of them.

10The honest edges