The delayed discharge problem: why bed management software alone won't fix it

Nottinghamshire County Council and three local acute hospital trusts faced a familiar coordination problem. Hospital discharge coordinators and social workers were working across different processes and needed access to the same information to make joint decisions.

Their Discharge to Assess process brought those partners into a shared workflow. The public case study describes more consistent working across the three hospitals, with hospital and social care teams able to see the information they needed to progress discharge decisions and reduce delays.

The lesson reaches beyond the technology used in Nottinghamshire. Discharge moves when the people responsible for the next decision can see the same situation, understand what has happened, and act without restarting the conversation. A patient leaves hospital when the pathway lines up, not when one department gains a better view of its own beds.

A widely cited estimate puts the scale at around 1 in 8 general and acute hospital beds occupied by patients who are medically fit for discharge. Digital Health reported the figure in May 2026 in an article arguing that delayed discharge needs a whole-system response.

That figure gives a useful sense of scale, but it needs careful attribution. It is a secondary estimate, not an NHS England statistic in the form often repeated in commentary.

NHS England's official approach uses measures such as the Discharge Ready Date, the Criteria to Reside framework, delayed discharges and delayed bed days. From 30th August 2026, the Acute discharge situation report added delayed-discharge and delayed-bed-day measures by discharge pathway. The change matters because it moves the conversation from a single bed count towards the reason a patient remains in hospital and the part of the pathway where the delay sits.

That shift should change how leaders ask the question. “How many beds are blocked?” describes the symptom. “Which pathway is delayed, who owns the next action, and how long has the patient waited?” gives a team something to work on.

Bed management software has an important job. Hospital teams need a current view of bed occupancy, admissions, transfers, discharges and patient movement. Without that information, staff spend time checking, phoning and reconciling different versions of the ward position.

Access Patient Flow Manager is our solution built for this acute operational problem. It offers a real-time patient-flow view that supports hospital teams with bed occupancy, admissions, transfers and discharges. That view, in our software or rival solutions, can help a Trust identify where pressure is building and which operational actions need attention. It can support earlier escalation, clearer ward coordination and a more reliable understanding of what is happening across the hospital.

The limit sits outside the bed board. A live hospital view cannot create a domiciliary care package, open a community bed, complete a social care assessment or resolve a disagreement about the safest place for a person to recover. Those actions belong to different teams, services and budgets. A system that improves only the acute view may show the delay more clearly while leaving the cause untouched.

NHS England's Model Discharge Pathway treats discharge as a process that spans hospital and community bedded care. It calls for a shared view of expected discharge dates, patients who are ready for discharge and the pathway that will support them.

That model reflects the operational reality. A patient may need a short period of rehabilitation, support at home, a care-home placement or follow-up from community services. Each option carries its own capacity, eligibility rules, assessment steps and handovers. The delay grows when information stops at an organisational boundary or when no one can see who must act next.

This is why discharge planning belongs in the admission conversation. The team does not need to predict every detail on day one. It does need to identify likely needs, involve the right partners early and keep the expected discharge date visible as the patient's situation changes. The Discharge Ready Date guidance gives Trusts a common way to record when a patient no longer meets the Criteria to Reside in an acute bed.

A date alone will not release a bed. It gives the system a point from which to measure the delay and ask who needs to act.

The evidence and policy direction point to four practical requirements.

• One shared operational picture
  Acute, community and social care teams need access to the information relevant to their part of the pathway. The view does not have to mean one giant system. It does need consistent definitions, current status and a clear route for updates.
  
  
• A named next action
  Every delayed discharge needs more than a status. It needs an owner, a decision and a date for the next review. “Awaiting care package” tells leaders less than “home-care provider to confirm two daily visits by Thursday, reviewed by the discharge coordinator.”
  
  
• Pathway-level measures
  A system should separate delays caused by short-term rehabilitation, social care assessment, home-care capacity, equipment, transport and patient or family choice. Each requires a different response. A single blocked-bed total hides that difference.
  
  
• Early planning with real capacity in view
  Discharge teams cannot plan from a list of theoretical options. They need current information about community beds, care packages, transport and local support. Where capacity does not exist, leaders need that fact early enough to change the plan or escalate the constraint.

Digital tools can support each requirement. They cannot replace the workforce, funding and clinical judgement that make the pathway function.

The strongest case for solutions like Access Patient Flow Manager are inside this wider model. Tools can help hospital teams maintain a live view of flow, coordinate actions across wards and identify bottlenecks before they become invisible in a spreadsheet or a morning meeting.

That acute-side visibility matters. A Trust cannot improve patient flow if staff cannot agree on the current position. It also creates a better starting point for conversations with community and social care partners, because teams can discuss the same patients, dates and pressures rather than exchange partial updates.

A software product should hold its place in the system. It is a way to make hospital flow more visible and manageable. It is not a substitute for care capacity beyond the hospital boundary. That distinction strengthens the case for using it as part of a wider discharge approach.

When a delayed discharge review shows that beds remain occupied after the patient is ready to leave, ask:

1. Which discharge pathway does this patient need, and where does that pathway currently stop?
2. Who owns the next action, and when will the team review it?
3. Can acute, community and social care teams see the same status and expected date?
4. Which delays repeat each week, and which organisation can change the constraint?
5. Does the current patient-flow view help staff act, or does it only describe the pressure?

The answers will show whether the problem sits in bed visibility, pathway capacity, information sharing, ownership or a combination of all four.

The NHS has spent years treating delayed discharge as a capacity problem because the occupied bed is easy to count. The harder work sits in the chain behind it: the community team that needs to assess, the care provider that needs to accept, the family that needs support, and the hospital team that needs to keep the plan moving.

In the last few days, Prime Minister Andy Burnham unveiled plans for a National Care Service; previously shelved proposals under his predecessor that would see social care in the UK overhauled to tackle the issues of staff recruitment, retention, fair pay, training standards, and most importantly adequate provision of care and care settings so that hospitals could be freed to focus on more appropriate care.

Big picture actions are important and welcomed, but better bed visibility remains part of the answer too. It helps Trust teams see demand, coordinate movement and protect capacity for patients who need acute care. The whole system still has to act on what that visibility reveals.

The next phase of discharge improvement should connect those two tasks: measure the delay by pathway, give each action an owner, share the information across the boundary where the patient moves next, and then use patient-flow software to help people act on the picture, rather than mistake the picture for the solution.