Record availability on the profile
Add dated windows for when someone is available, preferred, unavailable or blocked. Each record carries a start, an end and notes, so context is never lost.
Staff & Workforce
Availability the roster respects.
Staff record when they can and cannot work, leave is entered with real dates, and the roster honours all of it automatically. Nobody gets rostered into a window they told you they could not work.
What you get with Availability & leave.
- Availability windows
Staff set when they can work, and the roster respects it automatically.
- On-leave status
Leave is honoured everywhere, so no one on leave gets rostered by mistake.
- Blocks unavailable staff
Unavailable staff are hard-blocked from assignment, keeping the roster honest.
Availability, leave and blocked windows on the staff profile.
Why it exists
The problem it solves.
Availability usually lives in text messages and a manager's memory. Someone gets rostered while they are on leave, the shift gets rebuilt at the last minute, and trust erodes on both sides. In BondiByte, availability and leave are recorded once and every rostering decision respects them automatically.
How it works
Enter leave with dates, not toggles
Leave is recorded as a dated window, and BondiByte manages the On Leave status from it. There is no manual switch to forget to flip back.
Staff keep it current themselves
Through the staff portal and mobile app, staff submit their own unavailability and leave, instead of texting a manager and hoping it lands on the roster.
Longer absences wait for your call
Staff-submitted unavailability longer than your threshold, three days unless you change it, goes to the Approvals queue and does not affect the roster until a manager approves it.
Rostering honours every window
Unavailable and blocked windows are hard blocks: those staff are not offered overlapping shifts. Matching availability lifts a person's ranking when shifts are being filled.
What you can do.
Dated availability windows
Available, preferred, unavailable and blocked windows with precise start and end times.
Leave that manages itself
Enter leave dates once and the On Leave status follows the window, rather than relying on someone remembering to change it.
Staff self-service
Staff submit availability changes and leave from the portal and mobile app, so the roster reflects reality without manager data entry.
Approval threshold for long absences
Short blocks apply straight away; anything longer than your configured threshold waits for a manager decision.
Hard blocks in rostering
Nobody unavailable, blocked or on leave is offered an overlapping shift, whether a manager or automation is filling it.
Preference-aware ranking
Preferred availability and shift-type preferences lift a person's ranking among eligible staff, without ever bypassing the hard checks.
You stay in control.
Decide how long a staff-submitted absence can be before it needs a manager's yes, in your workspace configuration.
Pending requests show the person, the dates and their reason, and nothing blocks the roster until you approve it.
When availability changes after future shifts are already assigned, those assignments stay visible for you to review and rearrange deliberately.
Learn how to use this feature.
Frequently asked questions.
Can staff set their own availability?
Yes, from the staff portal and mobile app. Short unavailability applies straight away; anything longer than your approval threshold waits in the Approvals queue for a manager.
What stops someone on leave being rostered?
Leave, unavailable and blocked windows are hard blocks in the suitability checks. Staff in those windows are simply not offered overlapping shifts.
Does preferred availability guarantee someone gets the shift?
No. It improves their ranking among eligible staff, but qualifications, availability and hour caps always come first.
What happens to shifts already assigned when availability changes?
They are not removed automatically. The assignments stay in place for a manager to review, so a roster never changes behind your back.
Who decides how much absence needs approval?
You do. The threshold is a workspace setting, three days by default, and anything longer submitted by staff needs a manager's approval before it affects rostering.
More in Staff & Workforce.
Staff & Workforce
Staff Management
Onboarding, capabilities and qualification expiry, availability and leave, hour caps, pay levels, contracts and approvals in one connected record.
Staff & WorkforceStaff profiles & onboarding
Add one support worker in minutes, or bring your whole team across in a single CSV import. Every staff record starts complete: contact and emergency details, employment and right to work, pay level, sites and rostering preferences, so rostering, timesheets and compliance work properly from day one.
Staff & WorkforceCapabilities & qualification expiry
Every qualification, clearance and check lives on the staff record, backed by the actual document. When evidence is due to expire, BondiByte chases the renewal, and staff without current mandatory evidence are simply not offered the shifts that require it.
Staff & WorkforceMax-hours & capacity controls
Set safe working limits once and every roster respects them. Site defaults set the baseline, per-person caps handle real employment arrangements, and Smart Rostering will not assign anyone past their limit.
Staff & WorkforceStaff requests & approvals
Swaps, cancellations, open-shift claims, leave, document uploads and AI review items all land in one Approvals queue. Each request arrives with the context to make the call, and every decision leaves a record.
Staff & WorkforcePay levels
Configure pay levels and assign them so timesheet lines carry the right rate.
See Availability & leave in BondiByte
Start your free trial, or book a demo to see it with your own operation in mind.