Person-centered planning is one of the foundational principles of modern IDD services. It is also a federal Medicaid requirement for home and community-based services under the HCBS Settings Rule, which requires that services be based on a plan developed around each individual’s unique strengths, preferences, goals, and needs. The principle is not new. The compliance requirement is not new. What remains inconsistent across the IDD sector is whether the software agencies use actually supports person-centered planning in daily practice or simply accommodates it on paper.
The gap between the two is significant. A case management platform that treats individualized service plans as compliance documents to be completed, filed, and revisited at renewal time is not person-centered. A system that makes ISP goals visible in every service interaction, connects documentation to individual outcomes, and makes each client’s stated preferences and priorities accessible to every staff member who supports them is genuinely person-centered. That distinction matters for both service quality and compliance.
What Person-Centered Planning Actually Requires
The Centers for Medicare and Medicaid Services HCBS regulations require that each person’s service plan reflect their own goals, preferences, and strengths as identified through a planning process the person meaningfully participates in. The plan must identify the outcomes the person wants to achieve, the services and supports that will help them achieve those outcomes, and how progress will be measured.
Beyond the federal baseline, state Medicaid programs add their own requirements around ISP content, documentation timelines, and the frequency of plan updates. Many states require that case managers document evidence of the individual’s participation in developing the plan and that the plan reflect the person’s own words and priorities rather than clinical language imposed by the planning team.
What this means in practice is that a compliant, genuinely person-centered ISP is not a template with blanks filled in. It is a living document that reflects a specific person’s life, that changes as their goals evolve, and that is actively used in every service interaction to guide what support looks like for that individual.
Where Most Software Falls Short
The most common failure mode in case management software is treating the ISP as a document rather than a framework. When ISP goals live in a separate module that case managers access during planning cycles but not during documentation, the connection between what the person wants and what is happening in services is severed in daily practice. DSPs documenting service notes do not see the individual’s goals. Case managers writing progress notes are not prompted to connect observations to specific outcomes. The ISP becomes a compliance artifact instead of a guide.
A second common failure is template rigidity. Software that forces ISPs into fixed formats with predetermined categories often cannot accommodate the diversity of goals and preferences that real people bring to their planning. A person who wants to learn to make their own meals, maintain relationships with specific family members, and eventually move to their own apartment has goals that may not fit neatly into the service categories a rigid template assumes. When the software cannot represent the person’s actual goals, case managers adapt by writing documentation that fits the system rather than the person.
A third failure is documentation disconnection. When the service notes DSPs write during shifts are not linked to the specific ISP goals they are addressing, the record of what happened in services cannot demonstrate progress toward what the person wants. This is both a clinical problem and a compliance problem, because Medicaid auditors reviewing service documentation look for evidence that services are individualized and goal-directed.
What Software Needs to Do to Support Person-Centered Planning
Purpose-built case management software supports person-centered planning when it treats the ISP as the organizing framework for everything else in the system, not as one module among many.
Vertex Case Manager is built around the principle that client goals should be visible and connected throughout the system. Service notes are linked to the specific goals they address at the time of documentation, which means every service interaction creates a record that directly supports the individual’s plan. Progress tracking is organized around the outcomes the person is working toward, making it possible for case managers and supervisors to see at a glance where a client is making progress and where goals may need review.
Specific things person-centered planning software should be able to do:
- Represent goals in the individual’s own language and priority order, not just in clinical or billing categories
- Make active goals visible to DSPs and case managers during documentation so service notes are connected to outcomes
- Track progress data over time in a format that supports both clinical review and compliance reporting
- Generate periodic summaries that tell the story of an individual’s progress toward their goals rather than listing service delivery statistics
- Flag when goals have not been updated recently or when progress documentation is overdue, so plans stay current rather than becoming stale between renewal cycles
- Support the individual’s meaningful participation in planning by making their plan accessible and reviewable, not locked in a system only clinicians can access
Person-Centered Planning and Compliance
The HCBS Settings Rule compliance environment in 2026 means that agencies face scrutiny not just on whether ISPs exist but on whether they demonstrate genuine person-centeredness. State quality reviews and Medicaid audits increasingly look for evidence that:
- The individual actively participated in developing their plan
- The plan reflects the person’s stated goals and preferences rather than service availability
- Services documented align with the goals in the plan
- Progress is being measured and plans are updated when goals change
Agencies that use software where goals are documented separately from services and progress are at a structural disadvantage in these reviews. When the documentation system connects ISP goals to service notes to progress records in an integrated chain, the evidentiary record of person-centered practice builds automatically through normal operations rather than requiring manual assembly at review time.
Connect with the Vertex Systems team to see how Case Manager’s goal tracking and documentation workflows support person-centered planning in daily practice rather than just at planning time.
