Core Setup
Prepare staff records for rostering and portal workflows.
Staff setup tells BondiByte who the person is, how they are employed, where and when they can work, what work they are qualified for, how much they should be rostered, their team relationships, and their account access. Smart Rostering draws on all of it.
Watch the walkthrough
Prefer to see it done? The short video below walks through the same steps in the live product.
Before you begin
Before creating staff records, make sure you have:
- Configured your organisation sites (if staff will be assigned to locations).
- Staff contact, emergency contact, employment, and right-to-work details.
- Pay level information, where pay levels are used.
- Qualification, clearance, and compliance documents ready to upload.
- A decision on whether the person needs staff portal or mobile app access.
- The three questions rostering asks about every worker: eligibility (can they work this shift), availability (when can they work), and priority (who should be preferred among eligible staff).
Recommended setup order
The steps below follow the complete lifecycle: create the record, configure employment and rostering settings, establish capabilities, and manage the profile day to day.
1 Open Staff and choose a creation method
Open Staff from the left navigation. Use Import for bulk onboarding, or Add staff to create one record at a time.
2 Import multiple staff using CSV
Open Import and download the current staff CSV template. Enter staff information without changing the column structure, save the file, then upload it back into BondiByte.
Run the import and review any validation feedback before continuing.
3 Create an individual staff record
Select Add staff and complete the staff member's profile, contact, and emergency contact information.
4 Set the operational status
Use Active for current workers. Inactive and Terminated staff are excluded from normal rostering consideration and are not counted as active staff for allowances or calculations that rely on the active staff count.
Keep the status aligned with the person's real employment state. Statuses drive operational eligibility, so they are not just labels.
5 Complete employment, right-to-work, pay and the initial site
Complete employment type, manager or supervisor, login UPN where used, start date, and right-to-work or residency information. Record these values accurately so compliance and document workflows track the right evidence.
If pay levels are used, select the appropriate pay level. Select an initial primary site where appropriate; additional site relationships can be added after creation.
6 Set ordinary hours, preferences and roster capacity
Set ordinary hours, rostering preferences and, where needed, a maximum rostered-hours-per-fortnight limit.
Preferences influence ranking. They never bypass hard suitability checks.
7 Create the record and explore the staff profile
Select Create staff. The staff profile becomes the central workspace for ongoing workforce management.
The profile tabs cover Overview, Login access, Documentation, Reports, Contracts & Pay, Availability, Capabilities, Sites, and Shifts.
8 Establish capabilities through documents
Capabilities represent qualifications, clearances, and evidenced skills used by rostering suitability, such as First Aid, CPR, NDIS Worker Screening, or a driver licence.
Upload staff documents using the correct document type. Where a document type maps to a capability, approved evidence can derive or update the capability and its expiry state.
Missing a mandatory capability is a hard suitability block. Missing an optional capability can be surfaced as a warning.
9 Approve documents staff upload themselves
Staff can upload documents through the staff portal and mobile app. Staff-submitted documents must pass the approval workflow before becoming trusted profile evidence.
Review pending submissions from Approvals, under Document requests.
10 Configure login access
Use the Login access tab when the worker needs staff portal or mobile access. Authorised administrators can send setup and login details, link an existing account, set a password, revoke sessions, and manage approved SSO exceptions, depending on the account state and identity configuration.
11 Manage availability, leave and blocked windows
Availability controls when a staff member can work. Blocked and unavailable windows are respected by suitability checks and Smart Rostering.
Each availability record is a dated window with a type: Available, Preferred, Unavailable, Blocked, or On Leave. On Leave needs a start and an end date, and it also sets the person's status to On Leave so they are not auto-rostered until it finishes.
Staff can add their own availability from the Staff Portal and the BondiByte Staff app. Time off longer than your organisation's leave approval threshold waits for a manager, and those requests appear in Approvals under Leave and unavailability.
If availability changes after future shifts are already assigned, review those assignments rather than assuming they are removed automatically.
12 Add site relationships and rostering priority
Assign the worker to additional sites where required. Primary, Secondary, and Relief team relationships help Smart Rostering rank eligible staff for each site, and assignment dates affect when a worker is considered part of that site.
Team relationship is a ranking signal. Being Secondary or Relief never makes someone invalid; mandatory capabilities, availability, and other hard rules stay authoritative.
13 Review contracts, reports and pay information
Use the staff profile to review reports and employment-related information. Where Staff Contracts are used, Contracts & Pay shows relevant contract and pay information, subject to permission.
14 Review the staff member's shifts
Open Shifts to see future and historical rostered work, then open a shift when more detail or further action is required.
Understanding staff setup concepts
Eligibility
Whether a person can work a shift at all. Active status, mandatory capabilities, overlapping shifts, and blocked or unavailable windows all feed suitability.
Availability
When a person can work. Availability records, leave, and blocked windows determine whether a shift time is workable. Availability never implies qualification.
Availability type
The type on each dated availability window: Available, Preferred, Unavailable, Blocked, or On Leave. On Leave requires start and end dates and sets the person's status for that period.
Leave approval threshold
An organisation setting. Staff time off longer than this many days needs manager approval before it takes effect, and the request waits under Leave and unavailability in Approvals.
Priority and ranking
Which eligible person Smart Rostering prefers. Team relationship, continuity, fairness, fatigue, staff interest, weekday and weekend balance, cancellation reliability, and cost where configured influence ranking. A preference never overrides a hard suitability block.
Capability
A qualification, clearance, or evidenced skill used in suitability decisions. Approved documents of a mapped type can derive or update capabilities, including expiry.
Mandatory capability
A capability a shift or site requires. Missing it is a hard block; missing an optional capability is surfaced as a warning.
Team relationship
Primary, Secondary, or Relief membership of a site team. Influences ranking and continuity preferences without making anyone invalid.
Maximum rostered hours
A per-fortnight capacity limit used when assessing how much the person should be rostered.
UPN (User Principal Name)
The login identity used for Microsoft Entra sign-in when enabled. Separate from the contact email address.
Staff status
The operational state of the record. Inactive and Terminated staff are excluded from normal rostering and from the active staff count.
Best practice
- Complete profile, contact, and emergency contact details, and confirm the operational status matches reality.
- Record right-to-work and residency information accurately so compliance workflows track the right evidence.
- Assign the pay level where used, and configure the primary site plus any additional site relationships.
- Review ordinary hours, rostering preferences, and maximum roster hours against the real employment arrangement.
- Upload and approve required documents so evidence-backed capabilities stay current.
- Configure login access where required, and keep availability, leave, and blocked windows up to date.
Common mistakes to avoid
- Treating an available staff member as qualified. Availability says when they can work; capabilities say what work they are qualified for.
- Assuming an unavailable period automatically removes a worker from already assigned shifts. Review affected assignments when availability changes.
- Changing the CSV template's column structure before importing.
- Relying on staff-submitted documents before they have passed the approval workflow.
- Treating Secondary or Relief team membership as a disqualifier. It is a ranking signal, not a block.
- Creating a login account without linking it to an active staff profile.
Take this guide with you
Download the Staff Setup Guide (PDF) A printable version of this guide with the same steps and screenshots.What to do next
Related guides
Clients
Step-by-step guide to creating a client or participant in BondiByte: NDIS number, representative and emergency contacts, plan management and billing details, and choosing site-based or standalone/community rostering.
Core SetupCapabilities
Create document-backed staff capabilities, collect evidence through document uploads, require capabilities per site, and use them in Smart Rostering suitability.
Service Agreements and ContractsStaff Contracts
Build an employment contract template for staff with variables and pay-level line items, generate a PDF, and send it to the staff member to sign electronically.
Need help applying this setup path?
Book a BondiByte demo and we can walk through the right setup order for your provider.