Looking at operations software usually means filling in a form and waiting for someone to call you back. Most of the questions people actually have are not worth a meeting: what does this part do, what does a plan cost, what would we have to set up first, and is this even built for an organisation our size.
Ask BondiByte sits on every page of this website. Open it, ask in your own words, and it answers from BondiByte's own published material, with links to the page or guide the answer came from. When it does not know, it says so and offers to put you in touch with a person.
You will find it as a small Ask BondiByte button in the corner of every page, including this one.
Every page suggests a few starting questions relevant to what you are reading, and you can ignore them and ask your own.
Feature questions, answered without a demo booking.
The commercial questions people ask first.
What the first fortnight looks like.
An honest read on fit, before you invest time.
These answers reflect released product capabilities and clearly identify mobile, migration and other workflows that still need confirmation.
BondiByte is a cloud-hosted operations platform for Australian NDIS providers. It connects staff, participants, sites, rosters, timesheets, documents, service agreements, incidents, reports, audit evidence and controlled automation in one workspace.
BondiByte is shaped around NDIS provider operations rather than adapted from a generic scheduling tool. Smart Rostering, configurable records, audit readiness and supervised automation work together, while managers keep review and approval control.
Smart Rostering checks hard requirements first, then ranks suitable staff using factors such as availability, capabilities, continuity, workload, fatigue settings and recent cancellations. Managers review recommendations and remain in control before shifts are published.
BondiByte supports open shifts, interest and claims, swap requests, cancellation requests and manager approvals. Coverage remains a managed workflow rather than an automatic decision made without oversight.
Staff records can hold employment context, site relationships, availability, documents, capabilities and qualifications. Invitations and login access connect staff to their own portal, while managers retain approval controls.
Participant records connect onboarding details, representatives, consent, sites, service agreements, documents, billing context, reports, incidents and history. Access follows roles and record relationships, so staff do not automatically see every participant.
Yes. Owners and admins can start from BondiByte templates or build organisation forms with sections, fields, choices, people fields and display rules. Published Report forms appear in reporting workflows; Incident forms are routed to incident workflows and their records stay in the incident area.
Reports capture an event, note or assessment. Charts capture the same structured observations repeatedly over time for a particular participant. Both use configurable forms, but Charts add client assignment, effective-dated configuration, a chronological entry register and period PDFs.
Yes. A Chart can be assigned to one participant with choices configured for that person, and can use a repeating Table field for structured rows. Changes take effect from the date you choose, while earlier entries retain the configuration that applied when staff recorded them.
BondiByte includes starter Chart templates for structured operational observations such as behaviour, food and fluid, sleep and medication-related records. These are configurable record-keeping tools, not clinical advice, a medication-management engine or a guarantee of compliance. Your organisation remains responsible for clinical decisions, policy and oversight.
Client Intelligence generates an AI summary of a participant's shift and incident reports over a period you choose (7, 14, 30, 90 days or custom), from the sources you pick. It reads reports your team already recorded, refuses to summarise a period with no matching records, and is one of the AI-assisted capabilities your organisation turns on rather than something switched on by default.
Yes. Incidents can be recorded with their participant, site, shift, severity, status, immediate action, follow-up owner and due date. Optional reminders and escalation support follow-up, but BondiByte does not decide whether an incident is reportable.
Yes. Client report PDF download is a released feature: a report downloads as a clean PDF that preserves the report's structure and sections, rather than a plain text dump. Downloads are available from the relevant Reports surfaces according to your permissions.
Yes. A downloaded report PDF mirrors the sections and structure of the published report it was completed on, rather than flattening it into plain text. Chart PDFs work the same way for a chosen date range of Chart entries.
No. Plain notes are not report PDFs. Report PDF download applies to completed Reports and Incident records built from a published form; for a plain note, use the report or note export the register already offers instead of expecting an automatic PDF.
Yes. Managers can download a Chart PDF for a chosen date range, generated from a participant's Chart entries. This is a separate download from client report PDFs, which cover Report and Incident records instead.
Build and publish an agreement template, generate a client PDF, add funded-support line items and send a secure browser link for e-signature. The signed copy is stored as a fixed record, and later template changes do not rewrite it.
Yes. Service agreement line items can be imported using the BondiByte CSV template, matched against your NDIS catalogue for review before anything is saved. Manual entry of catalogue and custom lines on the agreement itself remains available alongside the import.
Screenshot-assisted capture is available where your organisation has the required capability and configuration enabled, reading a screenshot of an existing agreement or plan into draft line items for review. Where it is not enabled for your organisation, use the CSV template or add lines from the catalogue instead.
No. Imported and screenshot-captured line items are held for review first, so you confirm the catalogue match, quantities and budgets before anything is saved to the agreement. The existing agreement controls, including read-only signed agreements, still apply to imported lines.
Timesheets can be entered manually, generated as drafts from rostered work, or optionally prepared after a period ends. Staff review and submit them; managers approve, return or reject them. Approved timesheets can be exported to CSV for payroll processing.
Yes. Staff can record work-related kilometres on a shift report, and that figure carries onto the matching timesheet line when the timesheet is generated. Staff can also enter or correct mileage directly on the timesheet. This is distance only; BondiByte does not calculate reimbursement, allowances or a pay rate for it.
BondiByte supports pay levels, pay rules and reviewable timesheet evidence, but it does not replace award interpretation or Fair Work advice. Providers remain responsible for checking rates and payroll outcomes against authoritative sources.
Yes. Connect a Xero Australia Payroll organisation from Configuration, map BondiByte staff to Xero employees, then send approved timesheets to Xero as draft timesheets from Timesheets. Xero Payroll stays the payment authority; BondiByte classifies approved time and nothing is sent until an administrator clicks Send.
A Xero Australia Payroll organisation with a payroll calendar that starts on the same weekday as your BondiByte roster period. The Payroll calendars panel compares every Xero payroll calendar your mapped employees sit on against your roster period and explains the fix when one does not line up.
Map each BondiByte staff member to their Xero employee, then choose a payroll rate source. With Pay Levels off, every approved hour sends against one default Xero earnings rate. With Pay Levels on, each pay item, such as weekday, Saturday, Sunday or public holiday, is mapped to its own Xero earnings rate in the Pay Level line item editor. Choosing Xero as the rate source means Xero's earnings rate supplies the dollar amount and BondiByte sends hours only; choosing BondiByte keeps your BondiByte rates authoritative, and the send is still hours only.
BondiByte sends approved timesheet hours to Xero as draft timesheets, one logical timesheet per employee for the roster fortnight, tracked in a transfer register with automatic retry. It does not send invoices, pay runs, leave, or new employees, and it does not sync with MYOB or Employment Hero through this connection.
The Audit Centre organises audit sessions, evidence, Practice Standards mapping, samples, findings and corrective actions. Invited auditors use separate, time-limited access to only the evidence released to them, and requests, views and downloads are logged.
BondiByte can run approved operational work such as roster preparation, reminders, draft generation, document scans and audit workflows. Automation Capacity measures that work; page views, basic editing and ordinary manual workflows are not metered. At the included limit, blockable automation pauses while manual work continues.
Yes. Related routine reminders can be grouped into a single organised email, which reduces separate reminder messages where grouping is appropriate. Urgent or action-sensitive notifications, such as incident escalation or a shift close to going unfilled, can still arrive individually.
The browser Staff Portal supports shifts, availability, open-shift requests, timesheets, reports, documents and notifications on a phone. BondiByte also has a native iOS and Android staff app in controlled release. Confirm current app access with the BondiByte team during onboarding; the Charts-enabled mobile build is not yet advertised as a public store release.
No. BondiByte uses organisation separation, role and permission controls, and staff-to-site and participant relationships so users see only the work and records available to them. The backend enforces access; visibility is not based on a hidden button alone.
BondiByte is a cloud-hosted SaaS platform on Microsoft Azure with Australian data residency, tenant separation, role-aware access and audit trails. BondiByte does not claim certifications it has not independently established.
Starter $99 per month (includes 10 active staff); Foundation $399 per month (includes 35 active staff); Growth $1,199 per month (includes 75 active staff); Operations $2,449 per month (includes 150 active staff); Robotics $5,499 per month (includes 300 active staff); Robotics Plus $9,999 per month (includes 500 active staff); Enterprise is custom. Starter, Foundation and Growth have a 28-day trial. Current plans include an active-staff allowance and Automation Capacity, with additional staff billed above the allowance.
BondiByte currently supports practical onboarding paths such as staff CSV import and guided setup of participant, site and operational records. A broader self-service Easy Migration workspace has been built and tested but is not yet a production feature, so migration scope is confirmed with the team rather than promised automatically.
Start a trial if you want to explore the platform directly and your plan offers one. Book a demo if you have a larger or complex operating model, need to discuss migration, mobile access, security review or Enterprise pricing, or want help mapping your workflows before setup.
BondiByte exports approved timesheet data to CSV and supports the published workflows described on this site. It does not claim a live integration unless that integration is specifically documented. Ask the team to confirm your target system before relying on an integration.
Answers are drawn from BondiByte's own published material: these product pages, the setup guides, and the current plan and pricing information. An answer usually arrives with the sources behind it, so you can open the page and read the detail yourself rather than taking a chat window's word for it.
Where the next step is obvious, the answer offers it: the relevant guide, the pricing page, a free trial, or a conversation with the team. Nothing is hidden behind the assistant that is not also on the site.
Typed exactly like this, in your own words.
Assistants get oversold. This one has a narrow job, and it is better to be clear about the edges of it than to let anyone find out the hard way.
It stays with you.
Only enough to make the answers better.
Usage, not content.
The full detail is in the Privacy Policy. If a question involves real participant, health or client information, please contact us instead of typing it into the assistant.
The same assistant is here when you are mid-setup and cannot remember whether sites come before staff, or which guide covers pay levels. It knows how the product is meant to be set up, so it can point you at the right written steps in a few seconds.
It does not have access to your workspace, your data or your records, and it cannot see or change anything in your account. For anything specific to your organisation, your own workspace and the BondiByte team are the right place to go.
Some things should not go through a chat window.
Open Ask BondiByte from the corner of any page, or talk to the team if your question needs a person.
Hi, I can help with BondiByte features, pricing, setup and more.
Please don’t include sensitive participant or personal information.