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, and the eight national elective experience standards that make it something a board answers for.
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 rather than a sentiment — and, in section 6, about the eight national standards that turn it into something a board is answerable for.
Each person carries a contact cadence, and going past it is the trigger. What happens next is the part worth reading, because it is where a well-meaning mail-merge does harm.
The default order of a waiting list is the date of listing. That is fair in the sense of a queue and unfair in the sense that matters, because long waits do not fall evenly.
On the list · overdue a keep-in-touch · enrolled in prehabilitation · deteriorating · CORE20PLUS5 · validated. Every tile is clickable and lands on the tab that lists exactly those people, filtered — a count you cannot open is a number nobody can act on.
Days since last contact against the cadence set for that person, per-row channel override, and a cohort send to everyone overdue at once. Respects preferences, writes to the CRM.
Prehabilitation and health optimisation — exercise, weight, smoking, nutrition, pain, mental health — plus social prescribing for the parts of waiting that are not clinical. Arriving fitter is the one thing a long wait can be used for.
Their position, an expected timeframe and the RTT clock, in language a person can use. Most waiting-list anxiety is not about the length of the wait but about not knowing.
Symptom and outcome check-ins with a green/amber/red reading, so deterioration during the wait becomes a reason to expedite or re-triage rather than something discovered at the pre-op assessment. Also carries validation and patient-initiated follow-up.
Surgery → discharge to assess → community rehabilitation, with the therapies, the length of stay against target and the reason for any delay. The episode does not end when the clock stops.
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.
Published as PRN02340_ii on 3 July 2026, the standards set out what every elective patient should experience from referral to care-complete. They are not 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.
| # | Standard | Where it is met | Status |
|---|---|---|---|
| 1 | Referral decision within 28 days A referral goes on a clock; the decision — accepted, rejected, more information, redirected — is due within 28 days, and recording it notifies the patient of the outcome and next steps in their required format. | /elective-clocks API built and tested ( ElectiveReferralDecision), but the page does not call it — the compliance figure on screen is seeded while a working API sits behind it. | Built, not wired |
| 2 | Clear communication, in an accessible format Accessible Information Standard (DCB1605) correspondence formats captured per person, consented, attributed and audited, with a required-format banner every outbound letter must honour. | /comm-needs Live and wired. PatientCommNeed; patients can self-declare through the portal. | Live |
| 3 | Information while you wait Position, expected timeframe, the RTT clock and what help is available — the Waiting Well surfaces this explainer is about. | /waiting-well Seeded cohort; the contact half is live. | Demonstrated |
| 4 | An update at least every 12 weeks A scheduled waiting update, sent through the communications record, honouring channel preference and the required format. | /comms-crm The CRM send is live; the cadence on the Waiting Well page is seeded. | Live |
| 5 | Reasonable adjustments NHS Reasonable Adjustment Flag adjustments captured alongside the DCB1605 formats, on the same spine, so one record answers both. | /comm-needs Live and wired, including portal self-declaration. | Live |
| 6 | Appointment information at least 21 days ahead Appointment detail issued in good time and in the required format. | /comms-crm · /appointments CRM and appointments are live. | Live |
| 7 | A cancelled appointment re-dated within 28 days Computed from operational timestamps against the 28-day standard rather than typed in by anybody. | /referral-hub · /rtt-ptl The clocks exist operationally; the standards view of them is seeded. | Demonstrated |
| 8 | Care complete, and what happens next The breach worklist and the care-complete tile, with next steps notified in the required format. | /elective-experience-standards Seeded dashboard. | Demonstrated |
/elective-clocks has zero references
in the API client or in the standards page. So the Standard-1 compliance figure a board reads is
seeded, while a working API sits behind it. An earlier version of this explainer rated that
row Live. It was wrong, and rating it Live is exactly how a gap survives a board meeting.The reason a national standard could be reflected quickly is not heroics. It is that the standards ask for clocks and a format, not for new information.
The decision clock, the 12-week update, the 21-day appointment notice and the 28-day re-date all compute from referral, waiting-list and appointment timestamps the organisation already records. Putting a referral on a clock adds nothing to capture — the timestamp exists.
Standards 2 and 5 need no new intake: the required format for every letter is read from the Communication Needs spine and the contact preferences already held — and a patient can self-declare through the portal, so the record maintains itself.
The standards surface is a display-and-clock layer over existing operational and communications data. That is why it is cheap to add and cheap to remove — and why the honest status of each row is visible rather than averaged into one number.
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 and /esign — and duplicates none of them.
| Capability | Where | How | Status |
|---|---|---|---|
| Keep-in-touch send — one patient | /waiting-well | resolve person → POST /crm/patients/{id}/log | Live |
| Contact preference and do-not-contact | /waiting-well | GET /crm/patients/{id}/preferences | Live |
| Cohort update to everyone overdue | /waiting-well | POST /crm/cohort-send | Live |
| The communications record itself | /comms-crm | one timeline per person, every channel | Live |
| The waiting cohort on this page | /waiting-well | seeded — 6 illustrative patients | Demonstrated |
| The real patient tracking list | /rtt-ptl | RTT clock, breach RAG, validation | Live |
| Prehabilitation and wait-well support | /waiting-well | seeded; links to social prescribing | Demonstrated |
| Expected timeframe shown to the patient | /waiting-well | seeded estimate — NOT a forecast model | Demonstrated |
| Symptom and PROM check-ins while waiting | /waiting-well | seeded | Demonstrated |
| Patient-initiated follow-up | /pifu | live module | Live |
| Recovery, discharge to assess and rehab | /waiting-well · /discharge-hub | seeded on this page; the discharge hub is the live surface | Demonstrated |
| Communication needs and reasonable adjustments | /comm-needs | DCB1605 formats + NHS Reasonable Adjustment Flag, on one spine | Live |
| Patient self-declares their communication needs | /portal/comm-needs | portal auth | Live |
| The 8-standard dashboard, breach worklist and board return | /elective-experience-standards | seeded dashboard; the board return is API-backed | Demonstrated |
| Board sign-off on the elective standards return | /elective-experience-standards | routed through commvita Sign | Live |
| Standard-1 referral-decision clock (28 days) | /elective-clocks | API built and tested — the page does NOT call it | Demonstrated |
The waiting cohort on this page is seeded. Six illustrative patients, chosen to show the states the page reasons about. The live patient tracking list is /rtt-ptl — RTT clock, breach and at-risk RAG, validation, inequality-weighted ranking — and it is that list a production deployment drives this from.
The communications half IS live. The keep-in-touch send, the preference lookup and the cohort send are real API calls against the Communications CRM. That is the part most easily faked in a demonstration and it is the part that is real here; the resolve-then-write gate exists precisely so the demonstration cannot cheat.
The expected timeframe shown to a patient is a seeded estimate, not a forecast. No model produces it. Showing a person a confident date the service cannot keep is worse than showing them a range and saying it is a range, so a production deployment should bind this to its own capacity and demand figures before showing it to anybody.
Prehabilitation, the check-ins and the recovery board are representative. The clinical argument — that a long wait is an opportunity to optimise and a risk of deconditioning — is well evidenced. The wiring to a real prehabilitation service, a real PROM instrument and a real rehabilitation caseload is deployment work, and the live discharge surface is /discharge-hub.
Non-SaMD. This module surfaces recorded information and prompts a human to act. It does not triage, does not prioritise clinically and does not decide who is expedited — a deterioration flag is a reason for a clinician to look, not a decision.