Staff raise requests where they already work
From the staff portal and mobile app, staff request shift swaps and cancellations, claim open shifts, submit unavailability and leave, and upload documents. No texts, no lost emails.
Staff & Workforce
Requests routed to the right approver.
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.
What you get with Staff requests & approvals.
- Staff request workflow
Staff raise requests in one place instead of scattered emails and texts.
- Manager approvals
Requests route to the right approver with a clear yes or no.
- Audit trail
Every request and decision is recorded, so there's always a clear paper trail.
Why it exists
The problem it solves.
Requests arrive as texts, calls and hallway conversations. Decisions go unrecorded, nobody is sure what is still waiting on whom, and a forgotten leave request turns into an unfilled shift. BondiByte gives staff one place to ask and managers one queue to answer, with every decision kept on the record.
How it works
Everything lands in one queue
The Approvals area shows six clear tabs: swap requests, shift cancellations, open shift requests, leave and unavailability, document requests, and AI Review, each with a live count of what is pending.
Review with full context
Each request shows who is asking, the dates and times involved and their reason, with a detail view when you want to dig deeper before deciding.
Approve or reject in one action
Decisions apply immediately. A staff-submitted absence, for example, only starts blocking the roster once you approve it.
Notifications take you straight there
Links in notification and email alerts open the right tab with the specific request expanded, so acting on a request takes seconds.
What you can do.
Shift swap approvals
Swaps that need a manager's review wait in the queue. Where your rules let staff complete swaps directly, those show as history rather than tasks.
Cancellation requests
Staff cancellation requests come to you for a decision instead of shifts quietly going uncovered.
Open shift claims
When staff put their hand up for an open shift, the claim waits for an approver before the shift is theirs.
Leave and unavailability
Longer staff-submitted absences queue for approval and only affect rostering once you say yes.
Document approvals
Staff-uploaded documents become trusted profile evidence only after a manager approves them.
AI Review
Where your organisation uses AI-assisted features, anything needing a person's decision waits in its own tab: reports flagged as a possible incident, and summaries awaiting sign-off. You can filter to either kind.
Live pending counts
Each tab shows how many requests are waiting, so nothing sits forgotten.
How it connects.
You stay in control.
Leave requests, cancellations, claims and documents take effect when a manager approves them, not when they are submitted.
Settings like the leave approval threshold decide which requests come to you and which apply automatically.
Rejecting a request asks you to confirm, so a busy day never produces an accidental no.
Learn how to use this feature.
Frequently asked questions.
What kinds of requests come through Approvals?
Shift swaps, shift cancellations, open shift claims, leave and unavailability, staff document uploads, and AI Review items where your organisation uses AI-assisted features. Each has its own tab with a pending count.
Do staff document uploads go live straight away?
No. They wait in the document requests tab and only become trusted evidence on the staff profile once a manager approves them.
How do we know something is waiting?
Notifications and emails link straight to the specific request, and the Approvals tabs show live counts of anything pending.
Can some swaps happen without a manager?
That is up to your settings. Swaps that complete under your rules appear as history for visibility, while anything needing review stays in the queue as a task.
When does an approved leave request hit the roster?
Immediately on approval. Until then, the pending request does not block rostering, so a speculative request never quietly holds up your roster.
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 & 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 & 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 & WorkforcePay levels
Configure pay levels and assign them so timesheet lines carry the right rate.
See Staff requests & approvals in BondiByte
Start your free trial, or book a demo to see it with your own operation in mind.