Common IEP Compliance Findings and How to Prevent Them

If you supervise IEP quality across a building or a district, you have probably noticed that the same findings come up again and again in state monitoring and file reviews. This is a plain-language look at those recurring documentation gaps and how to catch them before they ever leave the team table. It is written for special-education coordinators, supervisors, principals, and directors. A quick note up front: this is general information, not legal advice. For questions about a specific case or your state's requirements, check with your district's counsel or your state education agency. These are the same handful of findings I watched repeat across file reviews year after year, which is exactly why they are worth naming plainly instead of rediscovering them every cycle.

Goals that cannot actually be measured

This is the finding that shows up most. IDEA requires measurable annual goals, and "measurable" has a specific meaning. Someone other than the author should be able to read the goal and know exactly how progress will be judged. The trouble usually is not bad intentions. It is goals that sound fine out loud but fall apart when you ask, "How would we score this?"

Here is a weaker version of a behavior goal:

By the annual review, Jordan will improve self-regulation and stay on task during instruction.

What does "improve" mean, and from what starting point? How is "on task" defined, and who decides? There is no condition, no clear behavior, no criterion, and no measurement plan. Now an improved version:

Given a teacher-provided check-in and a visual timer, Jordan will remain engaged in independent work (eyes on task, materials out, working) for at least 15 of 20 minutes, in 4 of 5 observed sessions across two weeks, as measured by teacher interval data.

Same intent, but now anyone can score it. When you review files, the fastest test is to ask the author one question: what number, on what task, measured how, by when. If they cannot answer in a sentence, the goal is not measurable yet.

Present levels that describe the disability but not the need

Present levels of academic achievement and functional performance, often called the PLAAFP, are supposed to be the foundation everything else stands on. A common finding is that the PLAAFP lists diagnoses, scores, and history but never names the specific need the goals are meant to address. When the present levels and the goals do not connect, a reviewer notices immediately.

A weaker PLAAFP snippet:

Maria has a specific learning disability. She struggles in math and gets frustrated with word problems.

That is a label and a feeling, not a baseline. A stronger version gives the reader something concrete to build a goal on:

On a recent classroom assessment of two-step word problems, Maria solved 3 of 10 correctly. She reliably identifies the operation when problems are read aloud but loses track of steps when solving independently. This affects her ability to complete grade-level math tasks without one-on-one support.

Notice that the last sentence names the educational impact. The simplest way to head off this finding is to require that every PLAAFP statement end by connecting the need to access or progress in the general curriculum, and that every goal trace back to a need named in the present levels.

Services written too vaguely to deliver

Findings around the services grid are common because the page looks tidy even when it is not specific. Reviewers and parents both need to know what is being provided, how much, how often, and where. "As needed," "consult," or "30 minutes weekly" without a clear setting or provider role leaves real questions about whether the service is actually being delivered as written.

A vague entry might read "Reading support, small group, as appropriate." A clearer entry specifies the amount, frequency, location, and duration. For example: 30 minutes, four times per week, in the special-education resource setting, for the full IEP year. The same care applies to specially designed instruction. Naming a program is fine, but the instructional design is what matters: what is being taught, how it is adapted, and how the intensity or method differs from core instruction. When you spot a service that could not be scheduled or staffed from the words on the page, send it back before the meeting, not after.

Accommodations that read like a wish list

A frequent finding is a long accommodations list that nobody could implement consistently. "Extra time," "preferential seating," and "frequent breaks" appear on file after file with no specifics. The risk is twofold. A general-education teacher cannot reliably follow it, and the team cannot tell whether it is working.

Tighten each one so it is observable. Instead of "extra time," write "up to time and a half on tests longer than one page." Instead of "frequent breaks," write "a two-minute movement break after every 20 minutes of sustained writing, initiated by a desk card." A good prevention habit at the building level: ask whether each accommodation names what it is, when it applies, and who provides it. If a substitute could not follow it, it needs another pass.

Progress notes that do not show progress

Even strong goals get undercut at reporting time. A common finding is a progress note that restates the goal or says "making progress" without data tied to the goal's own criterion. If the goal is measured in correct responses across sessions, the progress note should speak in those same terms.

A weaker note: "Sam is working hard and showing improvement." A stronger note: "Sam read 62 words correct per minute on a grade-2 passage this quarter, up from 48 at the last report. The goal criterion is 90. Sam is making progress but is not yet on track to meet the goal by the annual date, so instructional minutes will increase." That stronger note also models something reviewers look for: an honest statement when a student is not on pace, paired with what the team will do about it.

Build a light pre-submission check into your workflow

Most of these findings are not caused by people who do not care. They are caused by busy teachers writing under deadline, with no second set of eyes before the document is final. The fix is structural. Give every draft a quick consistency pass before the meeting.

A short reviewer checklist catches the bulk of recurring findings:

• Does every goal state a condition, an observable behavior, a clear criterion, and how and when it is measured?
• Does every goal trace back to a specific need named in the present levels?
• Does the PLAAFP state educational impact, not just a diagnosis or scores?
• Can each service be scheduled and staffed exactly as written (amount, frequency, location, provider role)?
• Could a substitute follow each accommodation without asking questions?
• Do progress notes report data in the goal's own terms and say so plainly when a student is off pace?

If you want a fast way to give teachers that second look on individual pieces of draft language before a meeting, IEP Pre-Flight is a pre-submission red-flag checker that flags what is missing, vague, or unmeasurable in pasted draft text and suggests revisions. Whatever tool you use, the principle holds: the cheapest finding to fix is the one you catch before the IEP is signed.

The note above is general information for educators, not legal advice. It does not determine compliance for any individual IEP. For guidance on your state's requirements or a specific student, consult your district's counsel or your state education agency.