One register for incidents, with severity, status and the full context of what happened. Follow-up is owned by a named person with a due date, and anything left sitting is escalated by email rather than forgotten. Complaints get their own register alongside it.
Every incident in one filterable list, with its severity, status and the record it relates to.
Someone by name owns the follow-up, and the date is on the record rather than in a diary.
Incidents left open and follow-ups falling due raise an email to the person who can act.
Incidents get written up in an email, a paper form or a message to a team leader, and then they drift. Nobody is certain which are still open, who agreed to follow one up, or whether the follow-up ever happened. When the register is finally assembled for an audit it is reconstructed from memory, which is exactly when it needs to be beyond question. Recording an incident properly at the time, with an owner attached, removes the reconstruction entirely.
An incident carries its own number, its type and severity, when it occurred, the participant and the site or another location, the shift it relates to, the staff involved, what happened, and the immediate action taken.
Severity and status come from your organisation's own catalogues, so the words match how your team already talks about incidents. A new incident opens, and moves through your workflow to closure.
Where follow-up is required, choose the staff member who owns it and the date it is due. Both sit on the incident, not in someone's head.
With incident escalation switched on, follow-ups approaching their due date raise a reminder, incidents left open and unresolved are escalated by email, and high or critical incidents notify the people you have nominated straight away.
Filter the register by status, severity and date to see what is still open, what closed, and what is coming due. The same data generates the incident register in an audit session.
Each incident carries its own reference, so it can be cited in a report, a conversation with the Commission, or an auditor's sample without ambiguity.
Severity levels and statuses come from your organisation's catalogues rather than a fixed vocabulary, so the register reads the way your team already speaks.
An incident points at the record it is actually about, including the shift it happened on, so the surrounding context is one click away instead of retyped.
Follow-up is assigned to a person, not to a team, with the date it is due held on the record where reminders can act on it.
Incidents left open and unresolved are escalated by email, follow-ups raise a reminder before they fall due, and high or critical incidents notify immediately, routed to the people you nominate.
Record a complaint with who it came from, whether that is the participant, family, a worker, an advocate or someone else, when it was received, and the detail. Acknowledge it, then resolve it with a written resolution.
Acknowledging promptly and resolving by the due date shows up in your readiness checks, so a complaint left sitting is visible before an auditor finds it.
Preparing an audit generates an incident register from these records: number, date, status, severity, summary, site, participant, follow-up detail and closure. No assembling it by hand.
Incident escalation, follow-up reminders and severe incident notifications run only while an owner or admin has that automation switched on.
Severe incident notifications follow the routing you configure, and you set which severity levels count as severe and whether the alert goes immediately or at the end of the day.
BondiByte records incidents, chases follow-up and produces the register. Whether something is reportable to the NDIS Quality and Safeguards Commission remains your organisation's judgement, made under its own policy.
If you switch on AI-assisted features, a shift report can be flagged for a person to look at and an incident report can be pre-filled from one. Both wait for a human decision, and neither changes the original report.
No. The register captures what happened, its severity, its status and its follow-up, and produces the evidence. Whether an incident is reportable to the NDIS Quality and Safeguards Commission is a decision your organisation makes under its own policy.
Every follow-up has a named owner and a due date on the incident itself. With incident escalation switched on, reminders go out before the date, and incidents left open and unresolved escalate by email to the person who can act.
They have their own register in the Audit Centre. A complaint records who it came from, when it was received and the detail, then moves from open to acknowledged to resolved with a written resolution. Both registers feed audit readiness.
Yes. Choose the shift it happened on, or record the date and time yourself where the incident falls outside a rostered shift. The participant, site or other location and the staff involved are recorded the same way.
The incident number, when it occurred, its status and severity, a summary, the site and participant, whether follow-up was required and when it was due, and when it was closed. It is generated from your live records when you prepare an audit.
Store, type, and manage participant, staff, site, and organisation documents.
Documents, Audit & ComplianceKeep your policies, procedures, insurance certificates, registration documents and contract templates in one organisation library, separate from staff and client files, so the whole team reuses the current copy instead of rebuilding it.
Documents, Audit & ComplianceA live readiness score with automatic checks, staff self-service compliance, and audit sessions with scoped auditor access.
Documents, Audit & ComplianceMap your audit evidence to the NDIS Practice Standards, outcome by outcome, so coverage and gaps are obvious months before an auditor asks.
Documents, Audit & ComplianceGive auditors a secure, time-boxed view of exactly the evidence you choose, organised by NDIS Practice Standard, with requests, findings and access logs kept in one place.
Documents, Audit & ComplianceStart from BondiByte's built-in templates or build your own: sections, fields, and rules that show a question only when it is relevant. Publish when you are ready, and every completed report keeps the version it was written on.
Start your free trial, or book a demo to see it with your own operation in mind.
Hi, I can help with BondiByte features, pricing, setup and more.
Please don’t include sensitive participant or personal information.