Support Worker Shift Notes vs Handover Notes: What's the Difference?

Shift notes and handover notes often contain similar information.

But they aren't necessarily the same thing.

A useful practical distinction is:

Shift notes record what happened during a support.

Handover notes highlight what another person needs to know next.

There is no single universal NDIS template or terminology that every worker and provider must use, and organisations may use different names for their records.

What matters is understanding the purpose of the record you're creating and any specific obligations that apply to your work.

What are shift notes?

Shift notes — sometimes called progress notes or support notes — generally provide a record of relevant information about the support delivered.

Depending on the participant and organisation, a shift note might record:

• activities completed
• support provided
• participant choices
• progress toward goals
• relevant observations
• appointments attended
• important events
• incidents or concerns
• outcomes
• follow-up required

The exact content will depend on the support arrangement and the record's purpose.

What are handover notes?

A handover is more forward-looking.

Its core question is:

What does the next appropriate person need to know?

For example:

Jordan attended physio this morning and the appointment was recorded in the shift note.

That may be useful history.

But if the physiotherapist asked Jordan to bring a particular item to the next appointment, that instruction may also belong in the handover because somebody needs to act on it later.

The NDIS Commission's supervision guidance specifically refers to organisations including key points in handover notes so relevant information is available to workers assigned to participants.

One records the support; one supports continuity

Consider this example.

Shift note

Supported Mia from 9 am to 1 pm. Mia chose to visit the library and supermarket. Returned home at 12:10 pm and prepared lunch. Mia selected pasta. Kitchen cleaned after lunch.

Handover

Mia's occupational therapy appointment tomorrow has moved from 11 am to 10 am. Transport needs to arrive by 9:30. Mia asked the morning worker to bring her communication device charger.

Both notes are useful.

But for different reasons.

The shift note records the support.

The handover tells the next person what matters next.

There will often be overlap

Suppose a participant says their knee is sore during a shift.

That fact may belong in the shift note because it occurred during the support.

It may also need to be communicated in the handover if it is relevant to what the participant wants the next worker to know.

Duplication isn't automatically a problem.

But repeatedly copying entire shift notes into a group chat is rarely the clearest system.

What belongs in a shift note?

A shift note may need to capture things such as:

Support delivered

What relevant support was provided?

Activities

What significant activities took place?

Participant choice

What did the participant choose or request?

Relevant observations

Was there something relevant to the person's support worth recording?

Goals or outcomes

Where appropriate, did the support relate to an agreed goal or outcome?

Incidents or concerns

Did something occur requiring separate action or reporting?

Follow-up

Is anything arising from the support still outstanding?

The record should remain factual and respectful.

What belongs in a handover?

A handover can be much shorter.

Think:

Changes

Has anything changed?

Risks

Is there a relevant ongoing concern?

Schedule

Has an appointment or support changed?

Tasks

Does something need to be completed?

Preferences

Has the participant asked for something different?

Follow-up

What does another person need to do or monitor?

Don't use either one to replace formal records that are required elsewhere

This distinction matters.

A handover shouldn't become a substitute for:

• an incident report
• a medication administration record
• formal clinical documentation
• other records required by an employer, provider, contract or law

The NDIS Commission requires registered providers to record and manage incidents through appropriate incident-management systems, including maintaining privacy and confidentiality of those records.

A short message saying “incident occurred today” may alert another worker.

It does not necessarily satisfy the underlying recordkeeping requirement.

Keep notes factual

Support documentation should avoid vague or judgemental descriptions.

Instead of:

“Liam was difficult today.”

consider:

“Liam declined the planned shopping trip and said he wanted to remain at home.”

Instead of:

“Sophie was aggressive.”

record the actual observable event where appropriate:

“Sophie raised her voice and pushed the dining chair away after being asked about leaving for the appointment.”

Context is more useful than labels.

Don't record everything just because you can

Detailed records can be valuable.

Unnecessary personal information can create additional privacy risk without improving support.

The NDIS Code of Conduct requires respect for the privacy of people with disability.

Ask:

Why does this need to be recorded?

and:

Who needs access to it?

The problem with keeping both inside one message thread

Some support networks use a group chat for everything.

That chat may contain:

• shift summaries
• handovers
• appointment changes
• tasks
• general conversation
• photographs
• questions
• availability

It can work when the support network is small.

But as activity increases, the user has to remember when something was said in order to find it again.

A task from Monday is still buried in Monday's conversation even if it's due Friday.

A calendar change is still a message rather than a calendar event.

A handover becomes harder to distinguish from general discussion.

A better structure

Think of care information as several connected types:

Timeline / shift note What happened?

Handover What does the next person need to know?

Task What needs to be done?

Calendar When is something happening?

Participant profile What is important to know generally?

Emergency information What could be needed urgently?

They're related.

But they're not interchangeable.

Where Neume fits

Neume is designed to organise those different types of care information around the participant.

Instead of forcing one message stream to do everything, Neume is being built around:

• a care timeline
• handovers and updates
• tasks
• schedules
• participant information
• health information
• documents
• contacts
• messaging
• emergency care information

The objective is simple:

Record information once in a place where it still makes sense when somebody needs it later.