Special education file review checklist: audit an IEP file the way state monitors do
Every state education agency monitors its districts’ special education files — IDEA requires it under the general-supervision rules at 34 CFR §300.600, and states like Missouri and West Virginia publish the very checklists their reviewers use. A file review is exactly what it sounds like: a reviewer pulls a student’s SPED file and verifies, document by document and date by date, that the IEP — the core SPED document — and everything around it meets the legal requirements. The smartest thing a case manager or director can do is run the same audit first. Below is the consolidated checklist: every item a reviewer looks for, with the federal citation behind it. Where your state adds requirements (most do), its rules stack on top of this floor.
1. Evaluation and eligibility
| Check | Citation |
|---|---|
| ☐ Signed parental consent for the initial evaluation is in the file, with a legible date | 34 CFR §300.300 |
| ☐ Eligibility determination completed within the governing timeline (federal default 60 days from consent; your state's rule controls if different) | 34 CFR §300.301(c) |
| ☐ Evaluation/eligibility report present and provided to the parent | 34 CFR §300.306 |
| ☐ Most recent reevaluation is dated within 3 years of the one before it — or a documented parent-district agreement that reevaluation was unnecessary | 34 CFR §300.303(b)(2) |
2. IEP content — every §300.320 component present
| Check | Citation |
|---|---|
| ☐ Present levels (PLAAFP) stating how the disability affects involvement and progress in the general education curriculum | 34 CFR §300.320(a)(1) |
| ☐ Measurable annual goals — baseline, condition, behavior, criterion, timeframe — tied to needs identified in the PLAAFP | 34 CFR §300.320(a)(2) |
| ☐ How progress will be measured AND when periodic progress reports will be provided | 34 CFR §300.320(a)(3) |
| ☐ Statement of special education, related services, and supplementary aids — with frequency, location, and duration for each | 34 CFR §300.320(a)(4), (a)(7) |
| ☐ Explanation of the extent, if any, the student will not participate with nondisabled peers (LRE statement) | 34 CFR §300.320(a)(5) |
| ☐ Individual accommodations for state and districtwide assessments — or a documented alternate-assessment decision | 34 CFR §300.320(a)(6) |
| ☐ For students turning 16 (earlier in many states): measurable postsecondary goals from age-appropriate transition assessments, plus transition services and course of study | 34 CFR §300.320(b) |
3. Process documents
| Check | Citation |
|---|---|
| ☐ Meeting invitation/notice for each IEP meeting, sent early enough to ensure the parent could attend | 34 CFR §300.322 |
| ☐ Required team membership present at each meeting — or a signed excusal with parent agreement and written input | 34 CFR §300.321 |
| ☐ Prior written notice for every proposal or refusal to initiate or change identification, evaluation, placement, or FAPE | 34 CFR §300.503 |
| ☐ Procedural safeguards notice provided at the required times | 34 CFR §300.504 |
4. Implementation evidence
| Check | Citation |
|---|---|
| ☐ IEP in effect at the start of the current school year; annual review held before the IEP's anniversary date | 34 CFR §300.323(a), §300.324(b) |
| ☐ Progress reports actually issued at the intervals the IEP promises — copies or system records in the file | 34 CFR §300.320(a)(3)(ii) |
| ☐ Evidence the IEP is accessible to every implementing teacher and provider, and that each was informed of their specific responsibilities and accommodations | 34 CFR §300.323(d) |
| ☐ Service delivery matches the services grid — schedules or logs reconcile with promised minutes | 34 CFR §300.323(c)(2) |
IEP-content and implementation citations verified against the current text of 34 CFR §300.320 and §300.323 at eCFR.
How to run the review without losing a week
Work in two passes. Pass one is dates only — for every file, four numbers: IEP date (is the annual review inside 365 days?), reevaluation date (inside 3 years?), eligibility date versus consent date (inside your state’s window?), and progress-report dates versus the intervals the IEP promises. This pass takes minutes per file and finds the majority of what state reviewers cite, because timeline compliance is objective. Pass two is content — open the IEP and walk the §300.320 table above. The two items that fail most often pair together: goals without baselines (the baseline data guide covers the fix) and services grids that don’t reconcile with actual schedules — the service minutes guide shows how to audit that line by line. Log every gap in one tracker with an owner and a date, then fix in deadline order: overdue timelines first, missing documents second, content quality third. Our IEP compliance checklist is the per-IEP companion to this per-file audit, and the SPED documentation checklist covers the paper trail between meetings.
What happens when the state finds what you didn’t
Findings aren’t suggestions. §300.600(e) requires that identified noncompliance be corrected as soon as possible, and in no case later than one year after identification — and §300.600(b) directs states to focus monitoring on the things that affect outcomes, particularly FAPE in the least restrictive environment. Expect a written finding, student-level correction (fix this file), systemic correction (prove the error pattern is gone), and follow-up verification. States publish their own procedures — Missouri’s tiered monitoring system, for instance, has districts upload files against a published checklist, one of the details we cover in our Missouri IEP requirements guide. The pattern to internalize: everything a reviewer checks is checkable in advance. A file that passes your September audit passes their March one.
FAQ
What is a special education file review?
A document-by-document audit of a student's special education file against legal requirements — does the file contain a signed consent, an eligibility determination inside the timeline, an IEP with every required component, meeting notices, prior written notices, and progress reports issued on schedule? States run file reviews as part of the general-supervision monitoring IDEA requires of them, and districts run internal ones to find problems before the state does.
What happens if a file review finds noncompliance?
Under 34 CFR §300.600(e), when a state identifies noncompliance it must ensure the noncompliance is corrected as soon as possible — and in no case later than one year after identification. In practice that means a written finding, a corrective action plan, evidence of correction for the individual student, and usually a systemic check that the same error isn't sitting in other files.
How often should a district run internal file reviews?
There's no federal schedule for internal reviews — the requirement is that the state monitors districts, not that districts self-audit. But the practical rhythm that works: a full-caseload sweep at the start of the year (dates and documents), a spot-check each grading period tied to progress reports, and a targeted review of any file 60 days before its annual review or reevaluation due date. Ten minutes per file in September is cheaper than a corrective action plan in March.
What do reviewers check first in an IEP file?
Dates. Timeline compliance is objective — the annual review before its anniversary, the reevaluation inside three years, the eligibility determination inside the state's evaluation window, progress reports at the promised intervals. A reviewer can verify all of it from four documents without reading a single goal, which is why date math failures are the most common findings.