Case study
Forty Visits, One City, One Morning: Routing Home Care Without Losing Continuity
A home care agency's schedule is a daily negotiation between geography, skill match and the client who wants the same caregiver they had last week. This is the transformation that drafts the day against all three, and lets a coordinator overrule it in one click.
No client engagement behind this piece: it is how this category of product would be transformed, with benchmark-sourced targets.
Who this is for
A typical Ontario home and community care agency
Signed off by Director of operations, with the scheduling lead scoping
Industry
Home and community care (personal support and nursing), 38 caregivers, 4 coordinators, about 190 active clients across a city
Legacy stack
Engagement
Concept
Contents
At ten past six a caregiver calls in sick and four coordinators start rebuilding a day. Forty visits have to move across a city. Some clients need a nurse rather than a personal support worker. Some have not met most of the roster and should not be meeting somebody new today. All of that lives in the coordinators’ heads, and none of it is in the scheduling software, which offers a calendar and no opinion.
This is the transformation we would run for that agency. It is presented as a concept, built on the same method we use in client engagements, so the before, the after, and the path between them are all visible.
Why is scheduling the whole business here?
Because in home care the schedule is the service. There is no waiting room absorbing variance and no building where staff and clients happen to be co-located. A visit that lands late or lands with the wrong person is not an inconvenience, it is the product failing.
The stakes sit with the family. The Canadian Institute for Health Information reports that more than 1 in 3 unpaid caregivers of long-stay home care clients experience distress within a year, and that distressed caregivers provide an average of 38 hours of care a week, twice what non-distressed caregivers provide. For caregivers of seniors with dementia the distress figure is 45%, against 26% for those caring for seniors without dementia.
Read that as an operational constraint rather than a sad statistic. When a scheduled visit does not arrive, or arrives with someone the client does not recognise and will not cooperate with, the hours do not disappear. They transfer to a family member who is already at 38 a week.
Before and after: the morning
Drag the handle. The before is the whiteboard reshuffle; the after is the drafted day designed in its place.
Weighting, stated openly
Continuity outranks travel. The agency can change that, and will be shown what it costs.
Pin anything that must not move. Nothing reaches a caregiver's phone unreleased.
Whiteboard
Skill match and continuity live in four coordinators' heads. Under pressure they are what gets dropped first.
The coordinator still owns the day. What changes is that they start from a draft that already respects skill, continuity and travel, instead of from a blank grid at 6am.
What we built
The concept above is the output of the same engagement steps we run in client work, and several are decisions a competent peer could argue with.
- We weighted continuity above travel efficiency by default, and this is the decision most likely to be argued with by anyone who has optimised logistics before. A router tuned for kilometres produces a better map and a worse service, and in dementia care in particular an unfamiliar face can cost more time than the drive it saved.
- We got client preferences and caregiver constraints out of coordinators’ heads and into structured fields, which is unglamorous, takes weeks, and is the precondition for everything else. An agency unwilling to do that work should not buy this.
- We made the draft explain every change against yesterday, because a schedule a coordinator cannot interrogate is one they will quietly rebuild by hand.
- We built pinning as a first-class action. A coordinator pins a visit and the draft treats it as immovable, which is how the system absorbs the context it will never have.
- We wire evals from day one against the agency’s own historical schedules, scored on continuity preserved and travel time, and every coordinator override becomes a test case.
How it works
The scheduling system stays the source of truth. Care plans, caregiver skills, availability and continuity history feed a drafted day. Travel is calculated rather than estimated. Each visit shows why it landed where it did, and any change from the previous day is annotated. A coordinator pins anything that must not move, adjusts, and releases. Only a released schedule reaches a caregiver’s phone. On a same-morning call-off the affected visits re-draft inside the same constraints and go back to a coordinator, never straight to a client.
Because care plans and schedules stay in Canadian infrastructure and processing runs with zero data retention, the design lines up with what PHIPA expects: a privacy impact assessment before deployment, an agreement naming the processor as an agent under section 17, and an audit log on every access.
Why this pays back
The measurable return is travel time, which in home care is real money and is currently invisible because much of it is absorbed unpaid by caregivers between visits. Break-even for the first slice is about thirty-five travel hours removed per week at the agency’s own loaded cost.
The limit worth saying before anyone signs: this cannot create caregivers. An agency short-staffed relative to its client list will get a better-ordered version of an impossible day, and the drafted schedule will make the shortfall more visible rather than smaller. Several coordinators have told us a version of that visibility is itself worth having. An operations director who wants a scheduling tool to solve a recruitment problem should not buy this, and should be told so before the engagement rather than during it.
The outcomes
Unpaid caregivers of home care clients experiencing distress
More than 1 in 31
Industry benchmarkWeekly hours provided by distressed unpaid caregivers
38 hrs2
Industry benchmarkInputs the daily schedule is balanced against
Geography, on a whiteboard Geography, skill, continuity, travel
1 to 4, explicitly3
Design targetBreak-even, in unpaid travel hours per week
About 354
Design targetTime to the first shippable slice
4-6 wk5
Design target1 Canadian Institute for Health Information, caregiver distress indicator: more than 1 in 3 unpaid caregivers of long-stay home care clients in reporting provinces and territories experience distress within a one-year period.
2 Canadian Institute for Health Information: distressed caregivers spend an average of 38 hours a week providing care, twice the hours provided by caregivers who are not distressed. For caregivers of seniors with dementia, 45% show symptoms of distress, against 26% for caregivers of seniors without dementia.
3 Design target measured against the recreated legacy scheduling flow shown in the before/after above, where continuity and skill match live in coordinators' memory rather than in the schedule.
4 Design-target arithmetic, not a measured result. The first slice is a fixed fee; break-even is stated as the number of paid or unpaid travel hours removed per week that would cover it at the agency's own loaded caregiver hourly cost, which the agency supplies.
5 Standard first-slice scope: one geographic zone, one metric, evals and a coordinator approval gate included.
Frequently asked questions
Will this schedule people automatically?
No. It drafts a day and a coordinator releases it. Every change from yesterday is shown with the reason, and a coordinator can pin any visit to any caregiver, which the draft then treats as fixed. The reason is not caution for its own sake: coordinators hold context the system will never have, including that one client is at the end of a bad week and one caregiver is not going back to a particular house.
Does optimising travel mean clients lose their regular caregiver?
That is the real tension and the design resolves it in the client's favour by default. Continuity is weighted above travel efficiency, not below it, so the system will accept a longer drive to keep a familiar caregiver on a familiar client. An agency can change that weighting and will be shown what it costs in continuity when it does. A router that silently optimised for kilometres would produce a beautiful map and a worse service.
What happens with a call-off at 6am?
That is the case worth buying this for. A same-morning call-off currently means a coordinator rebuilding a day by hand under pressure, which is when continuity and skill match get dropped first. The system re-drafts affected visits within the same constraints and shows which clients are affected and why, ranked by care need rather than by convenience. A coordinator still confirms every reassignment.
Does client information leave the agency?
No. Client details, care plans and schedules stay in Canadian infrastructure, processing runs with zero data retention, and nothing trains anyone's model. A privacy impact assessment is completed before deployment and the agreement names the processor as an agent under section 17 of PHIPA. Caregiver location data is treated as employee personal information and is retained only for the shift it relates to.
What would this cost to try?
A fixed-fee first slice on one geographic zone, because routing quality is easiest to judge where a coordinator already knows what a good day looks like. It ships in four to six weeks, and break-even is stated in travel hours removed per week rather than in licences.
Go deeper on the method
The Scheduling Problem Hiding in Your Clinic (and Why an LLM Is the Wrong Tool for It)
Caregivers to visits, patients to rooms, studies to scanners, therapists to a day of clients: it looks like four problems and it is one. Ask a language model to solve it and you get a fluent, infeasible answer. A short quiz sorts your problem into language, search, or both.
Read articleWhy Your Staff Won't Use the AI You Bought (and How to Fix It)
Clinic software fails at the front desk far more often than it fails in the architecture. Here are the five real reasons a working tool sits unused in a practice, and a practical way to close the gap between paid for and actually used.
Read articleMore transformations
Down the Hall, Never Booked: The Internal Referral Nobody in the Clinic Owns
A multidisciplinary clinic's cheapest appointment is the one a practitioner refers to a colleague thirty feet away, and it is the one most likely to evaporate. This is the transformation that catches the referral where it is made, carries only what the patient agreed to let travel, and escalates the ones that go quiet.
Untracked to 5 days
The Refill Line: Turning the Pharmacy's Loudest Conversation Into Something You Can Work in Batches
A community pharmacy answers the same question forty times a day, one interruption at a time, in the middle of dispensing. This is the transformation that lets the request arrive as structured intake instead of a phone call, keeps a pharmacist signing every fill, and measures the change at the counter rather than in a dashboard.
21.7%
Ontario pharmacy professionals naming workload as their top driver of burnout
Get the next transformation in your inbox.
When there is something worth your time, you will be first to know. No spam, unsubscribe anytime.