SOAP vs ISBAR vs Progress Notes vs Case Notes: Which Format Should You Use?
Last updated 2026 · SupportNotes · Made in Australia
Use the format that matches the job. Progress notes and case notes are the everyday record of what happened on a shift — start here for most NDIS and aged-care documentation. SOAP and DAP are structured clinical formats that shine when you're recording an observation, a change, or a therapy session. ISBAR is a handover tool — it's how you pass information to the next worker or a nurse, not how you write your daily note. STAR is a short way to capture a behaviour or incident moment (Setting, Trigger, Action, Result). None of these replaces your provider's required forms — they're just structures that make your writing clearer, faster and audit-ready.
Why do these note formats exist (and why the confusion)?
If you've worked a few shifts in NDIS support, SIL, or aged care, you've probably been handed five different words for "write it down": progress notes, case notes, SOAP, DAP, ISBAR, STAR. It's confusing because they overlap — and because most are borrowed from nursing and clinical work, then adapted for disability and community settings.
Here's the simple truth: a format is just a checklist for your brain. It tells you what to capture and in what order so you don't forget anything important and so the next person can read it fast. The right format depends on one question: what are you documenting, and who is it for?
This guide is the hub. Below you'll find one master comparison table, then a short worked example of each format. Where there's a deeper guide on the format, we link to it so you can go as far as you need.
The 30-second comparison table
Read this table once and you'll be able to pick the right format on any shift. "Who uses it" is a guide, not a rule — formats cross over between disability, nursing and aged care all the time.
- Progress note — What it's for: the routine record of a shift or support session (what you did, what the person did, how they were). Who uses it: support workers, SIL staff, aged-care staff. Example below.
- Case note — What it's for: a record tied to a person's case over time, often used by support coordinators, case managers and allied health (decisions, contacts, follow-ups). Who uses it: support coordinators, case managers, social workers. Example below.
- SOAP — What it's for: a structured clinical note for an observation or change (Subjective, Objective, Assessment, Plan). Who uses it: nurses, therapists, allied health, clinically-minded support staff. Example below.
- DAP — What it's for: a shorter clinical cousin of SOAP (Data, Assessment, Plan) — fast when you don't need to split subjective from objective. Who uses it: therapists, support workers recording a session. Example below.
- ISBAR — What it's for: a spoken or written handover to pass critical info to the next person (Identify, Situation, Background, Assessment, Recommendation). Who uses it: nurses, paramedics, SIL handover, anyone escalating to a clinician. Example below.
- STAR — What it's for: a quick way to capture a behaviour or single event (Setting, Trigger, Action, Result). Who uses it: behaviour support, support workers logging an incident moment. Example below.
Progress notes: your everyday record
A progress note is the workhorse. It's the note you write at or after most shifts to record what support you provided, how the person was, and anything worth flagging. In NDIS settings, good progress notes are also your main evidence at audit — they show that the supports in someone's plan actually happened and were delivered safely.
The golden rule: write facts, not opinions. Describe what you saw and heard, link it to the person's goals where you can, and avoid vague filler like "had a good day."
Case notes: the running story of a person's case
A case note is similar to a progress note but it's framed around a person's case over time rather than a single shift. Support coordinators, case managers and allied health professionals use case notes to record contacts (phone calls, emails, meetings), decisions made, referrals, and what happens next. They're the paper trail that shows coordination actually occurred.
If you're a support worker writing daily, you're almost always writing progress notes. If you're coordinating a person's supports — chasing providers, booking assessments, following up — you're writing case notes.
SOAP and DAP: structured clinical notes
SOAP stands for Subjective, Objective, Assessment, Plan. It comes from nursing and medicine and is widely used in allied health and therapy. It's the format to reach for when you're recording an observation or a change — because it forces you to separate what the person reported (Subjective) from what you measured or saw (Objective), then your interpretation (Assessment) and the next step (Plan).
DAP is the shorter cousin: Data, Assessment, Plan. It folds "subjective" and "objective" into one Data section. Use DAP when splitting the two doesn't add value and you want to write faster.
For a full walkthrough with more worked examples, see our deeper guides on SOAP notes for NDIS and DAP notes for NDIS.
ISBAR: how you hand over, not how you log
This is the one people mix up most. ISBAR is a handover and escalation tool — it's how you pass information clearly to the next worker, a team leader, or a nurse, especially when something matters. It stands for Identify, Situation, Background, Assessment, Recommendation. It's used heavily in Australian hospitals and clinical settings (you'll see it referenced by bodies like SA Health and in national clinical-communication guidance), and it works just as well for a SIL shift handover.
Key point: ISBAR is the structure of the conversation or handover, not your daily progress note. You still write your progress note for the record — ISBAR is what you say (or jot) when you pass the baton. If you do a lot of handovers, our NDIS shift handover guide breaks ISBAR down step by step.
STAR: a quick capture for behaviour and incidents
STAR stands for Setting, Trigger, Action, Result. It's a short, structured way to capture a single behaviour-of-interest or a moment that needs explaining — often used in behaviour support. It helps you record the context around an event rather than just the event itself, which is exactly what a behaviour support practitioner needs to spot patterns.
Important: STAR captures the moment, but if something crosses into a reportable or serious incident, STAR does not replace your incident process. You still complete the required incident report and follow your provider's procedure. If you're ever unsure whether something is "just" a progress note or an incident, read incident notes vs progress notes — getting that call right matters.
So which one should you actually use?
Match the tool to the task:
Writing your normal shift note? Progress note (or case note if you're coordinating a person's supports). Recording a clinical observation or change? SOAP or DAP. Handing over to the next worker or escalating to a nurse? ISBAR. Capturing a behaviour or a one-off event? STAR — then your incident process if it's serious.
You don't have to memorise all of these. Pick the one your workplace expects, learn it well, and keep your facts clear, specific and goal-linked. The format is the easy part — strong, honest, person-centred writing is what passes audits and, more importantly, keeps people safe and well supported.
- Default to progress/case notes for day-to-day documentation.
- Use SOAP or DAP when there's a clinical observation worth structuring.
- Use ISBAR for handovers and escalations — it's spoken or written, not your daily log.
- Use STAR for behaviour moments, then escalate to incident reporting if needed.
- Always check your provider's required forms — formats sit inside those, they don't replace them.
Turn rough notes into clear, audit-ready ones
If English isn't your first language, or you're just rushing at the end of a long shift, the hardest part isn't choosing a format — it's turning a quick scribble into a clear, professional note. That's exactly what SupportNotes is built for.
Paste your rough notes and the free tool helps rewrite them into clean, factual, NDIS-aligned wording — in SOAP, progress-note, or plain structure — without changing what actually happened. It's a fast way to learn good note-writing by seeing your own notes done well. Try the free notes tool and see the difference on your next shift.
If you run or manage a SIL home, getting documentation consistent across a whole team is a bigger job. Our SIL Rescue Kit gives you ready-to-use templates and policies so every worker records the right things, the right way — and you walk into audit with evidence already in order.
Frequently asked questions
Is ISBAR a type of progress note?
No. ISBAR (Identify, Situation, Background, Assessment, Recommendation) is a handover and escalation tool — it structures how you pass information to the next worker or a nurse. You still write a separate progress note for the official record. Think of ISBAR as what you say, and the progress note as what you file.
What's the difference between a progress note and a case note?
They're close cousins. A progress note records a single shift or support session — what you did and how the person was. A case note is framed around a person's case over time and is typically used by support coordinators and case managers to log contacts, decisions and follow-ups. Most daily support-worker documentation is progress notes.
Should I use SOAP or DAP for NDIS notes?
Both work. SOAP (Subjective, Objective, Assessment, Plan) separates what the person reported from what you observed, which is useful for clinical or changing situations. DAP (Data, Assessment, Plan) merges those into one section and is faster. Use SOAP when the subjective/objective split adds clarity; use DAP when it doesn't. Always follow your provider's preferred format if they have one.
Does the NDIS require a specific note format?
The NDIS Practice Standards and Quality and Safeguards Commission require accurate, contemporaneous records that show supports were delivered safely and in line with a person's plan — but they don't mandate one fixed format like SOAP or DAP. Your provider chooses the templates. The format matters less than whether your notes are factual, specific, goal-linked and written at the time. When in doubt, check your provider's documentation policy.
What format is best for recording a behaviour or incident?
STAR (Setting, Trigger, Action, Result) is a clean way to capture the context around a behaviour, which behaviour support practitioners rely on. But if the event is serious or reportable, STAR does not replace your incident process — you must still complete the required incident report and follow your provider's procedure.
I'm not confident writing in English — which format is easiest?
Start with progress notes using plain, factual sentences: what you did, what the person did, anything you noticed, and what happens next. Avoid vague words like 'good' or 'fine' and describe what you actually saw. A free notes tool can help you turn rough wording into clear, professional notes so you improve with every shift.
Turn your rough notes into an audit-ready note — free
Paste how you really write. Get a clear, objective, NDIS-aligned note in seconds. Private — runs on an Australian server, never sent to ChatGPT.
Paste your note → free