Skip to content

DocumentationThe practical guide

Behaviour support documentation in Australia: a practical record checklist

For growing teams: a realistic session example, a record checklist, and primary NDIS Commission sources. Not legal advice. Noteable’s advanced documentation layer sits beside the practice software you already use.

Before you read

In short

  • The plan is not the whole record. Session notes have to show whether agreed strategies were used.

  • Use the example and checklist below before you add more policy documents.

  • Primary rules live with the NDIS Commission. This article does not speak for the regulator.

This is for growing behaviour support teams — more than one worker delivering the same plan. If you only write your own notes, start with how to write NDIS session notes instead.

The practical outcome: a file another practitioner can read without calling the person who wrote it. This is not legal advice, and it does not say what any auditor will ask for.

A realistic documentation example

Plan (abridged): For transitions away from preferred activities, use a two-minute warning, then a visual countdown, then offer the agreed next activity. Do not skip the warning.

Weak session note

Community access. Client was dysregulated at the shops. Settled after support. Worked on goals. No RP.

A supervisor cannot tell whether the transition protocol was used, skipped, or replaced with something else.

Improved session note

3:10pm leaving the supermarket. Sam was engaged at the self-checkout and objected when asked to leave. Worker gave the two-minute warning, then the visual countdown card from the plan. Sam walked to the car after one additional verbal prompt. No regulated restrictive practice used. Next time: have the countdown card in the bag before checkout, not in the car.

That note shows the planned strategy, what was delivered, the client response, and a follow-up. It does not prove the whole plan is working. It makes implementation visible.

Practical record checklist

Use this on a sample of recent sessions before a review:

  • The active behaviour support plan (interim or comprehensive) is identifiable in the file.
  • Session notes say which strategy was used, not only that the session “went well.”
  • Client response is observable (what they did or said), not only a mood label.
  • If a regulated restrictive practice was used or considered, the note points to the plan protocol and the implementing-provider record — see the Commission’s behaviour support pages.
  • Follow-up for the next worker is written, not left in chat.
  • Notes are completed close enough to the session that the sequence is still true.

Commission guidance on developing plans is clear that a plan should include preventative strategies, response strategies, and — if relevant — how regulated restrictive practices may be used. Session notes are how you show those strategies appeared in delivery.

Specialist behaviour support providers also have registration conditions around consultation, functional behavioural assessment for comprehensive plans, and review of plans that include regulated restrictive practices at least every 12 months while in force. Confirm the current Restrictive Practices and Behaviour Support Rules with your compliance lead.

Where Noteable fits for a growing team

Noteable can keep the session note with the client’s recent context and goals so covering workers are not reconstructing the week. It does not replace the NDIS Commission portal, state authorisation, or your practice-management roster. That advanced documentation layer is optional. The checklist above still applies if you write notes in another system.

For plan-drift specifically, read intervention fidelity tracking.

Behind this guide

Sources

For growing teams

Build a shared record your team can use.

Start with a session, review the draft, and invite your team. Confirm what matters so useful client knowledge stays available across workers and weeks.

14 days free. No card required. You review every note.

Read next