IEP Goals Based on WISC-V Scores: Connecting Cognitive Data to Measurable Objectives

WISC-V scores tell you where the cognitive bottleneck is. IEP goals are supposed to address the educational impact of that bottleneck. The problem most parents encounter: the two rarely connect. The report identifies a Working Memory Index of 79, and then the IEP proposes generic reading goals that have nothing to do with working memory.

Here is how to bridge the gap.

How Cognitive Scores Connect to IEP Goals

An IEP goal must be measurable, tied to an identified area of need, and achievable within the IEP period (usually one year). The WISC-V does not directly produce IEP goals — it identifies the cognitive processing weaknesses that cause academic difficulties. The chain works like this:

WISC-V index weakness → classroom impact → present level of performance → measurable goal

A Processing Speed Index of 76 does not become a goal like "improve processing speed." Processing speed is a cognitive trait, not a skill to teach. Instead, the goal addresses the academic consequence: "Given extended time of 1.5x, [child] will complete grade-level math assessments with 80% accuracy within 30 minutes, as measured by classroom test data, by [date]."

Goals for Low Working Memory (WMI Below 90)

Low working memory shows up as difficulty following multi-step directions, losing place during reading, struggling with mental math, and forgetting instructions before completing them.

Example goals:

• "Given a graphic organizer, [child] will independently plan and compose a grade-level paragraph with a topic sentence, three supporting details, and a conclusion in 4 out of 5 trials, as measured by teacher-scored writing rubrics."
• "After receiving two-step verbal directions with one repetition, [child] will accurately complete the task in 80% of opportunities, as measured by teacher observation data collected over 6 consecutive weeks."
• "[Child] will use a self-monitoring checklist to verify completion of multi-step assignments with 85% accuracy across all academic subjects, as measured by weekly checklist review."

The key: these goals do not ask the child to "improve working memory." They teach compensatory strategies (graphic organizers, checklists, chunked directions) that work around the bottleneck.

Goals for Low Processing Speed (PSI Below 90)

Low processing speed means the child works slowly on routine tasks, takes longer to copy, and cannot finish timed work in standard time. Goals should address fluency and output efficiency, not speed for its own sake.

Example goals:

• "Given access to typed response options, [child] will complete grade-level reading comprehension assessments with 80% accuracy within the extended time accommodation of 1.5x, as measured by quarterly benchmark data."
• "[Child] will demonstrate keyboarding fluency of 20 words per minute with 90% accuracy, as an assistive technology support for written expression, as measured by monthly keyboarding assessments."
• "[Child] will complete daily math assignments to 80% completion within the class period when provided printed problems (no board copying required), as measured by daily assignment tracking."

Goals for Low Verbal Comprehension (VCI Below 90)

Low verbal comprehension affects vocabulary acquisition, reading comprehension, and the ability to explain reasoning verbally.

Example goals:

• "Given pre-taught vocabulary for each content area unit, [child] will correctly use 8 out of 10 target words in context on weekly vocabulary assessments."
• "[Child] will answer literal and inferential comprehension questions about grade-level passages with 75% accuracy when provided visual graphic organizers, as measured by bi-weekly reading probes."

Goals for Low Fluid Reasoning (FRI Below 90)

Low fluid reasoning affects abstract thinking, novel problem-solving, and making inferences from incomplete information.

Example goals:

• "Given explicit instruction in a step-by-step problem-solving model (CUBES or similar), [child] will solve grade-level multi-step word problems with 70% accuracy, as measured by monthly math probes."
• "[Child] will identify the main idea and two supporting details from grade-level informational text with 80% accuracy, using a provided text structure template, as measured by bi-weekly reading assessments."

What to Watch For in the IEP Draft

When reviewing the proposed IEP goals, check:

1. Does each goal connect to a documented weakness? If the WISC-V shows working memory and processing speed are the only low areas, goals should address the academic impact of those two — not unrelated areas.

2. Are compensatory strategies built into the goal? A good goal for a low-working-memory child includes the support (graphic organizer, checklist, written directions) as part of the condition. The support is how the child accesses the curriculum, not a crutch to be removed.

3. Is the goal measurable? "Will improve reading" is not measurable. "Will answer inferential comprehension questions with 75% accuracy on bi-weekly probes" is.

4. Is the baseline stated? Each goal should include where the child is performing now and where the goal targets. Without a baseline, you cannot measure progress.

If the IEP team proposes goals that do not reflect the WISC-V findings, point to the specific index scores and ask how each goal addresses the identified cognitive processing weaknesses. You have the right to propose goal language, and the team must consider parent input under IDEA.

The WISC-V Score Report Decoder includes a complete index-to-goal framework with example language for each cognitive processing area, designed for parents preparing for IEP meetings.