Every crew business starts the same way: a spreadsheet for the roster, a group chat for the offers, a whiteboard on the office wall and a shoebox — sometimes literally — of photocopied tickets. It works, for a while, because the founder holds the whole operation in their head. The honest question isn’t whether that setup is wrong; it’s when it stops being enough. This is a straight look at spreadsheet rostering vs workforce management software: where each manual method breaks, what replaces it inside OnCrew, and what moving across actually involves.
If you’re reading this at 9pm after another evening of filling tomorrow’s shifts by text, you already suspect the answer. One note on framing: this isn’t a moral argument — manual methods are the right tool at the size they suit. The comparison below is about what happens past that size, and what each tool’s replacement inside OnCrew does differently.
The setup almost every crew business starts with
The classic stack has four parts. The spreadsheet holds the roster — names, sites, times, maybe a colour code for confirmed. The group chat is the dispatch channel: “Who can do Botany tomorrow, 6:30 start?” The whiteboard is the office’s shared picture of the week. And worker credentials live in a folder, a drawer or a camera roll.
None of this is stupid. It’s free, everyone understands it, and up to a certain crew size it genuinely works. The manual rostering problems Australia-wide operators describe don’t come from the tools being bad — they come from the tools having no memory, no rules and no connection to each other. Each one fails in its own particular way, and they tend to fail together, on your busiest morning.
Where each method breaks
Spreadsheets — no live truth, no audit trail
The spreadsheet’s fatal flaw is versions. Someone edits the shared file, someone else works from yesterday’s copy, and now there are two rosters — the moment operators most often decide to stop rostering in spreadsheets is the morning two workers show up for one shift, or none for two. There’s also no audit trail: when a shift changed hands three times last Tuesday, the spreadsheet shows only the final name, not who agreed to what and when. Hours get disputed later precisely because nothing recorded the middle. And a spreadsheet doesn’t know your workers — it can’t tell you the name in cell C14 has a White Card issue. The deeper reason why spreadsheets fail for labour hire is structural: a grid stores values, but a roster is made of rules — who may work where, holding what, until when — and a grid has nowhere to put a rule.
Group chats — decisions lost in a scroll
The group text feels fast, and it is — at broadcasting. It’s terrible at everything after the broadcast. Offers go to everyone including the unqualified and the unavailable; replies land out of order; “I’ll take it” from two people creates a double-booking; and the actual allocation decision lives somewhere in a scroll of 60 messages. Anyone trying to move off group chat rostering usually cites the same breaking point: a shift everyone thought someone else had confirmed. The chat has no state — it doesn’t know what’s filled, what’s pending and what’s still open, so a human has to hold that state in their head, at 5am, every day. The fix isn’t a better chat app; it’s giving the offer, the acceptance and the roster the same home.
Whiteboards — invisible the moment you leave the office
The whiteboard is a good shared display with a fatal constraint: it’s bolted to a wall. The supervisor on site can’t see it, the allocator working from home can’t update it, and by Wednesday it’s a palimpsest of smudges that may or may not reflect reality. A roster whiteboard replacement has to do what the board did — the whole week visible at a glance — without the wall. That’s a live screen, not a better marker, which is why OnCrew’s dispatch map opens straight to the whole operation.
Shoeboxes of tickets — expiries nobody is watching
The quietest failure is the credential folder. Photocopied White Cards, first aid certificates and licences go in; nothing ever comes out to warn you. Expiry dates sit unread until a worker is turned away at a gate — a lost shift, an embarrassed client, and the sudden discovery that more tickets lapsed the same month. Of all the reasons why spreadsheets fail for labour hire, this is the one with real compliance consequences: the manual stack doesn’t just make you slow, it makes you blind to the one thing your clients assume you’re watching.
What replaces each one
The point of software isn’t to digitise the spreadsheet — it’s to give each manual tool’s job to something with memory, rules and connections. Inside OnCrew, the mapping is one-for-one.
Live dispatch map instead of the whiteboard
OnCrew’s live dispatch map puts every site, every crew and every open gap on one screen — in the office, at home or on a phone at the site. Who’s clocked in, who’s late, what still needs filling: the whiteboard’s job, minus the wall, and always current because it’s fed by the same system that fills the shifts and records the clock-ins.
Smart Fill instead of the group text
Smart Fill replaces the broadcast with a ranked shortlist. It reads each shift’s requirements, searches your whole pool, and surfaces only qualified, available, compliant workers — ranked by role fit, site and client history, and distance — then lets you send one-tap offers to their phones. Acceptances update the roster in real time, so the state the group chat forced you to hold in your head is held by the system instead. The spreadsheet’s grid becomes a live roster, the text blast becomes targeted offers, and nothing depends on your memory.
Compliance register instead of the shoebox
Every worker’s tickets and licences enter OnCrew photographed from their own phone during onboarding, each catalogued with an expiry date. Expiries trigger reminders — and, more importantly, the hard compliance gate: a worker missing a required, in-date credential can’t be assigned to a shift that needs it. The shoebox becomes a register that acts, not a drawer that waits.
Geofenced clock-ins instead of paper timesheets
Paper timesheets carry two problems: they’re filled in from memory and they’re re-typed into payroll. OnCrew’s clock-ins are GPS-stamped and geofenced — attendance is recorded in the site’s local time as it happens, and a clock-in taken away from the site is flagged for the supervisor. Supervisors approve hours from their phones, and approved timesheets become a payroll-ready export file for Xero or Employment Hero. The hours that get paid are the hours the supervisor approved — GPS-stamped at the gate, with no re-keying in between. OnCrew also flags a missed clock-in the moment it happens, so a no-show becomes a refill, not a discovery.
Comparison table — manual vs OnCrew
| The job | Manual method | Where it breaks | In OnCrew |
|---|---|---|---|
| The week at a glance | Whiteboard | Invisible off-site, instantly stale | Live dispatch map on any screen |
| Holding the roster | Spreadsheet | Version conflicts, no audit trail | Live roster with full change history |
| Filling shifts | Group chat blast | Wrong people offered, decisions lost in scroll | Smart Fill’s ranked one-tap offers |
| Credentials | Folder / shoebox | Unwatched expiries, gate turn-aways | Compliance register + hard gate |
| Proving attendance | Paper timesheets | Memory-based, disputed later | Geofenced, GPS-stamped clock-ins |
| Getting hours paid | Re-keying into payroll | Errors and hours of admin | Payroll-ready export for Xero / Employment Hero |
What migration actually involves
The move is smaller than the years of habit suggest. The teams that stop rostering in spreadsheets most smoothly do it in this order:
- Workers first. Send your pool an onboarding link; each worker completes their profile from their phone — details, photographed tickets, your induction, tax, super and bank. Your compliance register builds itself as they finish.
- Clients and sites next. Set up each client, their sites, their supervisors and each site’s requirements. This is where the old whiteboard columns and spreadsheet tabs become structure.
- Run one roster in parallel. Keep the spreadsheet open for a week or two while your first shifts flow through Smart Fill, clock-ins and approvals. Most teams find the parallel week is what converts the sceptics — the first 5am gap filled from a phone does the arguing.
- Retire the stack. Cut payroll over to the export file, wipe the whiteboard, archive the spreadsheet. Teams that replace excel rosters completely — payroll included — report the deepest gains; half-migrations keep the version problem alive. Keep the shoebox as a souvenir.
