I run a small SaaS team in Australia, and I kept watching hospitality venues burn hours on rosters in spreadsheets — then get stung by the wage bill they didn't see coming, or by a Fair Work rule they didn't know they'd broken.

So I built Roster Flow: rostering software for Australian small business. Cafés, venues, retail, any team that runs on shifts. And building it taught me that the Fair Work rules aren't a compliance layer you bolt on at the end. They shape every feature, because the roster is where the rules actually bite.

Here are five rules that shaped the product.

1. Show the cost before you publish it

Most rosters are built blind. You place the shifts, publish the week, and only find out what it cost when the pay run lands. That's backwards. A roster is a spending decision, and the person making it should see the number while they're still making it.

So the estimated wage cost adds up as you build — per shift, per day, per week — with weekend and public holiday loadings applied automatically for your state. If Saturday is going to cost more than you thought, you find out on Tuesday while you can still change it, not on payday when you can't.

2. The one-hour shift that costs two hours

Under the Hospitality Award, a casual shift has a two-hour minimum engagement. Roster someone for one hour and you're paying for two. It's the kind of rule that looks small on paper and quietly eats margin across a whole roster.

This is why the roster has to know the rules, not just the hours. When a shift is too short to be worth rostering, the person building the week should see that before they publish — not discover it in the pay run.

3. Roster the break in. Don't skip it.

Breaks aren't spare time you can trim when the week gets busy. Under the Hospitality Award, a shift over a certain length carries a meal break, and skipping it is the kind of breach that shows up later as a complaint, not as a saving.

So breaks are rostered in, not assumed. If a shift needs a break, it's on the roster where everyone can see it. The roster is the record of who was there and what they were owed — treat it that way and the arguments mostly disappear.

4. Pay real hours, not rostered hours

The roster says what you planned. The clock says what happened. The pay run should follow the clock.

Staff clock in and out on any phone, no app download. At the end of the week you review the exceptions — the late finish, the early start — approve the hours together, and send them to the payroll system you already use. On Roster Flow that's Xero on paid plans, with MYOB coming soon; the free plan exports the same approved hours as a CSV. And keep the records: Fair Work requires employment records to be kept for seven years, and the roster plus the approved timesheet is the cleanest version of that record you'll ever have.

5. Copy last week. Don't rebuild it.

The biggest time saving in rostering isn't a clever feature — it's not starting from a blank page. Most weeks look like last week, with a few things moved. Copy the week, change what moved, publish. That one action is worth more than any template.

What it is

Roster Flow is the focused tool for teams that don't need an enterprise HR suite. It does the week between the roster and the pay run, and stops there: copy last week's roster, see the estimated wage cost as you build, let staff clock in on any phone, approve the hours and send them to Xero. It deliberately doesn't do recruitment, performance reviews, pay runs or award interpretation — those belong in your payroll system.

It's free permanently for up to 5 staff, every feature except the payroll connection, no card, unlimited venues. Paid plans are $29 a month for up to 10 staff, $49 for up to 25, and $79 for up to 50 — AUD including GST, with 28 days free on paid plans.

If you run a café, a venue, or any small shift-based team in Australia, have a look: https://rosterflow.com.au

And if you've been burned by a rostering rule you didn't know existed, I'd genuinely like to hear which one — the comments are open.