The participant is the centre of their care.
One platform, one care team, one source of truth, with the family in control of consent.
The NDIS works through coordination. Families coordinate with providers. Support coordinators coordinate with families. Occupational therapists coordinate with everyone. Clearline Connect is the layer that lets the people working with the same participant share what they need to share, with the family deciding what flows and what doesn't.
Care that's fragmented.
Today's NDIS sector runs on workarounds. Support coordinators piece together evidence at plan review time from emails, calendar notes, and phone calls. SIL providers log compliance work that sits in spreadsheets nobody reads. Families chase updates from three different providers about one participant. OTs send report PDFs into the void.
The same information exists across all these systems. None of it flows.
What's missing isn't more software. It's connection.
One graph per participant.
Every participant in Clearline is the centre of their own care team graph. Family. Support coordinator. SIL provider. OT. Behavioural support practitioner. Each one is a node. Each connection between nodes is consented to, logged, and revocable.
When a new node joins the team, say a family signing up for Compass after six months with a provider, they can see the existing graph at a glance. Approve who stays. Decline who shouldn't. Connect, with the family's consent, to the people who already work with their participant.
This is different from how every other NDIS platform works. Others ship bilateral data-sharing agreements between providers and coordinators, one B2B agreement at a time. Clearline ships the graph itself. The participant is the anchor. Every node serves the participant.
One note. The whole care team.
The same shift note travelling every seat of the team with the family's consent: written once by the worker, seen by the family, joined by the OT's report, cited by the coordinator.
CONNECT ID · CLR-4391-MT
This is what "one connected NDIS" looks like in architecture terms. Four apps at the edges, Connect in the middle, every link bidirectional. The graph the previous section described is the data flowing across these lines.
Different data, different consent levels, different defaults.
Connect splits what gets shared into three tiers, each with its own consent rule. The defaults reflect the work everyone is already doing: identity is free, aggregate is default-approved, detail is opt-in.
Free and automatic for everyone in the graph.
Team awareness is essential. You can't coordinate with people you don't know about. Identity is shared the moment a connection is approved, no further consent needed.
Default-approved. Numbers, totals, scores, trends.
Aggregate data is how funding cases get made: how many hours, how many incidents, what's the training picture. Shared by default, can be unchecked when the family approves a connection.
Explicit opt-in only.
Detail records are where the sensitive content lives. Individual shift notes, full incident detail, training records. The family ticks each detail scope they're comfortable sharing. Nothing flows by default.
Identity is free because team awareness is essential. Aggregate is default-approved because it's how funding cases get made. Detail is opt-in because it's where the sensitive content lives. The three tiers map to how the NDIS sector already thinks about data, not a new framework imposed on top.
You decide, you control, you can change your mind.
Consent ownership depends on the participant. If the participant is an adult with capacity, they own consent for their own data. If they have a substitute decision-maker, such as a family member, a formal guardian or an attorney under power of attorney, that person owns consent through their Compass account.
If the participant isn't on Compass and doesn't have one yet, providers attest they have consent through their own intake processes. That fallback recognises the reality of the sector today; it doesn't change the principle.
Connections form when one side invites and the other approves. Both sides see the same connection in their apps. Either side can pause, revoke, or modify scopes at any time. Every data access is logged for the consent owner to see.
If a family revokes a provider's access, the provider sees a notice in their app, data flow stops, and the historical record stays preserved for audit but isn't re-accessible.
Every access, every time.
Three audit views, three audiences.
The consent owner sees a plain-English log of every access in their Compass account. Who accessed what, when, with one-click revocation from any log entry.
The provider or coordinator view will show what they've shared with whom, what other parties have read, and last-access timestamps.
For NDIA compliance audits, a per-participant data-flow report will be exportable on demand, in a standardised format, signed and immutable, ready to hand to a Privacy Commissioner.
Currently available in Compass for families. Expanded audit views for providers and exportable NDIA-format reports are part of upcoming releases.
How consent works, in plain English.
Who approves a connection?
Both sides. One side invites, the other approves, and the consent owner approves for the participant: the participant themselves if they're an adult with capacity, or their substitute decision-maker through Compass. Either side can pause or revoke at any time.
What can a connected provider see?
Identity from the moment the connection is approved. Aggregate numbers by default, which the family can switch off. Detail records, like individual shift notes, only where the family has opted in, scope by scope.
What happens when consent is revoked?
The provider sees a notice in their app, data flow stops, and the historical record stays preserved for audit but is not re-accessible.
Where is the data held?
Customer data is stored and processed in Australia. We use US sub-processors for narrow purposes, error reporting, payments and AI features, each named in the privacy policy.
Defensible by design.
Most NDIS software is a slice. Clearline connects the whole picture: a support coordinator's funding case backed by operational evidence from the providers delivering the supports, captured as it happens, with the participant's family in control of consent.
That's what "connected" actually means.