Guides

What your clients see

Give a client site a login and the daily who's-coming-tomorrow phone call mostly disappears. Here's what's on their side of the fence.

Your site's rosterRaise a requestMedic · Day shiftCompliantOperator · Night shiftCompliantRigger · Day shiftInduction dueFlights booked ✓   Accommodation booked ✓123
The client's view: their own site's bookings with compliance status (1), a raise-a-request button (2) and logistics tick-offs (3).

Their roster, live

The client sees the people booked to their site: who, what role, which shift, and whether they're compliant for the work. Flights and accommodation status shows against the shift where that's relevant. What they can't see matters just as much: other client sites, your wider workforce, your other business. The scoping is absolute, each client sees their world only.

Requests instead of phone calls

When they need someone, they raise a request straight on their roster: the day, the role, any specific competencies, and a note if they have a preference. It lands in your office queue. You allocate a worker to it, and the same compliance check that guards every other booking runs before the allocation lands. A request is a preference, not a booking, and your office always confirms who attends.

Logistics they keep current

For upcoming shifts the client can tick off the practical detail: flights booked, accommodation sorted, access notes for handover. It's the sort of information that otherwise lives in three email threads, and here it lives on the shift where both sides can see it.

They manage their own people

The client invites their own site users: a supervisor, a head-office admin, whoever needs eyes on the roster. Everyone they invite is scoped to their site, sets their own password, and signs in with two-factor authentication like every other Mustr login. You don't administer their staff list, and you don't get the password-reset phone calls either.

Shift requestsNorth Site · DayMon 14 to Fri 18 · Role: Medic · 4WD requiredAssignA request lands in the office queue. Assigning a workerruns the compliance check before the booking is made.Blocked: worker is missing 4WD (required for this site).12
Client requests are allocated by your office, and the compliance check runs before anything is booked.

The client portal page has the short version. Better, book a demo and look at the client view through your own client's eyes.

Bring one roster to the demo. We'll show you Mustr running it.

Book a 20-minute demo