NDIS Handover Documentation Across Workers, Teams, and Providers

Learn how to document NDIS handovers that preserve participant choice, communicate current risks, clarify follow-up, and protect privacy across services.

Published by Integrated Support Team

A Handover Should Change What the Next Person Knows or Does

Effective handover communicates information needed for safe, consistent, participant-led support. It should identify relevant changes, current instructions, unresolved actions, and the participant's preferences without repeating an entire file or sharing information beyond authorised purposes.

Focus on Current and Actionable Information

  • Changes from the participant's usual presentation or routine.
  • Choices, planned activities, and communication preferences.
  • Current support instructions and temporary changes authorised by the appropriate person.
  • Incidents, hazards, equipment faults, or safeguarding actions relevant to the next support.
  • Appointments, referrals, results, or contact attempts still pending.
  • The next action, deadline or trigger, and accountable person.

Example Worker-to-Worker Handover

"Alex chose not to attend swimming this afternoon because his wheelchair cushion felt uncomfortable. Skin was not inspected by the undersigned because Alex requested RN review. RN notified at 2:25 PM and assessed Alex under the current plan. Alex agreed to use his spare approved cushion for evening activities. Main cushion labelled and removed for equipment review. Tomorrow's worker to confirm the occupational therapy appointment and follow the temporary seating instructions recorded by RN."

Cross-Provider Handover Needs Consent and Boundaries

Before sharing information with another provider, confirm the participant's consent or another lawful authority, the purpose of sharing, and the minimum information needed. Record what was shared, with whom, when, how, and any response or action agreed.

A broad service relationship does not mean every worker should access every detail. Use approved secure channels rather than personal messaging accounts.

Keep Participant Voice Visible

Handover language can unintentionally turn a preference into a fixed instruction. Distinguish what the participant requested, what was clinically or operationally authorised, and what remains to be discussed. Avoid labels such as "attention-seeking" or "non-compliant."

Read-Back and Confirmation

For high-risk or complex changes, the receiving person should confirm they understand the instruction and responsibility. Document confirmation in the approved system rather than assuming a sent message was read.

Common Handover Failures

  • "Monitor closely" is used without saying what to observe or when to escalate.
  • The next worker receives a verbal update but the current record is not updated.
  • Pending actions have no owner.
  • Old temporary instructions remain in circulation after review.
  • Unnecessary sensitive information is shared across provider boundaries.

When communication methods need to be tailored, refer to the guide on participant communication assessment documentation. External clinical recommendations can be tracked using the allied health follow-up framework.


This article was written by AccuNote's Integrated Support Team for general documentation education. Providers should follow participant consent, privacy, incident, clinical governance, and information-sharing requirements.