ISP Part V (Plan for Supports), Section by Section

Parts I through IV of the ISP describe the person and the team. Part V — the Plan for Supports — is the part your staff actually deliver against every shift, and the part a reviewer reads most closely, because it's where the plan turns into documentable action. If Part V is vague, everything downstream (daily notes, quarterlies, billing) inherits the vagueness.

Here's what each section is for, and what a reviewer checks.

1. Individual & plan information

The basics that anchor the document: the individual, Medicaid identifier, the service and code, the plan dates, and the review schedule. A reviewer checks that the plan dates are current and that the service matches what's actually being billed. An expired plan date is an easy, common finding.

2. Provider & team

Who's responsible and who to contact — provider, the professional writing the plan, the support coordinator, and the guardian or authorized representative. Reviewers check that the guardianship status is accurate, since it drives who signs.

3. Objectives (or outcomes)

The measurable results the supports are working toward. Each should be specific enough that a DSP knows what "progress" means and a reviewer can tell whether it's being achieved. "Improve independence" is not reviewable; "order and pay for a meal with verbal prompting only" is.

4. Desired outcomes & life areas

What the individual wants, mapped to the life area it serves (community living, safety, health, employment, and so on), plus the key steps to get there. This is where the plan proves it's person-centered — the outcome should read like the individual's goal, not the provider's checklist.

5. Activities

The concrete activities that build toward each outcome: what staff do, what to record, how often, and by when. This is the bridge between the plan and the daily note — the activities named here are what the daily note documents against.

6. Essential supports & risks

The identified and potential risks, and the routine supports, each with how often it applies, how staff support it, and the dates it's in effect. This is the section reviewers use to check that documentation matches need — if a risk is listed, the daily notes had better show it's being monitored.

7. Signatures

The individual or guardian, the provider, the support coordinator, and other team members. A plan without the required signatures isn't in effect, no matter how well-written the rest is.

Where CareHub fits

CareHub's Part V editor builds each of these sections in a stepped, autosaved form, pulls outcomes and supports straight into the daily note so staff document against the actual plan, and exports a PDF that matches the state template — with wet or typed signatures captured by secure magic-link email. When the plan and the documentation come from one system, the "does the note match the plan?" question answers itself.

If your Part V lives in a Word template that drifts out of sync with your notes, that gap is where citations come from. Try CareHub free for 14 days and keep the plan and the documentation in one place.