Record participation rather than just presence
Attendance establishes when someone was present. Participation describes the activities they chose, the supports provided and how they engaged. Keep these measures separate so program reports do not confuse time on site with individualized outcomes.
The underlying problem
A participant can be present for six hours without engaging in a meaningful activity. Attendance records are necessary for many operations, but they answer a different question from whether the person had opportunities to participate, make choices, and work toward their own goals.
A practical approach
Separate presence, opportunity, participation and outcome. A useful activity record identifies what was offered, whether the person chose to participate, what assistance was needed, and what mattered to the individual. Do not turn declining an activity into a failure: choice is itself relevant context.
A realistic example
At a gardening group, a participant might choose to observe rather than plant. Recording only 'did not participate' misses that they selected the activity, watched for twenty minutes, and discussed the plants with staff. The more useful record respects the choice without inventing goal progress.
How to test whether the change works
Audit ten anonymized activity records. Can a supervisor tell which activity was offered, whether the person made a choice, what support was provided, and whether the entry relates to an approved goal? If not, revise the prompts and train with contrasting examples.
Boundaries and responsibilities
Do not use attendance or activity counts as a substitute for person-reported experience. Review patterns with the person and their support team, and follow the specific program's required service verification rules.
Where KinNotice fits
Structured participation notes and goal context are areas KinNotice is designed to support; it is not a replacement for payer attendance or billing records.
Questions to bring to your next team meeting
- What information is repeatedly missing when responsibility passes from one person to another?
- Which existing record is authoritative, and where is information being duplicated?
- How will we know the proposed change helps the person receiving support rather than merely producing more documentation?
- Who is responsible for reviewing exceptions, privacy boundaries and unresolved follow-up?
Further reading and standards
For person-centered planning and HCBS operations, consult CMS HCBS training resources. For communication and transitions, see AHRQ transitions-of-care resources. These resources provide general context; check the requirements that govern your own program.
Explore the KinNotice DSP documentation guide and software evaluation checklist for complementary workflows.
Discuss your documentation challenge
Tell us where information gets lost or repeated in your current process. KinNotice is exploring more useful everyday documentation and care coordination, and we'd value the opportunity to understand your team's needs.
Discuss an organization workflow