SCHADS for rostering: the parts that actually bite

This is for the coordinator building next week’s roster, not the payroll officer reconciling last week’s.

Most of the damage in SCHADS rostering happens weeks before anyone notices it. A coordinator builds a roster that looks fine on a calendar — a shift here, a sleepover there, a quick top-up visit squeezed between two clients — and the cost implications only surface when payroll runs the timesheets, or worse, when an audit years later finds a pattern of underpayment. By then the roster has already been worked. The fix is a back-payment, not a rebuild.

The handful of provisions below are the ones that most often cause this gap between “looks fine” and “costs more than planned”: minimum engagement, broken shifts, sleepovers, and travel between clients. None of them are exotic. All of them are easy to build into a roster without realising it.

If you want the wider primer on how these pay elements work and where they get lost on the way to payroll, that’s a separate piece: SCHADS award basics for care rostering. This one is narrower — it’s the list of things to look for while you’re still building the week.

The award sets a minimum number of paid hours for a single shift, regardless of how long the actual work takes. If a coordinator rosters a 45-minute check-in because that’s what the client needs, the worker is still owed the minimum engagement for that shift — the shorter booking doesn’t reduce the cost. Roster three of those in a day for three different workers instead of consolidating them into fewer, longer visits, and the gap between “hours rostered” and “hours paid” adds up fast, without a single line item looking wrong on its own.

A broken shift is one that’s split into two or more separate blocks of work in a day with an unpaid gap in between — a morning support visit, a gap, then an evening one, for example. The award constrains how that gap can be structured and how many breaks a single shift can be broken into, and a broken shift often carries its own allowance on top of the ordinary rate. Rostering software that just shows two calendar blocks doesn’t tell you whether the gap between them is compliant, or whether the day has quietly become a broken shift that needs to be paid as one.

Sleepover shifts — where a worker is required to be on-site overnight but is primarily sleeping — are paid differently from active shift time, but the award doesn’t stop at the rate. It also governs how long a sleepover shift can run, how many sleepovers can be rostered in a row before a worker needs a break from the pattern, and how much rest has to follow a sleepover before the same worker can be rostered again. A roster that gets the sleepover rate right can still get the frequency or the rest period wrong, and that’s the part that’s harder to spot by eye across a multi-week roster.

When a worker travels from one client to the next within a shift, that travel is generally working time under the award, separate from the client-facing hours either side of it. It’s easy for a roster to account for the two visits and miss the travel between them entirely, especially when the visits are built as two independent shifts rather than one continuous piece of work. The cost isn’t just the missed minutes — it’s the pattern of missing them across every worker who does multiple visits a day.

The common thread across all four is timing: each one is a rule that’s cheap to fix on a draft roster and expensive to fix on a paid one. A coordinator who can see, while still building the week, that a shift is under minimum engagement, that a gap has turned two visits into a broken shift, that a sleepover pattern doesn’t leave enough rest, or that travel between two client visits hasn’t been accounted for, can change the roster instead of explaining a back-payment.

That’s the practical argument for checking award mechanics at the roster stage rather than the payroll stage — the roster is still free to change; the paid timesheet isn’t.

Corella runs nine SCHADS checks over the draft roster — minimum engagement, break between shifts, broken shift, shift span, daily and weekly overtime, sleepover length, sleepover frequency, and rest after a sleepover — surfaced as a chip on the shift, a weekly breach banner, a per-worker summary, a warning at assignment, and on the printed staff roster (deliberately not on the client-facing print). It warns rather than blocks, because sometimes a provider has to knowingly wear the cost, and every threshold is configurable per organisation. Paid travel time is claimed at clock-off as part of the timesheet.

Worth being precise about what this isn’t: it’s a set of rule checks a coordinator can verify by hand, applying award rules to a draft roster — not an interpretation engine, and the payroll calculation behind it runs on a labelled, simplified SCHADS-style band structure rather than a full award interpretation. If your roster depends on nuances beyond those nine checks, that’s still a job for someone who knows the award, or for a system built specifically to interpret it.