PLAAFP Statements That Actually Drive IEP Goals — And How IEP Pilot Writes Them from Your Assessment Data

The Present Levels of Academic Achievement and Functional Performance statement — PLAAFP, sometimes called PLOP (Present Levels of Performance) — is required by IDEA 2004 at 34 CFR §300.320(a)(1). The statute is precise: the IEP must include "a statement of the child's present levels of academic achievement and functional performance, including how the child's disability affects the child's involvement and progress in the general education curriculum."

In practice, PLAAFP statements range from genuinely useful — data-rich, specific, clearly connected to goals — to statements that read like boilerplate, reference no assessment data, and could have been written for any student with a similar disability label. The latter are the ones that generate findings in compliance reviews, fuel disputes in IEP meetings, and leave general education teachers without the information they need to support a student in their classroom.

A PLAAFP statement is not a diagnosis summary. It is not a list of services the student currently receives. It is not a paragraph describing the student's personality or attitude. It is a data-referenced description of where the student currently performs academically and functionally, and a clear statement of how the identified disability affects access to and progress in the general curriculum.

Current performance data with specific references. A defensible PLAAFP cites actual data. Not "performs below grade level in reading" but "as measured by the Woodcock-Johnson IV administered in January 2026, the student's Broad Reading score was 72 (standard score), placing performance at approximately the 3rd percentile for same-age peers." The difference is not cosmetic. The first statement tells the IEP team nothing actionable. The second establishes a baseline from which goals can be written and progress can be measured.

Functional performance across domains. IDEA requires both academic achievement and functional performance. Functional performance includes communication skills, social-emotional functioning, adaptive behavior, motor skills, and any other area where the disability creates educational barriers. A PLAAFP that addresses academic achievement but ignores functional domains is incomplete, and the goals that follow from it will be incomplete as well.

Disability impact statement. IDEA specifically requires a statement of how the disability affects involvement and progress in the general curriculum. This is the connective tissue between the evaluation findings and the goals. It answers the question: given what we know about this student's disability, what does that mean for their ability to access grade-level content, demonstrate learning in the general education environment, and make meaningful progress?

Student strengths. Best practice — and the language of IDEA itself — calls for strengths to be documented alongside areas of need. Strengths are not filler. They inform instructional decisions, shape how goals are designed, and provide the foundation on which intervention is built. A student who struggles with reading decoding but demonstrates strong listening comprehension has a very different instructional profile from a student whose comprehension difficulties are equally pronounced.

When a provider uploads an evaluation report or previous IEP, IEP Pilot identifies and extracts the specific data categories required for a complete PLAAFP statement: standardized assessment scores and their normative comparisons, identified areas of need by domain, documented strengths, and any existing present level language that can inform the current statement.

IEP Pilot then constructs a PLAAFP statement that is referenced to the actual assessment data in the document. If the uploaded psychoeducational evaluation includes a Broad Reading standard score of 72, that score appears in the PLAAFP. If the speech-language evaluation documents expressive language scores significantly below age expectations on a standardized measure such as the CELF-5, that finding is reflected. The PLAAFP IEP Pilot generates is specific to the student whose documents were uploaded — not a template with a name field populated.

For providers working without documents — during planning conversations, initial eligibility meetings where evaluation data is still being gathered, or any situation where complete assessment records are not at hand — IEP Pilot's guided question flow collects the same data categories through structured prompts. The provider enters the best available information, and IEP Pilot generates a PLAAFP that reflects that information accurately, flagging where data gaps may require follow-up.

One of the most common compliance findings in state and federal monitoring of special education programs is a failure to connect IEP goals to the PLAAFP. IDEA requires that goals "meet the child's needs that result from the child's disability to enable the child to be involved in and make progress in the general education curriculum" (34 CFR §300.320(a)(2)). Needs are established in the PLAAFP. Goals address those needs. The chain of reasoning must be traceable.

When IEP Pilot generates goals following a PLAAFP generation, the goals are directly connected to the present level data. A PLAAFP that documents a reading fluency rate significantly below grade-level expectation produces goals targeting the specific fluency skills indicated by the data — not reading comprehension, not decoding in isolation, but fluency, at the appropriate level of challenge, with criteria calibrated to the documented baseline.

This connection is not just a compliance requirement. It is the difference between goals that are educationally meaningful and goals that exist on paper to satisfy documentation obligations. Students make progress when their instruction is targeted at their actual needs, documented with precision, and measured with fidelity. IEP Pilot is designed to produce the documentation foundation that makes that kind of instruction possible.

• No data references. Statements like "performs below grade level" without citing any assessment instrument, score, or observation data are legally insufficient and instructionally useless. Every performance claim in a PLAAFP should be traceable to a source.
• Copy-forwarded language from prior IEPs. The PLAAFP must reflect current performance. Carrying forward PLAAFP language from a previous IEP without updating it to reflect new assessment data is a compliance violation and, more importantly, a failure of the student — their present level has presumably changed, and their IEP should reflect that change.
• Goals that don't match the PLAAFP. If the PLAAFP documents needs in reading fluency and mathematics calculation, the goals must address those areas. Goals in unrelated areas, or goals that address areas not mentioned as needs in the PLAAFP, signal a drafting process that was not grounded in the student's data.
• Missing disability impact statement. The PLAAFP must address how the disability affects curriculum access — not just what the student's scores are, but what those scores mean for the student's educational experience. This is the component most frequently omitted.
• No strengths documentation. IDEA's language calls for strengths to be considered in IEP development. A PLAAFP that is entirely deficit-focused misses the statutory intent and leaves the IEP team without information that matters for instructional design.