How to Coordinate Multiple Independent Support Workers Without Losing Important Information

Using multiple independent support workers can give an NDIS participant greater choice, flexibility and control over who provides their support.

But it can also create a coordination problem.

One worker knows about an appointment.

Another knows the participant wasn't feeling well yesterday.

A family member knows the schedule changed.

Someone has agreed to collect something on Friday.

Another worker doesn't know any of that.

Nobody has necessarily done anything wrong.

The problem is that each person may only hold one part of the picture.

A practical way to coordinate multiple support workers is to create a shared system covering five things:

1. Who is supporting the participant?
2. What's happening and when?
3. What's changed recently?
4. What still needs to be done?
5. Where does important participant information live?

Start with the participant

The system should be built around the person receiving support — not around whichever worker, family member or app happens to be organising it.

The participant should be involved in decisions about:

• what workers need to know
• what information can be shared
• who should be involved
• how they prefer support to be delivered
• what matters to them
• how workers should communicate

NDIS Commission guidance specifically encourages participants to think about what workers need to know and what information they are comfortable having workers access or share.

Create one reliable schedule

If several people provide support, there should ideally be one place that answers:

Who is coming, and when?

The schedule may include:

• worker shifts
• appointments
• community activities
• therapy
• transport
• recurring support
• family commitments relevant to support

Problems begin when one person uses a phone calendar, another uses SMS and another relies on memory.

A schedule change communicated in a chat should also make its way into the actual shared schedule.

Otherwise information becomes inconsistent.

Make shift changes visible

Suppose Alex normally supports a participant Tuesday at 9 am.

The participant asks to move the shift to Wednesday.

If that change exists only in a private text between those two people, somebody else involved in transportation or another support may still be working from Tuesday's schedule.

A good coordination system should reduce these disconnected updates.

Create a consistent handover process

Workers do not necessarily need lengthy reports after every support.

But there should be a predictable place for relevant updates.

Useful handovers may cover:

• meaningful changes
• participant preferences
• activities
• relevant health observations
• incidents or concerns
• tasks completed
• tasks requiring follow-up
• upcoming changes

The NDIS Commission's supervision material recognises handover notes and written records as methods for making relevant information available to workers.

Consistency matters.

If one worker texts the participant's parent, another writes in a notebook and another sends an email, information becomes fragmented even when everybody is communicating.

Separate conversations from tasks

This is a surprisingly important distinction.

A message such as:

“Can someone remember to call the equipment supplier tomorrow?”

is not really a message.

It's a task.

Inside a busy group chat it can easily disappear underneath ten later messages.

A dedicated task could instead show:

Call equipment supplier — due Tuesday — assigned to Sarah — outstanding.

Conversations and tasks are both useful.

But they serve different purposes.

Separate scheduling from conversation too

Similarly:

“Physio has moved to Thursday at 2 pm.”

is communication.

But the appointment itself belongs in the calendar.

Good coordination means the information reaches the part of the system where people expect to find it later.

Build a participant profile for information that doesn't change every shift

Some information shouldn't need to be retyped into handovers repeatedly.

Depending on the participant and what they want workers to know, this may include:

• communication preferences
• routines
• support preferences
• important contacts
• mobility information
• relevant risks
• instructions
• health information relevant to support
• important documents

NDIS Commission guidance encourages a shared understanding of the participant's needs and preferences when workers join a support team.

The aim is for a new authorised worker to understand the participant's support arrangements without reconstructing everything from old messages.

Decide who needs access to what

Not everybody necessarily needs access to everything.

The participant may want:

• all workers to see the shared schedule
• particular workers to see particular care information
• family members included in coordination
• some information restricted
• specific information shared only with certain people

This should be intentional.

The NDIS Code of Conduct requires workers and providers to respect participant privacy, while OAIC guidance emphasises protecting personal information from unauthorised access and disclosure where the Australian Privacy Principles apply.

Avoid making one family member the entire system

In many families, one person gradually becomes the coordinator.

Every change goes through them.

Every worker messages them.

They remember who is available.

They forward information.

They remind people about appointments.

They know where the documents are.

It can work.

But it also creates a single point of failure.

If that person is busy, unavailable or simply forgets something, the rest of the support network may not have the same information.

A better system allows appropriate members of the support network to access what they need directly.

Use a simple structure

A coordinated support network should make these questions easy to answer:

Today

• Who is supporting me?
• What is happening?

Recently

• Has anything important changed?
• What happened during recent support?

Next

• What is coming up?
• What needs to be done?

Participant

• What do I need to know to provide support the way this person wants?

Important information

• Where are the relevant contacts, documents and care information?

If answering those questions means searching through several apps and asking three people, the system can probably be improved.

Where Neume fits

Neume is designed around a care group centred on the participant.

Instead of expecting families and independent workers to connect unrelated tools themselves, Neume brings core care coordination into one place.

This can include:

• a shared schedule
• care updates and handovers
• tasks
• participant information
• health information
• documents
• contacts
• care instructions
• group and direct communication
• emergency care information

The goal is straightforward:

Everyone shouldn't need to know everything — but the right people should be able to find what they need.