← Back to Blog
Technology

How AI Is Changing NDIS Progress Note Writing

March 2026 · 7 min read

Progress notes are the backbone of NDIS service documentation. Every support session requires a written record of what was provided, how the participant responded, whether goals were progressed, and what follow up actions are needed. For support workers delivering multiple sessions per day, this documentation requirement adds up to a significant portion of their working time.

The challenge is not that progress notes are unnecessary. They are essential for compliance, continuity of care, and demonstrating outcomes. The challenge is that the traditional method of writing them, typing on a phone screen or laptop at the end of a long shift, is slow, error prone, and deeply unpopular with workers. AI powered voice to text technology is fundamentally changing how these notes get written, and the results are measurable.

The Progress Note Bottleneck

Ask any support worker about the least favourite part of their job and progress note writing will be near the top of the list. The reasons are straightforward.

Typing on a phone is slow and frustrating. Most support workers do not carry laptops. They use their mobile phones to complete documentation, often while sitting in their car between sessions or during their commute home. Typing detailed notes on a small screen with autocorrect fighting every clinical or NDIS specific term takes 10 to 15 minutes per note. For a worker completing four sessions per day, that is 40 to 60 minutes of typing.

End of shift fatigue degrades quality. The best progress notes are written while details are fresh. But in practice, workers often leave their notes until the end of the day or even the next morning. By then, specific details have faded. The note becomes vague: "Assisted John with daily living activities. He was in good spirits." This kind of note tells an auditor nothing about what specific support was provided, whether goals were referenced, or what outcomes were observed.

Missing details create compliance risk. NDIS progress notes should reference the participant's specific goals, describe the support provided in relation to those goals, note the participant's response and any observable outcomes, and identify follow up actions. When workers are rushed or fatigued, one or more of these elements is frequently missing. Coordinators then spend additional time reviewing notes, sending them back for revision, and following up on incomplete entries.

How Voice to Text Works

Voice to text for progress notes is not a futuristic concept. It uses the Web Speech API built into modern mobile browsers, combined with AI processing to transform spoken words into structured documentation.

The process is simple. The support worker opens the progress note form on their phone, taps the microphone icon, and speaks naturally about the session. They describe what happened in their own words, using the same language they would use if they were telling a colleague about the session. The system transcribes their speech in real time, displaying the text as they speak.

The speech recognition is configured for Australian English (en-AU), which means it handles Australian accents, colloquialisms, and pronunciation patterns accurately. Medical and NDIS specific terminology is handled well because the underlying recognition models have been trained on healthcare and disability service vocabulary.

Workers do not need to speak in a formal or structured way. They simply narrate what happened: "I picked up Sarah from her home at 9am and we drove to the Chermside shopping centre. She wanted to practice using public transport for her independence goal so we took the bus on the way back. She was a bit nervous at first but managed to tap on with her Go Card independently. She was really pleased with herself. I will follow up with her coordinator about adding another public transport session next week."

That natural narration contains all the elements of a good progress note: the support provided, the goal referenced (independence, public transport), the participant's response (nervous then pleased), the outcome (independent Go Card use), and the follow up action (coordinator discussion about additional sessions).

AI Structuring

The raw transcription is valuable, but AI takes it a step further. After the worker finishes speaking, AI processes the transcript and restructures it into a professional NDIS progress note format.

The AI identifies and extracts several key components from the narration:

The AI does not fabricate information. It only structures and reformats what the worker actually said. If a worker does not mention goals or outcomes, the AI flags these as missing rather than inventing content. This ensures the note remains an accurate record of the worker's observations.

The worker reviews the structured note, makes any corrections or additions, and submits it. The entire process, from tapping the microphone to submitting the final note, takes 2 to 4 minutes instead of 10 to 15 minutes of typing.

Time Savings at Scale

The time saving per individual note is meaningful. But the real impact becomes clear when you multiply it across a team.

A support worker completing four sessions per day saves approximately 30 minutes per shift by using voice to text instead of typing. Over a five day work week, that is 2.5 hours per worker. For a team of 20 support workers, the collective saving is 50 hours per week.

Those 50 hours are not just time saved. They are time returned to direct participant support, or time that was previously unpaid (many workers complete notes in their own time after shifts). Either way, the impact on workforce satisfaction and retention is significant. Workers who spend less time on documentation are less likely to experience administrative burnout, one of the top reasons support workers leave the sector.

From a coordinator's perspective, AI structured notes are also faster to review. Instead of reading through unformatted paragraphs trying to identify whether all required elements are present, coordinators see a consistently structured note where goals, support, outcomes, and follow ups are clearly separated. Review time per note drops from 3 to 5 minutes to under 1 minute.

The cumulative effect is substantial. A provider with 20 workers and 4 sessions per worker per day generates approximately 400 progress notes per week. At 3 minutes saved per note (combining worker writing time and coordinator review time), that is 20 hours per week of recovered productivity across the organisation.

Compliance Benefits

Beyond time savings, AI progress notes improve compliance outcomes in several measurable ways.

Missing element detection: The AI checks each note against a compliance template before submission. If a note does not reference any participant goals, the worker is prompted to add this information. If no follow up actions are identified, the system asks whether any are needed. This pre submission check catches gaps that would otherwise only be identified during coordinator review or, worse, during an audit.

Consistency of documentation: Manual progress notes vary enormously in quality, length, and structure depending on who wrote them. Some workers write detailed, well structured notes. Others write two sentences. AI structuring normalises the quality across the team. Every note follows the same format, covers the same required elements, and meets the same minimum standard.

Audit trail integrity: Voice to text notes include timestamps showing when the note was started, when the transcription was completed, and when the final note was submitted. This creates a clear audit trail demonstrating that notes were completed contemporaneously with the support session, not backfilled days or weeks later.

Goal tracking over time: Because AI consistently identifies which goals are referenced in each note, it becomes possible to generate reports showing goal progression across multiple sessions. This data is valuable for plan reviews, where evidence of goal progress (or lack thereof) directly influences future funding decisions.

Draft Auto Save and Photo Attachments

Practical features around the voice to text capability make it even more useful in real world support settings.

Draft auto save ensures that no work is lost. If a worker starts a voice note and is interrupted (a common occurrence in disability support), the partial transcription is saved automatically. They can return to it later, continue the recording, or edit the text directly. This is particularly important for workers in SIL settings where interruptions are frequent.

Photo attachments allow workers to add visual evidence to their progress notes. A photo of an activity, a completed project, or a community outing adds context that words alone cannot capture. Photos are taken directly through the app using the phone's camera and are stored securely alongside the note. For mobile workers, the camera integration uses the device's rear camera by default, making it easy to capture the participant's environment or activities.

Together, these features create a documentation workflow that fits naturally into a support worker's day rather than disrupting it. Notes are completed while details are fresh. Photos provide visual context. Drafts are never lost. And the final product meets compliance standards consistently.

The Future of NDIS Documentation

Voice to text and AI structuring represent the current state of progress note innovation, but the trajectory points toward even greater automation. Future capabilities include AI that can suggest support strategies based on patterns across a participant's notes, automated alerts when a participant's progress toward goals appears to stall, and integration with plan management systems that automatically link documented supports to billable line items.

For providers evaluating their documentation processes today, the question is not whether AI will change how progress notes are written. It already has. The question is how quickly your organisation can adopt these tools and start realising the time savings, quality improvements, and compliance benefits they deliver.

The support workers who try voice to text for the first time almost universally have the same reaction: "Why did not we have this sooner?" The answer, of course, is that the technology needed to mature to a point where speech recognition was accurate enough, AI structuring was reliable enough, and mobile devices were powerful enough to run the entire process locally. That point has arrived.

Try Voice to Text Progress Notes

Save your support workers 30 minutes per shift with AI powered documentation. Australian English. NDIS compliant.

Login