Objective vs Subjective Language in Progress Notes: The #1 Reason Notes Fail Audit

Last updated 2026 · SupportNotes · Made in Australia

What is the difference between objective and subjective language in progress notes?

Objective language describes facts: what you saw, what you heard, what the person said and did, the time it happened, and the support you provided. Two different workers reading the same situation would write roughly the same objective note, because they are recording the same observable events.

Subjective language describes your interpretation: how you think the person felt, what you assume they meant, or a label you have put on their behaviour. Subjective notes are opinions, and an auditor cannot verify an opinion. That is why subjective language is the single most common reason progress notes get flagged in an NDIS audit.

Here is the quickest test there is. Read your note and ask: could a worker who wasn't on shift picture exactly what happened? If yes, it's objective. If they only learn what you thought or felt, it's subjective — and it needs a rewrite.

• Objective = observable, time-stamped, verifiable (what happened).
• Subjective = opinion, assumption, or label (what you thought).
• The test: a stranger should be able to reconstruct the shift from your note alone.
• Objective notes protect the participant, protect you, and stand up at audit.

Why does subjective language fail an NDIS audit?

Under the NDIS Practice Standards, providers must keep records showing each participant received the supports they were funded for, in line with their goals and any behaviour support or risk plans. During an audit, an assessor samples participant files and reads the progress notes to confirm support was actually delivered. Notes are the evidence trail — in practice, if it isn't written down, it didn't happen.

Subjective language breaks that evidence in three ways. First, an opinion ('good day', 'settled well') proves nothing was delivered. Second, judgement labels ('lazy', 'attention-seeking', 'manipulative') are disrespectful and can breach the NDIS Code of Conduct, which requires workers to treat participants with dignity and respect. Third, vague words hide risk — 'a bit agitated' could mean anything from a frown to a safety incident, and an auditor will treat a hidden risk as a serious finding.

You do not need to be a perfect writer to pass. You need to be factual. Most workers already see the right things on shift — the gap is simply turning what they saw into plain, observable language on the page.

Words to never use in a progress note

These words are red flags because they record a judgement, not a fact. Some are vague, some are disrespectful, and all of them give an auditor nothing to verify. Wherever one of these appears, stop and write the behaviour you actually observed instead.

• Judgement labels: lazy, rude, angry, aggressive, difficult, manipulative, attention-seeking, non-compliant, challenging.
• Lazy summaries: did well, did good, good day, bad day, struggled, coped, settled, as usual, normal, fine, okay.
• Mind-reading words: seemed, appeared, looked like, obviously, clearly, wanted to, tried to, refused (without context).
• Vague intensity words: a bit, quite, very, somewhat, slightly — they mean different things to different readers.
• Slang or blame: kicked off, played up, was being silly, gave me a hard time.

Subjective phrase to objective rewrite (comparison table)

This is the heart of the skill: take the lazy phrase and swap in the fact. You are not softening the truth — you are recording it more precisely. Notice how every rewrite adds a time, a behaviour, and what you actually did.

• "He had a good day" → "From 9–11am, attended the men's group at the community centre, joined two activities, and chatted with two other members."
• "She refused her medication" → "At 8:05am, declined her morning medication, saying she felt nauseous. Offered again at 8:40am; she took it with water."
• "Client was aggressive" → "At 2:15pm, raised his voice and pushed his chair back from the table. I gave him space, lowered my tone, and he sat back down within two minutes."
• "Did well with cooking" → "Prepared a stir-fry with verbal prompts for the chopping steps and independently used the cooktop; this links to his goal of cooking one meal a week unassisted."
• "Seemed upset" → "Was tearful and quiet from 4pm, told me she missed her sister. I sat with her and we phoned her sister at 4:30pm."
• "Struggled with the outing" → "Asked to return home twice during the shopping trip and covered her ears near the checkout. We moved to a quieter aisle and finished the shop in 10 minutes."
• "Lazy and unmotivated" → "Stayed in his room until 11am and declined two prompts to join breakfast. Agreed to a walk at 11:30am when I offered his favourite route."

A simple method to rewrite judgement into fact

You do not need to memorise a long list. Run every sentence through four quick questions and your notes will pass. This works on the night shift, on your phone, in two minutes.

If you get stuck turning a rough note into objective language, the free Notes Rewriter on supportnotes.com.au does exactly this — it restructures your own words into objective, goal-linked notes in seconds without inventing any details. It will never add a fact you didn't write, so the record stays true to your shift.

• WHAT did I actually see or hear? (Replace the label with the behaviour.)
• WHEN did it happen? (Add the time — 'at 8:10am', not 'this morning'.)
• WHAT did I do? (Record the support you provided in response.)
• WHICH goal does it link to? (Connect it to the participant's plan where relevant.)

Quick wins for ESL workers and busy shifts

English doesn't have to be perfect for a note to be excellent. Auditors want facts, not fancy words. Short, plain, true sentences beat long ones every time.

Write at the point of support, not from memory at the end of the shift. A two-line note written when it happened is more accurate — and more defensible — than a paragraph written three hours later.

• Use short sentences. One fact per sentence is fine and often clearer.
• Always include a time. Times turn a vague memory into evidence.
• Write what you saw, not what you guessed. 'She was crying' is fact; 'she was sad' is a guess.
• Avoid 'I think', 'maybe', and 'seemed' — they signal opinion.
• If a real incident happened, note it factually and follow your provider's incident process as well.

Frequently asked questions