Real rosters change: someone cancels, someone wants to swap, a gap appears. BondiByte turns each change into a proper workflow: staff interest collected before assignment, open shifts claimed from the phone, cover offers when someone cancels, swaps that keep the roster true, and escalation that makes sure a gap is never discovered the morning of the shift.
Any published shift still short of its required staff is offered to eligible workers instead of sitting empty on a board.
Staff raise changes from their own portal, the rules are checked, and the roster stays true to reality.
Unfilled shifts are emailed to the site manager ahead of time and escalate to admins as the shift gets close.
Cancellations and swaps build per-staff reliability signals that quietly inform the roster, at a weight you control.
Interest, claims, swaps and cancellations all start from the staff member's own device.
Each site can start the day with a summary of tomorrow's shifts.
An uncovered shift usually becomes a ring-around. Someone works down a list, the same reliable few get asked first, swaps get arranged over text until the roster no longer matches reality, and a late-night cancellation starts a scramble nobody can reconstruct afterwards. Coverage should be a workflow, not a phone marathon: the eligible people see the gap, the ones who want it put their hand up, the decision is made once, and everything is on the record.
Open a roster period for interest and staff mark the shifts they want from their own portal, with an optional preference order. Unsuitable responses are filtered out at the door, and interest feeds the roster suggestions as a weighted signal.
Once a roster is published, any shift still under its required staff count is claimable by the site's eligible teams. Staff claim from their phone, and each site decides whether the first eligible claim takes it or an approver does. Approving one claim declines the rest, with everyone told where they stand.
A staff member cancels from their portal with a reason, inside the notice window you set. Where you require it, the request waits for approval; either way the manager knows immediately, and with cover automation on, the freed shift is offered to suitable staff in ranked order.
Staff request a swap from the eligible options BondiByte presents, the other person accepts or declines, and where approval is required a manager has the final say before the roster changes.
Coverage is checked across the week ahead. The site manager is emailed about each upcoming gap with the reason it is unfilled, reminders follow your cadence, and a shift within 24 hours of starting escalates to your admins, once, without duplicate noise.
Ask the whole team who wants the shifts in one step, and roster from real availability instead of guesswork. Staff can rank preferences and withdraw while the window is open.
A published shift still needing staff is automatically claimable. No parallel list to maintain, and staff only ever see shifts they are eligible to work.
Turn the approver requirement off and the first eligible claim takes the shift. Leave it on and a manager decides. A stable house and a complex one can run differently.
Every cancellation request carries a written reason, and portal cancellation closes inside the cutoff you set. Requests and cover offers carry clear statuses from offered through to completed, rejected or expired.
Switch cover offers on and suitable staff are offered the freed shift in ranked order, cutting the ring-around out of most cancellations. The first suitable acceptance fills it.
Staff choose from workable swap options only, the other person always gets the choice, and swaps respect the same suitability and safety rules as any assignment.
The site manager is emailed about gaps in the next seven days, with the exact reason a shift could not be filled, down to which staff are already rostered where. Daily next-day summaries keep the rhythm.
Completed cancellations and swaps are recorded per staff member, measured over the last 28 days, and inform smart recommendations at the weight you choose. New staff start neutral, and staff can see their own record where you enable it.
Swaps, staff cancellations and automated cover offers all ship switched off. An owner or admin enables each one deliberately, per organisation and per site, and can switch it back off.
Which teams see a site's open shifts, whether claims need an approver, how many swaps a person can request, and the cancellation notice window are all per-site settings.
Expressing interest or claiming a shift never bypasses the rules. Suitability checks still run, and manager review still decides where you require it.
Coverage reminders respect a cooldown, escalations are sent once per shift, and every email links straight to the relevant site and period on the roster.
No. Interest is one weighted signal among many, and claims are checked against the same suitability and safety rules as any assignment. Where a site requires an approver, a manager still decides.
Only within the rules you set. Once your notice window has closed, or the shift has started, the portal will not accept the cancellation and staff are told to contact their manager.
With cover automation on, BondiByte offers the shift to suitable staff in ranked order and the first acceptance fills it. Offers are chosen on merit, not mateship, and you can always assign someone manually instead.
No. Staff choose from the eligible options BondiByte presents, the other person must accept, and where approval is required a manager confirms before the roster changes.
The gap stays visible with its reason, the site manager is reminded on your cadence, and a shift within 24 hours of starting escalates to your organisation admins so a single busy inbox is never the last line of defence.
No. It is one weighted signal you control, based on recorded workflow events over the last 28 days rather than opinion, and it mostly works by recognising dependable staff. Genuine attendance no-shows are not tracked.
The full rostering cycle in one supervised workflow: patterns and periods, shift creation, suitability and hard-block checks, weighted recommendations, sleepovers, and scheduled automation.
Smart RosteringSet up your roster calendar once, capture how each site really runs, and let every future period start from that shape.
Smart RosteringCreate a whole period of shifts from your configured patterns and site or period settings, including recurring shifts.
Smart RosteringAsk the whole team who wants the shifts, in one step, and get answers you can actually roster from. Staff respond from their own portal, unsuitable responses are filtered out automatically, and interest flows straight into the roster suggestions.
Smart RosteringCritical conflicts are blocked before staff are even considered, then suitability signals rank who fits best.
Smart RosteringOnce blockers clear, BondiByte ranks and prepares assignment options using the signals that matter to your operation.
Start your free trial, or book a demo to see it with your own operation in mind.
Hi, I can help with BondiByte features, pricing, setup and more.
Please don’t include sensitive participant or personal information.
