Skip to content
Corella

SCHADS award checks

Catch the award problem while the roster is still a draft.

Most systems apply award rules at payroll — after the week is worked and the money is already spent. Corella runs nine SCHADS-shaped checks over the roster while it's still a draft, so the overtime conversation happens when the shift can still be moved, not when the pay run makes it permanent.

How it flows

Award-check flow: nine SCHADS-shaped checks run over the draft roster as it's built, findings are flagged on the shift and summarised per staff member, the coordinator fixes the shift or accepts the cost knowingly — it warns, it never blocks — and payday holds no surprise.as you rosterreason on hoverweek banner on a breachwarn, never blockchosen, not discoverednext week, same nine checksDraft rosternot yet workedNine checksSCHADS-shaped · tunableFlagged, in placered breach · amber reviewAward check viewgrouped per staff memberYou decidefix it — or wear itPayday, no surprisethe cost was known

Most systems apply award rules at payroll, after the money is spent. These run while the week is still a draft.

Nine checks, run as you build the week

Minimum engagement. Break between shifts. Broken shifts and their total span. Daily overtime and weekly overtime. Sleepover length, sleepover frequency, and the rest break after a sleepover. Each one is checked against every staff member's week as the roster takes shape — the same nine questions a careful coordinator asks, asked every time, about everyone.

Minimum engagementBreaks, spans & broken shiftsDaily & weekly overtimeSleepovers & rest after

Red is a breach. Amber is a decision.

A red flag means the draft crosses an award limit. An amber flag means something lawful that costs money or deserves a look — overtime loading, a broken-shift allowance. Findings appear where you're already working: a chip on the shift with the reason on hover, a banner when the week contains a breach, an award-check summary grouped per staff member, the same warning at the moment you assign someone — and on the printed staff roster, so the paper on the office wall carries the same flags as the screen. The client-facing print never does: pay warnings don't belong in a participant's hands.

Chip on the shiftWeek bannerPer-staff summaryWarning at assignmentPrinted staff roster
your-organisation's Corella
Week roster board with a red Award check button, a banner reading that one shift sits past a SCHADS limit, and a warning chip on that shift
The week board flags the breach while the roster is still a draft — the reason is on the chip

It warns. It never blocks.

That's deliberate. A provider sometimes has to roster a breach knowingly — a client emergency, a staff request — and wear the overtime. Software that blocks would just push the week back into a spreadsheet. Corella's job is to make sure nobody wears a cost by accident: the warning states its reason, and the decision stays yours.

Warn, never blockThe reason, in wordsYour call, made knowingly

Tuned to your organisation, rule by rule

The SCHADS award lands differently by stream and employment type, and many providers run enterprise agreements on top — so every threshold is yours to set, and every rule has its own switch. Defaults are SCHADS-shaped: a two-hour minimum engagement, a ten-hour break between shifts, a thirty-eight-hour week before overtime. Rules you switch off stay listed in Settings, so nothing is hidden from the next coordinator.

Every threshold configurablePer-rule switchesNothing hidden when off

One engine, one answer

The week board, the per-staff summary, the assignment warning and shift matching all consult the same engine — so the flag you see on a shift is the same answer the ranking used when it suggested who should work it. These checks are prompts to look, never a legal opinion, and they complement Corella's clearly-labelled simplified payroll engine rather than pretending to replace your payroll process.

Board · assignment · matchingPrompts, not legal opinionsSimplified & labelled

Fair questions

Asked about this, often.

Is this award interpretation?
No — and the label matters. These are nine specific, configurable checks with simplified SCHADS-shaped defaults: prompts to look, never a legal opinion. The award applies differently by stream and employment type, and many providers run enterprise agreements on top — which is exactly why every threshold is yours to set, and why pay execution and full award interpretation stay with your payroll process.
Why doesn't it just block a breach?
Because sometimes the breach is the right call. A client emergency or a staff request can make knowingly wearing the overtime the best available decision — and software that refuses would send the roster back to a spreadsheet. Corella warns with the reason and leaves the decision, and the accountability, with you.
Can we adjust the rules?
Every threshold — engagement hours, break hours, span, overtime limits, sleepover rules — is set per organisation, and each of the nine checks has its own switch. Switched-off rules stay visible in Settings so an incoming coordinator can see what's been turned off, not wonder.
Is it AI?
No. It's arithmetic over your draft roster — times, thresholds and rules you can read and check by hand. For pay and rosters we think that's the stronger property: every warning traces to a shift, a threshold and a rule, not to a model's opinion.

See your organisation in Corella.

A 30-minute walkthrough with the people who built it — your workflows, your terminology, not a canned demo.