| Rostering software is a system that builds and publishes staff shifts, records swaps and unavailability, and costs a roster before it goes out. The unit it works in is the shift, so it sits upstream of payroll and apart from the systems that price customer work. |
The roster for next week is a spreadsheet on somebody’s laptop. It went out by group chat on Thursday, three people have since asked to swap by text, and Saturday afternoon still has nobody in it.
Nobody has counted what the week costs either. That figure turns up a fortnight later in the payroll run.
Ask what the finished work turns into. Work quoted against a job number ends as an invoice, and the software that runs quotes, jobs and invoices handles it. A shift works differently: somebody had to be there between eight and four whether the phone rang or not, and that time gets paid for as a wage cost.
Treat the following as illustrative. A Dunedin operator runs two sites seven days a week with 28 staff on rotating shifts, and builds every roster by hand.
The duty manager spends five hours a week building the roster and reworking it after swaps. At a loaded $38 an hour, about $9,880 a year.
Shifts are published before anybody costs them, so about six hours a week across the two sites turn out to have been overstaffed. That is about $8,736 a year at $28 an hour.
Hours are retyped from the roster into payroll every fortnight, three hours a cycle, and disputed hours get corrected afterwards. About $4,160 a year.
Those three lines come to about $22,800 a year. None of it appears as a software line in the accounts, because it is spread across management time and wages.
What Is Rostering Software Used For?
Rostering software is used to decide who works when, publish that to staff, and keep a record of every change to it. In a small business it replaces a spreadsheet, a group chat and a wall planner with one place managers and staff both read.
The shift is the unit it works in: a block of time somebody has to cover, which exists even when no customer work is booked into it.
Payroll sits downstream and works out what those hours are worth. Choosing a payroll product is a separate decision.
What is the difference between a roster and a timesheet?
A roster is the plan for hours that have not happened yet, and a timesheet is the record of hours that have. A rostering system holds both and shows you where the two disagree.
Timesheets against a job number belong with the system that prices work for a customer. The hours in a roster are never billed to anybody, so they are measured as a wage cost.
Which businesses need a roster system?
Any business that sells open hours needs a roster system. A cafe, a shop, a clinic, a rest home, a gym or a yard with two crews all have to cover a time window whether or not the phone rings.
Look at the shape of the week. If somebody has to be there between fixed hours and the person covering it changes, a roster exists even if nobody calls it one.
Rest homes feel it hardest, because the cover runs around the clock and cannot be thinned out on a slow night. Technology in aged care and rest homes covers the rest of that picture.
Staff scheduling software is the other name vendors use for this category, and the international products call themselves employee scheduling software. Search any of the three and you get much the same shortlist.
What Can Rostering Software Do That a Spreadsheet Cannot?
A spreadsheet cannot do four things that matter: publish a roster staff can read on a phone, hold a swap or an unavailability request as a record, cost the week before it is published, and apply break and minimum-hours rules while the roster is being built.
The spreadsheet will hold the grid. Everything around the grid happens in a group chat nobody can search six weeks later.
When somebody disputes a shift, you need to know what was published and when it changed. A chat thread running back two hundred messages will not settle it, and somebody has to read the whole thing anyway.
The break and minimum-hours rules are the least visible of the four things a spreadsheet cannot do. A system that knows a rest break is due catches it while the roster is still a draft.
The other case is the morning somebody rings in sick an hour before the doors open. Rebuilding the week on a phone takes about ten minutes, and everybody sees the new version at once.
How do staff see the roster and request a swap?
Staff see it through an app on their own phone, with the published roster and a request button against each shift. The request goes to a manager, and once approved the roster updates for everybody at once.
Handled that way the swap leaves a dated record with the name of whoever approved it, so nobody has to take somebody’s word for it later.
How do you cost a roster before you publish it?
The software multiplies each rostered shift by the right pay rate and totals it against the revenue you expect. You see the labour cost percentage while you can still change it.
Most operators notice that change first. Once the hours are worked there is nothing left to decide.
Watching labour cost move over months is a job for business reporting software that sits above your operational systems. On a Thursday afternoon you need one figure, while the roster is still a draft.
Why Do You Need Clock-In as Well as a Roster?
You need both because a roster is a plan and payroll has to be paid on what happened. Clock-in, which vendors sell as time and attendance, records the actual start and finish against each rostered shift.
The two numbers are never identical. Somebody starts ten minutes early, a shift runs forty minutes late, a break gets skipped, and none of it reaches payroll unless something recorded it.
In most businesses that difference covers the subscription several times over, in wages you are already paying.
How big is the gap between rostered and worked hours?
The gap commonly runs between two and five per cent of the wage bill, in both directions. Some of it is unpaid work the business owes, and some of it is paid time nobody asked for.
Neither half is deliberate. They come from a roster and a payroll that nobody ever reconciled against each other.
The Dunedin operator above had never measured it. The roster lived in a spreadsheet and the clock-in was a signature on a printed sheet, so there was nothing to compare.
What is buddy punching?
Buddy punching is one staff member clocking in or out on behalf of another, and most time clocks exist to stop it. Products stop it with a photo taken at the punch, a PIN, a QR code, facial recognition, or a geofence that refuses a clock-in from outside the site.
Decide how far you want to go before you shop. A photo at the punch settles most arguments and costs nothing extra. Facial recognition and geofencing collect biometric and location data about staff, which is worth taking advice on.
How Do Rostered Hours Get Into Payroll?
Approved hours reach payroll through a single connection that carries them across with nobody retyping anything. Roster to payroll integration is the first thing to ask a vendor about, and the answer decides how much admin the software actually removes.
The path has five points. The roster is published, then swaps and unavailability get logged, staff clock in and out, a manager approves the exceptions, and the approved hours go to payroll.
Each of those is a place the data can stop. The fifth gets sold as a tick box and often turns out to be a comma separated values file, or CSV, that somebody uploads by hand.
What breaks in a roster to payroll connection?
Pay codes, most often. The roster knows a shift fell on a public holiday, and payroll needs that arriving as the right code against the right day.
Ask for a test in your own payroll product with your own pay codes before you sign, whether that is Xero Payroll, MYOB, PayHero, Smartly or iPayroll. A demonstration against the vendor’s sample data proves nothing about your setup.
The same questions come up whenever two business systems have to talk to each other, and the business software integration work behind any such link goes through them in full.
Does Rostering Software Handle New Zealand Public Holidays?
Yes for the products built for New Zealand, and no for several sold from offshore. The test is whether the rules engine knows about the otherwise working day, Mondayisation, alternative holidays and time and a half.
Employment New Zealand tells employers they cannot take somebody off the roster on a public holiday that would otherwise have been a working day, to avoid the entitlement, and that failing to recognise it is against the law. The roster appears in its own published list of factors for deciding the question.
So the roster is evidence. A system that keeps the published version and every change to it is doing compliance work alongside the scheduling.
What is an otherwise working day?
An otherwise working day is a day an employee would have worked if it had not been a public holiday or a day of leave. It decides whether they get a paid day off, whether working it earns time and a half, and whether an alternative holiday follows.
Two people doing the same job can land differently. The Employment New Zealand worked example has one staff member on a three-day rotation missing both Good Friday and Easter Monday, while the colleague they alternate with is paid for both.
Rotating rosters make this hard. Anything that varies week to week needs the pattern held somewhere a manager can check.
What changes when the Employment Leave Act replaces the Holidays Act?
Leave moves to hours-based accrual against standard hours, and public holidays get a new otherwise working day test. The Employment Leave Act 2026 received Royal assent on 6 August 2026 and comes into force on 6 August 2028, replacing the Holidays Act 2003.
The two-year gap is deliberate. MBIE says it is there so payroll providers and employers can change their systems, which makes the next two years the window for getting hours recorded properly.
Hours-based accrual raises the value of an attendance record. A system that already knows the hours each person worked holds most of what the new calculation needs.
What Records Must an Employer Keep About Hours Worked?
You must keep the number of hours worked each day in a pay period and the pay for those hours, recorded as you go. Business.govt.nz states that personnel files must be kept for at least six years and pay records for seven, and that details have to be recorded on a daily basis.
The same list covers hours worked on public holidays, the payment for public holidays both worked and unworked, and alternative holidays taken. A roster and a clock-in record produce most of it.
A labour inspector can ask for these, and so can the employee or their representative.
What Should You Check Before Buying a Rostering System?
Check six things, and only one of them is about features. The rest decide whether the system survives contact with a real week.
- Who owns the data, and how you get it out. Ask for an export of your own roster and attendance history in a readable format, and ask what happens to it if you leave.
- Whether the app works with no signal. Staff clock in from cool stores and from rural yards, and an app that needs a live connection fails in both.
- Whether the rules engine is built for New Zealand. Public holidays, Mondayisation and the otherwise working day all need to live in the product, where a manager can rely on them.
- How hours reach payroll, tested in your own payroll product with your own pay codes and a full cycle.
- What happens on the morning somebody has to rebuild the roster before opening. Ask to see a published roster copied, then edited and republished, with staff notified.
- What it costs when headcount moves. Per-user pricing on a business with seasonal staff behaves differently from the quoted monthly figure.
Ask to see that roster rebuild demonstrated. A vendor who cannot rebuild a roster live has never watched somebody do it under pressure.
How Much Does Rostering Software Cost in New Zealand?
Expect $4 to $12 per employee per month for rostering with attendance included, plus a one-off setup. The price is per person, so the monthly figure follows headcount. The setup depends on how many systems it has to talk to.
| What you are paying for | What it covers | Indicative range |
|---|---|---|
| Subscription for rostering and attendance | Per employee per month, usually billed on active staff | $4 to $12 a person a month |
| Setup and configuration | Sites, roles, pay rates, break rules and the roster templates | $1,200 to $3,500 |
| Payroll connection | Mapping pay codes, joining the two systems and testing a full cycle | $800 to $2,500 |
| Clock-in hardware, where used | A tablet or terminal per site, for places phones do not suit | $300 to $900 a site |
| Training | One session per site plus a session for managers | $400 to $900 |
Set that against the illustrative operator above. Twenty-eight staff at $6 a head is $2,016 a year, and the setup, the connection and the training come to about $3,800 in the first year.
Roster building drops from five hours a week to about ninety minutes, which is roughly $6,900 of somebody’s time back. Halving the overstaffed hours saves about $4,400. The retyping goes entirely, and once the corrections stop with it that is another $3,700.
Call it about $15,000 recovered against $5,800 of first-year cost, so about $9,200 net. From year two only the subscription remains, so the figure settles near $13,000 a year.
Those figures scale with headcount and with how many sites one roster has to cover.
How Do You Roll Out a Roster System Without Losing a Week?
Run the new roster alongside the old one for two full cycles, then stop building the old one. Rollouts fail when a business switches over on a Monday and finds out on payday that the hours never arrived.
- List every site, every role and every pay rate before you look at products, because that list is the configuration.
- Load one site and one team first, and leave everybody else on the spreadsheet.
- Publish the same week in both systems and compare the totals before anybody relies on the new one.
- Run one full pay cycle end to end, with hours flowing into payroll and a manager approving the exceptions.
- Check the first public holiday that falls inside the trial and confirm the entitlements came out right.
- Switch the remaining sites once a full cycle has cleared with no manual correction.
Steps one to three take a fortnight and cost nothing but attention. Steps four and five decide whether payday works, and neither can be proved without a real pay cycle.
Book a Rostering Systems Review
Exodesk has supported South Island businesses since 1989 and works with clients across Canterbury, Otago and Southland from offices in Christchurch and Dunedin. We scope, set up and connect the business software a company runs on, from the roster and the clock-in record through to the pay cycle at the end of it.
Contact us today to discuss how we can help your business or connect with us on LinkedIn to stay updated with more insights.
Frequently Asked Questions
Is a rostering system the same thing as payroll software?
No. A rostering system plans and records who works which shift, and payroll software calculates and pays what those hours are worth. The handoff between them is a single connection that sends approved hours across.
Can you run a roster in Excel?
Yes, and it stops working somewhere around fifteen staff or two sites. A spreadsheet holds the grid and cannot publish to phones, record a swap, cost the week before it goes out, or send hours to payroll. Most businesses move when a payroll error or a disputed shift makes the missing record expensive. The spreadsheet usually survives as a printed backup on the wall.
Is there free rostering software?
Yes, several products offer a free tier, and the limit is usually the staff count, the number of sites, or the payroll connection. A free plan will roster one small team and stop short of sending hours to payroll, and that handoff saves the most admin. Price the paid tier you will actually need before you start, because migrating a second time costs more than the subscription.
Does a rostering system work out public holiday pay?
No, not the final calculation. A rostering system works out the entitlement and passes the hours across, and payroll does the maths. A product built for New Zealand will flag that a shift falls on a public holiday, apply the otherwise working day test to the roster pattern, and mark the alternative holiday owed. Test it against your own roster before you buy, because offshore products often miss the New Zealand rules.
What is time and attendance software?
Time and attendance software records when staff actually started and finished, against the shifts they were rostered to work. It is usually sold with rostering as one product, and it supplies the hours that payroll gets paid on.
Do staff need a smartphone to use a roster app?
No. Most products offer a browser login, a printable roster, and a tablet or terminal at the site for clocking in. Check the offline behaviour if staff clock in somewhere with no coverage.
How long do employers have to keep records of hours worked?
At least six years for personnel files and seven years for pay records. The details have to be recorded on a daily basis, and reconstructing them afterwards does not satisfy the requirement. That covers hours worked each day, the pay for those hours, and the dates and payment for public holidays both worked and unworked. Labour inspectors, the employee and their representative can all ask to see them.
Will a rostering system reduce overtime?
Yes, usually, and the saving comes from costing the roster before it is published. Most operators find some shifts overstaffed once the labour figure is visible while they can still move it. Expect the effect inside the first two or three cycles.
Can employees swap shifts themselves?
Yes, within limits a manager sets. The staff member requests the swap in the app, a named colleague accepts it, a manager approves it, and only then does the roster change.
Does a rostering system integrate with New Zealand payroll?
Yes, most established products connect to the payroll systems New Zealand businesses actually run, including Xero Payroll, MYOB, PayHero, Smartly and iPayroll. The quality of those connections varies a great deal. Insist on a trial run inside your own payroll product, using your real pay codes and one complete cycle. A vendor can say truthfully that a connection exists and still have it map your codes wrongly.
What happens if the internet goes down during a shift?
Staff can usually still clock in on a device that stores the punch and uploads it once the connection returns, provided the product supports an offline mode. Confirm that before you buy, and confirm what happens to a punch recorded while offline. A printed roster on the wall remains a reasonable fallback. Ask the vendor to demonstrate it with the device in flight mode.
Who sets up rostering software for businesses in Christchurch and Dunedin?
Exodesk sets up and supports rostering software for employers across Canterbury, Otago and Southland, working from offices in Christchurch and Dunedin. That covers the configuration, the payroll connection and the pay cycle test that proves it works. Exodesk has operated since 1989 and provides IT support, managed services, cloud, cyber security and AI solutions to New Zealand businesses.
