NDIS support coordinator platform

What should a support coordination platform let me do?

Start with the participant's goals and the particular assistance they have requested. Help them describe support needs, compare suitable workers and keep track of the tasks they have authorised. The participant chooses the worker; coordinator access does not make that choice for them.

NableU's support coordination tools use explicit, scoped participant permissions. Access to one area does not automatically give access to private messages, My Manual or every record. Review the scope, expiry and current access before acting.

What support coordinators can do

• See participant relationships that have been explicitly delegated.
• Work with profile summaries, support needs, jobs, sessions, messages, notes or billing only when that area is authorised.
• Track open coordination tasks, evidence records and unread messages.
• Communicate with managed participants inside the correct relationship context.
• Request additional scoped access with a reason and expiry instead of relying on broad standing access.

How the experience should feel

The coordinator is a distinct actor, not a worker mode and not a substitute participant account. The Dashboard is compact and relationship-led. Each participant view makes visible, private and not-authorised areas unmistakable, so an unavailable control does not look like missing data or a system fault.

The interface should show whose decision is required, what scope has been granted and when that access ends. Participant preferences and permissions remain visible at the point where an action is attempted.

Permission boundaries

Shadowing a participant profile never transfers ownership. Messages, billing, private notes and My Manual fields may each have different permissions. Support access does not imply permission to inspect unrelated personal information. Every sensitive access request needs a named scope, purpose, participant decision and expiry.

A typical flow

1. Open a participant relationship that has been delegated.
2. Review the approved scope and current coordination tasks.
3. Act only within visible authorised areas.
4. Request a specific additional permission when genuinely needed.
5. Return control to the participant and let temporary access expire.

Current stage

NableU is an early release before version 1.0. Participant-controlled delegation and scoped coordination workflows are implemented, with access determined by the participant’s permissions and the current release. This is not blanket access to a participant’s private information. Real-user testing and operational review continue; implemented software does not by itself establish compliance or readiness for every support setting.