When a shift falls through, the clock is running — on continuity for the participant and on your coordinators' evening. Cascades close the gap without the group-text scramble.
A worker calls in sick an hour before a morning shift. The old playbook is a flurry of texts to whoever might say yes, a race to see who replies first, and a coordinator refreshing their phone. It works, eventually, but it is slow, stressful and impossible to do fairly or to evidence later.
How a cascade works
A shift-offer cascade automates the chase. When a shift opens, the system offers it to workers who are actually suitable — qualified, available, nearby, and ideally known to the participant — and escalates through channels until someone accepts:
- A push notification goes to matched workers first.
- If no one accepts within a set window, it escalates to SMS.
- Still open? It escalates again — a call — so urgent gaps do not sit unseen.
- The first worker to accept gets the shift, and the offer closes automatically for everyone else.
Why it beats the group text
Speed is the obvious win — gaps that used to take an hour of phoning close in minutes. But the quieter benefits matter just as much. Offers only go to workers who can genuinely take the shift, so you are not spamming your whole team. Acceptance is first-come and on the record, so there is no favouritism to manage or explain. And because the whole exchange is logged, you can show exactly how a shift was filled if anyone ever asks.
Continuity for the participant
Behind every unfilled shift is a participant whose support did not turn up. Prioritising workers the participant already knows — and filling gaps before they become cancellations — protects the relationship at the centre of the whole service, not just the roster.
Cascades will not eliminate call-outs. But they turn the response from a scramble into a system: faster, fairer, fully documented, and far kinder to the coordinator who would otherwise spend their evening on the phone.