Incidents and Reporting
Record incidents and keep them ready for review.
Capture incident records linked to the right participant, staff, site, and shift, with the severity, immediate action, and follow-up detail you need for review and audit readiness. Your organisation can add its own incident forms alongside the standard one.
Overview
Incidents let you record what happened, link it to the relevant participant, staff, site, and shift, and keep the detail organised for review and audit.
Incidents use the same template model as Reports. The standard BondiByte incident report is one incident type, and every form your organisation builds and publishes with the category Incident becomes another. With no organisation incident forms, Add incident opens the standard form straight away.
Incident records support follow-up and evidence readiness; they do not replace your incident-response process or reporting obligations.
Before you begin
- Have your own incident-response and reportable-incident process in place; BondiByte does not handle emergencies.
- Know which participant, staff, site, and shift the incident relates to.
- Decide whether the standard incident form is enough, or whether your organisation needs incident forms of its own.
Recommended setup order
- Open Incidents and select Add incident.
- Choose the incident type. Where your organisation has published incident forms, a chooser offers the standard BondiByte incident report alongside them; where it has none, the standard form opens directly.
- Enter the date and time, incident type, severity, and a clear summary and description of what happened.
- Record the immediate action taken.
- Link the client, the site or another location, the shift, and every staff member involved.
- Set whether follow-up is required, its due date, and who owns it.
- Review the record in the register, and keep supporting evidence in Documents against the client, staff member, or site.
Key fields and settings
Incident record
The captured record of what happened, when, and who was involved. Each one carries its own incident number.
Incident type
Which incident form is being filled in: the standard BondiByte incident report, or one of your organisation's published Incident forms.
Severity
How serious the incident was. The register counts high-risk incidents, and severe incident notifications route on it.
Status
Where the record is up to, starting at Open. The register shows totals for all, open, awaiting follow-up, and high risk.
Linked records
The client, site or other location, shift, and staff involved that the incident is connected to.
Follow-up
Whether follow-up is required, the date it is due, and the staff member who owns it.
Evidence
Supporting files, kept in Documents against the client, staff member, or site the incident concerns.
Best practice
- Record incidents promptly and factually.
- Set severity honestly. It drives the high-risk count and any severe incident notification.
- Link the right people, site, and shift so the record stands on its own at review time.
- Keep supporting evidence in Documents so it is there when the Audit Centre needs it.
Common mistakes to avoid
- Relying on BondiByte for emergency or urgent safety response.
- Treating an incident record as meeting your reportable-incident obligations.
- Building an incident form and then looking for it under Reports. A published form categorised Incident opens here, in the Incidents area.
- Leaving incidents unlinked to the participant, staff, site, or shift.
- Marking follow-up required and then leaving the due date and owner blank.
What to do next
Related guides
Audit Centre
Live audit readiness score, compliance checks and enforcement, the Prepare Audit wizard, evidence packs, NDIS Practice Standards mapping, secure auditor portal, staff ratings, and audit sessions.
Audit, Documents, and EvidenceDocuments
Upload and manage documents linked to staff, clients, sites, or organisation areas: document types, expiry dates, renewal reminders, compliance checks, certificates and licences, and audit evidence readiness.
Incidents and ReportingReports
Use the Reports register for records attached to a staff member, client, site, or shift, build and publish your own report and form templates in Configuration under Reports and Forms, review submissions as a manager, and keep everything ready for evidence.
Need help applying this setup path?
Book a BondiByte demo and we can walk through the right setup order for your provider.