If you’ve been a support worker for more than a few months, you’ve probably heard about SOAP or DARE. They’re documentation frameworks that organise progress notes into named sections. Some providers teach one or the other. Some teach both. Some teach neither and just hand workers a blank template.
The pitch is that picking the right framework will fix your notes. It won’t. A framework is a template, and a template can’t make a note compliant. What goes inside it can. This post walks through SOAP and DARE honestly, then explains why the more important question is something the framework debate doesn’t touch.
Short version: SOAP was built for doctors. DARE is closer to support work but has no structure for incidents, restrictive practices, or NDIS goal linking. Both are templates. Neither stops a note from being inaccurate, embellished, or fabricated. The thing that actually decides whether your notes survive an audit is whether they reflect what happened.
The SOAP method
SOAP stands for Subjective, Objective, Assessment, and Plan. It was developed in the 1960s by an American physician for medical records, and it’s been the standard structure in hospitals, GP clinics, and allied health practices ever since.
Where SOAP works
SOAP works in clinical settings. When a physiotherapist assesses range of motion or a psychologist tracks treatment progress, the Assessment section makes sense, because clinical interpretation is part of their scope of practice.
Where SOAP doesn’t fit NDIS support work
The Assessment section is the problem. Support workers aren’t clinicians, and the NDIS Code of Conduct requires honesty and transparency in documentation. When a worker writes “reduced participation likely due to fatigue,” they’re making a clinical judgment they’re not qualified to make. SOAP also has no natural place for the things NDIS auditors specifically look for: incident classification, restrictive practice records, or goal linking. A SOAP note can be a good note, but the template doesn’t prompt for the things that matter most in an NDIS audit.
The DARE method
DARE stands for Description, Action, Response, and Evaluation. It’s more common in aged care and disability than SOAP, and it’s closer to what support workers actually do day to day.
Where DARE works
DARE keeps the focus on what was done and how the participant responded. That’s closer to the lived reality of support work than SOAP’s clinical framing. Workers find it easier to apply because the section labels match what they’re actually doing during the shift.
Where DARE doesn’t fit NDIS support work
DARE has no dedicated structure for safety, incidents, or compliance. If a participant fell during the shift, where does that go? Description? Action? The Evaluation section invites the same problem as SOAP’s Assessment, just under a different name. “Sarah responded positively” is an evaluation, not an observation. The note doesn’t say what Sarah actually did. DARE also has no prompt for NDIS plan goal linking, which is one of the first things auditors check.
The thing both frameworks miss
SOAP and DARE are templates. Templates organise what’s already in the worker’s head, but they can’t check whether what’s in the worker’s head is accurate, and they can’t catch what’s missing.
A SOAP note can describe a perfectly clean session that never happened. A DARE note can document a participant’s response that the worker never observed. Both notes would tick the framework boxes. Neither would survive an audit if the auditor noticed the gap between the note and reality.
This is the part of NDIS documentation the framework debate doesn’t touch. The framework decides where information goes. Whether the information is true is a separate question, and it’s the one that actually matters under mandatory registration. We’ve covered the specific risk this creates for workers who use AI documentation tools that invent content.
The framework isn’t the audit risk. The audit risk is a note that doesn’t reflect what happened. SOAP, DARE, or any other structure can house a fabricated note just as easily as an accurate one. The template doesn’t protect the worker. The integrity of the content does.
Clio’s approach to NDIS notes
Clio Care isn’t a framework. It’s a documentation tool built on a principle: the AI organises and prompts, the worker authors. The structure underneath is built directly from what NDIS regulators actually require, but the worker never has to learn it.
The way it works: you describe your shift in plain English, the way you’d tell a colleague what happened. Clio organises that description into a structured note. If anything required by NDIS compliance is missing from what you said, Clio doesn’t invent it. It inserts a coloured placeholder inside the note that you must fill in before you can sign off. You can’t accidentally sign off a note that’s missing required information, and you can’t accidentally sign off a note that contains information you didn’t observe. This is the Note Integrity Standard, and it’s the principle Clio is built on.
What this means in practice
If you described the activity but didn’t mention how the participant presented, Clio prompts you to add it. If a goal would naturally apply but you didn’t reference it, Clio prompts you. If you mentioned an incident but didn’t classify it, Clio prompts you. The worker’s description stays intact. The prompts close the gaps an auditor would notice.
What Clio doesn’t do is fill those gaps for you. The AI never invents an observation, a goal link, an incident detail, or a participant reaction. Every line in the final note traces back to something the worker said or confirmed. If an auditor reads the note, the worker can walk them through it point by point and defend every word. That’s the difference between structure (which templates provide) and integrity (which templates can’t).
The right question isn’t which framework to pick. It’s whether your documentation reflects what actually happened. Pick whichever structure your provider expects, but the integrity of what’s inside it is the thing an auditor will care about.
If you’re used to SOAP or DARE
You don’t need to unlearn anything. Clio uses an internal structure that maps cleanly to both frameworks. If you’re used to thinking in SOAP, the Subjective and Objective sections both feed into how Clio captures participant presentation. If you’re used to DARE, Description and Action map to how Clio captures the activities and supports provided. The Assessment section of SOAP and the Evaluation section of DARE don’t have direct equivalents, by design. Clio doesn’t ask workers to interpret behaviour. The reader (a supervisor, a coordinator, an auditor) draws their own conclusions from the facts.
So which framework should NDIS support workers use?
If your provider mandates SOAP or DARE, use what they require. If they don’t, use the one that fits your work. SOAP makes more sense in allied health contexts where clinical assessment is part of the role. DARE is closer to general support work. Either is workable.
But picking the framework is the easy part. The harder part is making sure what goes inside it is accurate, complete, and yours. That’s the part Clio is built to handle, regardless of which framework label your provider attaches to it.
Describe your shift. We’ll handle the structure.
Write your shift in your own words. Clio organises it, prompts you on anything missing, and lets you sign off only when every line is yours. Built on the Note Integrity Standard. No framework knowledge needed.
Start for free →