Core Setup
Prove who can do what, with evidence.
Capabilities are document-backed records of staff training, qualifications, and skills. Sites can require them, Smart Rostering respects them, and evidence flows in automatically through document uploads.
Overview
Capabilities describe what a staff member is trained, qualified, or skilled to do, backed by uploaded evidence documents.
They power site capability requirements and Smart Rostering suitability checks, and appear on each staff member's Capabilities tab.
Before you begin
- List the trainings, qualifications, and checks your sites genuinely require.
- Decide which capabilities expire and need renewal tracking.
Recommended setup order
- Open Configuration, select Rostering rules, and find Capability Requirements in the Smart Rostering workspace settings.
- Add a capability with a clear name, for example Diabetes Management Training.
- Choose the type: Training, Qualification, Skill, or Capability.
- Turn on Requires expiry date when the evidence must be renewed, such as checks, licences, and certificates.
- Upload the matching evidence document against each staff member: their capability record updates automatically.
- On each site, add the capability requirements that matter for that site's clients.
Key fields and settings
Capability
A named, document-backed record of something a staff member can do, such as a training, qualification, skill, or check.
Capability type
The category of the capability: Training, Qualification, Skill, or Capability.
Requires expiry date
Marks the evidence as renewable. Expired evidence shows up in document expiry tracking.
Evidence document
The staff document upload that proves the capability. Creating a capability creates the matching upload type automatically.
Site capability requirement
A capability a site requires. Smart Rostering treats missing required capabilities as a suitability signal when assigning staff.
Staff Capabilities tab
The read-only view of a staff member's capability records, including which are backed by documents.
Best practice
- Name capabilities the way auditors and coordinators talk about them.
- Use expiry dates for anything renewable so document expiry tracking chases renewals.
- Keep site requirements realistic: require what the site's clients actually need.
Common mistakes to avoid
- Creating capabilities but never uploading evidence: unproven capabilities cannot support suitability decisions.
- Skipping expiry dates on renewable checks, which hides lapsed evidence.
- Requiring so many capabilities per site that no staff member ever qualifies.
What to do next
Related guides
Staff
Create and manage staff in BondiByte: CSV import, employment and rostering settings, availability, evidence-backed capabilities, compliance documents, login access, and site relationships.
Audit, Documents, and EvidenceDocuments
Upload and manage documents linked to staff, clients, sites, or organisation areas, with expiry dates and audit evidence readiness.
RosteringSIL / Automated Rostering
Set up SIL rosters that run at a site with supervised Smart Rostering automation, covering base recurring shifts, staff interest, suitability checks, draft assignments, manager review, and publishing.
Need help applying this setup path?
Book a BondiByte demo and we can walk through the right setup order for your provider.