Adult Day Program Software: Attendance, Ratios and T2025 Units

Short answer: Most adult day program software is built for adult day health — an elder-care model where attendance, meals and nursing oversight are the record. I/DD day habilitation is a different problem: the same group attendance has to become individually billable units, staffing ratios have to be evidenced rather than asserted, and every unit has to trace back to a participant's own service plan. Before you buy, check how the system turns one group into many defensible individual records.

"Adult day program" covers two models that look similar from the outside and bill nothing alike.

Adult day health serves primarily older adults. The centre provides supervision, meals, activities and often nursing oversight. The documentation record is largely attendance plus health monitoring.

Day habilitation serves adults with intellectual and developmental disabilities. Attendance matters, but it is not the product. The product is progress against an individual service plan, delivered in a group setting, billed in units, and audited participant by participant.

Vendors in this category mostly come from the first world. That is fine until an auditor asks you to show which goal was worked on, by whom, at what staffing ratio, for a specific person on a specific Tuesday.

The distinction that decides which software fits

If your program is the right-hand column, software from the left-hand column will take attendance beautifully and leave you assembling the rest by hand.

The three places day programs actually break

1. Group attendance that must end as individual records

A day program documents dozens of people at once, in groups that reshuffle through the day. The natural workflow is a group roster. The billing and audit requirement is individual records.

Systems that stop at the roster push the gap onto staff, who reconstruct individual notes at the end of the day or the end of the week. Reconstructed documentation is where units go missing and where goal notes quietly become copies of each other.

What to check in a demo: take attendance for a group, then ask to see what came out the other side. You want one action by staff producing separate records per participant, each attached to that person's own plan — not a roster you have to decompose later.

2. Staffing ratios as evidence, not assertion

Supervision requirements are a condition of the service. In an audit, "we maintained the ratio" is a claim; the system either evidences it or it does not.

Ask how the platform captures who was supervising which group, for which part of the day, and what happens when a staff member covers two groups or leaves early. A ratio recorded once at the top of the day, and never again, describes an intention rather than a day.

3. Units that survive partial days and absences

Real program days are ragged. People arrive late, leave for appointments, go home ill, or are absent entirely. Units have to follow what actually happened.

This is a common source of clean-claim problems in day programs, and it is worth being specific in a demo: ask the vendor to bill a participant who attended two hours of a six-hour day, and a participant who did not attend at all. Watch whether the system produces the right answer on its own, or whether someone has to remember to adjust it.

For how this connects to the rest of the revenue cycle, see billing and claims.

What T2025 changes about the software question

In Colorado, day habilitation is billed under the waiver using T2025. The code itself is simple enough; what it implies for a documentation system is not.

Each billed unit needs a chain behind it: an attendance record showing the participant was present, for how long, at what staffing ratio, with documentation written against that participant's ISP goals, signed by the staff member who delivered it. An audit follows that chain backwards.

The practical software question is whether that chain is produced automatically by the act of documenting, or assembled afterwards from separate places. Systems that keep attendance, goals and billing in different modules can absolutely produce the chain — but usually only when someone has time to reconcile them, which is exactly when audits find gaps.

Our page on day habilitation software for Colorado providers covers how we handle T2025 units, group attendance and ratios specifically. Agencies delivering both day programs and in-home services should also look at HCBS waiver software, because keeping one participant's residential, personal care and day program records on a single timeline is much harder to retrofit than to start with.

Questions to ask any adult day vendor

Ask all of these, of everyone, including us.

• Was this system built for adult day health, day habilitation, or both? What changed to support the second?
• Show me group attendance becoming individual billable records, in one workflow.
• How do you capture staffing ratios through a day, not just at the start of it?
• Bill me a two-hour attendance on a six-hour day, and an absence. Show me both claims.
• Where does ISP goal documentation happen — during the program day, or afterwards?
• What does an auditor see when they ask for the evidence behind one billed unit?
• Does documentation work when the building's connectivity drops?
• Which states' waiver billing rules are built in, and which are configured by us?
• What can we export if we leave, in what format, and at what cost?

The export question tells you as much about a vendor as any feature answer. So does asking which model the product was originally built for — the honest answer is often "the other one, and here is what we added."

Where OutcomeGrid fits

We build for Colorado I/DD, HCBS waiver and self-direction agencies specifically rather than for every state and every program type at once. For day programs that means group attendance that splits into individual billable records, staffing ratios captured as the day actually runs, ISP goal documentation written during the program rather than reconstructed after it, and T2025 unit handling including partial days and absences.

It also means we are the wrong answer for a pure adult day health centre serving older adults under state plan rates. That is a real product, and it is not this one.

We run in our managed private cloud, on your own server, or fully air-gapped, with the same functionality in each deployment.

If you are evaluating systems, bring one of your program days — a real one, with the late arrivals and the early departure — and we will document and bill it in front of you.