What Makes a Progress Note Compliant

Before we look at examples, you need to understand the four principles that separate a compliant NDIS progress note from a non-compliant one. Every example below traces back to these:

  1. Factual and observable — document what you saw, heard, or measured. Not what you think it means.
  2. Time-specific — include shift times, the time of any significant event, and duration where relevant.
  3. Goal-linked where appropriate — notes for capacity-building, community access, and independence supports should reference the relevant NDIS plan goal.
  4. Objective language — no "seemed", "appeared", "was good", or "refused". Use direct descriptions of observable behaviour.

With those principles in mind, let's look at the examples.

Morning Routine Support (Examples 1–2)

Example 1: Morning Routine — Bad

Bad Note
"Supported James with his morning routine. He was in a good mood and did well. Helped him get ready for the day."
Why it fails: No times. No specifics about what was done or what James did independently. "Good mood" and "did well" are subjective. An auditor cannot verify any support was delivered from this note.

Example 1: Morning Routine — Good

Compliant Note
"Shift 7:00am–10:00am. Supported James with morning routine including showering (verbal prompts only — James washed independently), dressing (James selected his own clothing and dressed without physical assistance), and breakfast preparation (James made toast and coffee with standby support). James stated he was feeling rested. Support provided aligns with Goal 3 — increasing independence in daily living tasks."
Why it works: Shift time stated. Specific tasks listed. James's level of independence documented. Observable quote used. Goal referenced.

Example 2: Morning Routine (Complex Needs) — Bad

Bad Note
"Sarah had a rough morning. She refused to get up and was difficult. Eventually got her showered and fed."
Why it fails: "Refused" implies deliberate non-compliance. "Difficult" is subjective. "Eventually" without time context. No detail on what support was provided or outcome achieved.

Example 2: Morning Routine (Complex Needs) — Good

Compliant Note
"Shift 7:00am–11:00am. At 7:15am, worker prompted Sarah to begin morning routine. Sarah indicated she wanted to remain in bed and stated 'I'm not getting up yet.' Worker provided Sarah with 20 minutes additional rest as per her support plan. At 7:40am, Sarah agreed to begin showering. Full physical assistance required for showering and dressing. Sarah ate breakfast (cereal and juice) at 8:45am with verbal prompting. Sarah appeared more settled by end of breakfast."
Why it works: Exact times documented. Sarah's words quoted directly. "Appeared more settled" is borderline but used only at end after clear context. Support plan referenced. Level of physical assistance specified.

Meal Preparation (Examples 3–4)

Example 3: Meal Prep — Bad

Bad Note
"Helped Michael cook dinner. He seemed to enjoy it. Good session."
Why it fails: No time. No specifics on what "helping" involved. "Seemed to enjoy" is subjective. "Good session" tells an auditor nothing.

Example 3: Meal Prep — Good

Compliant Note
"Shift 4:00pm–8:00pm. At 5:30pm, supported Michael to prepare pasta with vegetables. Michael independently retrieved ingredients from the fridge, chopped vegetables with verbal prompts for safety, and boiled pasta without assistance. Worker provided standby support during stovetop use as per his risk assessment. Michael stated 'I like cooking, it makes me feel good.' Goal 4 (developing independent living skills) supported."
Why it works: Specific time, specific task, specific steps, independence level documented, safety measure referenced, direct quote, goal linked.

Example 4: Meal Prep (Assistance Required) — Bad

Bad Note
"Made lunch for Emma. She can't do much in the kitchen because of her disability."
Why it fails: Demeaning language. No times. No specifics. "Can't do much" is a blanket claim not supported by the note. Non-person-centred language.

Example 4: Meal Prep (Assistance Required) — Good

Compliant Note
"Shift 12:00pm–3:00pm. At 12:30pm, worker prepared lunch (cheese sandwich and fruit) with Emma. Emma directed her preferences (cheese sandwich, no tomato) and selected her own drink. Full physical assistance required for food preparation due to fine motor limitations. Emma ate full lunch at the dining table."
Why it works: Emma's preferences and choices documented. Level of assistance described accurately. No demeaning language. Emma's agency respected in the note.

Community Access (Examples 5–6)

Example 5: Community Access — Bad

Bad Note
"Took Tom to the shops. He bought some things. Had a good outing."
Why it fails: No time. "Took" implies the participant was passive. No goal reference. No specifics on what was practiced or achieved. Worthless for plan review evidence.

Example 5: Community Access — Good

Compliant Note
"Shift 10:00am–1:00pm. Supported Tom with community access — shopping at Woolworths Bendigo Central (10:30am–12:00pm). Tom used his shopping list to locate 6 of 8 items independently, asked a staff member for assistance to locate pasta (required one verbal prompt from worker to initiate), and used the self-checkout with minimal support (worker provided verbal prompts for payment steps). Tom stated he felt confident using self-checkout. Goal 2 (increasing independence in community participation) supported."
Why it works: Specific location and times. Specific tasks and outcomes. Independence level graded. Direct quote. Goal referenced. Perfect for plan review.

Example 6: Community Access (Anxiety) — Bad

Bad Note
"Went to the library with Lisa. She got anxious when it was too loud so we left early."
Why it fails: "Got anxious" — how do you know? What did you observe? "Too loud" is subjective. No times. No detail on support provided or strategies used.

Example 6: Community Access (Anxiety) — Good

Compliant Note
"Shift 2:00pm–5:00pm. Supported Lisa to Bendigo Library (2:30pm–3:45pm) for Goal 5 (building comfort in community environments). At 3:30pm, a group of school students arrived creating increased noise. Lisa covered her ears, stated 'I want to go', and moved toward the exit. Worker supported Lisa to use her grounding strategy (3 deep breaths as per her support plan) — Lisa was able to calm within 2 minutes. Lisa chose to leave at 3:45pm, stating 'it was too busy today.' Debrief conducted in the car. No further distress observed."
Why it works: Observable behaviours described exactly. Support strategies referenced. Lisa's words quoted. Outcome documented. Goal referenced. Support plan referenced.

Medication Support (Examples 7–8)

Example 7: Medication — Bad

Bad Note
"Gave John his medication in the morning. He took it fine."
Why it fails: No time. No medication name or dose. "Took it fine" is vague. Medication documentation requires exact details for legal and safety reasons.

Example 7: Medication — Good

Compliant Note
"At 8:00am, administered John's morning medication as per Medication Administration Record (MAR): Metformin 500mg x1 tablet (oral) with water. John took medication without difficulty. MAR signed. No adverse reactions observed during shift."
Why it works: Exact time, medication name, dose, route, reference to MAR. Observable outcome. Adverse reaction check documented.

Example 8: Medication Declined — Bad

Bad Note
"Maria refused her medication. Not sure why. Left it for the next shift."
Why it fails: "Refused" is loaded language. No time. No detail on what was said or done. "Not sure why" and "left it" without any escalation or documentation is a safety and compliance issue.

Example 8: Medication Declined — Good

Compliant Note
"At 8:15am, offered Maria her morning medication (Quetiapine 25mg as per MAR). Maria stated 'No, not today, I don't want it.' Worker acknowledged Maria's right to decline and did not administer medication. Worker contacted on-call coordinator at 8:20am and documented declined dose on MAR. Handover note completed for incoming shift. Medication not administered — participant decision documented."
Why it works: Maria's words quoted. No "refused" language. Escalation documented. Rights respected. MAR documentation referenced. Handover completed.

Behaviour Support (Examples 9–10)

Example 9: Behaviour Incident — Bad

Bad Note
"Jake had a meltdown today and was very aggressive. We managed to calm him down eventually."
Why it fails: "Meltdown" is a clinical diagnosis term, not an observable behaviour description. "Aggressive" is a label. "Managed to calm him down" — how? What strategies? No times. No antecedents documented.

Example 9: Behaviour Incident — Good

Compliant Note
"Shift 9:00am–3:00pm. At 11:30am, Jake's TV program was interrupted by a system update. Jake vocalised loudly, struck the couch cushions with both hands, and stated 'I hate this!' Worker calmly acknowledged Jake's frustration and offered his preferred stress tool (stress ball) as per his Positive Behaviour Support Plan (PBSP). Jake accepted the stress ball and vocalisation decreased within 3 minutes. Jake's preferred TV program resumed at 11:40am. Jake was calm for remainder of shift. Incident not reportable — behaviour managed within PBSP strategies. No injury to Jake or worker."
Why it works: Antecedent documented (TV interrupted). Observable behaviours described specifically. Jake's words quoted. PBSP strategy referenced. Outcome documented. Reportability assessed.

Example 10: Behaviour (Restrictive Practice) — Bad

Bad Note
"Had to restrain Ben briefly when he got aggressive. He calmed down after."
Why it fails: "Restrain" is a regulated restrictive practice — this note is wholly inadequate. No authorisation referenced. No NDIS Commission reporting triggered. No detail whatsoever. This note could result in serious compliance consequences.

Example 10: Behaviour (Restrictive Practice) — Good

Compliant Note
"Shift 2:00pm–8:00pm. At 4:45pm, Ben struck the dining table repeatedly and moved toward another resident. Worker implemented brief physical guide (arm guiding to redirect, lasting approximately 8 seconds) as authorised under Ben's NDIS Behaviour Support Plan and regulated restrictive practice approval (Approval Ref: [REF]). Ben was guided to his room. Worker remained calm and continued de-escalation. Ben settled within 5 minutes. No injury to Ben or other residents. Incident report completed and submitted to coordinator at 5:00pm. Restrictive practice use recorded on register."
Why it works: Observable antecedents described. Exact type and duration of restrictive practice documented. Authorisation referenced. Outcome documented. Mandatory reporting steps completed and noted.

Incident Documentation (Examples 11–12)

Example 11: Fall — Bad

Bad Note
"Participant fell in the bathroom. Was okay. Called family."
Why it fails: No time. No description of how the fall occurred. "Was okay" is a conclusion — not observable facts. "Called family" — when? What was said? No medical check documented.

Example 11: Fall — Good

Compliant Note
"At 9:20am, Helen was found seated on the bathroom floor. Helen stated 'I slipped getting out of the shower.' Helen was conscious, alert, and responsive. Worker conducted basic first aid check — no visible bleeding, Helen denied pain when asked and was able to weight-bear with assistance. Helen was assisted to stand and guided to her bedroom to rest. Coordinator notified at 9:25am. Helen's daughter (emergency contact) notified by coordinator at 9:30am. Helen monitored for remainder of shift — no further concerns noted. Incident Report completed and submitted. See Incident Register entry [date]."
Why it works: Exact time, Helen's words, first aid assessment documented, escalation chain documented with times, ongoing monitoring noted, incident report referenced.

Example 12: Property Damage — Bad

Bad Note
"Participant broke a window. It was an accident. Fixed it up."
Why it fails: No time. No context. "Accident" is a conclusion. "Fixed it up" is vague. Property damage may be a reportable incident depending on value and context.

Example 12: Property Damage — Good

Compliant Note
"At 2:15pm, while playing ball in the living room, Adam kicked the ball which struck and cracked the lounge window (approx. 30cm crack, glass intact). No one was injured. Worker immediately ensured the area was safe and taped the crack with masking tape to prevent injury. Adam stated 'I didn't mean to.' Coordinator notified at 2:20pm. Property damage documented on Incident Register. Maintenance arranged by coordinator. Adam was not distressed after initial event."
Why it works: Exact time, how damage occurred, description of damage, immediate safety action, Adam's words, escalation, register entry noted — not a conclusion about fault.

Goal-Linked Activity (Examples 13–14)

Example 13: Goal-Linked — Bad

Bad Note
"Worked on Sophie's goals today. Made some progress. She's getting better."
Why it fails: "Goals" — which one? "Some progress" — at what? "Getting better" — compared to what baseline? Useless for plan review. An NDIA planner cannot use this as evidence of goal progress.

Example 13: Goal-Linked — Good

Compliant Note
"Shift 1:00pm–5:00pm. Supported Sophie with Goal 1 (improve ability to manage personal finances independently). Sophie reviewed her weekly budget spreadsheet and identified she had $40 remaining for the week. Sophie independently decided to allocate $20 to groceries and $20 to savings. Worker provided verbal prompts only (2 prompts). This is Sophie's third consecutive week independently completing her budget review — previously required full assistance."
Why it works: Specific goal named. Specific task. Sophie's decision-making documented. Prompt level recorded. Progress compared to baseline — evidence for plan review.

Example 14: Capacity Building — Bad

Bad Note
"Did some skill building with Ryan. He seemed to enjoy learning. Good progress."
Why it fails: "Some skill building" — what skill? "Seemed to enjoy" — subjective. "Good progress" — how measured? Not evidence-based at all.

Example 14: Capacity Building — Good

Compliant Note
"Shift 10:00am–2:00pm. Supported Ryan with public transport training (Goal 3 — developing independent travel skills). Ryan successfully planned a route from Bendigo Station to the shopping centre using the PTV app with verbal prompts (required 1 prompt to check timetable). Ryan purchased his own Myki top-up independently. Return journey completed without support required. Ryan stated 'I didn't need help on the way back.' Next session: practice journey to medical appointment."
Why it works: Specific skill, specific steps, independence level quantified, direct quote, goal referenced, next step documented — full evidence trail for plan review.

Overnight Shift (Examples 15–16)

Example 15: Overnight SIL — Bad

Bad Note
"Quiet night. All residents slept well. No issues."
Why it fails: This note could be written without anyone being present. No check times. No individual resident documentation. "All residents slept well" — were checks conducted? When?

Example 15: Overnight SIL — Good

Compliant Note
"Overnight shift 10:00pm–7:00am. Welfare checks conducted at 11:00pm, 1:00am, 3:00am, 5:00am — all three residents observed in their rooms, no concerns noted. At 2:30am, Resident B (Tom) woke and requested water. Worker provided water and Tom returned to sleep at 2:35am. All residents asleep at shift end. No incidents. No medication required overnight. Handover provided to morning shift worker [Name] at 7:05am."
Why it works: Check times documented. Individual resident noted by name. Any overnight events documented. Handover documented. No incidents clearly stated.

Example 16: Overnight Active Support — Bad

Bad Note
"Woke up at night a few times to help a resident. Nothing serious."
Why it fails: "A few times" — how many? When? Which resident? What was the support? "Nothing serious" is a conclusion. If billing for active overnight support, this note does not justify the claim.

Example 16: Overnight Active Support — Good

Compliant Note
"Overnight active shift 10:00pm–7:00am. 11:30pm: Sandra woke and was distressed, stating 'I had a bad dream.' Worker sat with Sandra, provided reassurance. Sandra settled and returned to sleep at 11:45pm. 3:15am: Sandra woke again requesting assistance to the bathroom. Worker provided physical assistance with transfer and hygiene. Sandra returned to bed at 3:25am. No further disturbances. Total active support duration: approx. 25 minutes. All other residents slept through night."
Why it works: Every overnight interaction documented with exact times. Type of support specified. Duration of active support recorded — justifies active overnight claim in billing.

Physiotherapy Support (Examples 17–18)

Example 17: Physio Support — Bad

Bad Note
"Did physio exercises with David. He did okay. Will do again tomorrow."
Why it fails: Which exercises? How many reps? Did David complete them? Any pain reported? No reference to physiotherapy plan. "Did okay" is subjective.

Example 17: Physio Support — Good

Compliant Note
"Shift 9:00am–12:00pm. At 10:00am, supported David to complete physiotherapy home program as per physiotherapist's program (dated [date]). Exercises completed: seated leg raises x10 reps x3 sets (David completed independently), standing balance exercises x5 minutes (worker provided standby support), shoulder stretches x5 reps each side (worker provided verbal cues for form). David denied any pain throughout. David stated 'My shoulder feels looser today.' Next physio appointment: [date]."
Why it works: Specific exercises, reps, sets. Independence level. Pain assessment documented. Physio plan referenced. Direct quote. Follow-up noted.

Example 18: Physio (Declined Exercise) — Bad

Bad Note
"Grace didn't want to do her exercises. Maybe she was tired."
Why it fails: "Didn't want to" — no direct communication documented. "Maybe she was tired" — speculation, not fact. No escalation or documentation of support plan deviation.

Example 18: Physio (Declined Exercise) — Good

Compliant Note
"At 11:00am, offered Grace her physiotherapy program. Grace stated 'I don't feel like it today, my back is sore.' Worker acknowledged Grace's preference and right to decline. Worker asked Grace to rate her back pain — Grace stated '6 out of 10.' Worker documented pain rating and notified coordinator at 11:10am. Physiotherapy exercises not completed today — participant decision. Coordinator to notify physiotherapist. Grace rested and watched television for remainder of session."
Why it works: Direct quote. Pain documented with rating. Rights respected. Escalation documented. Deviation from plan noted appropriately.

Social Skills Development (Examples 19–20)

Example 19: Social Skills — Bad

Bad Note
"Went to the community group with Liam. He interacted with others. It was good for him socially."
Why it fails: No times. "Interacted with others" — how? What was observed? "Good for him socially" — a worker's opinion, not evidence. This cannot support a capacity-building plan review.

Example 19: Social Skills — Good

Compliant Note
"Shift 10:00am–1:00pm. Supported Liam to Thursday social group at Bendigo Community Centre (10:30am–12:30pm) — Goal 2 (building social connections and community participation). Liam initiated conversation with two group members without worker prompting (first time observed initiating unprompted). Liam participated in group card game for 45 minutes. When another participant made a joke Liam misunderstood, Liam stated 'I got confused' and worker provided brief social cue explanation. Liam re-engaged with group immediately. Liam stated on return 'I like this group' and asked when the next session is."
Why it works: Specific location and times. Observable behaviours described. Milestone noted (first unprompted initiation). Worker support described. Direct quotes. Goal referenced. Strong plan review evidence.

Example 20: Social Skills (Challenging Interaction) — Bad

Bad Note
"Amy had trouble socialising today. She got upset when someone was mean to her. Had to leave."
Why it fails: "Had trouble socialising" — what specifically happened? "Someone was mean" — what occurred? "Got upset" — what was observed? "Had to leave" — why was leaving the decision made?

Example 20: Social Skills (Challenging Interaction) — Good

Compliant Note
"Shift 1:00pm–4:00pm. Supported Amy to weekly social group (Goal 3 — developing social skills and friendships). At 2:15pm, another group participant told Amy 'you're not doing it right' during an art activity. Amy was observed to stop speaking, cross her arms, and look at the floor. Worker acknowledged Amy's visible change in body language quietly and offered to step outside for a moment. Amy accepted. Outside, Amy stated 'She was rude to me.' Worker validated Amy's experience and practised the assertiveness script from her support plan ('It's okay to say: I'd like to try my way'). Amy chose not to return to the group and stated she wanted to go home. Amy's decision respected. Event discussed with coordinator for debrief planning."
Why it works: Observable behaviours (crossed arms, looking at floor). Event described factually. Direct quote. Support strategy used. Amy's decision respected. Escalation for debrief noted. Goal referenced.

Common Words to Avoid: Subjective Language Table

These are the most common words that auditors and NDIS Commission reviewers flag in progress notes. Replace each one with observable, factual language.

Avoid This Word/Phrase Why It's a Problem Use This Instead
seemed / appeared Implies you're guessing at the participant's internal state stated / said / was observed to / [specific behaviour]
was good / had a good day No meaning — what did "good" look like in observable terms? completed [task] independently / engaged with [activity] for [duration]
refused Implies non-compliance or wilfulness; removes agency declined / stated they did not want to / indicated a preference not to
was aggressive / was violent Label rather than description; legally problematic struck [object] / raised voice / stated [exact words] / threw [specific item]
challenging behaviour Clinical label that belongs in a behaviour support plan, not a progress note Describe the specific observable behaviour and its context
was upset / was emotional Subjective interpretation — what did you actually observe? cried / raised their voice / stated '[quote]' / was observed with tears
struggled / had difficulty Vague — what exactly was the difficulty? required [X] prompts to complete [specific task] / was unable to [specific step] without [specific support]
refused to take medication "Refused" is wrong — participants have the right to decline declined medication / stated 'I don't want to take it today' / medication not administered — participant decision
was happy / was in a good mood Subjective — you cannot know someone else's emotional state smiled / laughed / stated they were feeling well / engaged enthusiastically with [activity]
couldn't do it / can't [anything] Permanent and demeaning — not reflective of a person-centred approach required full physical assistance to complete [task] on this occasion

Turn Your Rough Notes Into Compliant Progress Notes

Type what happened during your shift — the NDISCompliant Notes Rewriter rewrites it into audit-ready language, removes subjective words, and links your note to participant goals. Free. No login required.

Try the Notes Rewriter Free

The 20 examples above cover the most common documentation scenarios support workers face. The pattern is consistent across all of them: observable facts + exact times + what the participant said and did + what support was provided + goal reference = a compliant note.

If you find yourself writing notes like the "bad" examples — you're not alone. Most support workers were never taught how to write compliant notes. The language habits run deep. The Notes Rewriter tool is built specifically to fix that gap without requiring a training course.

Important: This article provides general guidance about NDIS compliance requirements. It is not legal or professional advice. Requirements may change as the NDIS Commission updates its policies and Practice Standards. Always verify current requirements with the NDIS Quality and Safeguards Commission or a registered NDIS consultant before making compliance decisions.