A waiting list still needs a conversation

What we found in the news

NHS England’s communication principles for people waiting for care (opens in a new tab), updated in October 2023, call for information suited to the person and their circumstances. One particularly useful phrase is:

“including likely and honest timescales”

— NHS England, October 31, 2023

The guidance concerns people waiting for NHS care. Our reflection here is about the everyday communication around a community service’s waiting list. It does not transfer clinical prioritization decisions to a booking team.

An honest estimate may be disappointing. A confident estimate that nobody can stand behind creates another problem for someone already trying to make plans.

Why this matters to us

Imagine a program coordinator receives a call about a place requested several weeks ago. The caller has no new question about eligibility. They want to know whether they should arrange something else for next month.

The coordinator can see the request, but cannot explain when it will be considered. A colleague might know more. That colleague is away.

At genus, we think the waiting period deserves its own operational attention. People continue to have commitments, preferences, and questions while an organization is deciding what it can offer. Silence leaves them to interpret the situation for themselves.

Agree what the team can actually explain

Start with the information colleagues are authorized and able to provide. Is the request complete? Is anything still being checked? Who can explain the next decision? When will the organization review the position again?

Keep these distinctions clear in staff guidance. Being on a list is different from having a confirmed place. A review date is different from a start date. A possible alternative needs checking before it becomes an offer.

Where no reliable estimate exists, say so plainly. Then give the person something useful: an agreed contact route, an explanation of the next step, or a date when the team will provide an update even if the position has not changed.

That commitment needs an owner and time in the working week.

Ask how the wait fits into someone’s life

A short conversation may reveal that the person’s circumstances have changed. Perhaps the day originally requested no longer works. Perhaps they would like to consider another location. Perhaps they simply prefer a telephone update to an email.

Give them a straightforward way to provide relevant changes through the organization’s approved process. Explain who will review the information. Staff should know where to refer questions beyond their role, including concerns that need a professional assessment.

Avoid making people repeatedly retell sensitive details just to find the right contact. Equally, do not assume a family member should receive every update. Agree the appropriate person and communication arrangements.

Check the handover between an update and an offer

When a place becomes available, the earlier conversation should help the team make a relevant offer. Before calling, check whether the recorded preference is still current and whether the practical arrangements can be confirmed.

Leave room for a decision. Someone who has waited a long time may still need to discuss transport, work, or another commitment. A hurried yes can conceal questions that deserve an answer.

After a busy month, review a few waiting-list conversations with colleagues. Where did they have to guess? Which questions kept returning? Use those findings to improve the explanation and the responsibility behind it.

What this means for the people you serve

A person should be able to understand what has been agreed and what remains uncertain. Offer a way to ask questions that fits their communication needs. Choosing to explore another service, postpone a request, or remain on the list should be a conversation they can take part in.

The genus connection

Today, configured genus care-team workspaces can support day-program reservation and waitlist workflows. Available modules, permissions, and local processes shape how an organization uses them.

A recorded status helps colleagues find the request. It does not establish a reliable start date or replace a thoughtful update. The organization still owns the offer, the explanation, and the follow-through.

One question for your next team meeting

If someone called about their place on our waiting list today, what useful answer could every relevant colleague give?