…
The Retail Roster Habits That Survive the Week
Most retail rosters aren't broken on Friday. They're broken on Sunday afternoon, the moment the first decision gets made. The operator opens a blank week, asks the wrong question first, and from there every other choice is downstream of that mistake. By Tuesday there's a hole in it. By Saturday someone's not answering their phone.
This isn't a list of best practices. It's the five or six habits that separate a roster that absorbs a callout from a roster that turns one callout into a ruined weekend.
Start with when, not who
The failure mode is familiar: you open the roster, look at the availability tab, and start dropping casuals into shifts based on who said they could work. Twenty minutes later you've got a roster that fits the team and has very little to do with the actual shape of the week.
Saturday between 11 and 2 is your busiest three hours. Did you put your two strongest people on the floor for those three hours, or did you put whoever happened to be available across the whole day? If you built the roster availability-first, it's almost always the second one. That's why you'll be sprinting to the till at 12:40 while a casual who's been on since 9 is restocking the back wall.
Flip the order. Before you look at a single name, sketch the demand. When does the door traffic actually hit? When does the delivery land? When is the one window where you genuinely cannot be one person short? Roster those slots first, then fit availability around the demand — not the other way around. You'll cut overstaffing on the slow Tuesday morning and you'll stop running thin during the Saturday rush at the same time.
Anchor the week before you fill it
Every roster has three or four shifts that are non-negotiable. The opener who knows the alarm code. The closer you trust with the cash-up. The one person who can run the till alone if you have to step out to the bank. These are anchors, not variables.
The mistake is treating them as just another shift to fill. You start at Monday 9am and work across, and by the time you get to Sunday close you're realising the only person rostered is the casual who's been there six weeks. So you reshuffle. The reshuffle breaks two other shifts. By the time you publish, the roster is held together with mental string and nobody but you can see why it's structured the way it is.
Place the anchors first. Sunday close goes to one of three named people, full stop. The Saturday open is one of two. Build everything else around those fixed points. A roster with anchors survives a callout because you know exactly which shifts can flex and which ones can't. A roster without anchors collapses the first time someone's sick, because every shift looks equally movable until you realise it isn't.
Rotate the bad shifts on paper, not in your head
Sunday close. Friday late. The 6am stocktake shift the week after a public holiday. Every store has them, and every store has one casual who quietly ends up doing more of them than anyone else.
You know the failure mode. You think you're being fair. You're rotating it in your head. Then in week eleven the casual who's been doing every second Sunday close hands in their notice and tells you, on the way out, that it always felt like they got the worst ones. And they were right, because "fair in my head" isn't a system — it's a story you've been telling yourself.
Write the rotation down where the team can see it. "Sunday close rotates between these four people, in this order." Stick it next to the roster. When someone wants to swap, they swap a slot in the rotation, not just one shift. The win isn't only retention — it's that you stop spending emotional energy on a decision the rota could be making for you.
Cost the week before you publish it
A Saturday shift isn't a Tuesday shift. Under the General Retail Industry Award, casual loading sits on top of the base rate, and Saturday, Sunday and evening penalty rates stack on top of that. The casual who costs you $32 an hour on a Wednesday afternoon costs meaningfully more on a Sunday — and if you didn't think about that when you were building the roster, you find out at payroll, not before.
The habit isn't to become a payroll officer. It's to roster with the cost of each shift somewhere in your peripheral vision. Two questions, every time you publish:
- Did I put my most expensive heads on my highest-margin hours?
- Is there a shift on this roster where I've got three people on penalty rates and the door traffic doesn't justify it?
That's it. You're not optimising to the dollar. You're catching the obvious leaks. The operator who never asks those two questions is the one who looks at the labour percentage at the end of the month and can't quite work out where the money went.
(Penalty rates and casual loading get their own treatment over on the award page — worth a read if you've never sat down and worked through how they stack.)
Publish early, and to the channel they actually check
A roster nobody has seen by Wednesday is a roster that gets callouts on Friday — not because more people are sick, but because casuals who haven't looked at their shifts until Thursday night suddenly realise they've got a clash, and now you're scrambling.
The other failure mode: you posted it in the group chat on Monday, but Jas mutes the group chat because there are 200 messages a week in there, and they didn't see they were on for Saturday until you rang them at 9:15 on Saturday morning.
Two habits here. Publish by Wednesday, every week, with no exceptions. And push it to a channel staff actually open — a roster app that sends a notification to their phone, not another message in the pile. The point isn't the tool; it's that "I sent it" and "they saw it" are not the same event, and pretending they are is what creates a Saturday morning phone call.
This is most of what Schedaddle's rostering is built around — publish once, every casual gets a push, swaps go through the app, and you stop being the message relay.
Build the callout list into the roster itself
This is the single habit that separates operators who absorb callouts from operators who spend Sunday morning on the phone.
When you build the week, for every shift that matters, write down two names who could cover it. Not "I'll figure it out" — two named people who have already said yes to being on the backup list for that slot. They know they might get the call. They know the answer is yes or no, not "let me check."
The failure mode without it is the one every operator knows: 7:04am text, "really sorry, can't make it in." You're now scrolling your contacts at 7:05, trying to remember who said last week they wanted more hours, calling three people who don't pick up, settling for whoever answers first regardless of whether they're the right fit for the shift. The shift gets covered, badly, and you've burned an hour of your Sunday and a chunk of goodwill.
With a backup list, the same callout is a two-minute job. You text the first name. If they're out, you text the second. The whole thing is over before the store opens. It feels almost embarrassingly simple, and yet most rosters don't have it written down anywhere.
Check what actually happened against what you rostered
The roster is the plan. What actually happened is the data. Most operators only compare the two when the payroll numbers look weird at the end of the month, and by then it's a detective hunt — six weeks of timesheets, three casuals' memories, and a vague sense that something doesn't add up.
The leak almost always shows up in the gap. Someone was rostered 9 to 3 and stayed until 4:30 because the delivery was late. Someone clocked in at 8:45 every Tuesday for a 9am start and nobody mentioned it. Someone's "30 minute break" was twelve minutes, three weeks running. None of these are villainy. They're drift. And drift is what eats labour budget.
The habit is a weekly five-minute check: rostered hours vs. actual hours, by person. If your clock-ins tie back to the roster, this is a glance, not an investigation. (Schedaddle's clock is geofenced to the store, so the clock-in is location-verified — which mostly matters because it means the data you're looking at on Monday morning is real, not "Jas reckons they started at nine.")
Once a week. Five minutes. The operators who do this find the leak in the week it happens, not the quarter it happens.
Open this week's roster. Don't read it — interrogate it. Which of these habits is missing? Is there a Saturday shift with no named backup? Is the anchor on Sunday close just whoever was available? Is there a shift you priced in your head as a Tuesday but is actually a public-holiday Monday?
Pick one. Just one. Change it for next week and see what breaks differently — because the goal isn't a perfect roster. It's a roster that survives the week it has to live through.
Which habit is the one you're skipping right now?