What is the difference between a behaviour of concern record and a reportable incident report?

A behaviour of concern record documents what happened, the context, and the response for clinical and governance purposes. A reportable incident report is a mandatory notification to the NDIS Commission for specific serious events defined in the NDIS Incident Management Rules, such as death, serious injury, or unauthorised restrictive practices. Some events require both — the behaviour record is an internal document; the incident report goes to the Commission.

How quickly must a behaviour of concern be documented?

There is no single prescribed timeframe in the Practice Standards, but the expectation is that records are completed as soon as practicable — ideally within the same shift and no later than 24 hours after the event. Delayed documentation is a common audit finding and reduces the clinical value of the record.

Do we need to document behaviours of concern even when no restrictive practice was used?

Yes. The obligation to document behaviours of concern exists independently of whether a restrictive practice occurred. Behaviour records are required to inform the Behaviour Support Plan, identify patterns, and demonstrate that your organisation is actively working to understand and reduce the behaviour.

Who can complete a behaviour of concern record?

Any support worker who directly observed or responded to the behaviour can complete the record. However, your organisation's policy should require a supervisor or team leader to review and countersign each record, and the Specialist Behaviour Support Practitioner must be notified when the behaviour meets your escalation threshold.

How long must behaviour of concern records be retained?

The NDIS Practice Standards require providers to retain records in accordance with applicable laws. As a general rule, records should be retained for at least seven years from the date of creation, or longer if the participant was a minor (typically until they turn 25). Always check state or territory legislation that may impose a longer minimum period.

What language should we avoid when describing a behaviour of concern?

Avoid interpretive, diagnostic, or value-laden terms such as 'aggressive,' 'manipulative,' 'attention-seeking,' 'non-compliant,' or 'tantrum.' Instead, use observable, factual descriptions of exactly what the person did or said. This makes records more useful for functional behaviour assessment and more defensible during an audit or investigation.

How to document a behaviour of concern in NDIS (template + steps)

Why accurate documentation matters for NDIS providers

Documenting behaviours of concern is not a paperwork formality — it is a clinical and legal requirement under the NDIS Practice Standards. Every registered provider who delivers behaviour support or uses regulated restrictive practices must maintain contemporaneous, objective records. These records are reviewed by the NDIS Quality and Safeguards Commission during audits, inform the work of Specialist Behaviour Support Practitioners, protect participants, and protect your organisation.

Under the strengthened 2026 NDIS Practice Standards framework, expectations around behaviour support documentation have been tightened. Auditors now look for evidence that records are completed promptly, are free of subjective language, and are consistently linked to each participant's Behaviour Support Plan (BSP). Providers who cannot demonstrate this risk non-conformance findings, conditions on registration, or referral for investigation.

What is a "behaviour of concern" in the NDIS context?

The NDIS Commission defines behaviours of concern as behaviours that are likely to cause harm to the person themselves or others, or that significantly impact the person's quality of life or participation. Common examples include physical aggression, self-injurious behaviour, property destruction, and elopement. The term deliberately avoids value-laden language — the focus is on impact and function, not moral judgement.

It is important to distinguish a behaviour of concern from a restrictive practice. A restrictive practice is a response to a behaviour; documenting the behaviour is a separate obligation that must occur regardless of whether any restrictive practice was used.

Step-by-step: how to document a behaviour of concern

Record immediately or as soon as practicable. Documentation should occur within the shift where possible, and no later than 24 hours after the incident. Memory fades quickly and delayed records carry less evidentiary weight during audits or investigations.
Use objective, observable language. Describe what you saw and heard — not what you interpreted or felt. Write "Participant struck support worker on the left arm with a closed fist" rather than "participant was aggressive." Avoid terms like "tantrum," "manipulative," or "attention-seeking."
Complete all required fields. A compliant behaviour of concern record must capture: date and time; location; the specific behaviour observed (using observable language); antecedents (what happened immediately before); consequences (what happened immediately after, including the participant's response); duration; intensity or severity (using your organisation's agreed scale); people present; immediate response by support workers; any first aid provided; and the name and signature of the staff member completing the record.
Link to the participant's Behaviour Support Plan. The record should reference whether the behaviour is identified in the BSP, whether the response was consistent with the BSP strategies, and whether the BSP needs to be reviewed as a result. This linkage is a key auditor checkpoint.
Notify the Specialist Behaviour Support Practitioner. If the behaviour is new, escalating in frequency or severity, or resulted in injury, notify the practitioner promptly. Your BSP should specify the notification threshold. Do not wait until the next scheduled review meeting.
Determine whether a reportable incident has occurred. Some behaviours of concern will also meet the threshold for a reportable incident under the NDIS (Incident Management and Reportable Incidents) Rules. If the behaviour resulted in serious injury, death, unlawful sexual or physical contact, unauthorised use of a restrictive practice, or a missing person, you must lodge a report with the NDIS Commission within the required timeframe. Behaviour documentation and incident reporting are separate obligations — both must be completed.
Store securely and maintain confidentiality. Records must be stored in accordance with your participant's privacy rights and your obligations under the Australian Privacy Act. Access should be limited to staff with a legitimate need, and records must be retained for the period specified in your record-keeping policy (generally a minimum of seven years, longer for minors).
Review and aggregate data regularly. Individual records are only useful if they are analysed. At a minimum, your team should review behaviour data at each BSP review meeting. Look for patterns in antecedents, times of day, settings, or staff involved. Trend data is what drives meaningful plan adjustments.

Behaviour of concern documentation template

The following template covers the minimum required fields. Adapt it to your organisation's system, whether paper-based or electronic.

Field	What to record
Participant name / ID	Legal name and internal client ID
Date and time	Date and exact time the behaviour commenced
Location	Specific setting (e.g., dining room, community outing at Westfield Doncaster)
People present	Names/roles of all staff and others present
Antecedent	What occurred immediately before the behaviour (observable facts only)
Behaviour description	Exact, observable description of the behaviour; duration; intensity on agreed scale
Consequence	What happened immediately after the behaviour; participant and environment response
Immediate response	Actions taken by staff; whether response was consistent with BSP strategies (yes/no + explanation if no)
Injury / first aid	Any injuries to participant, staff, or others; first aid provided
Restrictive practice used?	Yes / No — if yes, type and duration; authorisation reference
Reportable incident?	Yes / No — if yes, incident report number and date lodged
BSP notification required?	Yes / No — if yes, date and method of notification to practitioner
Completed by	Full name, role, date, and signature (or electronic equivalent)
Reviewed by (supervisor)	Name, role, date, and any follow-up actions required

Common documentation mistakes and how to avoid them

Subjective or interpretive language. Phrases like "participant was being difficult" or "tried to manipulate staff" are not observable descriptions. Replace with factual accounts of what was seen or heard.
Incomplete antecedent recording. Antecedents are the most clinically valuable part of the record for a behaviour support practitioner. Leaving this field blank or writing "unknown" without genuine investigation is a common audit finding.
Delayed completion. Records completed days after the event are considered unreliable. Auditors will check timestamps in electronic systems. Build completion into your shift handover routine.
No link to the BSP. A standalone record that does not reference whether the response followed the BSP is of limited compliance value. Always cross-reference.
Conflating documentation with incident reporting. Not every behaviour of concern is a reportable incident — but every reportable incident requires both a behaviour record and a Commission report. Confusing the two leads to either over-reporting or missed obligations.
Inadequate storage and access controls. Leaving paper records in unsecured locations, or granting system access to all staff indiscriminately, breaches privacy obligations and can constitute a separate non-conformance.

How this fits into the 2026 strengthened framework

The NDIS Commission's strengthened Practice Standards, which apply to providers registered under the 2024–2026 transition timetable, place increased emphasis on human rights, least restrictive practice, and evidence-based behaviour support. Auditors under the new framework are specifically trained to examine whether documentation demonstrates a genuine commitment to reducing and eliminating restrictive practices over time — not merely recording their use. Behaviour of concern records are a primary source of evidence for this assessment.

If your organisation is preparing for a registration renewal or initial audit, reviewing the quality and consistency of your behaviour documentation is one of the highest-leverage activities you can undertake. Providers who use the ndiscompliant.com.au 74-document audit-ready SIL compliance kit have access to pre-formatted behaviour recording templates, incident escalation flowcharts, and BSP review checklists designed specifically for the 2026 audit cycle.

Practical tips for SIL providers

Build behaviour documentation into your shift handover checklist so no incident is inadvertently missed at changeover.
Provide regular, scenario-based training for support workers on what constitutes a behaviour of concern and how to describe it objectively. Competency in this area is a Practice Standards requirement.
Use your electronic care management system to generate monthly frequency reports by participant, setting, and time of day. Share these reports at BSP review meetings.
Keep a clear escalation pathway documented: who is notified when a behaviour is new, when it reaches a threshold frequency, and when the BSP practitioner must attend in person.

Important: This article provides general guidance about NDIS compliance requirements. It is not legal or professional advice. Requirements may change as the NDIS Commission updates its policies and Practice Standards. Always verify current requirements with the NDIS Quality and Safeguards Commission or a registered NDIS consultant before making compliance decisions.