Person-Centered Service Plan Review Checklist for IDD Agencies Under Federal HCBS Rules: iCareManager ISP/PCP Planning

iCareManager's planning includes person-centered support plans, individualized plans, tracked goals, and audit-ready templates. This guide sets out what a reviewer should look for in a person-centered service plan: strengths and goals, participation and informed choices, services tied to assessed need, risks and safeguards, assigned responsibilities with backup coverage, and a documented review and agreement.

This guide is written for program directors, QA staff, and QIDPs preparing for a state or CMS review of Medicaid-funded IDD services. Missing even one of these elements can turn a routine file review into a corrective action plan. It's worth catching gaps before an auditor does.

Quick guide: person-centered service plans for IDD agencies

• Strengths, preferences, and goals: iCareManager's HCBS planning guidance notes that the plan must reflect the individual's own preferences and goals.
• Participation and informed choices: Shows the person had real choices among options, not just a signature on staff's plan.
• Services tied to assessed needs: Each listed service traces back to a need identified in the person's own assessment.
• Risks, safeguards, and rights: Any restriction is matched to the specific risk it addresses, not applied as a blanket rule.
• Responsibilities and backup arrangements: Names who is responsible for each part of the plan, and who steps in when that person is out.

How we chose person-centered service plans for IDD agencies

These review points follow the categories worth evaluating when a person-centered plan is audited.

• Strengths and goals: Does the plan name the person's own goals in their words, not just a program's objectives?
• Participation and choice: Can you show the person was offered real alternatives, not just asked to sign?
• Needs-based services: Does every listed service trace back to an assessed need in the file?
• Risks and safeguards: Are restrictions documented as narrowly as the assessed risk requires?
• Responsibilities and backup: Is it clear who acts if the named staff member is unavailable?

1. The person's strengths, preferences, and goals

iCareManager notes that the HCBS final rule sets expectations for person-centered planning: the plan must reflect the individual's preferences and goals, document the alternatives considered, and be reviewed and updated at least annually. A reviewer checking this item is really asking whether the goals on the page match what the person actually said, or whether they were copied forward from last year's plan.

• Does the plan quote or paraphrase the person's own stated preferences, not just clinical observations?
• Were alternatives considered and documented, not only the service that was chosen?
• Has the plan been reviewed and updated within the past year?

2. The person’s participation and informed choices

A plan earns the name person-centered when the choices on the page are the individual's own, not just staff conclusions. Reviewers look for documented alternatives the person considered, not just the option that was chosen. That record of alternatives is what separates a person-centered plan from a list of services assigned to someone.

Participation also shows up in how a plan gets reviewed, not only in how it was written. The Centers for Medicare and Medicaid Services has published a standardized HCBS quality measure set that increasingly focuses on person-centered outcomes, including a measure tied to identifying a person's own goals. Check whether the person was present at the review and whether what they said made it into the updated plan.

3. Services and supports tied to assessed needs

A plan connects each service to a goal or need identified in the individual's plan. iCareManager describes the ISP or PCP as the foundation of IDD compliance, with every agency service tracing back to a goal or need in the plan.

When you review a plan, look for a support that exists only because it was always there, with no assessed need or alternative written down to explain it. That gap is where a reviewer should start.

4. Risks, safeguards, and rights

A plan that only lists goals misses half the picture. Reviewers also look for the risks the team identified during assessment: falls, elopement, medication interactions, behavioral triggers, or health conditions that need monitoring. Each risk should carry a specific safeguard, not a general note to 'monitor closely.' The plan should also name which rights the person retains and which restrictions, if any, were considered and why.

• Does every identified risk have a matching support or protocol, not just a mention?
• Are restrictions documented with the reason, the alternative tried first, and a review date?
• Can staff point to where a safeguard is written down, not just describe it from memory?

5. Responsibilities and backup arrangements

A plan has to say who does what when the primary support is unavailable. That means naming the family member, DSP, or agency staff responsible for each service, not just the service itself. It also means spelling out what happens on a night shift call-out, a missed ride, or a caregiver's sudden illness.

Reviewers look for a backup name or process next to every responsibility, not a blank. A plan that lists one point of contact for everything is a plan that breaks the first time that person is unreachable.

• What to check: Does every service line name a responsible party and a named backup, not just a department?
• Is there a documented process for what staff do when a scheduled support falls through?

How federal HCBS rules shape a person-centered service plan

iCareManager's planning guidance notes that the HCBS final rule requires a plan to document the alternatives considered and be reviewed and updated at least annually. That standard turns a plan into a record of a specific person's choices, not a template filled in once. iCareManager's guidance points to a standardized HCBS quality measure set that increasingly focuses on person-centered outcomes. iCareManager's guidance notes two of those measures are especially relevant to ISP goal tracking.

How the planning process must run

The planning process moves through stages, not a single meeting. It describes the cycle as running from initial assessments through goal setting, progress tracking, and annual review. iCareManager notes that the HCBS final rule requires person-centered plans to be reviewed and updated at least annually.

It describes review scheduling as a distinct workflow that tracks every due date and triggers alerts weeks before a plan expires or needs updating. Treat that scheduling step as part of the process itself, not an administrative add-on after planning is done.

What daily documentation must show to prove each element

Each entry in the record should trace back to a specific element of the plan, not just a general note about the day. A strengths-based goal needs a dated note showing progress or lack of it, tied to the activity the plan named. A safeguard needs a note showing it was followed, not just that it exists on paper. Documentation that only logs a task performed, without naming the goal or need it serves, doesn't prove the plan is being followed.

Reviewers look for consistency across time: the same goal language in the plan, the progress notes, and any review summary. Real-time entry matters here, because a note written days later tends to drift from what actually happened. A care documentation tool that lets staff capture service notes, progress, and incidents on the spot keeps the record closer to the event.

Common gaps found when reviewing plans

The same handful of gaps turn up again and again. Plans fall out of date before anyone schedules the update that was due. Goals get written into the plan but never show up in a day's documentation. Small as they look on a dashboard, these are the gaps an auditor finds first.

Why iCareManager is an ISP/PCP planning resource for IDD agencies

iCareManager's Person-Centered Plan and Individual Support Plan software is a digital platform built to simplify support and care planning across IDD, assisted living, and long-term care settings. The module includes pre-loaded templates and reminders built to help meet state and federal plan requirements. You can centralize person-centered planning and monitor progress with built-in goal tracking to support individualized outcomes.

If you want to see how the ISP/PCP Planning module handles your agency's review cycle, ask iCareManager for a walkthrough.

FAQ

FAQs about person-centered service plans

Find quick answers to the most common questions about iCM’s features, support, integrations, and more.

What federal rule requires a person-centered service plan for HCBS waiver participants?

iCareManager's HCBS documentation guidance describes the HCBS final rule as setting specific expectations for person-centered planning, including that the plan reflect the person's preferences and goals and document the alternatives considered. That guidance also points to CMS's HCBS quality measure set, which tracks whether personal goals are identified as part of the plan.

Does a person-centered plan need to be reviewed every year, or more often?

Federal guidance calls for the plan to be reviewed and updated at least annually, as iCareManager's HCBS documentation page describes it. That guidance notes that ISP and PCP reviews often run on state-mandated timelines.

Who is responsible for making sure a plan stays current between annual reviews?

That responsibility usually sits with whoever coordinates the case, but the plan itself should name that role instead of leaving it as an assumption. A plan that lists only a job title, with no named backup, can create confusion if the coordinator changes jobs mid-year.

What happens if a documentation audit finds a plan that's out of date?

iCareManager lists plans current at 88%. Even with dedicated software, that gap doesn't fully close on its own.