What is ISP goal tracking?

Recording progress on the goals in an individual service plan, visit by visit, in a form that can be added up at review time. It works when each goal has a defined measurement method and every note against that goal records one data point in that form.

Is an ISP the same as a Person-Centered Support Plan in Colorado?

Colorado's current rule uses Person-Centered Support Plan (PCSP) for the plan the case manager prepares, and Provider Care Plan for the plan each provider agency writes from it. Many agencies still say ISP. The federal HCBS rule calls it the person-centered service plan.

How often do ISP goals have to be reviewed?

Under the federal rule, the person-centered service plan must be reviewed, and revised as appropriate, at least every 12 months, when the person's needs change significantly, or at the person's request. In Colorado, each provider agency's Provider Care Plan must also be reviewed at least two times a year.

What does a Colorado service note need to include?

For each unit of service, 10 CCR 2505-10 § 8.7405 asks for the location, the date with beginning and end time, the name of the person who rendered the service, the exact tasks performed in line with the service definition, any change in the member's condition and the action taken, and the units provided.

How long must goal and service records be kept in Colorado?

Seven years, unless another section of the rule or the provider participation agreement requires a longer period (10 CCR 2505-10 § 8.130.2.D).

ISP Goal Tracking That Survives an Audit

Short answer: An ISP goal survives an audit when the record connects three things: a goal written so it can be measured, notes that say what was done toward it on each visit, and reviews that show results over time. Findings rarely come from support nobody gave. They come from a chain that breaks somewhere between the plan, the daily note and the review. Software earns its place by keeping that chain intact while staff document, not by adding a goals tab.

The name changes from state to state and from rule to rule. Many agencies still say ISP, for Individual Service Plan or Individual Support Plan. The federal HCBS rule calls it the person-centered service plan. Colorado's current rule calls the case manager's plan the Person-Centered Support Plan (PCSP), and the plan each provider agency writes from it the Provider Care Plan. The chain an auditor follows is the same under every name. This guide walks through it with the federal rule and Colorado's 10 CCR 2505-10 § 8.7000, then turns it into a checklist for choosing ISP goal tracking software.

What the rules ask for

The federal rule sets the floor. Under 42 CFR 441.301(c)(2), the person-centered service plan must "include individually identified goals and desired outcomes" and reflect the services and supports, paid and unpaid, that will help the person reach them. Under 441.301(c)(3), the plan must be reviewed, and revised as appropriate, based on a reassessment of functional need at least every 12 months, when the person's circumstances or needs change significantly, or at the person's request. Beginning July 9, 2027 (later for some managed care contracts), states must also show that they meet that 12-month review for at least 90 percent of people continuously enrolled in a waiver for a year or more.

Colorado adds the provider's layer. The PCSP is prepared by the case manager and "identifies the supports needed for the individual to achieve personally identified goals" (§ 8.7001.A.11). Every provider agency named in it must keep the plan on file where the staff who need it can reach it, and must develop a Provider Care Plan for each member, using the PCSP as its basis (§ 8.7410). At a minimum, that plan should name the member's service and care needs, the date it was developed, the goals or objectives of the service, the methods staff will use in plain language, and how long and how often the service is provided.

Then comes the daily record. For each unit of service, § 8.7405 asks for the location, the date with beginning and end time, the name of the person who rendered the service, "the exact nature of the specific tasks performed that align with the service definition(s)", any change in the member's condition and the action taken, and the units provided. Per-diem services add a daily attendance tracker, notes on activities and, where it applies, a medication administration record. Medicaid records are kept for seven years (§ 8.130.2.D).

The chain an auditor follows

Layer	Who writes it	What it has to show	Colorado rule
Person-Centered Support Plan	The case manager, directed by the person whenever possible	Personally identified goals and the supports needed to reach them	§ 8.7001.A.11
Provider Care Plan	Each provider agency named in the PCSP	Goals or objectives of the service, methods, duration and frequency	§ 8.7410.C
Service documentation	The staff member who delivered the service	Time, place, who, the exact tasks, units, changes in condition	§ 8.7405
Plan review	The provider agency, at least twice a year	Results achieved, and whether the plan still matches the PCSP	§ 8.7410.C.5
Retention	The agency	All of the above, for seven years	§ 8.130.2.D

Each link points at the next one. A reviewer starts from a claim or a note, walks back to the goal it served, and asks whether the plan said to do that, at that frequency, for that person. Where a link is missing, the service may well have happened, but the record cannot show it.

Where goal records break

The goal has no measurement. "Improve communication skills" can only be narrated. If the goal never says what counts as progress, every note describes it differently and no review can add them up.

The note describes the day, not the service. "Had a good day, enjoyed lunch" says the person was there. Colorado asks for the exact nature of the tasks performed. A note that names the skill worked on, the support given and the response is a different record.

The note never names a goal. Staff write down what they did, but nothing ties it to an objective in the Provider Care Plan. At review time someone has to guess which notes belonged to which goal.

The plans drift apart. The case manager revises the PCSP, the Provider Care Plan is not updated, and staff keep documenting against last year's goals. The twice-yearly review exists to catch this: it must check whether the services still fit the needs assessed in the PCSP.

The review is written from memory. A coordinator reads months of notes under deadline and writes a summary. It is only as good as the reading, and it rarely compares with the last one.

Write goals that can be tracked

A trackable goal names a behavior someone can observe, the condition or level of support, a criterion, and how it will be measured. Two examples, both invented for illustration:

Written for the meeting	Written to be tracked
Sam will improve communication.	Sam will ask for a break using a picture card, with no more than one verbal prompt, in 4 of 5 opportunities, two weeks running. Measured as opportunities and prompt level per shift.
Sam will become more independent with money.	Sam will pay for a purchase under $20 and check the change, with a gestural prompt or less, on 3 community outings a month. Measured as outings, prompt level and accuracy.

The measurement method matters most. Decide it once, on the goal: a count, a percentage of opportunities, a duration, or a prompt level. Then every note against that goal produces the same kind of data, whoever writes it.

Document against the goal, not the shift

A note that holds up does two jobs at once. It carries the § 8.7405 elements, so the unit can be billed, and it records one data point for each goal worked on: which goal, what was done, the support given and the person's response. Captured during the visit, that takes a few taps. Reconstructed at the end of a week, it turns into the generic narrative that reviewers flag.

Reviews that start from the data

Colorado's Provider Care Plan review answers four questions: what results were achieved, whether the plan reflects the member's needs, whether the services fit the needs assessed in the PCSP, and what actions are needed. With measured goals, the first question is a chart for the period, not a reading exercise. A goal that has been met gets a new objective. A goal with no movement gets a different method or a conversation with the case manager. Either way the review shows a decision, which is what the rule asks for.

What to look for in ISP goal tracking software

The measurement method lives on the goal. Staff should not choose a format each time they document.
Notes attach to active goals in the current plan version. Plans should carry dates, so a note from March reads against the March plan.
The required elements are captured at entry. Start and end time, location, staff name and units should come from the visit, not from a second system.
A review can pull goal data for any date range, with the notes behind each data point one click away.
Late documentation is visible while the visit is still fresh.
Everything exports. Seven years of retention outlives most software contracts.

Where OutcomeGrid fits

OutcomeGrid defines the measurement method on each ISP or service-plan goal and applies it every time staff document. Notes are captured during the visit and tied to the authorized service and the goal being addressed, templates are set per program and service type, late documentation shows per staff member, and progress reports are built from the goal data rather than rewritten each quarter. See Documentation & outcomes for how it works, and our guide to PASA requirements in Colorado for the rest of what a provider agency must document.

Sources: 42 CFR 441.301(c)(2) and (c)(3), eCFR current as of October 6, 2026; 10 CCR 2505-10 § 8.7000, version effective August 14, 2026 (§§ 8.7001.A.11, 8.7405, 8.7410); 10 CCR 2505-10 § 8.130.2.D. This article is general information, not legal advice.