Share and privacy
The group chat is not the current plan
A care-team group chat can work well when people can find the current agreed information and know what needs a reply. For a lasting change, confirm the decision, update the agreed reference, name who has accepted the next action and check that the people affected can access and understand it. A new app is not a requirement.
Here, 'current plan' means the agreed information people use for day-to-day support. It does not replace the NDIS funding plan, clinical instructions or a provider's records. Whether you use WhatsApp, another chat app, email or paper, the checks and three tools below can help without a Kinovo account.
- For:
- NDIS participants, chosen supporters, coordinators and workers sharing day-to-day support information
- Includes:
- Care-team update, current-picture note and chat agreement + printable PDF and editable text
- Time:
- 12 minute read
Published 5 September 2026 · Updated 23 October 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.
Choose a practical tool
Choose a care-team update, a current-picture note for someone joining, or a chat agreement to adapt together. Copy them here or download all three as a printable PDF or editable text. Use the prompts that help and add the detail your situation needs. No account is required.
- Copy the care-team update
- Copy the current-picture note
- Copy the chat agreement
- Keep the update and source in step
An update that needs confirming
Fictional example: Sam's worker asks whether a change to the morning routine still applies. A chat reply sounds different from the printed routine and the provider's handover. The next step is to ask the responsible person to resolve the conflict and confirm the current instruction, then update the agreed working copies. The worker should not have to choose an instruction by guessing which message sounds most recent.
Start with the system people actually use
Ask the participant how they want to be involved and what communication support they need. Then ask the people doing the work where they look before a shift, visit or appointment. A clearly dated pinned note may work for one team; another may need a paper handover, an approved provider system or a shared folder alongside the chat.
Agree where the current information will be kept, who will maintain each part and how changes will reach people using another system. The participant or family need not become the person who copies every professional's notes. Ask the provider or professional responsible for the source to confirm it and contribute their part.
The Commission's Working Together guide supports agreeing responsibilities, communication preferences and ways to keep the key points of conversations. It also recognises that participants can choose how much they want to be involved. Use that conversation to make the approach workable for your team.
Check whether people can use the current information
Try these checks with the people who need the information, including someone covering at short notice:
- Access: Can the intended person open the full relevant source where support happens? Check permissions, devices, connectivity, accessible formats and where paper is displayed. Agree an authorised alternative if access fails.
- Version clarity: Can a reader identify the source, version or reference, effective date and person who confirmed it? A recently forwarded screenshot may contain an old instruction.
- Decisions: Is the information a suggestion, an unresolved question or a confirmed decision? Record who made or confirmed the decision, within their role, and what still needs checking.
- Privacy: Who can read the chat, attachments or history, and who can see the paper copy? Check the actual audience rather than assuming everyone has the same access needs.
- Real use: Can someone find the current answer and explain the next step without searching an archive? If not, ask what is getting in the way before introducing another place to maintain.
If your team needs a place for the current picture and agreed next steps, explore the shared NDIS care-team workspace in Kinovo and compare it with the system you use now.
Turn a useful update into agreed work
The route depends on what changed:
- A late arrival or practical change today: contact the people affected through the channel they are using for that support. Check receipt when the arrangement depends on it.
- A lasting change to a routine or instruction: confirm it with the participant and the person responsible for that instruction, using the appropriate professional process. Record the current source and effective date, then tell the people affected where to find it.
- A task or decision: separate the proposed action from work someone has accepted. Record the next step, accepted owner, needed date or trigger and next check. If acceptance is still missing, leave that visible and name who is arranging it.
- A report, plan page or sensitive detail: agree the intended readers and suitable sharing method. A message pointing to an appropriately restricted file may be more useful than copying its contents to the whole group.
As a practical check, ask the relevant person to confirm the action or explain anything unclear. A read receipt, reaction, forwarded message or name on a list does not establish understanding, accepted responsibility or required training. Contact the provider about any training or handover needed before the work.
If the usual approach is not working
- Two instructions conflict, or a change is unconfirmed
- Identify the specific difference and contact the responsible provider or practitioner before the affected task. Keep the uncertainty visible; avoid silently rewriting a clinical instruction or treating a chat suggestion as approval. If the usual person is unavailable, use the provider's agreed alternative contact and ask what should happen while clarification is pending.
- Nobody has accepted the next step
- Ask the proposed owner whether they can take it on, what they need and when they can respond. If they cannot, agree another route with the people responsible. A forwarded request does not transfer responsibility, and a family member should not have to absorb unassigned work by default.
- The reply has not arrived
- Check whether the person is working, whether the request reached the right contact and what timing was actually agreed. At the agreed check date or relevant trigger, use the fallback contact route. If a support arrangement depends on the answer, contact the provider directly about that arrangement rather than waiting indefinitely in the chat.
- Someone cannot use the app or open the file
- Arrange an accessible alternative with them and the relevant provider: for example, a phone handover or a controlled paper or offline copy. Check that it is the current version and agree who updates it. They still need the information relevant to their work; not using the app should not make them responsible for reconstructing it.
An urgent safety concern needs the agreed immediate contact or emergency route. The NDIS Commission's reporting guidance says to call 000 if life may be at risk or there is an emergency involving critical harm or serious injury. A chat, scheduled update or high-priority label is not an arrangement for immediate response.
Use a care-team update when it helps
An update can bring confirmed changes, waiting information and accepted actions together. A weekly check may suit your team, or you may need a different rhythm. Communicate important changes when they need attention rather than saving them for the next scheduled note.
Use the prompts that help and add the detail needed to understand the work. Point to the full current source where appropriate. Keep professional records in the systems that are responsible for them; avoid copying the same report into every channel simply to fill out an update.
Copyable care-team update
Use these prompts when support information changes or at a check-in rhythm that suits your team. Add the context needed so people can understand and act.
Update prepared on / by / intended readers: ___
What changed and when / participant's view or decision: ___
Current confirmed information / source title, version and effective date / confirmed by: ___
Still uncertain or waiting / who is checking / agreed contact or fallback: ___
Next action / person who accepted it, or not yet agreed / needed date or trigger / next check: ___
Where intended readers can open the full source / any access gap / handover checked with: ___
Relevant detail or additional context needed: ___
Check the participant's sharing choices and the current source before sending. Communicate important changes when they need attention; do not wait for a scheduled update. An urgent concern needs the agreed immediate contact route.
Keep the update and source in step
Confirm changes with the participant and person responsible for the source, using the appropriate process. The update should point to the agreed current version and leave unresolved questions visible.
- Identify the source, version or reference and effective date; a newly sent file is not necessarily a new instruction.
- Name the person who accepted each next action and the next check. If acceptance is missing, record who is arranging it.
- Check intended readers can access and understand the relevant information. Arrange a suitable alternative where needed.
- Replace superseded working copies, retain required records in their proper system and tell the people affected what changed.
When someone joins or leaves the team
Give a new worker or covering person a current briefing for their role, an opportunity to ask questions and access to the relevant source. Include what is still uncertain and who is following it up. The person should not have to infer the current position from old conversations.
Before adding someone to the chat, confirm the participant's sharing choices and the person's role. Check the history, attachments, personal contact details and device access they may receive. Review membership and linked file permissions when someone leaves, while preserving records that need to be retained.
History access depends on the app and settings. For example, WhatsApp's Group Message History guidance describes sharing recent messages with new members. Check the options available to your team and agree any history sharing before using them; do not assume a new member can see everything or nothing.
Copyable current-picture note
Adapt this for the person's role and agreed sharing. Ask the people responsible for the source information to help prepare and confirm it. This note supports a handover; it does not replace full instructions, induction or training.
Subject: Current information for [name or agreed reference] - checked [date]
Hi [name],
You are supporting [name] with [agreed work / shift or visit]. Their current priorities and communication preferences relevant to this work are [details].
Current confirmed information: [relevant summary / source title, version and effective date / confirmed by whom]. Full source and agreed access: [location or method].
What changed recently: [change and effective date / no relevant change known]. Still uncertain or waiting: [issue, who is checking and agreed contact or fallback].
Next action and acceptance: [action / accepted by whom and agreed date or trigger / acceptance still needed / next check]. Please confirm you can open the current source and tell [contact] if anything is unclear or conflicts with your instructions or training before the affected work.
For an urgent concern, use [agreed immediate contact or emergency route]. Do not wait for a reply to this note or chat.
Thanks, [name / role]
Copyable chat agreement
Agree this with the participant, using the decision support they need, and the people doing the work. Adapt the responsibilities, availability and alternatives to your actual arrangements.
Purpose and intended members: [what we use this chat for / names or roles agreed with the participant].
Current agreed information is kept at [place / source or version]. [People or roles] maintain their parts. Proposed or unconfirmed changes stay labelled until the responsible person confirms them.
An action is accepted when [how the person confirms]. We record [next step / accepted owner or not yet agreed / date or trigger / next check] at [place].
Availability and missed replies: [usual working/contact arrangements]. If a response is needed and does not arrive by [agreed point or trigger], use [agreed fallback]. For someone not using this chat, [agreed accessible alternative and who keeps it current].
Sharing and membership: [person or role] reviews members, history sharing and linked-file access with the participant's choices and relevant authority. Check before sharing reports, plan pages, images or other sensitive information. Explain any legal obligation that affects an agreed restriction.
Urgent concerns use [agreed immediate contact or emergency route]. A chat message, read receipt or priority label is not a promise of immediate response.
Review this agreement when the work, participant's choices or team changes. Providers keep the professional records they are responsible for in their appropriate systems.
Keep privacy and authority clear
Involve the participant in deciding what is shared and who is involved, with the support they need. A chosen supporter can help express a decision; where someone else has authority to decide, check its scope. Being a family member, chat administrator or Kinovo Team leader does not itself give someone representative authority.
Where an organisation relies on consent, the OAIC's consent guidance explains that consent should be informed, voluntary, current and specific. Discuss recipients, purpose and the practical consequences of declining or changing a sharing arrangement. Consent is not the only possible lawful basis for information handling, so ask about any obligation affecting a restriction you request.
The NDIS Code of Conduct includes respect for privacy and applies to registered and unregistered NDIS providers and workers. Ask providers which communication methods and records processes they can use. An app's encryption alone does not settle whether the audience or handling is appropriate.
The OAIC's information-security guide explains broader safeguards such as access controls and protecting information on devices and in transit. Check recipients, links, lock-screen previews and shared devices as part of your practical sharing arrangements.
Messages can also be copied outside the original group. WhatsApp's privacy policy explains that recipients may capture or share information. Removing a member, changing a file's access or deleting a message cannot be relied on to retrieve copies already saved or forwarded.
Sending your own NDIS plan copy is separate from access to NDIA-held information. The NDIA's plan-sharing guide explains its provider access arrangements. Its consent guidance separately addresses permission for specified actions. Joining a chat or Kinovo care team does not change those permissions.
For the fuller sharing decision, use who should see my NDIS plan.
Providers remain responsible for their records
Agree with each provider what belongs in its formal record and who records an important decision or change there. A family update, pinned note or Kinovo discussion should not be treated as automatically replacing clinical, incident or other professional records. Remove superseded working copies from use without deleting history that must be retained.
Where the core information-management requirements apply, the Commission's Practice Standards and core information-management guidance address accurate, current and confidential participant information and appropriate records processes. The applicable requirements depend on the registered provider's supports and registration; this checklist is a practical aid, not a substitute for them.
Check whether the approach works in practice
Ask someone who missed the last conversation to find the current source and explain their next step. If they cannot, fix the specific gap: clarify the version, resolve a conflict, arrange access, confirm who accepted the work or agree another contact route. Review again when the work, sharing choices or team changes. A new platform is only useful if the people involved can use and maintain it.
How Kinovo can help alongside the conversations
Kinovo can keep agreed goals, accepted tasks, relevant support information and shared files connected. Use a care-team Messages topic for the discussion and link the relevant goal, task or document so people can return to the work. Confirm who has accepted an action and keep the source current; a message does not do that by itself.
Check each conversation's audience separately from who receives an alert, and review document visibility too. Restricted conversations can include Team leader oversight and retained creator or owner access. Changing who is included can change access to the conversation history. Software permissions do not confer authority to make decisions for the participant.
Kinovo does not provide clinical instructions, replace provider records or monitor a chat for urgent response.
A founder observation
The people supporting my sister each held useful information: an emailed report, a phone conversation, an update in a message thread. The work was bringing those pieces together.
- Callum Cruikshank, founder of Kinovo. More about why I started Kinovo.
To put the current files and outstanding requests in order, use the document index and sharing checklist.
If you are choosing where the current information should live, use the care coordination app comparison checklist to compare chat, folders, shared lists and workspaces.
Official guidance checked for this resource
Sources checked on 23 October 2026. The checks and templates are practical coordination suggestions, not NDIA rules for group chats, prescribed forms or an independent professional review. Follow the participant's choices, relevant authority and applicable provider processes.
Keep the discussion connected to the current work
Kinovo can bring agreed goals, accepted tasks, relevant support information and shared files together for your invited care team. Link a Messages topic to the work, check its audience and keep the source current. Team leader oversight and document permissions still apply.
You can keep using this resource without an account. Set up or join a care team when you are ready.
FAQ
Can an NDIS care team use WhatsApp or another group chat?
A group chat can be useful where the participant's choices, actual audience, provider policies and relevant obligations support its use. Agree where current information is kept, how changes are confirmed and how people accept actions. Agree the channel with the provider; the app name alone does not settle privacy or recordkeeping requirements.
Does every chat update need to be copied into another system?
No. Agree which information needs to remain findable or be recorded by the responsible provider. A late-arrival message and a lasting change to a support instruction have different needs. Keep required professional records in their proper system and use a current summary or pointer where it helps.
Does a read receipt mean someone has accepted a task?
Do not treat it as acceptance. Ask the person to confirm the work they can take on, the timing and anything they need before proceeding. Record unresolved ownership and who is arranging the next step. Reading a message also does not establish understanding or required training.
What if the chat and the written instruction disagree?
Identify the conflict and contact the responsible provider or practitioner before the affected work. Keep the uncertainty visible and ask which source is current. Use the agreed alternative contact if needed, and the immediate or emergency route for an urgent safety concern rather than waiting in the chat.
Who decides who joins the care-team chat?
Involve the participant with the support they need and check any representative's authority. Agree membership, what history or attachments may be shared and who reviews access when the team changes. A family relationship, chat administrator role or Kinovo Team leader role does not itself grant representative authority.
How often should we update the current picture?
Use a check-in rhythm that suits the work; weekly is one option. Communicate an important change when it needs attention, update the agreed current source and tell the people affected. Do not wait for a scheduled note to address an urgent issue or a change relevant to the next support.
What if someone does not use the chat or cannot open the file?
Agree an accessible alternative with the person and relevant provider, such as a phone handover or controlled paper or offline copy. Confirm the source and version, who keeps it current and how changes reach them. They should not have to reconstruct the information from other people's messages.
Does joining the chat or Kinovo give someone NDIA portal access?
No. Chat membership, Kinovo permissions, NDIA provider access and authority to act are separate arrangements. Check each through the relevant process. A document link or alert also does not automatically make its contents available to everyone who sees the message.
Disclaimer
General coordination information, not individual clinical, legal, privacy or NDIS funding advice. Follow confirmed professional instructions, applicable provider processes and agreed immediate or emergency contact arrangements.
Related resources
Who should see my NDIS plan (and who should not)
Read resourceWhat to send your new OT before the first appointment
Read resourceSupport coordinator on leave: who to contact and what to hand over
Read resourceCare Instructions for NDIS Support Workers: Keep the Current Version Easy to Find
Read resource