NDIS Support Coordination Documentation: Meeting Compliance While Managing a Full Caseload

What the NDIS Quality and Safeguards Commission Expects

The NDIS Quality and Safeguards Commission sets the compliance framework for all registered NDIS providers, including support coordination services. The NDIS Practice Standards (specifically the Core Module and the Provision of Supports module) require:

• Records of all supports delivered: Every interaction with or on behalf of a participant must be documented, including the date, duration, nature of the contact, and outcomes.
• Evidence of person-centred practice: Documentation must reflect that the participant's goals, preferences, and choices are driving service delivery.
• Progress reporting: Regular documentation of progress towards NDIS plan goals, including barriers encountered and strategies to address them.
• Risk management documentation: Identified risks and the actions taken to mitigate them.
• Incident reporting: Any incidents, near misses, or safeguarding concerns documented and reported according to the NDIS Incident Management Rules.
• Service agreements: Written agreements between the participant (or their nominee) and the provider, outlining the supports to be delivered.

During compliance audits, the Commission reviews case files for completeness, consistency, and evidence that supports were delivered as claimed. Gaps in documentation can result in findings of non-compliance, payment recovery, or conditions placed on registration.

The Support Coordination Documentation Framework

1. Contact Notes (Every Interaction)

Every contact with or on behalf of a participant requires a case note. This includes:

• Phone calls (to participants, families, service providers, government agencies)
• Emails (summarise key content rather than filing the email alone)
• Face-to-face meetings
• Service coordination activities (researching providers, making referrals, following up on waitlists)
• Attendance at planning meetings, case conferences, or reviews
• Advocacy activities

A compliant contact note includes:

• Date and time of the interaction
• Duration (important for billing accuracy)
• Participants in the interaction (who was contacted or present)
• Purpose of the contact (linked to NDIS plan goal where possible)
• Content of the interaction (what was discussed, what information was shared, what was agreed)
• Outcome and next steps (what will happen as a result of this contact, and when)
• NDIS plan goal reference (which goal does this activity support)

2. Progress Notes (Regular Updates)

Separate from individual contact notes, progress notes provide periodic summaries of a participant's status, typically monthly or quarterly. These should cover:

• Progress towards each NDIS plan goal (using measurable indicators where possible)
• Supports currently in place and their effectiveness
• Changes in the participant's circumstances, needs, or preferences
• Barriers encountered and strategies implemented or planned
• Upcoming actions and priorities

Progress notes form the basis of plan review reports and should be written with the awareness that an NDIA planner will read them when determining whether to continue, increase, or reduce support coordination funding.

3. Plan Review Evidence

The plan review is the highest-stakes document in support coordination. It determines whether the participant's coordination funding continues, and at what level. The plan review report should demonstrate:

• Goal progress: What was achieved during the plan period, with specific examples and evidence.
• Coordination value: What would not have happened without coordination? This is the key question NDIA planners ask.
• Complexity evidence: For Specialist Support Coordination, document the complexity of the participant's situation (multiple service providers, high-risk behaviours, housing instability, justice system involvement, etc.).
• Future need: Why ongoing coordination is required, linked to specific remaining or emerging needs.
• Capacity building evidence: How has the participant or their network increased their ability to manage supports independently? If independence has not increased, explain why (e.g., the nature of the disability, complexity of the service system, cognitive limitations).

The most common reason for reduced coordination funding at plan review is insufficient evidence that coordination made a difference. If your case notes throughout the plan period are thorough, compiling the review report is straightforward — you are summarising existing records rather than trying to reconstruct twelve months of activity from memory.

4. Service Agreements

Every participant should have a current service agreement that outlines:

• The type of support coordination provided (Support Coordination or Specialist Support Coordination)
• The participant's goals as stated in their NDIS plan
• The activities the coordinator will undertake
• The frequency and mode of contact
• Fees and billing arrangements (aligned with the NDIS Pricing Arrangements)
• Cancellation and exit terms
• Consent and information sharing arrangements

Service agreements must be reviewed and updated at each new NDIS plan.

The Caseload Challenge

The fundamental tension in support coordination documentation is volume. A coordinator managing 40 participants might make 15 to 20 contacts per day — phone calls, emails, meetings, and follow-up activities. Each of these requires a case note. At five minutes per note, that is 75 to 100 minutes of documentation daily, assuming uninterrupted writing time.

In practice, coordinators rarely have uninterrupted writing time. The day is a continuous flow of calls, travel, meetings, and ad-hoc problem-solving. Documentation gets pushed to the end of the day or the end of the week, at which point the specific details of individual interactions have been lost.

This is where mobile documentation workflows become essential. Rather than writing full case notes at a desk at 5pm, the most efficient approach is capturing the core information immediately after each interaction.

The 60-90 Second Dictation Workflow

After each phone call, meeting, or community visit, dictate a brief case note covering the essential elements:

• Who you spoke with and when
• What was discussed and decided
• What the next steps are
• Which NDIS plan goal this supports

A 60 to 90 second dictation captures these elements while they are fresh. An AI documentation tool like Grounded Scribe can then structure the dictation into a consistent case note format, ensuring every note contains the required fields (date, duration, participants, purpose, content, outcome, goal reference) regardless of how quickly the dictation was delivered.

This approach transforms documentation from a batch task at the end of the day into an incremental task distributed throughout the day. The total documentation time may be similar, but the quality is significantly higher because notes are recorded at the point of interaction rather than reconstructed from memory hours later.

Template for Support Coordination Progress Notes

A consistent structure for progress notes makes both writing and reading more efficient. The following template satisfies NDIS Quality and Safeguards Commission expectations:

Participant: [Name and NDIS number]

Plan period: [Start date] to [End date]

Report period: [This progress note covers X to Y]

Support coordination type: Support Coordination / Specialist Support Coordination

Goal 1: [State NDIS plan goal]

• Activities this period: [Specific coordination activities undertaken]
• Progress: [Measurable progress indicators, specific achievements, barriers encountered]
• Current status: [On track / Partially on track / Significant barriers / Goal achieved]
• Next steps: [Planned activities for next period]

Goal 2: [State NDIS plan goal]

• [Same structure]

Risk and safeguarding:

• [Any identified risks, incidents, or safeguarding concerns and actions taken]

Capacity building:

• [Evidence of participant or informal support network developing skills to manage independently]

Coordination summary:

• Total contacts this period: [Number]
• Service providers engaged: [List]
• Referrals made: [List with status]
• Meetings attended: [List]
• Key coordination achievements: [What was accomplished that required coordination]

Meeting Both Internal and External Compliance

Support coordination documentation must satisfy multiple stakeholders:

• NDIS Quality and Safeguards Commission (compliance audits): Complete, consistent records demonstrating supports were delivered as claimed
• NDIA planners (plan reviews): Evidence of goal progress and coordination value
• Participants and families (transparency): Clear records of what has been done on their behalf
• Internal management (quality assurance): Consistent documentation across the team
• Auditors (financial compliance): Notes that support billing claims with accurate date, time, and duration records

A single, well-structured case note system can serve all of these audiences. The key is consistency — every note follows the same structure, every note is linked to a plan goal, and every note is recorded promptly.

Practical Tips for Sustainable Documentation

Set a 'notes by end of day' rule. Every interaction documented before you leave for the day, even if some notes are brief. An incomplete note written today is more useful than a detailed note you plan to write tomorrow but never do.

Use travel time for dictation. The drive between appointments is often the only gap in a coordinator's day. Dictating case notes during this time (hands-free, obviously) converts dead time into documentation time.

Batch administrative documentation. Service agreements, progress reports, and plan review reports are best completed in dedicated blocks rather than squeezed between contacts.

Link every note to a goal. This habit ensures that when plan review time arrives, you can filter notes by goal and immediately see the evidence trail. It also demonstrates person-centred practice to auditors.

Review your notes as if you were the auditor. Before closing a case note, ask: does this note clearly show what was done, why it was done, what was achieved, and what happens next? If a stranger reading this note could understand the interaction and its purpose, it is sufficient.

The goal is not perfect documentation. The goal is consistent, compliant documentation that protects participants, supports funding decisions, and does not consume more of your day than the actual coordination work it records. When the documentation system works with your workflow rather than against it, both the quality and the sustainability improve.

Disclaimer

*Grounded Scribe is a documentation tool that assists practitioners in structuring their clinical notes. All AI-generated content must be reviewed, edited, and approved by the practitioner before it becomes part of the clinical record. The practitioner retains full professional responsibility for the accuracy, completeness, and clinical appropriateness of all documentation.*

---