Why the provider is the anchor
Around every participant there's a team — the family, the support coordinator, the OT or behaviour support practitioner — but the provider is the one generating the day-to-day record. Shifts, incidents, medications, the handover: that's the spine everyone else builds on. So the provider is the natural anchor of a connected team, and the work of running one mostly comes down to letting that spine reach the right people, with consent, instead of trapping it in one system.
The good news is you don't reorganise anything to do it. A connected team isn't a new workflow bolted onto your week — it's the same records you already keep, reaching further. For the why beneath all this, see the pillar on the connected care team. This piece is the how.
The order to connect: highest-relief first
The family
Connect the family first — it's the highest-trust, highest-relief link. The family stops ringing the house for updates; you stop fielding the same questions on shift. Invite them by email from Aura OS; they accept in Compass and, from that moment, see shift briefs and appointments — and can revoke access any time. One invitation, accepted once.
The support coordinator
Bring the coordinator in before plan review, not during it. Evidence accumulates from the day the link is made, so a coordinator connected in July walks into a March plan review with eight months of dated record instead of a fortnight of reconstruction. They work in Pilot; the connection lets them pull your delivered hours, incidents and resolutions as cited evidence — with the family's consent.
The OT or behaviour support practitioner
Let the clinicians deliver into the record. When an OT or behaviour support practitioner signs a report in Scrive, it lands in your messages feed as a card, mapped to the participant — no forwarding chain, no version drift — and their strategies surface on the shift brief where the work happens.
What to put in place (it's lighter than you think)
Three things make a connected team run, and none of them is a project:
- Make the shift brief the hub. The handover your incoming worker reads is where the team converges: the family's notes on who the person is, the OT's strategies, the coordinator's goals all arrive there, written once each. Treat the brief as the single thing a worker has to open, and the rest follows.
- Set a consent norm, not a consent scramble. Decide up front that connections are invited openly and the family controls them. Because nothing is shared until both sides approve and access is logged, you never have to wonder whether sharing is allowed — the consent state is explicit and current.
- Write once, on purpose. The whole saving is in not re-keying. Capture the incident, the shift note, the medication once in Aura OS; let the connection carry the relevant parts outward rather than re-typing them into an email.
Running a connected team is mostly a decision: write each thing once, and let it reach the people who need it — with consent.
A connected week, from the provider's chair
Monday, an incident is logged and the investigation step opens — the coordinator can later pull it as evidence, already dated and sourced. Wednesday, the OT signs an updated behaviour-support plan in Scrive; its strategies appear on Thursday's shift brief without anyone forwarding a PDF. Friday, the family adds a note in Compass about a rough weekend coming up; the Saturday worker reads it on the brief before the shift starts. Nothing in that week was re-entered, and nothing moved outside the family's consent.
The common mistakes
What stalls a connected team
Treating it as all-or-nothing. You don't connect everyone at once. One link at a time, highest-relief first — the family — and the rest as you're ready. A team that waits for the "full rollout" never starts.
Keeping a parallel paper trail. If the brief is the hub, it has to be the hub. Running the connected record and a separate clipboard means doing both jobs and trusting neither.
Sharing without saying so. Connection earns trust only because it's consent-first. Invite openly, let the family hold the keys, and the family leans in rather than worrying about what's moving.
What it costs
Running a connected team on Clearline doesn't add a line to your software bill. Aura OS is flat $49 a month for Pro — never per-user — with an unlimited, audit-ready free tier; the family's app is free forever; the coordinator's solo tier is free. The connection itself is the platform doing what it's for. For the money side in full, see the hidden cost of disconnected NDIS systems.
Anchor your care team in a tap.
Run your houses as one team on Aura OS, then invite the family, the coordinator and the OT — with consent, on Clearline Connect. Flat $49/month, unlimited audit-ready free tier, Australian-hosted.
Questions
Where does a provider start?
The provider–family link — highest trust, highest relief. Invite the family by email from Aura OS; they accept in Compass and see shift briefs and appointments, with the right to revoke any time.
Does it add admin for support workers?
No — it removes it. Write each record once; the connection carries it to the family, the coordinator and the OT instead of three re-types. The shift brief becomes the hub.
Does everyone have to be on the same software?
Each role uses its own app — Compass, Pilot, Scrive — connected to the provider's Aura OS with consent. The Connect graph links them; connection is optional.
How long does a connection take?
A single invite. Email or scan a Connect QR; the request lands in their app, nothing is shared until both approve, and the link is live on acceptance.