Nobody starts with software. Every organisation running casual staff starts with a spreadsheet, a group chat and somebody's phone, and for a while that is genuinely the right answer. A tab with twelve names on it is faster than any system you could buy, and it costs nothing.
The question is not whether spreadsheets work. It is when they stop.
Below are five points where the arrangement usually stops holding. None of them is about the number of people you have on the books — plenty of organisations run forty casuals on a spreadsheet perfectly well, and plenty come unstuck at twelve. They are about the shape of the work, not the size of it.
1. You cannot answer "who worked that shift?" without opening three things
The test is specific. Pick a Tuesday six weeks ago and ask who covered a particular room, store or site, what hours they actually worked, and whether the person who approved those hours is the person who booked them.
If answering means opening a spreadsheet, scrolling a group chat and then asking somebody, you do not have a staffing record. You have three partial records that mostly agree.
That is survivable right up until the day it matters — a payroll query, a dispute about hours, an audit, a parent or a client asking who was on. At that point "mostly agree" is the problem, and reconstructing it costs a day.
2. Compliance is tracked by memory
This is the sign that turns from an inconvenience into a real exposure, and it is the most common one we see.
Somebody in your organisation knows that a particular certificate expires around March. They know it because they remember it. It is not in a system that will tell them — it is in a spreadsheet column that is only correct on the day somebody last updated it, which was some time last year.
The specifics differ by industry — a practising certificate in education, a Site Safe card on a construction site, a duty manager's certificate in a venue serving alcohol, a nursing registration in aged care. The pattern is identical. They all have dates, and dates in spreadsheets go stale silently.
3. Filling a shift means texting people one at a time
Most people who run a casual pool have a ranked list in their head. They know who to try first, who is reliable at short notice, and who has worked that site before and will not need showing around.
That knowledge is genuinely valuable. The problem is the delivery mechanism: you are working down it serially, waiting for each person to reply before trying the next. A 7am gap becomes a forty-minute phone tree, and the person doing it cannot do anything else during those forty minutes.
Worse, that ranked list lives in one person's head. Which brings us to the sign that tends to be the actual trigger.
4. One person is a single point of failure
Ask what happens to your casual staffing when the person who runs it is away for two weeks.
If the honest answer is that things get noticeably harder — that somebody covers it badly, or that shifts go unfilled that would normally be filled — then the process is not a process. It is one person's expertise, and it is not written down anywhere.
This is usually what finally forces the change, and it is worth naming plainly: the risk is not that they leave. It is that the organisation has no way to operate at their standard without them.
5. Your invoice and your payroll figure disagree
If the hours that go to payroll and the hours that go on an invoice come from two different records, they will eventually disagree, and somebody will have to work out why.
That reconciliation is pure overhead. It produces nothing, it happens every cycle, and it gets harder the longer the gap between the shift and the moment somebody notices. When both figures come from the same approved timesheet, the question cannot arise.
What actually changes
Worth being precise about what software does and does not do here, because the category is full of overstatement.
It does not find you staff. Aroha Connect is a platform for managing the casual workforce you already have — your own people, in your own pool, employed by you. It does not recruit, supply or vet anybody, and it does not make your organisation compliant. Your team still decides who is fit to work.
What it does is remove the three things above that are really the same thing: information that exists but is not in one place, in a form you can rely on, at the moment you need it.
- One record of every booking, who worked it, and the hours you approved
- Certificate and registration expiry dates watched automatically, not remembered
- A shift offered to everyone qualified at once, rather than one person at a time
- The ranked pool held by the organisation instead of by one manager
- Invoices and payroll built from the same approved timesheet
If none of the five signs above sound like your organisation, you probably do not need this yet, and we would rather say so. If three or four of them landed, the spreadsheet is not the problem — it is just being asked to do a job it was never going to hold.
Want a number rather than an argument? The ROI calculator estimates the admin hours behind these five signs, using deliberately conservative assumptions that are all stated on the page.
