Field notes › Choosing software
What software implementation should actually involve
Software demos are about the product. Implementations are about your data and your busiest fortnight. Plenty of rostering projects die between the two, not because the software was wrong but because nobody planned the landing. Here is what the landing should involve, and what to ask any vendor before you sign anything.
The spreadsheet does not die on its own
The most common failure mode is not a crash. It is a quiet parallel life, where the new system holds half the workers and the old spreadsheet keeps holding the truth. Whichever tool is more complete wins the daily habit, and a half-migrated system is never the more complete one. So the first goal of any implementation is blunt: get everything in, fast enough that the spreadsheet can actually be retired rather than kept around "just in case". A spreadsheet kept just in case is a spreadsheet still in charge.
Data comes first, and it is dirtier than you think
Workers, certificates, clients and sites need to come across before anyone can roster anything. Ask how that happens. Bulk import from CSV should be table stakes, and Mustr ships with CSV bulk import for workers and clients, because typing three hundred workers in by hand is how projects stall in week one.
Expect the export from your old world to be messy. Certificates recorded in a notes column, expiry dates missing, three spellings of the same client. Treat the cleanup as part of the project rather than an annoyance, and budget real hours for it. Migration is the best certificate audit you will ever do, because every record gets looked at by a human exactly once, and the expired tickets you find during it are ones the old system was silently letting through.
Pilot on one slice, not the whole book
Do not cut the whole operation over on a Monday. Pick one client site or one crew, run it in the new system for a full cycle, a swing or two if you roster remote work, and keep the rest where it is. A pilot surfaces the awkward details while they are still cheap to fix: the odd shift pattern, the worker with no email address, the client contact who needs their own login. It also gives your coordinators time to trust the new tool before their whole week depends on it. This is why Mustr's smallest plan is $660 a month, month to month, rather than asking you to commit the whole roster on day one.
Ask who actually does the work
Somebody has to import the data, set up the sites and shift patterns, create the client logins and get the first roster built. Find out who. "Free onboarding" often means a help centre and a welcome email, which really means you are doing it yourself between everything else. A vendor that charges a setup fee should be able to tell you exactly what the fee buys and who does what, week by week. Either answer can be fine. Not knowing the answer is not fine, because the gap between "we help you get set up" and what actually happens is where implementations quietly fail.
How you will know it worked
A few unglamorous signals tell you the system has landed. Workers are setting their own availability and uploading certificates instead of texting photos to the office. Clients are logging in to check the roster instead of ringing about it. The old spreadsheet has not been opened in a month. And the compliance conversation has changed shape, from digging out records after the fact to fixing expiries the system surfaced weeks ahead. If those things are true after a couple of months, the implementation worked. If they are not, the new software has become the parallel system, and it is worth asking why before the subscription quietly renews.
If you want to talk through what a pilot would look like on your crew, book a demo.