Rostering
Most rostering tools tell you about an award problem when payroll runs, which is about three weeks after you could have done something about it. This one tells you while you are still dragging the shift around, and tells you what it will cost.
Workers down the side, days across the top, shifts where the two meet. Set a pattern once and it generates forward. Shift types bring their own defaults with them. And when the support changes halfway through a shift, you split it into sections rather than inventing two shifts that pretend to be one.
Double-bookings, unavailability and worker pairings that should not happen show up while you are still moving things around. Whether someone is free is answered once, from all three places that can say no — the preference they set, the leave they booked, and the shift they are already on. Three sources, one answer.
Publish a gap and let the workers qualified for it take it from their phone. The claim is conflict-checked on the way in, so a shift somebody picked up at 9pm is exactly as safe as one you assigned yourself.
Minimum engagement, the daily ordinary-hours cap, the ten-hour rest break, the weekly cap and the broken-shift allowance are all evaluated as the week takes shape. Each warning tells you what it will cost the organisation — the hours at the right penalty, plus casual loading, grossed up by on-costs. That makes it a decision you are making, rather than a red badge you are dismissing.
The part that is hard to copy
Casual loading and the on-cost gross-up are per-organisation, effective-dated data rather than numbers baked into the product — so if you are on an EBA that pays differently, the alerts, the pay run and the margin all cost your shifts at your rates instead of at the SCHADS defaults. Two honest limits: the overtime multipliers stay fixed at the award's 1.5× and 2×, because those are not ours to vary, and an agreement that changes them is not expressible today. Competitors we have looked at hand-type a flat rate table and treat a timesheet as scheduled-minus-break, which cannot describe a broken shift at all, let alone price one.
Not modules you buy separately. They read the same records, which is why nothing between them ever needs reconciling.
What the breach costs, before you publish
Read about it →From clock-in to payslip without retyping
Read about it →Bulk claims that match their own remittance
Read about it →Notes tied to the goal they were for
Read about it →Clocks that run whether or not anyone remembers
Read about it →Authorisation that expires on its own
Read about it →Evidence that accumulates instead of being assembled
Read about it →