Made by people who run a bakery and a catering business

We built Roster Flow for the week we work: a bake that starts before the street is awake, event crews at a different address from one job to the next, and every hour still reaching payroll by the pay run.

A baker carrying a tray of fresh bread rollsCatering staff setting out glassware for an outdoor event
Stock photographs of the kind of work we do, not our own kitchen.

Two businesses, one week

Run a bakery and a catering business at once and the roster is never one thing. There is a crew that starts in the dark, a counter that opens when the bread is out, and a list of casuals who make up whichever event is on, wherever it is.

Those crews barely overlap, and they all come out of the same wage bill and the same pay run. A spreadsheet can hold the roster. It cannot warn you that the Saturday wedding and the Saturday bake both have the same person on them, and it has no idea what anybody actually worked.

Roster Flow is the tool that week needs, and it does one job: get a small business from next week’s roster to approved hours in payroll. Everything else is somebody else’s product.

The shape of our week

Two trades on one roster, in the order the week runs.

  1. Before dawn

    The bake starts while the street is still empty, and the crew is gone by the early afternoon.

  2. Morning

    The counter opens when the bread is out, and it is busiest at breakfast and again at lunch.

  3. Midweek

    Smaller catering jobs: a work lunch here, a function there, each at its own address with its own crew.

  4. The weekend

    The biggest bake of the week and the biggest event can land on the same day, with casuals across both.

  5. Pay run

    Every hour worked, in the kitchen, at the counter and on site, has to reach payroll and be right.

What that week needs from a roster

Each of these is in Roster Flow because a bakery and catering week does not work without it.

  • A shift that crosses midnight is one shift

    A 10pm to 6am bake is placed as one shift and counted as the hours worked, not as a negative number the next morning.

    Rostering
  • Every job has its own address

    Each event site can be its own location with its own clock in distance, so the roster reads as who is where.

    Multi venue
  • Casuals say when they can work

    Staff keep their own availability by the hour, in more than one window a day if they need it, so Saturday’s crew is visible before anyone rings round.

    Availability by the hour
  • Clock in at the door, on their own phone

    A 3am start becomes a time record rather than something remembered on Friday, with the distance from the site recorded if you switch it on.

    Clock in and out
  • Set up and pack down are shifts too

    They go on the roster with their own start and finish, so the hours that reach payroll are the hours worked, not the hours the event ran.

    Timesheets and approvals
  • Approved hours go to payroll

    Once they are approved, hours go to Xero, or out as a CSV for any other payroll system. MYOB is coming soon. Pay itself stays in your payroll system.

    Payroll sync

What it refuses to do

  • Interpret awards or calculate pay. You set your own rates and loadings, and the figures on a roster are estimates from exactly what you set. Award interpretation stays in your payroll system, where it is maintained by people whose job that is.
  • Score or grade your staff. Attendance is counted, not judged. Roster Flow will tell you there were three late starts. It will not tell you what that means about somebody.
  • Block you. Rostering somebody over their unavailability gives you a warning with the reason, not a refusal. Software that refuses is software people work around.
  • Charge for venues, or hold features back. Every feature except the payroll connection is on every plan, including the free one for up to 5 people. Sending approved hours into payroll is what a paid plan adds, and after that the price follows how many people you employ and nothing else.
  • Lose a clock in. A time record is a pay record. Hours survive a failed payroll send, a lapsed card and a lost connection, and every change to one is recorded with who made it and why.

If your week looks like ours

The same two trades, each with a page of its own: the shape of the week, a sample roster, and the questions people in it ask.

Questions about any of this are welcome at hello@rosterflow.com.au, or through the contact page.

Get next week's roster out tonight

Add your venue and your team, build the week, and publish it. Payroll can be connected later.

Start freeQuestions? Contact us
Free for up to 5 staff, permanently. No card to start.