How to write a progress note that protects you

Progress notes feel like the most boring part of the job — a quick line at the end of a shift. But when an auditor or, worse, an investigator goes looking, your notes are the record of what actually happened. Good notes protect you and the participant. Sloppy ones do the opposite.

The golden rule: objective, not opinion

Write what you observed, not what you assumed. "Was aggressive" is an opinion. "Raised his voice and pushed his chair back from the table" is an observation. The first invites argument; the second is a fact nobody can dispute.

What a strong note includes

• Who, when, where — participant, date, time, location.
• What you did — the support actually delivered against the plan.
• What you observed — facts, in plain language, including the person's own words where relevant.
• What you did about it — any action taken, follow-up or report made.

Good vs bad: real examples

Sometimes the easiest way to understand what good looks like is to see it side by side with what bad looks like. Here are a few common examples:

• Bad: "Had a good day. Was happy and cooperative." Good: "Assisted participant with meal preparation as per support plan. Participant made her own sandwich with minimal prompting and said she was pleased with how it turned out. No issues noted during the 2-hour shift."
• Bad: "Difficult shift. Participant was non-compliant." Good: "Participant declined to attend his scheduled day program, stating he was tired. We discussed options and agreed he would rest at home. I contacted the supervisor to advise. Participant was calm and engaged for the remainder of the shift."
• Bad: "Minor fall. Seems okay." Good: "At approximately 2:15pm, participant lost footing in the bathroom and fell, landing on her left side. No visible injury. Participant reported no pain. I assisted her to stand, checked for signs of injury, and completed an incident report. I notified the participant's emergency contact and my manager. Participant requested to rest for the remainder of the shift."

Notice that the good versions take maybe 30 extra seconds to write, but they tell a complete story. Anyone who reads them months later knows exactly what happened, who was involved, and what was done about it.

A simple template for everyday notes

You don't need elaborate software to write a good note. A consistent structure helps. Try this as a mental checklist:

• Opening line — Date, time, who you supported, what the shift was for (e.g., "Community access support, 10am–2pm").
• What was delivered — What actually happened during the shift, linked to the participant's goals or support plan where possible.
• What was observed — How the participant was presenting, any notable behaviour or conversation (in their own words if relevant), any concerns.
• Actions and follow-up — Anything you escalated, reported or communicated to anyone else. If nothing needed following up, say so briefly.
• Sign-off — Your name and signature (or digital equivalent), and the time you wrote the note.

Words to avoid

Steer clear of vague, judgmental or diagnostic language: "good day", "difficult", "manipulative", "non-compliant". They tell the reader nothing useful and can read as disrespectful. Stick to specifics.

Also avoid medical or clinical diagnoses in your notes unless you are qualified to make them. Instead of "appeared depressed," write "appeared quiet and withdrawn, made minimal eye contact, and declined to engage in planned activities." That's observable. "Depressed" is a clinical judgment you likely aren't qualified to make.

If it isn't written down, it didn't happen. If it's written badly, it can be used against you.

Progress notes vs incident reports: what's the difference?

This trips a lot of workers up. A progress note is a routine record of the support delivered during a shift. An incident report is a separate, specific document for when something goes wrong or outside the ordinary.

If something happened that needs an incident report (a fall, an allegation, a near-miss, a significant change in the participant's condition), you should write both: a brief mention in the progress note AND a full incident report in the incident management system. Don't try to fit the incident into the progress note and call it done. The incident report is what gets assessed for reportability to the NDIS Commission.

Privacy and storage

Progress notes contain sensitive personal information. They need to be stored securely, accessible only to the people who need them, and kept for the period required by your jurisdiction's records laws (check the specific requirements for your state, as they vary). A few basics:

• Paper notes — If you're still using paper, they need to be in a locked location, not sitting on a kitchen bench or left in a car.
• Digital notes — Use a password-protected system. Don't store participant information in personal email or general messaging apps like WhatsApp.
• Access controls — Not everyone in your organisation needs access to every participant's notes. Limit access to those who are actively supporting that person.
• Participant access — Participants have the right to see their own records. Your privacy policy should explain how they can request access.

Common phrases to replace

Here's a quick cheat-sheet for language upgrades. Replace these:

• "Had a good day" — Replace with a specific description of what happened.
• "Was upset / emotional" — Replace with what you actually observed: "Cried during the morning routine" or "Raised his voice when asked to leave the house."
• "Refused to cooperate" — Replace with what specifically happened: "Declined to attend the day program, stating he preferred to stay home."
• "Challenging behaviour" — Describe the specific behaviour instead: "Paced the hallway for approximately 20 minutes, declined to speak with me, and did not eat at lunch."
• "As per usual" — This tells the reader nothing. Write what actually happened, even if it was routine.

What auditors look for in your notes

During a certification audit, your progress notes are one of the primary evidence sources for the "provision of supports" quality area. Auditors look for:

• Consistency — Do the notes match what's in the support plan? If the plan says the participant is working toward cooking independently, are the notes tracking that goal?
• Completeness — Are there notes for every shift? A support period with gaps in the notes is a question mark. What happened on those days?
• Objectivity — Are the notes factual, or full of opinions and judgements? The more objective, the better.
• Timeliness — Are notes being written at the time of the shift, or clearly backdated? Notes dated three days after a shift raise questions.

Using notes to track participant progress toward goals

Progress notes shouldn't just document what happened — they should, over time, tell the story of the participant's journey toward their goals. If a participant's NDIS plan includes a goal around community participation, your notes should reflect what you're doing to support that goal, how the participant is progressing, and any barriers or achievements along the way. This is what makes notes valuable to the participant, not just to the auditor.

A practical habit: at the start of each shift, briefly remind yourself what goals this participant is working toward. At the end, ask: did anything happen today that's relevant to those goals? If so, include it in the note. This connects your day-to-day work to the purpose of the NDIS plan.

Getting your team to write better notes

If you have support workers who write poor notes, address it early. Vague notes are a habit, and habits are easier to fix in the first few weeks than after months of reinforcement. Some practical approaches:

• Share examples — Show your workers a good note and a poor note side by side. Make it concrete. "This is the standard we're aiming for."
• Review notes regularly — As a manager, check in on notes weekly for new workers. Praise good examples. Gently correct poor ones in supervision, not in front of other staff.
• Use the AI writer as a support tool — Not as a replacement for workers writing notes, but as a way for workers to check whether their rough draft is hitting the right standard before they submit it.

How long to keep progress notes

Progress notes need to be retained for a minimum period after the support is delivered. The specific requirement varies by state and territory and may also be covered in your privacy policy obligations. As a general principle, most providers retain participant records for at least seven years after the last service delivery, or longer if the participant was a child. Check the requirements that apply to your state and build your retention schedule into your privacy policy. When records are disposed of, they should be destroyed securely — shredded if paper, properly deleted if digital.

When notes become legal documents

Progress notes can be subpoenaed as evidence in legal proceedings — including investigations by the NDIS Commission, coronial inquiries, civil claims, and criminal matters. This is not meant to frighten you, but to underline why accuracy matters. A note written in the heat of the moment, with language that sounds dismissive or judgmental, can be read very differently in a formal context months or years later. Write every note as if a judge might read it. Not because it's likely — but because that standard produces the clearest, most professional record.

Making note-writing part of the shift routine

The hardest part of good note-writing is not the skill — it's the habit. By the end of a long shift, the temptation to write something quick and move on is very human. Here are some practical ways to build the habit into the shift structure:

• Write notes at the end of each support task, not just the end of the shift — If you're supporting someone for four hours across different activities, jot a few words about each activity as you go. It's faster and more accurate than trying to reconstruct a whole shift from memory.
• Use voice-to-text for a rough draft — Many workers find it easier to speak their notes than type them. Use your phone's voice-to-text function to capture the rough version, then tidy it up before submitting.
• Set a rule: notes before you leave the shift — Whatever system you use, the note should be written before the support worker leaves. Notes written the next day are less accurate and look worse in an audit.
• Review your own notes occasionally — Once a month, read back through your own notes for one participant. Are they telling a coherent story? Would someone unfamiliar with this person be able to understand what's been happening? If not, that's your calibration check.

Good notes are a habit, and habits get easier with the right tools. Get them right and you've turned a chore into your best protection.