A morning run that is late by the third call
A carer's morning run starts at 7am. Six calls, each 30 or 45 minutes, back to back on the rota, with five minutes between them. The first two clients live on the same estate. The third is across town, over a level crossing, in the school run. By the fourth call the carer is 25 minutes late. The client rings the office, upset, because they were waiting to be helped to get up.
The coordinator knows the run is tight. They built it on a Friday afternoon, fitting new clients around existing ones, on a screen that showed names and times but not where anyone lives in relation to each other.
Why runs do not fit the road
Most home care rosters are built client by client. A new package arrives, and the coordinator finds a carer with a gap at the right time. Over months, runs become a patchwork: calls in the right time windows, but spread across a wide area in an order nobody chose.
Travel time is treated as a fixed allowance, or ignored because the council pays for contact time only. Drivers and walkers are scheduled the same way. Traffic at 8.30am is not the same as at 11am.
Continuity pulls the other way. Clients prefer the same carers, and the coordinator protects that, even when it means a carer crossing town. That is a reasonable choice, but it should be made knowingly.
What unrealistic runs cost
| Effect | Who feels it |
|---|---|
| Late calls | Clients waiting for personal care |
| Shortened visits | Carers cutting calls to catch up |
| Carer stress | Driving fast, eating in the car, leaving the job |
| Office calls | Clients and families ringing about lateness |
| Unpaid travel | Carers' real working time higher than recorded |
Carers leave home care for many reasons, and impossible runs are commonly among them. How travel time is paid is a matter for your pay policy and adviser, but a realistic run is where it starts.
Route-aware scheduling
- Client and carer locations geocoded from addresses, with carers marked as driver, walker or public transport.
- Travel time between each pair of calls calculated from a routing service such as Google Maps or an open routing engine, for the time of day the travel happens.
- Client time windows, required skills, two-carer calls and preferred carers held as rules, so suggestions respect them.
- A run check on your current rota, read from your rostering system's API or export, highlighting calls where arrival is likely to be late given realistic travel.
- Suggestions for reordering or reassigning calls that reduce travel while keeping continuity where you have marked it as important.
- A map view of each run, so the coordinator can see at a glance when a carer is crossing town between every call.
The coordinator stays in charge. The system shows problems and suggests alternatives; it does not publish a rota on its own.
Runs the carers can actually do
The coordinator sees a warning when a run is unrealistic, before it goes to the carer. New clients are added where they fit on the map, not just on the clock. Carers get runs with travel they can manage, and clients see carers closer to the agreed time.
Over time, you can see which areas are hard to cover and where recruiting a local carer would make the biggest difference.
Could this be your rota?
- Runs have the same fixed gap between every call
- Carers are regularly late by mid-morning
- Walkers and drivers are scheduled the same way
- New clients are slotted in by time, not by location
- You cannot see a run on a map