Rostering for aged care: what is different from disability

If you already roster for NDIS clients and you are now picking up home care package or CHSP work, do not assume the same roster logic just ports across. It mostly does — but three things behave differently in aged care, and getting them wrong shows up as blown travel budgets, inconsistent care, and rosters nobody can explain by the third week. This is for the coordinator or scheduler who needs to know what to actually check before they build the week.

An NDIS roster tends to have longer visits spread across a smaller number of clients per worker per day — a two-hour community access shift, a four-hour support session. An aged-care roster, particularly home care, is the opposite shape: many short visits, often 30 to 60 minutes, stacked back-to-back across a suburb or a town. A support worker in disability might see three clients in a day. A home care worker might see eight.

That density changes what “efficient rostering” means. In disability, the main risk is a gap — an unfilled shift, a worker double-booked, a cancellation nobody caught. In aged care, the roster can be technically full and still lose money, because the time between visits — the driving — is where the day actually gets eaten.

This is the biggest practical difference and the one most new-to-aged-care rosterers underestimate. When visits are short, travel time stops being a rounding error and becomes a real slice of the paid day. Ten minutes between visits, six times a day, five days a week, adds up to more paid hours than most services budget for at the planning stage — and under SCHADS-based arrangements, travel between clients during a shift is generally paid time, not a gap in the timesheet.

The rostering fix is not cleverness, it is sequencing: building routes that minimise dead travel, keeping a worker in one geographic cluster for the day rather than zig-zagging across town, and being honest at the roster-build stage about how much travel a pattern actually generates before it goes live, not after payroll runs.

The payroll fix is visibility: travel time needs to be captured against the actual worker and the actual day it happened, not estimated after the fact. If your system can record paid travel time at the point a worker clocks off a visit — tied to that shift, not batched at the end of the week — you get a roster cost that matches reality instead of a payroll surprise at month end. That is worth checking for specifically when you are comparing systems, because “GPS shows where the visit happened” and “travel time is captured and paid correctly” are two different features, and only one of them protects your margin.

In disability work, continuity matters, but rosters are often smaller and relationships get held informally — the coordinator just knows who goes with whom. In aged care, particularly with older clients living at home, continuity is a bigger deal clinically (a familiar face notices decline faster) and structurally harder to hold, because the roster is bigger, shifts are shorter, and casual and part-time staff cover more of the workforce.

The practical failure mode is a client seeing five different workers in five weeks because each individual swap looked reasonable in isolation. Nobody made a bad decision; the roster just drifted.

Two things help here, and both are roster-building discipline rather than magic: keeping the client’s preferences — who they get on with, who they do not, cultural or language needs — visible on the client record where whoever is building the roster can actually see them, not buried in a case note; and reviewing rosters for pattern, not just for gaps, so a coordinator can ask “how many different people saw this client this month” as a deliberate check, not an accident they notice too late.

Under NDIS, a client’s plan is a set of funded line items with per-item rates and caps — you are checking whether a specific service against a specific code is affordable. Aged care funding (Home Care Packages, CHSP) works differently: it is typically a classification-level budget for a period, and the client draws down against it across whatever mix of services they use. The scheduling question shifts from “is this item still within cap” to “at this rate of delivery, will this client’s package last the month.”

That is a burn-rate problem, not a per-item problem. It means rostering and finance need to look at the same number from different angles more often — the coordinator building next week’s visits and the finance officer watching the month’s spend both need to see whether the current pattern is sustainable, before it is the client (or the provider) absorbing a shortfall. A budget view with a running utilisation bar, checked as part of the normal roster cycle rather than at the end of the period, catches this while there is still time to adjust the pattern.

None of the above replaces the underlying award mechanics — broken shift allowances, minimum engagement periods, sleepover rates, weekend and public holiday loadings. Those apply the same way they do in disability rostering, and they are just as easy to get wrong when visits are shorter and rosters change more often, because more frequent change means more chances to accidentally create a broken shift or drop below a minimum engagement without noticing. If you have not already, it is worth reading through the traps in detail rather than relying on a rostering tool to catch them silently — see SCHADS for rostering: the parts that actually bite for the specifics; we will not repeat them here.

Given the above, the checklist for aged-care-specific rostering is short but firm: can it handle high visit density without the roster view turning into noise; does it capture travel time at the point of clock-off against the actual shift, not as an estimate; can client preferences sit on the record where the person building the roster will actually see them; and does it give you a running utilisation view against a period budget rather than only a per-item cap check. A tool built purely around NDIS line items and single-item caps will handle the funding question badly for aged-care clients, even if the rostering board itself is fine.

Corella’s rostering board (recurring and group visits, sleepover, conflict checks, a job board for open shifts, copy-week for repeating patterns) runs the same underlying engine for aged-care and NDIS clients, with paid travel time captured at clock-off and client preferences held on the client record. Client budgets with utilisation bars work for tracking burn against a period as well as spend against a line item.

It does not do everything a specialist aged-care system might — it is a general care-operations platform, not a Home Care Package funding engine — so if your funding management needs go deeper than budget tracking, check that specifically before you commit. What lands on 1 October 2026 inside Support at Home is covered separately.