…

Five Penalty Rate Mistakes Australian Retail Operators Make When Building the Roster

You build the roster Sunday night. The hours look fine — a bit heavy on Saturday, but you've been busier. Then Thursday rolls around, you run payroll, and the number is a few hundred dollars higher than you'd mentally pencilled in. You scroll back through the week looking for the extra hours that aren't there, because it wasn't extra hours. It was the rate.

If that feeling is familiar, you're almost certainly making one of the five below. None of them are exotic. All of them are quiet — they don't show up when you're staring at the grid on Sunday night, only when the bill lands.

Mistake 1: "I just put them on 8 to 5 Saturday."

The roster scenario: a casual rostered 8am–5pm Saturday. One block. One rate in your head — the "Saturday rate."

Under the General Retail Industry Award, Saturday ordinary hours for a casual aren't a single flat number. There's a Saturday loading on ordinary hours, and if that shift pushes the person past the daily or weekly ordinary-hours threshold, you're now into overtime rates on top — which is a different, higher multiplier again. A nine-hour Saturday where someone's already done four weekday shifts is not the same cost as a nine-hour Saturday where it's their only shift of the week.

Where it bites: you budgeted a flat Saturday number across nine hours. Payroll applied the correct mix of ordinary-Saturday and overtime rates. The gap is real money, and it shows up most often on the casual who's also working three or four weekdays.

Mistake 2: "I forgot the loading sits on top."

The roster scenario: a casual on Sunday. You know Sunday has a penalty rate. You apply it. Done.

This is the single most common underpayment I see in small retail, and it's the one operators feel worst about when they spot it — because it's not aggressive, it's just a misunderstanding of how the maths stacks. A casual on Sunday isn't paid the Sunday penalty rate. They're paid the Sunday penalty plus the casual loading. The 25% casual loading doesn't disappear because the day attracts a penalty. It rides along.

Where it bites: you mentally costed Sunday at the penalty multiplier. Payroll costed it at the penalty multiplier plus 25%. On a six-hour Sunday shift, that's not a rounding error. Multiply by the three or four casuals you've got on the floor for the Sunday trade and it's the line item that surprises you most often.

If you've never sat down and looked at how the loadings stack day-by-day, the penalty rates reference is worth a read before your next rostering session. Not as a legal exercise — just so the numbers in your head match the numbers payroll is going to run.

Mistake 3: "I treated the public holiday like a Sunday."

The roster scenario: it's the Queen's Birthday Monday. You're open. You need three casuals. You roster them like it's a Sunday, because Sunday is the highest rate you usually deal with and a public holiday "feels Sunday-ish."

Public holiday rates under the retail award are a separate, higher multiplier than Sunday. They're not Sunday plus a bit. They're their own band. And the minimum engagement on a public holiday can differ from your normal weekend minimums depending on how you've classified the staff member.

Where it bites: the wage bill for the long weekend comes in noticeably above what you costed. You assumed a Sunday-equivalent day with Sunday-equivalent rates. You got a public holiday day with public holiday rates. The difference per casual per hour is meaningful — and you've usually got more casuals on for a public holiday trading day than a normal Sunday, so the error compounds.

Mistake 4: "The weekday roster looked clean."

The roster scenario: it's Wednesday. You've got a casual on 2pm–9pm to cover the late shift. Nothing about that looks expensive. It's a weekday. It's seven hours. You move on.

The blind spot: under the retail award, weekday evening hours past a certain time attract an evening loading on top of the ordinary rate. The hours past 6pm Monday to Friday aren't priced the same as the hours before 6pm. If your late shifts routinely cross that line — and most retail evening shifts do — there's a loading on every hour past the threshold that you might not be costing in your head.

Where it bites: this is the quietest of the five, because the roster looks completely normal. There's no weekend in sight, no public holiday, no overtime trigger. Just a Wednesday. But if you're regularly running 4pm–9pm or 2pm–9pm shifts and not accounting for the evening hours, you're under-costing every late-trading weekday you've got.

Mistake 5: "I split the shift to dodge it."

The roster scenario: you've spotted a penalty window — say, the late-evening hours or a stretch that would tip someone into overtime. You're a step ahead of the award. So you split the shift. Instead of one 4pm–9pm block, you put a different casual on 4pm–6:30pm and another on 6:30pm–9pm. You've sidestepped the penalty window. Or you've put the same casual on two short blocks across the day.

The problem: the retail award has minimum engagement provisions for casuals. If a single shift gets split into two short blocks, you can trigger the minimum engagement twice — and the floor is usually three hours per engagement. So a 2.5-hour block and a 2.5-hour block aren't paid as five hours. They're paid as two three-hour minimums. Six hours of pay for five hours of work. The penalty you dodged was smaller than the minimum you doubled.

Where it bites: you feel clever on Sunday night and you feel less clever on Thursday. Splitting to avoid a penalty almost never saves money unless you've actually checked the minimum engagement maths against the penalty maths. Most of the time, the unsplit shift is cheaper.

Before you sit down to build next week

The thread through all five is the same: the mistake happens when you're committing people to times before you've looked at which hours attract which loading. Sunday night, kettle on, dragging names across a grid, costing in your head.

The fix isn't a different tool. The fix is doing the rate lookup before the grid, not after the bill. Know that this week has a public holiday in it. Know which of your casuals is going to cross the weekly threshold. Know that your Wednesday late shift has evening hours on it. Once you know what each hour costs, the roster you build is a different roster — sometimes by fifteen minutes here or there, which is often all it takes.

The penalty rates reference is the lookup. Keep it open in a tab while you roster.

What a cleaner roster actually solves (and what it doesn't)

Honest bit. Schedaddle doesn't enforce award compliance. It won't block you from rostering a casual into a shape that triggers minimum engagement twice, and it won't auto-calculate the Sunday-plus-loading rate for you. Award interpretation and pay calculation are payroll's job — that's what HankHR is for.

What rostering in Schedaddle does do: it shows you the week clearly enough that you can see the late shifts, the public holiday, and the casual who's about to cross into their fifth day. It runs a geofenced time clock so the clock-in data ties back to the shift you actually rostered, instead of someone's memory of when they walked in. And it exports clean hours to payroll, so on Thursday you're not the detective trying to reconcile a paper sign-in sheet against a spreadsheet against a bank transfer.

That's the boring promise. Fewer surprises on payroll day, because the inputs are cleaner. Not because the software made the award decisions for you — because you made better ones in front of a clearer picture.

Five mistakes. If you've made one of them — and most of us have made at least three — which one was it? I'd genuinely like to know which one stings the most when you spot it. It's usually not the one operators expect.