A shift handover should tell the incoming worker what has changed, what remains to be done and where to find the reliable source information. It should leave less room for an important task to become “something the next shift probably knows about.”
The most useful record is specific enough to support action and short enough to review. It does not need to repeat the entire shift note or copy every participant plan into another document.
This guide suggests a non-clinical handover structure. It does not provide treatment instructions, change staffing requirements or replace the participant's current authorised support arrangements.
Use handover to connect the work
The Core continuity indicators address consistent access to supports and making participants' needs and preferences available to workers. A handover can help connect those arrangements across a shift change. The indicators do not prescribe the table in this article. NDIS Commission: continuity of supports.
Think of handover as a bridge between the current plan, the record of what occurred and the next responsible person. Each has a different purpose.
A plan tells workers what the agreed arrangements are. A shift record describes events and work completed. The handover highlights the relevant changes, unresolved questions and actions for the incoming shift. A separate incident or complaint process may also be needed.
Set the boundary before writing
Identify the date, shift, location, author and receiving worker or role. Record when the handover was prepared and when it was received. If it is updated later, make the addition traceable.
Use the provider's approved system and access arrangements. Keep participant-specific information available only to the workers who need it. A house-wide handover view does not justify sharing one resident's private information with another resident or unrelated staff.
Decide what needs a conversation as well as a written entry. For an urgent concern, use the established escalation channel immediately. Do not rely on a worker eventually opening a routine handover list. The Code of Conduct includes prompt action on concerns affecting the quality and safety of support. NDIS Commission: Code of Conduct.
Use a consistent order
Start with matters requiring prompt attention, then move to planned tasks and ordinary updates. The following fields make a useful starting point:
| Field | What to capture |
|---|---|
| Item reference | The participant or task reference appropriate to the authorised record |
| Change or unfinished work | What is different or still needs attention |
| Known facts and source | What was observed, reported or confirmed, with the underlying reference |
| Action already taken | Who did what and when |
| Next step and timing | What the incoming person needs to do and by when |
| Owner and acceptance | Who now owns that step and when they confirmed it |
| Escalation or uncertainty | What remains unresolved and the relevant contact or process |
Use the same order consistently so people can scan for what matters. A field called “other” tends to collect important information without making its purpose clear.
Write actions that another person can complete
“Follow up transport” leaves several questions unanswered. Which booking? What needs confirming? Who has already been contacted? When is the answer needed?
Try: “Confirm whether the amended pickup time has been accepted; booking reference DEMO-T04. Request sent to the approved contact at 13:10. No confirmation received as at 14:00. Incoming shift lead to check the booking record before the planned departure and escalate unresolved arrangements under the usual procedure.”
The entry separates the request from the result. It does not describe the booking as changed merely because someone sent a message.
For each action, ask whether a worker who was not present could understand it. Replace “as discussed” with a reference to the actual decision or instruction. Keep only the detail needed for the next step; the full supporting account can remain in its original location.
A fictional handover example
The following example is invented. It concerns an ordinary community-activity booking and provides no clinical direction.
Record: DEMO-H08. Prepared: 14 September 2026, 14:00. Outgoing worker: Sam. Incoming shift lead: Jo. Participant record: DEMO-P06, accessible only through the approved support record.
Change: “The person told me they would prefer to attend tomorrow's afternoon activity instead of the morning session. I recorded their request at 12:45. The activity organiser has confirmed the afternoon place in the booking record. Transport confirmation remains outstanding.”
Action completed: “At 13:10 I sent the transport change request through the approved booking channel. The organiser's confirmation and the transport request are linked in DEMO-T04.”
Next step: “Jo to check the transport response, explain the confirmed arrangements to the person using their preferred communication method, and record any unresolved issue. Do not describe transport as confirmed until the response is available.”
Receipt: “At 14:08 Jo read back the outstanding transport action and confirmed responsibility. The person's existing support arrangements remain in place while the request is resolved.”
The handover does not assume that another provider will accept a change. It also keeps the person's request distinct from the arrangements that have actually been agreed.
Reference current plans without copying clinical instructions
If an item relates to a support plan or specialist instruction, identify the approved source and relevant version or review date. Make sure the receiving worker can access it through the correct system.
Do not use a free-text handover to invent or vary a medicine dose, clinical threshold, equipment setting, restrictive practice or emergency protocol. A message saying “do it this way tonight” is not a substitute for the required authorisation and competence.
If instructions appear inconsistent or the current source cannot be found, record the uncertainty and use the appropriate escalation process. Do not silently choose an older copy because it is easier to open.
The SIL practice-governance standard connects consistent practice across workers with each person's needs and preferences. A useful handover supports that consistency without claiming to establish it by itself. NDIS Commission: SIL practice governance.
Keep reporting processes visible
An incident may need an immediate response, an internal record and separate reporting assessment. A handover can link to the incident reference and identify the next responsible person, but it does not complete those steps automatically. NDIS Commission: incident management.
Avoid statements such as “all dealt with” where the assessment or follow-up remains open. Say which action was completed and which decision is still pending.
The same applies to complaints. Passing a concern to the next shift is not the same as acknowledging it to the person or assigning it to the complaints owner. Link the appropriate record and confirm the handover reached the person responsible.
Make receipt meaningful
For important unfinished work, ask the receiving worker to state the next step back in their own words. This can reveal a missing detail before the outgoing worker leaves.
A read receipt may show that a message was opened. It does not establish that the task was understood or accepted. If a worker cannot take responsibility because they lack authority, access or competence, identify the appropriate person and escalate the gap.
Where shifts do not overlap, use the provider's approved alternative arrangement. Record the contact, acknowledgement and unresolved questions. Do not invent a fixed overlap duration or treat this article as a rostering or industrial-relations rule.
Review one handover before changing every form
Through your authorised process, select one recent handover and check:
- Can the next worker distinguish confirmed facts from requests or assumptions?
- Does each unfinished action have an owner and timing?
- Are current source records accessible to the right people?
- Are urgent concerns escalated separately?
- Is the participant's preference represented accurately?
- Does the record show receipt or a failed handover needing action?
- Are amendments traceable without erasing the earlier account?
Use what you find to improve one weak part of the process. A clearer owner field or source reference may be more useful than adding another page of checkboxes.
To see an issue recorded with its next review still visible, watch the ProviderQMS walkthrough.
Official sources reviewed 14 September 2026. This is a suggested recording method, not a clinical instruction, staffing model or prescribed NDIS handover form.
Existing published source retained. Original source review: 2026-09-14. Citations appear in the guide above. The new layout does not imply a new regulatory review.