Your Roster Is a Budget. Start Treating It Like One.

The Fair Work Commission's 4.75% minimum wage increase lands on most retail rosters without ceremony. A few updated award rates in the payroll system, a quiet recalculation, and suddenly the wage line looks different. Most operators absorb it, adjust their roster marginally, and move on. What they rarely do is treat retail roster productivity as the actual question, whether those hours were worth it at the old rate, let alone the new one.

A roster is a spending decision. Every line on it is a commitment to exchange dollars for a set of tasks being completed during a specific window. When wage costs rise, the question isn't just "how do we cover the same hours for less" but "which hours were generating a return, and which were just filling the schedule?"

Task economics: what each shift is actually purchasing

Most retail rosters are built around coverage, not output. The logic is: store opens at 9, closes at 6, here's the headcount that feels right for a Tuesday. That model made sense when labour was cheap relative to revenue. It makes less sense when a casual team member costs $30–35 an hour all-in, and the tasks they're completing between 2pm and 5pm on a Tuesday could be done in less time, at a different time, or consolidated with another shift.

Start by mapping what actually happens in each shift block. Not what the job description says. What actually happens. A typical four-hour afternoon shift in a mid-size specialty retailer might look like this:

• 45 minutes on the floor serving customers
• 90 minutes on replenishment and stock handling
• 60 minutes on admin and transfers
• 45 minutes on general tidying and downtime

That's not a customer service shift. It's a logistics shift with some customer interaction.

Mapping tasks against shift blocks doesn't require a time-and-motion study. It requires honest observation over two or three weeks, ideally across different days and dayparts. Managers often discover that price changes, markdowns, and stock audits are running during peak trading hours for one reason: that's when they've always been scheduled. Not because it makes sense.

The cost of low retail roster productivity

Low-payoff hours are hours where the output doesn't justify the wage investment. They exist in every roster. The honest question is how many there are and what they're costing.

Some low-payoff hours are unavoidable: compliance requirements, safety coverage, minimum shift lengths under the relevant Award. But a significant portion are structural habits. Opening shifts that start 30 minutes before there's anything meaningful to do. Closing shifts padded to cover a task that takes 20 minutes. Double coverage on a daypart that converts 40% of what the peak hour delivers.

Apply the wage increase to those hours specifically. If you're running 180 unproductive hours a month across a small team and wages go up 4.75%, that's not an abstract percentage. It's a number you can calculate and a decision you can make.

Consolidate the tasks. Shift the timing. Adjust the minimum hours. The award sets a floor, not an obligation to schedule inefficiency.

Building a roster from tasks up, not coverage down

The alternative to coverage-based rostering is task-based rostering: building the schedule from the work that needs to happen, then assigning hours to cover it.

Start with a task audit for the week. Every task the store needs to complete: customer service, replenishment, stockroom management, visual merchandising, compliance checks, cash handling, admin. List each with a realistic time estimate. Be specific, "replenishment" is not a task, "replenish the impulse bay after the Tuesday delivery" is a task. The specificity matters because vague tasks expand to fill available time.

Once you have the task list, group by urgency, customer impact, and required skill level:

• Customer-facing tasks belong in your peak trading windows
• Logistics and stock tasks belong in your quieter dayparts or before open
• Administrative tasks should be batched, not scattered across multiple shifts in small fragments

Then build the roster. The hours that result from this process will almost certainly be fewer than your current schedule, sometimes significantly so. The question to ask before adjusting back up isn't "does it feel like enough?" but "what task am I adding this hour to cover?"

What the wage increase is really telling you

Wage growth isn't going to reverse. The 4.75% in 2026 follows increases in prior years and the direction of travel is clear. Businesses that respond by absorbing each increase as a one-off adjustment are running a strategy that compounds against them. A 4.75% increase on an inefficient roster is more expensive than a 4.75% increase on an efficient one — not just in dollar terms, but as a proportion of the return those hours are generating.

The smarter response is to treat each wage movement as a prompt to review retail roster productivity, not just the cost of it. Are the hours you're paying for generating the output you need? Are low-payoff tasks clustered in shifts that could be restructured? Are you scheduling coverage or scheduling outcomes?

The retailers who will manage this well aren't the ones cutting hours indiscriminately. They're the ones who know exactly what each shift is buying them — and make the call accordingly.