A late visit needs a response, not just an update

What we found in the news

NICE’s 2015 home-care guidance calls for contingency plans to be put into action:

“when visits are missed or late”

The guidance connects this with monitoring risk and keeping people informed. It does not mean a generic message resolves every delay. Read the NICE recommendations (opens in a new tab).

Why this matters to us

From a scheduling desk, a delayed visit can look like a gap to rearrange. For the person at home, it may interrupt the shape of the day. They may be waiting to begin an activity, wondering whether to call, or unsure whether an alternative arrangement has been made.

A message saying someone is running late can be useful. It is not the same as checking what the delay means for this person and agreeing what happens next.

We are interested in that space between notification and response. It is where a clear service process needs to meet the person’s actual circumstances.

Start with the individual plan

Consider an illustrative afternoon when a worker’s earlier visit takes longer than expected. The coordinator can see the next visit will be delayed. The response should follow the service’s approved process and the person’s individual plan, including any required professional escalation.

The coordinator needs to know who is assessing the effect of the delay and who is arranging the next step. A person with a time-sensitive need should not be treated as another interchangeable slot on a rota.

This article does not provide a risk-assessment method or a rule for how long a visit can wait. Those decisions require the appropriate professional judgment and local procedures. The operational point is that somebody must own the response, not merely record the changed time.

Make the update useful to the person

An honest update can explain what is known, what is still being checked, and when the person should expect another contact. If a replacement is arranged, the service can explain who is coming and how the person can recognize them.

Communication should use the person’s agreed route. A message in an app will not help someone who is expecting a telephone call or who cannot access that app. Where a chosen supporter is involved appropriately, the service should be clear about what they have been asked to do.

Avoid promising an exact arrival that has not been confirmed. Uncertainty is easier to work with when it is acknowledged and followed by a reliable next update.

Do not make informal help the invisible backup

A relative or neighbor may be willing to help on a particular occasion. That does not make them an automatic substitute for a service.

Teams should check whether any proposed arrangement is appropriate, agreed, and actually available. Someone who helped last month may be working today. The person receiving care may also prefer a different option.

Once the arrangement is made, close the loop. Has the replacement visit happened? Did the person receive the promised call? Is there an unresolved concern that needs to reach another professional? A delay can be marked resolved in a scheduling system while still leaving the person uncertain.

For leaders, repeated delays deserve review of the service conditions behind them. Staff should be able to report unrealistic travel time or a visit that routinely needs more support without being reduced to a punctuality score.

The genus connection

Today, configured genus communities can support shared calendars, agreed tasks, and authorized communication. Those capabilities may help teams keep practical follow-up visible around a change in arrangements.

They are not a claim that genus automatically detects a missed visit, assesses its risk, or dispatches replacement care. Organizations need to establish those service responsibilities and use the appropriate systems. Our interest is in helping the people involved understand the agreed next step and who will follow through.

A useful update is part of care. So is making sure the update leads somewhere.

One question to take away

When a visit is delayed, can your team explain who owns the response and how the person will know what happens next?