What a Clean Day in Day Hab Looks Like in the Data

Short answer: A clean day in day habilitation is one where every 15-minute unit you bill can be traced, without anyone reconstructing anything, to a record that shows when the activity started and ended, who delivered it, what the activity was, which goal in the member's Person-Centered Support Plan it served, and whether it was a group day, a one-to-one block or a telehealth session. If the record carries those fields as the day happens, the claim writes itself and the audit reads itself. If any of them is added afterwards, from memory or from the schedule, the day is not clean, however good the program was.

This guide uses Colorado's current HCBS rule, 10 CCR 2505-10 § 8.7000, as the worked example. The section numbers and the unit caps are Colorado's. The shape of a defensible record is the same anywhere day habilitation is billed in units.

What day habilitation is in Colorado's rule

Under § 8.7517, Day Habilitation is a benefit of the Developmental Disabilities and Supported Living Services waivers. It covers three kinds of habilitative service: Specialized Habilitation (SH), delivered out of a non-residential setting the agency runs; Supported Community Connections (SCC), delivered in the community alongside people who are not paid to be there; and Prevocational Services, which follow the supported employment rules. SCC may be provided in a group or one-to-one, as identified in the member's Person-Centered Support Plan, and activities that are purely recreational are not a benefit and are not reimbursed (§ 8.7517.B.2).

Two limits shape the data before anyone bills a unit. Services may not be delivered virtually 100% of the time, and an SH provider must keep a physical location where in-person services are offered (§ 8.7517.C.2). And the rule expects integrated employment to be considered the primary option for everyone receiving day habilitation (§ 8.7517.D.2), which is why a clean record also shows what the member is working toward, not only what they attended.

The fields every unit needs

Two sections of the rule describe the record. Section 8.7405.A.1 lists what HCBS documentation must contain for incremental units of service. Section 8.7517.D.1 adds what day habilitation providers must keep on top of that. Put together, they describe a record that most paper systems only approximate.

Notice that the rule asks for the goal, not for a paragraph about the goal. A clean record names the goal from the plan and says what happened against it. A note that reads well but mentions no plan goal is the most common way a well-run day fails on paper.

Units, caps and tiers: the arithmetic the record has to respect

One unit is fifteen minutes of service (§ 8.7517.E). The caps are set per support plan year and they are combined caps, so the day habilitation record has to be read alongside prevocational and supported employment units:

Colorado also bills day habilitation in three tiers, and the tier is a fact about the day that the record has to carry:

That last line is where arithmetic enters the day. A member who has a Tier 3 block in the morning and joins the group in the afternoon has two differently priced services on one day, and an annual dollar limit that both of them count against. A record that stores "attended 9 to 3" has lost the information the claim needs.

The rule does not set a fixed staff-to-member ratio for day habilitation. The tier and the plan do: a Tier 3 block is 1:1 by definition, and a Tier 2 group is whatever the plan and the program design say it is. That is exactly why the ratio belongs in the record rather than in the policy manual. Staffing that is asserted in a document nobody updates is not evidence; staffing recorded for the block, with the names, is.

A clean day, hour by hour

Here is what the data looks like when the day is recorded as it happens, for one member on a Developmental Disabilities waiver whose plan includes a Tier 3 community block.

8:55 Check-in at the center. The member's record opens with the date, the arrival time and the staff member who signed them in. Nothing is billable yet; the first unit starts when the first activity starts.

9:00 to 10:30 Specialized Habilitation, group, Tier 2. The activity is a kitchen skills session. The note names the plan goal it serves, say "prepare a simple meal with decreasing prompts," and records what happened against it. The six units carry the setting (the center), the lead staff member and the activity.

10:30 to 12:00 Supported Community Connections, one-to-one, Tier 3. One staff member takes the member to a volunteer shift at a food bank. The record shows the location, the named staff member, the 1:1 tier, the plan goal ("participate in a community role with natural supports"), and six units at the Tier 3 rate, counted against the member's individual annual limit.

12:00 to 12:45 Lunch. If no habilitative service is delivered, no units are recorded. A clean record is comfortable with gaps.

12:45 to 2:10 SH group again, Tier 2. At 2:10 the member becomes unwell and a family member collects them. The record shows the end time as 2:10, not the scheduled 3:00, so the units are five and not nine, and the change in condition and the action taken are written on the same record under § 8.7405.A.1.e, where an auditor will look for them.

End of day The program manager sees the day as a list of blocks with tiers, not as a single attendance tick. The claim for the day is generated from those blocks. The running total for the plan year moves by eleven units for day habilitation, and the Tier 3 dollar amount moves by the morning block only.

Nothing in that day required a second document. That is the test.

Five places the data goes wrong

1. Attendance on paper, transcribed later. The transcription inherits the schedule, not the day. Early departures and late arrivals disappear, and with them the units that should not have been billed.
2. One group note copied to every member. Twelve identical notes prove that a group met. They do not prove that any one member's plan goal was worked on, and § 8.7517.D.1 asks for the goal per member.
3. Tier recorded by default. A 1:1 community block logged as a group day is under-billed; a group day logged as 1:1 is over-billed and over-counts the annual dollar limit. The tier has to be chosen for the block, not inherited from the program.
4. Recreation billed as habilitation. An outing with no plan goal attached is, in the words of the rule, "provided exclusively for recreational purposes," and is not reimbursed (§ 8.7517.B.2.b.v). The goal field is what separates a community connection from a trip.
5. The condition change filed somewhere else. The seizure goes into an incident system, the early pickup into the attendance sheet, and the units into billing. Three systems, three stories. The rule wants the change and the action on the service record itself.

What to look for in day habilitation software

• Group attendance that becomes individual records. Staff check a group in once; the system produces one record per member with its own times, tier, staff member and goal.
• Start and end times from the clock, with per-member departures. Units are computed from recorded times, and a member leaving at 2:10 changes that member's units and nobody else's.
• Tier and setting on every block. Group, one-to-one or telehealth is chosen for the block, and the Tier 3 dollar counter moves only for the 1:1 blocks.
• Plan goals inside the note. The note is written against the member's current Person-Centered Support Plan goals, selected from the plan rather than typed from memory.
• Running totals against the caps. The plan-year unit count for day habilitation plus prevocational, the cumulative count with supported employment, and the individual Tier 3 dollar limit are visible before the claim is created, not after a denial.
• Condition changes on the same record. A refusal, an illness or an incident is written where the units are, and still feeds the incident workflow.
• Claims generated from the blocks. What is billed is what was recorded, in the same units, with the documentation attached to the claim line.

Where OutcomeGrid fits

OutcomeGrid was built for programs that document many people at once against plans that no two of them share. Attendance is taken at the group level and split into individual, billable records automatically, with per-member check-in and check-out. Staff document once, against the member's own plan goals, and the record carries the staffing for the block, the activity and the progress noted. Units are tracked with partial-day and absence handling, and the Medicaid waiver claim is generated from documented attendance, with denial management on the same record.

Agencies that run day habilitation alongside residential or in-home services keep all of it on one member timeline, and the platform runs in our managed private cloud, on your own server, or fully air-gapped.

If you want to see a day program recorded this way with your own service codes and tiers, we will walk through one with you.