Field notes › Industries
The realities of remote workforce logistics
Rostering a workforce in a capital city is forgiving. If someone does not show, you can usually get a replacement across town by lunchtime. Rostering a workforce onto sites that are hours from anywhere is not forgiving at all. The distances change what a mistake costs, and that changes what your systems need to be good at.
Distance turns small errors into big ones
In town, a roster error costs an awkward phone call. Remote, the same error costs a seat on a flight that left without your worker, a room that sat empty, and a site that runs short for days because the next practical way in is the next swing. The error itself is identical. The geography multiplies it. That is why remote operators end up obsessive about their rosters, and why tools that tolerate small errors, like a spreadsheet that lets you book anyone anywhere, are a bad fit for this work.
The roster and the travel are one thing
For a remote workforce, a shift is not just a start time. It is a flight in, a bed, a stretch of days and nights, and a flight out. Most firms roster in one tool and track travel in another, usually an inbox, and the gap between the two is where people fall through. Mustr puts flights and accommodation on the shift itself, so the question is never whether the travel spreadsheet matches the roster. There is no travel spreadsheet. The roster timeline shows the whole picture, day and night shifts and swing patterns included, across every client site at once.
Workers need answers without ringing the office
When your workforce is scattered across sites and time zones, the office phone becomes the bottleneck. When am I flying. What is my next swing. Can I pick up extra work. Every one of those calls interrupts a coordinator who is trying to do actual rostering. The worker portal gives workers their own view: their shifts, their availability, open shifts they can register interest in, and a place to upload certificates. It works on any phone with no app to install, which matters when the phone in question is an old handset on patchy regional coverage. Workers stop calling because they stop needing to.
Clients want to see, not ask
Remote clients have the same problem in the other direction. They cannot walk over to your office, so they email and call, and the answers they get are only as fresh as the last time someone updated them. Giving each client site its own portal login flips that. They see their own roster and only theirs, raise shift requests directly, tick off flights and accommodation on their side, and invite their own site users. Fewer status calls, and a client who feels in control tends to stay a client.
Where your data lives matters out here too
Remote operations already accept enough operational risk without adding avoidable digital risk. Mustr is hosted in Australia with data onshore, every login uses 2FA, access is invite-only with no public signup, and backups are encrypted and taken offsite daily. None of that is glamorous. All of it is what you want to be true of the system holding your entire workforce's details and your clients' rosters.
The firms that do remote work well are not the ones with the biggest crews. They are the ones whose systems assume the distance instead of ignoring it, so the roster, the travel and the communication all hold together when the nearest fix is hundreds of kilometres away.
If your workforce is a long way from your office, see it on your own roster.