Practical guide · Documentation
DSP progress notes: examples and writing guidelines.
Published 2026-10-27 · Updated 2026-10-27
A DSP progress note, also called a daily note or shift note, records the support a direct support professional provided, how the person responded and what the next person needs to know. Good notes are factual, specific, tied to the person's plan and written during or right after the shift. The examples below use invented people.
Your people verify facts, correct AI drafts, sign records and approve consequential actions.
Read the guide ↓30 days free · Then $20 USD per person supported per month.
$0 setup for system initialization · Month-to-month · No long-term contract
Migration scope and costs are separately agreed.
Key points
The short version.
- Include the service, time, plan goal, support given and response.
- Write observable facts, not labels or guesses.
- Record the prompt level your plan defines.
- Record refusals respectfully as the person's choice.
- Report health changes and incidents through the required route.
- Never copy a note from another day.
01 · Documentation
What a progress note is for.
A progress note does several jobs at once. It tells the next shift what happened. It shows progress, or the lack of it, on the goals in the person's support plan. It documents the service your agency bills to Medicaid. And it is part of the person's legal record, read by supervisors, case managers, surveyors and sometimes courts.
Because so many people rely on it, a note has to stand on its own. Someone who was not there should be able to read it and understand what support was given and how the person responded.
02 · Documentation
What to include in every note.
Your agency and state set the required fields, so follow your template first. Most programs expect the same core facts.
- Date, start and end time, service and location.
- Your name, credentials if any, and signature.
- The plan goal or outcome you worked on.
- What you did: the support, teaching or prompts you provided.
- How the person responded, in observable terms and in their own words where it helps.
- Health, safety, mood or behavior changes you observed.
- Anything that needs follow-up and who you told.
03 · Documentation
Write what you saw and heard, not what you assume.
Describe behavior you can observe instead of labels or guesses about feelings. "Was agitated" is an interpretation; "raised his voice, said 'leave me alone' and walked to his room" is an observation another person can picture.
Use neutral, respectful, person-first language. Write about the person as you would want to be written about. Leave out other people's names; refer to another person served by initials or a role only if your agency allows it, because their information belongs in their own record.
- Avoid: "good day", "fine", "noncompliant", "attention-seeking".
- Use: what the person did and said, the time, and the support you gave.
- Separate facts from your next-step recommendation.
04 · Documentation
Example 1: a community goal.
Weak: "Took J. to the store. Good outing."
Stronger: "10:00–11:30 a.m. Community integration, goal: J. will choose and pay for items independently. J. made a list of three items at home with one verbal prompt. At the grocery store he found two items on his own and asked a staff member where the bread was. At checkout he counted out $12 and waited for change without a prompt. J. said, 'I did it myself.' Next step: practice asking store staff for help, as written in his plan."
05 · Documentation
Example 2: a daily living skill with prompt levels.
Record the level of help as your plan defines it, such as independent, verbal prompt, gestural prompt, model, partial physical or full physical assistance.
"5:00–5:45 p.m. Meal preparation, goal: M. will prepare a simple meal with no more than two verbal prompts. M. washed her hands and gathered the pasta, pot and strainer independently. She needed one verbal prompt to turn the burner down when the water boiled over and one gestural prompt to use the oven mitt for the strainer. She served herself and a housemate. Two verbal prompts, one gestural prompt; goal met at the verbal-prompt level."
06 · Documentation
Example 3: a refusal.
A refusal is information, not a failure, and the person's choice should be recorded respectfully.
"2:00 p.m. Exercise goal: walk 15 minutes. Offered a walk at 2:00 and 2:30. T. said, 'Not today, my feet hurt,' and stayed on the couch. Checked his feet with his permission; no redness or swelling observed. Offered a seated stretching video instead; T. did 5 minutes. Told the house supervisor about the foot comment at 2:40 p.m. for follow-up."
07 · Documentation
Example 4: a health observation that needs follow-up.
"7:15 a.m. During morning routine R. coughed several times and said her throat hurt. Temperature 99.8°F at 7:20 a.m. using the house thermometer. Ate half her usual breakfast. Reported to the on-call nurse at 7:30 a.m. per agency procedure; nurse instructed to recheck temperature at 11:00 a.m. and call back if over 100.4°F. Rechecked 11:00 a.m.: 99.4°F. Information passed to day shift at 3:00 p.m."
If something meets your agency's definition of an incident, such as a fall, injury, medication error or allegation, write the incident report your policy requires as well. A progress note does not replace it.
08 · Documentation
Mistakes reviewers flag most often.
Reviewers comparing notes with billing and plans tend to find the same problems across agencies.
- Copied notes that are identical from day to day.
- Times that do not match the schedule, the time record or the service billed.
- No link to a plan goal, so progress cannot be shown.
- Vague words and opinions instead of observations.
- Notes written days later, or by someone who was not there.
- Errors erased or overwritten instead of corrected the way your agency's policy allows.
09 · Documentation
Templates and software.
A good template asks for the fields above in order, so nothing is forgotten. Software can also prompt for the plan goal and keep the note next to the person's schedule and plan.
In LunahUP, staff record the observations and service facts, and AI prepares proposed note wording from those facts. The DSP reviews the draft, corrects or rejects it and signs; AI does not decide what happened or sign anything.
Questions people ask
Short answers.
How long should a DSP progress note be?
Long enough to show the service, the plan goal, the support given and the person's response. That is often a short paragraph per service; follow your agency's template and required fields.
When should I write my progress notes?
During the shift or right after it, while details are fresh. Late notes are less accurate and reviewers often question them. Follow your agency's deadline.
Is a progress note the same as an incident report?
No. A progress note records the support and response for the shift. A fall, injury, medication error or allegation usually also needs the incident report your agency policy requires.
Can I use abbreviations in progress notes?
Only those on your agency's approved list. Unclear abbreviations make a note hard for reviewers and other staff to read.
Can AI write DSP progress notes?
In LunahUP, AI prepares proposed wording only from the facts staff provide. The DSP checks it, corrects or rejects it and signs; AI does not decide what happened.
Sources
Check the official source.
Requirements change and differ by state. Confirm current rules with your state agencies and payers.
Keep the work connected
Related LunahUP workflows.
Start with one recurring task
Bring the note your supervisors keep sending back.
Inspect a fictional note draft prepared from staff facts, and the review and signature before it is saved.
Book a 30-minute compliance demoUse sample data. No patient or employee records needed for the demo. Booking does not create an account or start billing.