Guides · Minnesota
245D progress note template and writing guide.
A copy-ready note structure, a realistic good-vs-weak example pair, and the habits that make notes hold up when someone else reads them.
The template: five parts every note needs
Minnesota’s 245D licensing statute (Minn. Stat. ch. 245D) expects service documentation that connects what staff did to the person’s support plan. You do not need a complicated form to meet that expectation. You need five parts, in roughly this order, every time:
- Date and time of service — the actual start and end, not the scheduled shift. This is also what your EVV record and any billed units must line up with.
- Service provided, tied to a support plan outcome — name the outcome or goal from the person's support plan that this visit worked on, not just the service category.
- Objective observations — what you saw and heard, in concrete terms. What the person did, what prompts or supports you provided, what changed from prior visits.
- The person's response — how they engaged, what they said, whether they declined anything, and any preference they expressed. Their voice belongs in the record.
- Staff signature and date — who wrote it and when. In electronic systems, an authenticated entry with a timestamp serves the same purpose.
Print that list, tape it inside the binder, or build it into your documentation system as required fields. The structure is the easy part. The rest of this guide is about the writing itself, which is where notes usually fail.
A good note next to a weak one
Here is the same visit documented two ways. Both are realistic. Only one would survive a licensing review or a billing audit with its credibility intact.
The weak note:
“Provided ILS services. Client did well today. No issues to report. Will continue per plan.”
This note has a service category and a mood, and nothing else. It does not say when the service happened, which outcome it addressed, what the staff actually did, or how the person responded. It could be pasted onto any date for any person. That is exactly what a reviewer will suspect.
The good note:
“[Date], 4:00 to 6:00 p.m. Worked with the person on the meal-planning outcome in their support plan. The person chose a recipe, wrote a grocery list with two verbal prompts, and measured ingredients independently. They needed one verbal reminder for stove safety, which is less support than the hand-over-hand assistance documented earlier this month. The person said they enjoyed the meal and want to cook it again for a family visit. Signed, staff name, [date].”
Same visit, same length of shift, a few extra sentences. The good note ties the time to the service, the service to an outcome, and the outcome to observable progress. It also captures the person’s own response, which is the point of person-centered documentation in the first place.
Rules of thumb that keep notes defensible
Structure gets you a complete note. These habits get you a credible one:
- Write the same day the service happened. A note is a record of the visit, not a memory exercise performed at the end of the week.
- Never copy-paste across days. If two notes are identical, a reviewer reads both as evidence that neither describes a real visit.
- Describe, do not diagnose. Write what you observed — words, actions, prompts given — rather than clinical-sounding conclusions you are not qualified or positioned to make.
- Keep corrections visible. Line through and initial on paper; use append-only edit history in software. Never erase, white out, or silently overwrite.
- Match the note to the clock. The times in the note should agree with schedule, EVV visit data, and timesheet. Contradictions between systems are what auditors look for first.
- Put the person's voice in the note. What they chose, said, declined, or asked for. Notes that never mention the person's response read as staff-centered, not person-centered.
Why this connects to billing integrity
Progress notes are not just a licensing artifact. They are half of the evidence that a billed service actually happened. When an agency bills for a visit, the claim asserts that a specific service was delivered to a specific person for a specific span of time. The progress note is the narrative record of that assertion, and the EVV record is the electronic one. Under the Cures Act, an EVV-verified visit captures the type of service, the individual receiving it, the individual providing it, the date, the location, and the time the service begins and ends. A reviewer can place your note beside that record and check whether they tell the same story.
When they do not — a note dated after the billed visit, notes that read identically across a week, times that drift between the note and the visit record — the problem stops being a documentation nitpick and starts looking like a billing problem. That escalation is avoidable. Same-day notes, no copy-paste, and visible corrections are the entire prevention program, and they cost nothing but discipline.
Minnesota’s EVV expectations are tightening on their own schedule, and the documentation habits above are what make those records agree with your notes. If you want the current thresholds and dates, they are covered in our Minnesota EVV requirements guide.
Common questions
Do progress notes have to be written the same day as the service?
Write them the same day as a working rule. A note written days later is a reconstruction, not a record, and reviewers notice the difference. Same-day notes capture what actually happened while it is fresh, keep the timestamp on the note consistent with the visit, and remove the awkward question of what the note was based on. If a note is genuinely late, date it honestly rather than backdating it.
Can I copy a note from a previous shift and edit it?
Do not. Copy-paste notes are one of the fastest ways to lose credibility in a review, because identical language across days signals that nobody documented what actually happened on each date. Two visits are never identical: the person responded differently, the activity varied, prompts changed. If your notes could be swapped between dates without anyone noticing, they are not doing their job as evidence of service delivery.
How do I fix a mistake in a progress note?
Corrections must stay visible. On paper, the convention is a single line through the error, the correction beside it, and initials and date, so the original text remains readable. In software, use a system that keeps an append-only history of changes rather than silently overwriting the record. What you want to avoid is any correction that makes the original entry disappear, because a record that can be rewritten quietly is worth less as evidence.
How long should a 245D progress note be?
Long enough to answer four questions: what service was provided, how it connects to the person’s support plan outcome, what you observed, and how the person responded. That is usually a short paragraph, not a page. Length is not the measure of quality; specificity is. One concrete, dated, outcome-linked paragraph beats a long note full of generic phrases like “client did well” that could describe any visit.
Where ClientCentric fits, plainly
ClientCentric is operations software for 245D and HCBS agencies, and case notes are one of its core features: notes follow a locked lifecycle, corrections live in an append-only audit history, and visit documentation runs alongside EVV workflows so the note and the visit record stay in agreement. It will not write good notes for your staff, and no software makes an agency compliant by itself. What it does is make the habits on this page — same-day entry, visible corrections, notes that match the clock — the default instead of a discipline problem.
Keep reading
- Case notes with a locked lifecycleHow ClientCentric structures notes, corrections, and append-only history.
- Minnesota EVV requirementsThe current thresholds, dates, and the HHAeXchange aggregator explained.
- 245D compliance checklistThe broader documentation and operations checklist this template plugs into.
Written and maintained by the ClientCentric team from the working product. Last reviewed . Based on documentation expectations under Minn. Stat. ch. 245D and federal EVV requirements. This is a general template and writing guide, not legal advice; confirm current requirements with your licensor.