Ask a SIL provider how they roster, and you'll hear about the tool they use — the app that builds the fortnight, sends shifts to phones, tracks who accepted, flags a clash. Good tools. They solve a real problem. But they all share the same blind spot: they schedule people against time. They know nothing about funding. They don't know that the participant in Room 2 is funded for 1:1 active support overnight, or that the house is funded on a 1:3 ratio during the day. They just fill the grid.
So the roster can look perfect — every shift covered, no clashes, everyone happy — and still be quietly wrong in the one way that matters at audit: it doesn't match what the plans fund. This is the check almost nobody runs, because no single system is set up to run it. Rostering lives in one app, participant funding lives in another (or in a plan PDF, or in someone's head), and nothing sits in the middle comparing the two.
What "funded ratio" actually means
In Supported Independent Living, participants are funded for a level of support that's often expressed as a ratio — 1:1, 1:2, 1:3, and so on — and it can change across the day and night. A shared home might be funded at 1:3 during waking hours and shift to a 1:2 arrangement in the evening, with one participant funded for 1:1 active overnight support and the others on a shared sleepover. That funding is set in each participant's plan. Your job as the provider is to deliver support that's consistent with it — and, when an auditor asks, to show that you did.
"Consistent with it" cuts both ways, and both directions cause problems:
Understaffed against funding — the safety and audit risk
On a given night, the roster puts one worker in a home where the mix of participant plans funds more support than that. Maybe someone's 1:1 overnight was absorbed into a general sleepover because that's how the shift got built. On paper the home is "covered." In reality it's staffed below what participants are funded — and need. If an incident happens, or an auditor samples that night's roster against the plans, the gap is exposed. This reads as a continuity-of-supports and safeguarding problem, and it's exactly the kind of thing sampled at a certification audit.
Overstaffed against funding — the money leak
The opposite is just as common and much quieter. The roster runs a level of support above what the plans fund — an extra shift "to be safe," a 1:1 where the funding assumes shared support — and the provider simply absorbs the cost. Nobody flags it because nothing breaks. Participants are well supported and the audit's fine. But every fortnight, real money walks out the door: wages you're paying that no plan is funding. For a provider running on thin margins, this is often the difference between viable and not — and most never see it, because their rostering tool has no reason to mention it.
Why no one catches it
It isn't carelessness. It's that the check falls between two tools. Consider what it actually takes to verify a single night:
- Pull the roster for that home, that night, and read the actual staffing level hour by hour.
- Open every current participant plan for that home and read the funded support ratio — which may differ by participant and by time of day.
- Add up the funded support across the participants present and compare it to what's rostered, for each part of the night.
- Do that for every home, every day, and keep doing it as plans get reviewed and rosters change.
Done by hand, that's hours of cross-referencing nobody has time for — so it doesn't happen. It gets replaced by a feeling: "we've always run it this way, it's probably fine." Sometimes it is. The nights it isn't are the ones that turn into an incident or a non-conformance.
How to actually close the gap
You don't need a data science team. You need to make the roster-to-funding comparison a routine, not a heroic one-off. A few practical moves:
1. Write the funded ratio down, per participant, where the roster lives
The single biggest reason this check doesn't happen is that funding information isn't next to the roster. Capture each participant's funded support level — including how it changes across day, evening and night — in a place your rostering decisions can actually see. If it only lives in a plan PDF in a folder, it may as well not exist when the fortnight's being built.
2. Check the ratio at the point of rostering, not after an incident
The cheapest time to catch a mismatch is before the shift is published. Build a habit (or a system) that compares planned staffing against funded support for each home and flags where they don't line up — before it's locked in, not in the post-mortem after something goes wrong.
3. Treat plan reviews as roster events
When a participant's plan is reviewed and their funded support changes, the roster assumption from last quarter is now wrong. Make "re-check the roster against the new funding" part of what happens whenever a plan changes or a new participant moves in.
4. Keep the evidence
If you've checked and the roster matches funding, that's a piece of audit evidence — capture it. Being able to show an auditor that you actively monitor staffing against funded ratios is a strong signal that your continuity-of-supports system is real, not aspirational.
The takeaway
Rostering tools answer "is everyone covered?" That's a necessary question, but it isn't the one that fails audits or drains bank accounts. The question that does is "does our staffing match what participants are funded for?" — and it sits in a blind spot between systems, which is exactly why it's worth owning. Run the check no one else runs, keep the evidence, and you close a gap that's costing other providers both money and sleep.