Professional workflow
How Support Coordinators Can Reduce Chasing Without Adding More Admin
Turn reports, decisions and provider follow-ups into visible work with an owner, waiting reason and next step—without recreating your case notes in another system.
Published 30 June 2026 · Updated 6 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.
Support coordinators rarely lose time because they forgot that a report matters. They lose time reconstructing where the request went, who last replied, whether the family decided, what the provider is waiting on and which attachment is current.
The five questions that stop a follow-up becoming a chase
Before sending or recording a request, make sure the person receiving it can answer these five questions without searching another email thread.
- What exactly needs to happen?
- Who owns the response or next step?
- When is it needed, or what event triggers it?
- Why does it matter to the participant or current goal?
- What does a useful response or completed outcome look like?
A low-admin system for clear requests
Step 1
Capture only the coordination layer
Record the shared action, owner, date, waiting reason and relevant file. Keep clinical notes, billable case notes and internal provider records in their proper systems.
Step 2
Give one person clear ownership
Several people can contribute, but one person should own the next response. If ownership changes, update it rather than leaving both people assuming the other will act.
Step 3
Treat waiting as useful information
Write what the item is waiting on, who is expected to respond and when it should be checked again. Waiting is a real state, not a failure.
Step 4
Ask for a specific response
Make it easy to answer: upload the final report, choose one of three options, confirm the expected date, review the attached instruction or state what is blocking progress.
Step 5
Close the loop
When a response arrives, mark it ready for review, record the outcome and close the action. Otherwise completed work keeps resurfacing as noise.
Make the next response obvious
The right-hand examples are not longer for the sake of it. Each one removes a decision the recipient would otherwise have to make before responding.
| Instead of | Send or record |
|---|---|
| Following up the OT report | Dr Emily Chen to upload Sophie's final wheelchair assessment by 24 July. Please include final seating measurements. Needed for the plan reassessment evidence pack. |
| Any update on the quote? | Provider admin to confirm the supplier's expected quote date by Friday. If no date is available, reply with the current blocker. |
| Can the family decide? | Claire to confirm whether the family wants to proceed with the equipment trial by Wednesday: proceed, do not proceed, or arrange a call. |
| Please review this | Marcus to review the updated transfer instruction before Monday and respond: current, changes needed, or not within my role to confirm. |
Copyable provider or professional request
Keep the context short and put the expected response before the background.
Subject: Action needed for [participant] — [short action]
Hi [name],
Could you please [specific action or response] by [date or trigger]?
A useful response is:
[upload / confirmation / option / blocker]
Why this matters:
[one or two sentences linked to the participant's current goal or decision]
Relevant file or context:
[link or document name]
Thanks,
[name]
A 15-minute weekly triage
Act now
- Responses ready for your review.
- Overdue work you personally own.
- A family decision blocking the next step.
- A newly identified risk that belongs in the appropriate urgent or professional channel.
Recover momentum
- Waiting items with no next check date.
- Work assigned to someone who has left the team.
- Requests that are too vague to answer.
- Documents received but not connected to the relevant goal or action.
Close noise
- Completed actions still showing as open.
- Requests that are no longer needed.
- Superseded files presented as current.
- Old access that should be reviewed or removed.
For provider intake, use the therapy waitlist tracker to distinguish an enquiry from a confirmed place.
What Kinovo should not ask you to duplicate
A shared coordination workspace is useful only when the contribution stays short and practical.
- Full clinical notes or assessment records.
- Internal provider case notes and compliance records.
- Invoices, claims or financial reconciliation beyond routing an action and document.
- Information unrelated to the shared participant outcome.
- Urgent or emergency communication that belongs in an agreed immediate-response channel.
Official NDIS guidance
Use these sources for current role and consent information. The coordination method in this guide is practical Kinovo guidance, not an NDIA requirement.
From template to live workspace
This is what Kinovo keeps live inside a shared care-team workspace.
Kinovo's professional dashboard surfaces the assigned, due and waiting work that needs you across invited client workspaces. Open one action to see its goal, current document, owner and care-team context.
Full MVP access is free for a limited time. No payment card required.
FAQ
How can a support coordinator reduce repeated provider follow-up?
Give every material request one owner, a needed-by date or trigger, a clear expected response and a visible waiting reason. Review waiting work on a regular rhythm and close it when the response is received.
Does Kinovo replace support coordination case notes?
No. Kinovo holds the shared coordination layer: current goals, assigned actions, waiting reasons, relevant documents and practical updates. Keep clinical, billable and internal provider records in the appropriate system.
Should support coordinators invite every provider?
No. Invite people when they need shared context or have a useful contribution to make. Access should reflect participant choice, consent, role and current involvement.
What should happen when a request is waiting?
Record what it is waiting on, who is expected to respond and when it should be checked again. Do not keep sending reminders without changing the information or next step.
Disclaimer
This resource provides general information only. It is not legal, clinical, financial, privacy or NDIS plan management advice. Follow current NDIA guidance, participant consent, professional obligations and agreed emergency or safeguarding processes.
Related resources
NDIS Plan Reassessment Evidence Checklist and Tracker
Read resourceNDIS Care Team Setup Checklist
Read resourceWho should see my NDIS plan (and who should not)
Read resourceHow to ask an allied-health clinician for a plan-review report
Read resourceChanging support coordinator: what should be in the handover
Read resource