Set the site baseline
Each site carries a default staff capacity in hours per fortnight. It applies to everyone rostered there unless a person has their own limit.
Staff & Workforce
Cap hours and protect your team.
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.
What you get with Max-hours & capacity controls.
- Staff hour caps
Set safe limits on hours so the roster protects your team from overwork.
- Site capacity controls
Give each site a default hours cap that covers everyone rostered there, so coverage stays realistic.
- Enforced during assignment
Limits are applied as you roster, not discovered after the fact.
Why it exists
The problem it solves.
Overworked staff, surprise overtime and quietly breached agreements all start the same way: nobody was counting hours while the roster was being built. On a spreadsheet you find out after the fortnight is over. BondiByte counts as you go, and stops an assignment before it pushes anyone past the limit you set.
How it works
Override per person where needed
Give any staff member their own maximum rostered hours per fortnight on their profile, down to quarter-hour precision. The personal limit always wins over the site default.
Every assignment is checked
Before suggesting anyone, BondiByte projects their hours for the roster period including the new shift. Over the cap means they are not offered the shift, and the reason shows the exact numbers.
Warnings before the wall
From ninety percent of capacity, assignments carry a near-limit warning, so you see who is filling up before anyone actually hits their cap.
Fallback staff wait their turn
While primary team members at a site still have capacity, automation does not reach for secondary or relief staff. Fallback workers are only considered once the core team is genuinely full.
What you can do.
Site default capacity
One hours-per-fortnight setting per site covers everyone who does not need an individual arrangement.
Per-staff caps
Individual maximum rostered hours per fortnight, entered in quarter-hour steps, that override the site default.
Hard stop at the limit
An assignment that would exceed someone's capacity is blocked, with the projected hours and the cap spelled out.
Near-limit warnings
From ninety percent of capacity, you are warned before you commit the shift, not after.
Any roster length
Caps are set per fortnight and scaled automatically to the actual roster period, so weekly and fortnightly rosters both behave correctly.
Demand vs capacity check
BondiByte compares the hours a roster needs against your team's combined capacity, so you can see a coverage shortfall before automation runs.
How it connects.
- Staff profile caps
- Site capacity settings
- Suitability checks
- Smart recommendations
- Published roster
- Timesheets
You stay in control.
Site defaults and individual caps are yours to configure and change at any time.
When someone is not offered a shift for capacity reasons, the reason states their projected hours against their cap, so there is never a mystery.
Where cost weighting is used, assignments projected past capacity are treated as more expensive, steering automation away from likely overtime.
Learn how to use this feature.
Frequently asked questions.
What happens if a shift would push someone over their limit?
Smart Rostering does not offer them the shift. The suitability result shows the projected hours against their capacity so you can see exactly why.
Do we set limits per person or per site?
Both. The site holds a default hours-per-fortnight capacity, and any staff member can carry their own cap that overrides it. Leave the personal field blank to use the site default.
What if our roster is not exactly a fortnight?
Caps are expressed per fortnight and scaled to the real roster period automatically, so a one-week or ten-day roster is measured fairly.
Do we get any warning before someone maxes out?
Yes. From ninety percent of their capacity, assignments carry a near-limit warning, and the remaining headroom is visible on suitability results.
Does this stop us leaning on relief staff too early?
Yes. While primary team members at a site still have capacity, automation will not assign secondary or relief staff. Fallback workers come into play only once the core team is full.
More in Staff & Workforce.
Staff & Workforce
Staff management overview
Profiles, capabilities, pay, and contracts 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 & WorkforceAvailability & leave
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.
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 Max-hours & capacity controls in BondiByte
Start your free trial, or book a demo to see it with your own operation in mind.