Field notes › Choosing software
Why an audit trail saves arguments
Ask anyone who has run a labour hire roster for a few years what causes the worst weeks, and it is rarely the software or the spreadsheet. It is the arguments. Who changed the shift. Who was told about it. Whether the certificate was uploaded before or after the swing started. An audit trail does not stop those questions being asked. It stops them being arguments.
A roster is a machine for generating disputes
Every roster sits between at least three parties with different memories. The worker is certain nobody told them about the changed start time. Meanwhile the client remembers requesting two extra crew, not one, and the coordinator swears the booking was updated before they went home on Thursday. Everyone is being honest, and somebody is wrong, and without a record the loudest or most senior version usually wins. That is corrosive in both directions, with clients and with your own crew, because the people who lose those arguments unfairly remember it for a long time.
Memory is not a record
Human memory is reasonable at what happened and terrible at when, and in what order. Whether the shift was changed before or after the worker last checked the roster is exactly the kind of detail memory invents with total confidence. A timestamped record has no confidence and no stake in the outcome. It just says what happened, which is why both sides of a dispute will accept it in a way neither will ever accept the other's recollection. The record does not need to be dramatic to be decisive. Most disputes collapse the moment someone reads out two timestamps.
What a useful audit trail covers
An audit trail is only as good as what it captures. The events that end arguments in labour hire are specific ones:
- Bookings created, changed and removed, with who did it and when.
- Certificate uploads and updates, so you can show what was on file at the moment a booking was made.
- Availability changes, for the difference between a shift that was declined and one that was never offered.
- Client requests, so a raised shift request is a record rather than somebody's recollection of a phone call.
Mustr keeps an audit trail alongside its compliance records, and pairs it with fit-for-work declarations and notices, so the paper trail is one trail rather than three systems and an inbox.
Shared logins quietly destroy the whole thing
An audit trail records which account did something, not which human. If three coordinators share one login, every entry carries the same name and proves nothing about anybody. This is one of the hidden costs of per-seat pricing: when logins cost money, people share them, and the audit trail dies without anyone ever deciding to kill it. On flat per-organisation pricing there is no reason for anyone to share an account, which turns out to be a security point and an evidence point at the same time.
It protects people, not just the business
It is easy to frame audit trails as management surveillance, and badly run ones can feel like it. In practice the record clears people at least as often as it catches them. The coordinator accused of forgetting a change can show the change, timestamped, made before close of business. The worker adamant they uploaded their certificate on time can be shown to be right, and owed an apology. Fair outcomes need a shared set of facts, and a good audit trail is the cheapest source of shared facts a workforce business can own.
If you would rather settle roster questions with a record than a memory, book a demo.