Who's actually on an NDIS care team
Strip away the org charts and every participant's support network has the same four seats:
- The provider and their workers — running the house, logging shifts, administering medications, managing incidents. The bulk of the day-to-day record starts here.
- The family or nominee — the people with the longest history and, under the NDIS, a central say in consent. Usually the last to hear and the first to worry.
- The support coordinator — at the centre of plan implementation, and once a year responsible for defending the participant's funding with evidence from everyone else's systems.
- The clinicians — the OT writing the FCA or AT report, the behaviour support practitioner, the allied health team. Their reports drive funding decisions and daily practice alike.
The participant sits in the middle. The roles around them change — workers come and go, coordinators hand over, OTs cycle in and out — but the participant's record should be the constant.
The disconnection tax
Here's how the same week looks when those four seats run on four disconnected systems. The OT finishes a functional capacity assessment and emails it to whoever's address she has; it sits in an inbox while the house keeps working to the old plan. The family asks how Tuesday went and gets an answer on Thursday. The support coordinator starts plan review by requesting twelve months of records from the provider — and rebuilds the year from emails, memory and a spreadsheet.
None of those people is doing a bad job. Each of them might even have good software. The information just stops at the edge of each tool, and the gaps get bridged by the most expensive integration layer in the sector: people re-typing things into other systems.
Everyone gives each role a better tool. The gap is the connection between them.
What "connected" actually means: three things
A connected care team isn't a group chat bolted onto a roster app. It cashes out as three concrete properties, and you can test any platform against them.
The team talks — and so do the tools
Information reaches the people who need it, across roles, without leaving the record. The provider's shift brief can reach the family. The OT's signed report lands in the provider's feed as a card, mapped to the participant — not as an attachment in someone's inbox. The coordinator pulls what the team already holds instead of requesting it.
The test
When something is written once, who else can see it without anyone re-typing it?
Everyone is seen, every record is confirmed
The family is part of the team, not outside it — they see what's happening and who has access. Records exchanged between parties are confirmed, not assumed: an invitation is accepted, a connection is approved, a handover is acknowledged. Nothing moves silently.
The test
Can the family see what's being shared about their participant — and would anyone notice if a record went nowhere?
The record proves it — and the participant's side controls it
Who did what is on the record: dated, sourced, exportable when the auditor or the planner asks. And control sits where the NDIS says it should — with the participant's side. Consent is granted per connection and can be revoked at any time, with every access logged.
The test
Could you produce the evidence for any day in the last year — and could the family cut off access today if they chose to?
Consent is the spine, not a checkbox
Who controls a connected record
Connection without consent is just surveillance with better UX. In a properly connected care team the participant's side holds the keys: the family approves each connection, sees what flows across it, and can revoke it at any time — and every cross-party access is logged where both sides can see it.
That's also what makes connection safe to adopt. A provider doesn't have to wonder whether sharing is allowed; the consent state is explicit, current and auditable.
A connected week, in practice
This is what the same week looks like when the team is connected. We'll use Clearline Connect as the worked example, because it's what we build — four apps, one for each seat at the table, linked by one Connect ID per account.
- The provider invites the family. From Aura OS, by email. The family accepts in Compass — and from that moment they can see shift briefs and appointments, see who has access, and revoke it any time.
- The shift brief reaches the family. The handover the incoming worker reads is the same brief the family can see — written once, acknowledged, on the record. "How was Tuesday?" gets answered on Tuesday.
- The OT's report lands where the work happens. When the OT signs an FCA in Scrive, it arrives in the provider's messages feed as a card mapped to the participant — no forwarding chain, no version drift.
- Plan review runs on the team's evidence. In Pilot, the coordinator pulls dated, source-attributed evidence from the connected team — hours delivered, incidents and resolutions, goal progress — instead of reconstructing the year from memory. The funding case cites its sources.
Notice what didn't happen in that week: no PDF attachments, no re-keying, no "can you resend that," and no one outside the consent boundary saw anything.
Running a connected care team: where to start
You don't connect a whole team in a day, and you don't need to. The order that works:
- Start with the provider–family link. It's the highest-trust, highest-relief connection — the family stops chasing and the provider stops fielding the same questions. One invitation, accepted once. (The full family-side picture: keeping the family in the loop.)
- Bring the coordinator in before plan review, not during it. Evidence accumulates from the day the connection is made. A coordinator connected in July walks into a March plan review with eight months of dated record.
- Let the clinicians deliver into the record. A report that lands in the provider's feed gets worked on the day it's signed, not the day someone finds the attachment.
- Keep the audit trail as the by-product, not the project. When the team works on one consented record, the evidence pack an auditor wants is what daily work already produced. That's the whole premise of the 60-second audit test.
For who actually gains from all this — and how it cashes out as an easier job, a truer record, real accountability and more sustainable supports — see what a connected care team means for the participant.
What this isn't
Two honest boundaries. First, a connected care team is not a client portal. A portal is a window into one provider's system, on the provider's terms; close the account and the family's view goes with it. A connected team gives each role its own workspace — the family's app is theirs, free, forever — and links the workspaces with consent.
Second, connection is optional by design. Each Clearline app works stand-alone, and a provider can run Aura OS for years without connecting anyone. The team gets more useful with each connection — but nothing breaks without one, and nobody is forced into the graph.
One participant. One care team. One record.
Four apps — for the provider, the family, the coordinator and the OT — connected with consent on Clearline Connect. Free to start, Australian-hosted.
Questions
What is a connected care team in the NDIS?
The people around one participant — the provider and their workers, the family or nominee, the support coordinator and the allied health clinicians — working on one shared, consented record instead of four disconnected systems.
Who controls what's shared?
The participant's side. The family approves each connection, sees who has access, and can revoke access at any time. Nothing moves silently — every exchange needs confirmation and every access is logged.
Does the family see everything the provider records?
No. Sharing is scoped to what each connection consents to — shift briefs and appointments, for example — and both sides can see what was shared. Consent is per-connection, not all-or-nothing.
Is this the same as a client portal?
No. A portal is a window into one provider's system, on the provider's terms. A connected care team gives each role its own app and links them with consent — each party owns their workspace, and the record flows between them.
What software connects an NDIS care team?
Clearline Connect links four apps around one participant: Aura OS for SIL providers, Compass for families, Pilot for support coordinators and Scrive for OTs. One Connect ID per account; every connection consented; Australian-hosted (Sydney).