Rostering software, or a roster tool of your own.

Where your roster lives now

In most businesses we meet, the roster is a spreadsheet, or several, shift swaps happen in a group chat, and the person who builds it carries the rules in their head: who holds which ticket, who worked a double last week, who can't do nights. When someone calls in sick at 5am, that person rings down a list until somebody says yes. It works because one person is careful, and it costs you. It takes hours of a manager's week. It makes mistakes nobody sees, such as a name spelled differently in different files, so a calculation quietly stops matching. And it carries risk, because the hours nobody writes down, like a training day, never count toward anyone's limits. In a spreadsheet a person can drop off the board entirely, and nobody notices until a shift goes uncovered.

What rostering software does well

Rostering software exists because most rosters need the same things, and the products do those well. Deputy publishes Lite at $6.75, Core at $8.75 and Pro at $13 per user per month, with payroll as a $5 add-on and a $30 monthly minimum. Tanda bundles rostering, HR and payroll at $12.80 per user per month. All prices here exclude GST. Depending on the plan, you get a staff app for shifts and swaps, clock-in and timesheets, Australian award interpretation and a link to payroll. They also handle more rules than most people switch on: Deputy can cap hours per shift, day and week and set a minimum break between shifts, and Tanda can stop someone without the right ticket picking up a shift and block a roster that breaks the rules you set. Award interpretation alone is worth the money, because awards change and keeping penalty rates right is a job you want someone else maintaining.

If your team works standard shifts under an award, pick one of these and set it up properly. If you've tried one and it didn't fit, check you turned on qualifications, hour limits and shift offers before you decide it can't do the job. If you're larger, with several sites and an enterprise agreement, look at the workforce platforms built for that scale too, such as Humanforce, which price on quote.

The signs you've outgrown it

Rented software is built for the common case. If a rule can be written as a cap or a gap, such as no more than 12 hours in a day or at least 10 hours between shifts, the software will hold it. The trouble starts when your rules don't reduce to settings: a fatigue policy that looks across a whole cycle of shifts, counts training and call-outs, and sends someone to a supervisor for sign-off at a threshold; an enterprise agreement with its own call-out order and overtime rules; sites that run different processes, one texting the whole crew and sorting out who's qualified afterwards, another ringing down a list in order; cover that depends on who is free, qualified, rested and close enough, and on what moving them does to another site's week. The better products can be set up for some of this, so before you decide, ask their sales teams to show you your own rule working in their product. When it still doesn't fit, you'll find yourself exporting the roster to a spreadsheet to check what the tool can't, while overtime, leave and timesheets sit in other places that someone reconciles by hand. That is a sign the hard part of your roster is particular to your business.

What owning part of the roster looks like

It's 5am and someone calls in sick. You open the roster tool on your phone, tap the shift, and it shows the people who can cover it, qualified for that area and inside your fatigue rules, with what moving each of them does to the rest of the week. You pick one, the tool drafts the message, and the change lands on the roster, the timesheet and the overtime count together. Every person carries a status every day, on shift, on leave, training, sick or available, so nobody drops off the board. The tool does the checking, and you still make the call: where a rule is a judgement, like letting someone close to a limit work one more shift, it flags it and leaves the decision with you.

Owning part of the roster doesn't mean replacing everything. The smallest version is a single tool beside the software you rent, such as a cover finder that reads the roster you already have, where the product lets it. The larger version owns the roster and the rules, and sends hours to payroll. Either way, decide where award or agreement interpretation lives. Keep it in a rented product built for it, and you keep paying for those seats. Write your agreement's rules into the tool you own, and they need checking against the agreement, and updating when it changes. Compliance stays yours as the employer whichever you choose, because a tool, rented or owned, only applies the rules it's given.

What each costs, and when it pays

Take a team of 40. Deputy Core for 40 people is $350 a month, or $12,600 over 3 years, and $19,800 with payroll added. A tool of your own starts from $6,000 for a single tool, which takes 4 to 8 weeks. A system that joins rostering, fatigue rules and timesheets starts from $16,000, and one covering several sites and an enterprise agreement costs well above that floor. On top of either you pay for hosting, support, and changes when your rules or agreement change, and we state those costs in the quote. You own it outright, with no per-user fee, but it rarely replaces payroll, so most businesses keep a rented payroll alongside it.

On subscription maths alone, a build seldom wins for a team of 40 on an award, and if that's you, rent. A build pays when the rules are the cost. Say a manager spends 6 hours a week checking fatigue and chasing cover by phone, at $70 an hour all-in: that is about $21,800 a year, before any overtime called out of order or a limit missed because a training day was never recorded. Put your own numbers on those first. Owning also brings jobs that renting hides: backups, keeping the tool running, and an answer to what happens if the people who built it are no longer around. A tool built properly answers that one with the code in your own accounts, a written runbook, and a roster that exports to a spreadsheet every day, so the old way still works as a fallback.