Rostering
Every site, one screen.
A horizontal timeline with a lane for each client site. Day and night shifts in their own sub-lanes, bars colour-coded by client, weekends shaded, and unfilled shifts visibly open until someone takes them.
What the roster handles
Built for swings
Day and night shifts, 2/1s, 8/6s, whatever pattern the site runs. Drag on the timeline to create a shift, click to edit, and the labels are yours to define.
Logistics on the shift
Flights and accommodation live on the shift itself, where the office and the client can both see and tick them off. No side spreadsheet for travel.
Open shifts fill themselves
Publish an open shift and your crew put their hands up from their phones. You confirm the allocation, and the compliance check runs before it lands.
The shift editor
Everything you need to fill a shift, on one screen.
Open a shift and the right-hand panel is the crew: avatar, role, verified competencies, and the exact dates each person is free, including partial fits. Tap a card to assign.
The people who want it, on the shift
Anyone who put their hand up for an open shift is listed on the shift itself, one tap to assign. No switching to the requests tab and back to work out who's interested.
Draft, open, assigned
A shift is a draft until you're ready, open to the team when you want hands up, or assigned to a person. Picking someone selects assigned for you, and drafts notify nobody on either side until they're released.
Repeat weekly for swings
Set a shift to repeat weekly and the pattern builds itself. Roster tiles are clickable too: compliance flags, open slots, weekend shifts and worker counts each open the list behind the number.
Nobody finds out by accident.
When a shift changes, the people it changes for are told. Dates, day or night, site or the allocated worker moving all send an email and a push notice to the crew member affected, and cancelling a shift tells them too, which it never used to. Clients hear when their request has been accepted and who is coming, when a shift changes (with the previous details shown), and when one is cancelled.
There's a "let the people affected know" tick on the shift form, on by default. Untick it to fix a typo or an office-only detail without mailing the client and the crew about nothing.
A queue that shows its work.
Crewing a shift used to make it vanish out of the requests list with no confirmation it had worked. The queue now has needs-action at the top and accepted-this-week underneath, showing what you've crewed in the last seven days, who's on it and how long ago.
Rostering and compliance are the same motion.
In most setups the roster lives in one place and the tickets live in another, and someone has to remember to cross-check them. In Mustr the check runs inside the booking. Assign a worker, and their competencies, induction, availability and existing shifts are all checked before the booking is made. The roster you're looking at is always a roster you can defend.
See the guide to building the roster for the full walkthrough, or how it works for the bigger picture.