Share and privacy
The group chat is not the current plan
A family WhatsApp can move a Saturday. It cannot be the current NDIS plan, the current instruction, or the place a new worker has to scroll.
This page is a split: what belongs in a thread, and what must still be findable when someone new joins. Use it on its own. Kinovo is optional at the end.
This is not “delete the group.” It is not “WhatsApp is illegal.” Providers may already be asked to keep formal records out of consumer apps. Families still run the real care team in Messenger, SMS and a chat named after the person at the centre. Both can be true.
- For:
- Participants, families, nominees, Team leaders, support coordinators, support workers
- Includes:
- what belongs in a thread, what must be findable, a copyable current-picture note, a short group-chat rule
- Time:
- about eight minutes to read
Published 5 September 2026 · Updated 8 September 2026
Written by Callum Cruikshank — Founder of Kinovo
Callum draws on his family's lived experience of coordinating support. These resources offer practical coordination ideas, not clinical, legal or NDIS funding advice. No independent clinical review is claimed.
Saturday starts in the thread.
Mum asks who is coming at two. A worker says they are running late. Someone drops a photo of the new hoist sling. An aunt asks whether the plan covers extra hours. The coordinator is not in this chat. Last month’s “please don’t use the back door” is 400 messages up. The new worker starts Monday and is not in the group yet.
The team is not careless. The current picture is in a scroll.
A thread is good at now. It is bad at still. “Still” is the instruction that has to be true when a different person walks in. “Still” is the latest document, the owner of the next step, and who is allowed to see the budget page. None of that lives reliably at the bottom of a Saturday chat.
What this page is not
This is not a ban.
Consumer messaging apps are how a lot of families keep a week moving. A text that says “use the side gate, the dog is in the front” is often the right tool for the next twenty minutes.
This page does not say:
- that WhatsApp, Messenger, SMS or email is unlawful
- that the NDIS has banned family group chats
- that a provider who messages you is automatically doing the wrong thing
- that you should move every hello into software
Provider organisations have their own communication, privacy and record rules. Follow those where they apply. Official sharing of plan information still sits with the participant or nominee and the NDIA process. A group chat is not that process.
If someone may be unsafe, do not wait for a thread to be read. Use the agreed emergency or safeguarding channel.
Why the thread keeps becoming the plan
It is already on everyone’s phone.
The people who actually show up are in it. The people with a formal system often are not. A decision gets made in the chat because that is where the question was asked. By Thursday the decision is treated as the plan, even though the coordinator, the new worker and next month’s casual have never seen it.
Three things then go missing:
- The current version. The latest instruction is the one that was typed last, not the one that is still true.
- The audience. A chat made for family now holds a budget question, a behaviour note and a worker’s personal number.
- The new person. Adding them to a 14-month thread is not an induction. It is a pile.
The cost is paid by whoever has to reconstruct the picture. That is usually the person who checks their phone.
What belongs in a thread
Use the thread for movement, not for memory.
Good in a chat:
- Who is coming today, and when
- Running late, door code change for this shift only, “please bring the spare key”
- A yes or no that has to happen before this afternoon
- “Can you call me”
- Thanks, photos the family has agreed can sit here, the ordinary warmth that keeps people coming back
A thread earns its keep when the message will be useless next week.
What must be findable when a new person joins
Findable means a new worker, a covering coordinator, or an OT on Thursday can get the current piece without reading the archive.
These do not belong only in a scroll:
- The current practical instruction — transfers, meals, communication, what not to do
- Who is at the centre this month, and who the family contact is
- What matters now — the live goal or problem, not the whole plan
- What is waiting — report, quote, booking, a decision
- Who owns that next step
- The latest labelled document
- Who is allowed to see which file
If a new person would have to ask “is this still true,” it is not findable enough.
The test is simple. Imagine the most useful person in the chat is on leave. Could the next person still find the current instruction without a briefing call? If not, the thread is holding something it cannot hold.
Thread versus findable
| Situation | Thread | Findable place |
|---|---|---|
| Worker is ten minutes late | Yes | No |
| New sling is in the cupboard on the left | Once, to the people on today | Current instruction, dated |
| “Don’t use the back door anymore” | Fine as an alert | Update the standing instruction the same day |
| Who is paying this extra hour | No | Plan-management / coordinator conversation, not the family-and-workers chat |
| Saturday roster confirmation | Yes | Provider roster stays in the provider system |
| Latest OT letter | Do not attach here “for everyone” | Labelled document, shared with the people who need that file |
| A new worker starts Monday | “Welcome, see you at two” | Current picture they can open before they arrive |
| A disagreement about the plan | Not in a mixed family-and-worker chat | Person with authority, then a short update to the people who must act |
If you send the standing instruction only in the thread, the thread is now the record. That is the failure mode.
Who should be in the chat
Smaller is safer.
A chat that includes every aunt, every worker from every provider, the coordinator, and the plan manager is not a care team. It is a forwarding list.
Split by job:
- Today’s shift chat — the people in the house or on the road today. Short life. Practical only.
- Family coordination chat — the people the participant has agreed may help decide. Still not the home of the plan PDF.
- Provider or coordinator channel — the official or agreed professional path. Do not copy those messages back into the family thread “for visibility.”
Do not add a new worker to a long family history as a shortcut. They need the current instruction, not last Christmas.
Do not add a person because it feels rude to leave them out. Access is not politeness. The participant or authorised decision-maker chooses who hears what. A family member is not automatically entitled to the worker chat, and a worker is not automatically entitled to the family chat.
If you need the longer judgement on who sees the plan itself, use the companion page once it is live: who should see my NDIS plan.
What not to drop in the group
Do not paste the plan because it is the file you have.
Leave out of a mixed chat:
- The NDIS plan, budget pages, or a photo of a plan page
- Diagnosis essays, old behaviour reports, hospital discharge summaries
- Other people’s private numbers shared “so everyone has them”
- Arguments about providers, funding, or family decisions
- Passwords, portal logins, gate codes that should not live in a 20-person history
- Clinical detail a worker does not need for this shift
- Anything the participant has not agreed this group may see
A photo of a document in a chat is still a copy. It will be screenshotted. It will still be there when that worker has left.
If a provider’s policy says certain information must not travel on a consumer app, follow that policy. The family thread does not override it.
When a new person joins
Do not send them the group and wish them luck. Send a current picture. Four fields. One screen.
- 1. Who they will meet
- Name the person uses. Who will be in the house. How to communicate on a first shift or visit.
- 2. What is current this week
- The instruction that would change how they walk in. If nothing special is current, write that.
- 3. What is waiting that involves them
- Only their next step. Not the whole team’s backlog.
- 4. Where the standing information sits
- One place or one labelled file. Not “it’s in the chat somewhere.”
Then, if they need a thread at all, add them to the smallest chat that matches the job. Welcome them there. Do not ask them to scroll back to March.
Copyable current-picture note
Paste this to a new worker, covering person, or anyone being added. Delete the lines that do not apply. Do not attach the group history.
Subject: Before you start — current picture for [first name]
Hi [name],
You are with [first name] from [day / date]. This is the current picture so you do not have to reconstruct it from a group chat.
Who you will meet
[First name]. Communication: [one line]. In the house / session: [who].
What is current this week
[Standing instruction that still applies.]
[Anything that changed this week.]
If nothing extra: “No special change this week — please ask on the day if you are unsure.”
Your next step only
[What they own. Or “run the shift as briefed; no extra follow-up.”]
Where the standing information sits
[One file, one page, one workspace link, or “held by [name]”.]
Please do not look for this in the family thread. If something in this note is wrong, reply here so we can correct the current picture — not a side comment in the group.
Thanks,
[Your name]
[Role]
Send it before the first shift, not after they have already guessed.
Copyable group-chat rule
Pin this, or send it once when the chat is created. Short on purpose.
This chat is for today: who is coming, running late, and anything that only matters this shift.
It is not the current plan, the current instruction, or the place for budget, reports or family decisions.
If an instruction has changed for good, we will update the standing picture as well as saying it here.
New people get a current-picture note. We do not add them to months of history instead.
If someone may be unsafe, do not wait for this chat. Use [agreed emergency channel].
If the chat cannot live with that rule, the chat is doing two jobs. Split it.
A weekly five-line update beats a 200-message catch-up
Once a week, write the picture down outside the scroll.
- What changed
- What is current now
- What is waiting
- Who owns the next step
- Where the latest document is
That update can live in email, on paper, or in a shared workspace. The form matters less than the habit. The care-team coordination guide is the longer version of the same idea. The Care Team Clarity Starter Pack has a one-page current-picture worksheet if you want it on paper first.
Do not paste the weekly update into three different chats “so everyone sees it.” One copy. The right people. Then a short pointer for anyone who only needed to know that Saturday moved.
What to tell support workers
Workers should not have to join a family history to do their job.
Share with a support worker:
- The current routine and preferences that change the shift
- Do / do not that is still true
- Who to call, and the emergency path
- Anything waiting that is actually theirs
Do not share, unless the participant has agreed and the job needs it:
- The full plan
- Family conflict
- Other providers’ notes
- The coordinator’s inbox
If their organisation already has a shift-handover system, use that for rostered work. The family thread is not a second roster. The family current picture is the piece their system often never sees.
If the current picture needs a home that is not the thread
The notes above work without new software. A pinned rule and a current-picture message already remove most of the reconstruction.
A shared care-team workspace is useful when the same picture has to survive a new worker, a covering coordinator, and a family member who was not in Saturday’s chat. The thread can keep moving the day. The workspace holds what must still be true tomorrow.
Kinovo is built for that split. It is not a general chat app and it is not a WhatsApp replacement. A care team workspace sits around one person. The Team leader invites people; a request to join does not open the door by itself. Messages stay client-scoped — attached to that person and, when useful, to a goal or task — instead of sitting in a mixed social thread.
What must remain findable can live as a current priority on the Dashboard, a Care Protocol for the standing instruction, a task with one owner when something is waiting, and a document with its own visibility so the budget page and the Saturday routine do not travel together. A professional can open only the client workspaces they have been invited to. They can answer a short request without turning the family chat into their inbox.
Kinovo does not replace a provider’s roster, a clinician’s record, or an emergency number. It does not need to hold every hello. You can keep the Saturday thread and still give Monday’s new worker a current picture they can find.
- Adding Care Protocols
- How document visibility works
- What Kinovo is and who it is for
- What Kinovo should and should not be used for
- How to keep an NDIS care team on the same page
- NDIS care-team setup checklist
- How support coordinators can reduce chasing without adding more admin
- Care Team Clarity Starter Pack
- What to send the new OT so you are not the briefing
- Support coordinator on leave: who to contact and what to hand over
Full MVP access is free for a limited time. No payment card required.
Official guidance
Use these sources for current communication, consent and provider-conduct information. The split on this page is practical coordination, not an NDIA rule about which app to use.
FAQ
Is a family WhatsApp group allowed for NDIS support?
This page does not ban family group chats and does not call them illegal. Families use them because they work for today. The problem is using the same thread as the current plan, the current instruction, and the induction pack for a new worker.
How should I share NDIS information with support workers?
Share the smallest useful set for the shift or visit: current instruction, who to call, what has changed this week. Do not drop the full plan into a mixed chat. If their organisation has a handover system, use it for rostered work and keep the family current picture somewhere they can actually find.
Should the support coordinator be in the family chat?
Only if that is an agreed, narrow channel and everyone in the chat should see those messages. A coordinator does not need Saturday running-late notes. Family decisions do not need every worker as a witness. Split by job.
What is a care team communication app for, if we already have a group chat?
A group chat moves the day. A coordination workspace is for the picture that must still be true when a new person joins: current priority, standing instruction, owner of the next step, latest document, deliberate access. Kinovo is designed for that second job. It is not a general chat replacement.
Do we have to stop using Messenger if we use Kinovo?
No. Keep the thread for today. Put standing instructions, waiting work and labelled files where a new person can open them without scrolling. Use each tool for the job it can do.
Disclaimer
This resource provides general coordination information only. It is not legal, clinical, privacy, safeguarding, financial or NDIS funding advice. It does not replace a provider’s communication policy, official NDIA consent processes, or agreed emergency channels.