Workplace and team automation
Testing shift swaps in NZ staff rostering software
Test a roster change across depots, skills, breaks and payroll. A practical software buying guide for NZ organisations that need reliable cover at public counters.

A library assistant offers to cover a colleague’s Saturday shift. Both staff members agree in a message, but the approved roster still assigns the original person. Meanwhile the replacement is scheduled to open another branch. A useful shift-swap workflow lets staff propose a change, checks whether the service will still have cover, and tells everyone which roster is current.
What should the roster check before approval?
Give each shift a location, times, duties and any capability required to deliver the service. A person who can open the building might still need a colleague authorised to supervise a particular activity. Agree with team leaders which gaps prevent approval and which require a person to make a judgement. Roster rules should reflect the team’s actual employment arrangements.
Employment New Zealand’s rostering guidance discusses demand, hours, breaks and employment agreements. Bring the person responsible for interpreting those arrangements into the design. Test a change involving travel between branches and a break that requires someone else to cover the desk. A simple check for overlapping shifts will miss both conditions.
Include one person who can work at either branch but has no access to one building before opening. The service manager can then decide whether to issue access, change the assignment or schedule an opener. Record the choice where the person publishing the roster can see it.
Whose roster is authoritative?
Keep a published roster version and make pending requests clearly visible. An employee reading a pending request should know which shift they are currently expected to work. Record each acceptance and the approval decision. Define who can handle the request when the usual supervisor is on leave, and when the request expires if nobody decides.
In the demonstration, have a supervisor publish an amended roster while a colleague has the previous version open. Ask that colleague to approve a swap that refers to the old shift. The software should explain what changed and ask them to review the current arrangement. Silently applying the earlier request can undo the correction the supervisor just made.
How does payroll learn what actually happened?
Treat the approved roster as the plan and capture the hours actually worked separately. In the library example, the relief assistant stays late when the building alarm will not set. Show who can submit a correction, who reviews it, and what payroll receives after the pay period closes. Give payroll staff access to the relevant history when they investigate a discrepancy.
Ask a supplier to export the planned and actual shifts, including an overnight example if the service uses them. Give the files to the payroll operator and ask them to reconcile a changed shift without the vendor on the call. Pilot the workflow at one branch and compare uncovered shifts, unresolved requests and corrections with the previous roster. Staff should also be able to say how they would find their next shift if the notification failed.