Documentation

Why "provided support" fails review — and what to write instead

It is the most common phrase in Colorado host home documentation and one of the most reliable ways to lose a unit. Here is what a reviewer sees when they read it, and three sentence patterns that hold up.

Nobody writes "provided support" out of laziness. They write it because it is true, because it is late, and because the note has to be finished before the shift ends. It describes a real thing that really happened.

It also documents nothing.

What a reviewer actually sees

When a surveyor or a post-payment reviewer opens a daily note, they are answering a short list of questions: Was a billable service delivered? Was it the service that was authorized? Is it tied to this person's plan? Did the caregiver describe it specifically enough that someone who wasn't there can tell it happened?

"Provided support with daily living activities" answers none of them. It could describe any person, on any day, in any home in Colorado. And when the same sentence appears in the same person's record on Monday, Tuesday, and Wednesday, it produces the worst inference available to a reviewer: that the note was copied rather than written, and therefore that nothing in the record can be trusted to reflect the actual day.

A generic note doesn't just fail to prove the service. It calls the notes around it into question.

That is the part agencies miss. A single vague note is a minor finding. A pattern of vague notes is a systemic documentation finding — and systemic findings are what get extrapolated across the sample.

The three things every note has to carry

Whatever your format, a defensible daily note contains three elements. Most failing notes have the first and are missing the other two.

  1. The activity. What specifically happened, with enough detail to place it in time and space.
  2. The support given. What the caregiver actually did — the billable act, not the presence.
  3. The person's response. How this individual reacted, participated, or progressed. This is what makes the note individualized, and it is the element auditors find missing most often.

The third one carries disproportionate weight. Activity and support can be inferred from a schedule. The person's response can only come from someone who was actually there, which is precisely why it is the strongest evidence that the service occurred as billed.

Three patterns that hold up

Pattern 1 — Activity, support, response

Fails review

"Provided support with meal preparation."

Holds up

"Made dinner with D. — she measured the rice and set the timer while I handled the stove. She asked to do the timer herself this time, which is new. Ate a full portion, no coughing."

The second version names the activity, states exactly what the caregiver did versus what the person did, and reports a response that no schedule could have predicted. It also quietly documents a swallowing observation, which matters if there is a dysphagia plan in the record.

Pattern 2 — Tie it to the goal

Fails review

"Worked on community goals. Went out in the afternoon."

Holds up

"Grocery run at King Soopers, 3:00–4:15. D. counted out the cash at checkout and got the change right without prompting — second time this week on goal #1. Chose the applesauce flavor herself."

When a note names the plan objective it advances, it stops being a narrative and becomes evidence that authorized services were delivered as authorized. This is the connection reviewers look for and rarely find.

Pattern 3 — Document the exception, not just the routine

Fails review

"Medications given as prescribed."

Holds up

"Morning meds at 8:02, all taken with breakfast. D. refused the evening sertraline — said it makes her stomach hurt. Recorded as refused, told Robert, she agreed to try it with food tomorrow."

Agencies get cited for unreported refusals far more often than for refusals. A documented refusal with a reason is a functioning system. A silent gap in the MAR is a finding. Write the exception.

What to stop writing today

These phrases are effectively invisible to a reviewer. If a sentence in your notes could be pasted into any other person's record without changing its meaning, it is not documentation:

Note that none of these are wrong. They are unfalsifiable, which in a documentary review is worse.

The practical fix isn't better writing training

Every agency has run the training. It works for about three weeks. The problem is structural: the note is written at the end of a long shift, from memory, in a blank text box, by someone whose actual job is caring for a person — not producing billing evidence.

Two changes move the number more than any workshop:

One test before you submit

Read the note and ask: could this sentence have been written about anyone else we serve? If yes, it needs one more detail — usually the person's own response. That single question, applied honestly, catches the large majority of documentation findings before they exist.

Find the generic notes before a reviewer does

Audit Shield checks every service note against A1924 and A4064 standards, flags duplicated and non-specific language while the caregiver still remembers the day, and holds billing units with unresolved problems. Book a 10-minute call and we'll run it on your own documentation.

Book a 10-minute demo

General information for Colorado HCBS providers, not legal or billing advice. Documentation requirements vary by waiver, service code, and payer; confirm specifics against current HCPF and CDPHE guidance.