How to Run an Effective IEP Quality Review
If you supervise IEPs across a team, you already know that "looks fine" is not a review process. This is a practical, repeatable way for special-education coordinators, supervisors, and building leaders to sample IEPs, know what to look for, and hand feedback back in a way that actually changes the next draft. Think of it as a pre-flight check for the documents your teachers are about to file. I have run this kind of review from the supervisor's chair, and the difference between a review that changes anything and one that does not almost always comes down to whether the sampling and the feedback loop are actually built, not improvised.
Decide what to sample and why
You cannot read every IEP closely, and you should not try. A good review samples on purpose.
Pull a small, representative set each cycle. A workable mix is a few IEPs per teacher, weighted toward the situations where quality matters most: students with the most complex needs, brand-new staff, anyone returning from leave, and any case where a parent has raised a concern. Rotate so that over a semester every teacher has had at least one IEP read closely.
Keep the sample small enough that you can read deeply. Ten IEPs reviewed with care will teach you more about your program than fifty skimmed. Track which ones you pulled so the next cycle covers different students and different teachers.
Use the same checklist every time
The fastest way to lose credibility as a reviewer is to flag one teacher for something you let slide for another. A written checklist keeps you consistent and makes your feedback feel fair instead of personal.
Your checklist does not need to be long. A handful of high-leverage questions covers most quality problems:
- Do the present levels describe current performance with specific data, not just labels or history?
- Does each annual goal name a measurable behavior, a condition, and a clear criterion?
- Can you tell exactly how progress will be measured, and how often?
- Do the services, accommodations, and specially designed instruction actually connect to the needs described in present levels?
- Would a new teacher picking up this IEP in January know what to do on Monday?
The thread running through all of these is internal alignment. The present levels name a need, a goal targets that need, and the services and instruction are built to move the goal. When those pieces drift apart, the document stops being useful even if every box is filled in.
A brief and honest note here: this is general guidance for document quality, not legal advice, and a quality review does not by itself establish legal compliance. IDEA does require measurable annual goals, but whether any specific IEP meets a legal standard is a determination for the team and, when needed, counsel.
Look hardest at goals and present levels
If your time is limited, spend it on the present levels and the annual goals. They drive everything downstream.
The most common goal problem is language that sounds rigorous but cannot be measured. Here is a weaker version next to an improved one.
Weaker: "Jordan will improve his reading comprehension to grade level."
You cannot measure that. "Improve" has no baseline, "grade level" is not a number you can score, and there is no condition or timeframe.
Improved: "Given a fourth-grade passage read aloud, Jordan will answer literal and inferential comprehension questions with at least 80 percent accuracy across three consecutive weekly probes by the annual review date."
Now the goal names the condition, the behavior, the criterion, and how often you will check. A teacher can collect data against it, and a parent can understand what success looks like.
Present levels deserve the same scrutiny. "Maria struggles with math" is a label, not a present level. A usable version reads more like: "On a recent computation probe, Maria solved single-digit addition facts at 12 correct per minute and made errors regrouping in two-digit subtraction." That gives the next goal something concrete to aim at.
Check that the pieces hold together
A surprising number of IEPs pass a box-by-box check and still fail as a document, because the sections were written in isolation.
Read across, not just down. If present levels describe a student who needs help with written expression, but every goal targets reading fluency and none touch writing, the document does not hang together. If the accommodations list "extended time" but no service or goal explains why, ask about it. If the specially designed instruction describes a program that has nothing to do with the stated need, flag it.
These cross-section gaps are easy to miss when you read top to bottom and tempting to forgive when each piece looks acceptable on its own. They are exactly what a parent's advocate notices, so they are worth your attention.
Give the feedback back so it sticks
A review only helps if the feedback lands and changes the next draft. How you hand it back matters as much as what you found.
Lead with patterns, not a pile of corrections. If three teachers all wrote goals without a clear criterion, that is a coaching topic for the whole team, not three separate scoldings. Name the strongest example you saw and say why it works, so people have a model to copy.
When you do give individual feedback, be specific and show the fix. "This goal is not measurable" leaves the teacher guessing. "This goal needs a criterion. Try adding 'with at least 80 percent accuracy across three weekly probes'" gives them something to use immediately. Pair every flag with a suggested revision and a short reason.
Close the loop. Note what you asked for, and glance at the next cycle's IEPs from those teachers to see whether it took. Improvement you never check on tends to fade.
Quick recap
A workable IEP quality review comes down to a short, repeatable routine:
- Sample on purpose: a small, representative set, rotated over time.
- Use the same written checklist every time, built around internal alignment.
- Read goals and present levels hardest; insist on measurable, specific language.
- Read across sections to catch pieces that do not connect.
- Hand feedback back as patterns plus specific fixes, then check that it stuck.
For teachers who want to catch the vague-goal and unmeasurable-language problems above before a draft ever reaches your desk, IEP Pre-Flight is a pre-submission red-flag checker that gives structured feedback on pasted draft language, and its District edition adds supervisor tools like quality checklists, observation frameworks, and coaching-email drafts.
This is general information, not legal advice. IEP Pre-Flight home
Loading the full page. JavaScript is required for the interactive app.