SPED compliance checklist: the caseload calendar that keeps you audit-ready

SPED compliance runs on two levels. The first is the document: does each IEP contain everything federal law requires? That one lives in our IEP compliance checklist. This page is the second level — the calendar: the recurring deadlines and event-driven triggers across a whole caseload that state monitors and district audits actually pull files to check. A perfect IEP reviewed thirteen months after the last one is still a finding.

The three clocks behind everything

  • Start-of-year: an IEP must be in effect for every eligible student at the beginning of each school year — 34 CFR §300.323(a). Not “scheduled,” not “in progress” — in effect.
  • Annual: the IEP team reviews and revises each IEP at least once a year, and sooner whenever progress data says the plan isn't working.
  • Triennial: reevaluation at least once every 3 years, unless parent and district agree it is unnecessary — and not more than once a year unless agreed (34 CFR §300.303).

The year, period by period

Before day one

  • Every student on the caseload has an IEP in effect — 34 CFR §300.323(a) requires it at the beginning of each school year, no grace period.
  • Accommodations pages distributed to every teacher of every student, with receipt you can point to later.
  • Caseload list cross-checked: annual review dates, reevaluation due dates, and upcoming 14th/16th birthdays (transition) mapped onto the year.

Every grading period

  • Progress reports written for every goal of every IEP, matching the reporting cadence each IEP promises (34 CFR §300.320(a)(3)).
  • Data behind each report actually exists — a progress report without probes or work samples behind it is an assertion, not a report.
  • Off-track goals flagged for the team: a pattern of no progress is a reconvene trigger, not a note for the annual.

Rolling, 30–60 days ahead

  • Annual reviews scheduled before their anniversary dates — spring clusters hard, so book March–May meetings by February.
  • Reevaluations initiated early enough that consent, assessment, and the eligibility meeting all land inside the 3-year deadline (34 CFR §300.303).
  • Transition content drafted before the IEP that must contain it — by 16 federally, and earlier where your state moves the date (Texas: 14).

Event-driven — the clock starts when it happens

  • Transfer student arrives: comparable services start immediately under §300.323(e)–(f); calendar the adopt-or-redo decision.
  • Removal days for discipline tracked per student; approaching 10 cumulative days triggers manifestation-determination planning under §300.530.
  • Parent requests an evaluation or revokes consent: prior-written-notice duties fire on state clocks (in Texas, 15 school days for referral responses).

The two triggers that catch good case managers

Scheduled deadlines are survivable with any decent tracker. The findings that blindside people are event-driven:

  • Transfers. When a student with an IEP moves in, comparable services must begin immediately — §300.323(e)–(f) — while the district decides to adopt the old IEP or write a new one (with a new evaluation for out-of-state arrivals). The service gap between enrollment and “we got the records” is exactly what complaints cite.
  • Discipline days. 34 CFR §300.530 lets schools remove a student for up to 10 consecutive school days like any other student — but beyond that (or a pattern of removals adding up to a change of placement) the manifestation determination machinery must run first. If nobody is counting the days, nobody knows the trigger fired.

Making it survivable

None of this requires heroics — it requires one tracker with every student's four dates (annual review, triennial, transition birthday, progress-report cadence) and a weekly twenty-minute appointment with it. That system, including the one-page caseload tracker, is laid out in SPED paperwork organization; the underlying documents each file needs are in the SPED documentation checklist. If you're in Texas, layer the state clocks — 45 school days to evaluate, 30 calendar days to the initial ARD, transition at 14 — from our Texas IEP requirements guide.

FAQ

What does SPED compliance actually mean?

Meeting every procedural requirement IDEA and your state attach to special education: an IEP in effect at the start of each school year, annual reviews on time, reevaluations every three years, progress reports on every goal at the promised cadence, and the event-driven duties (transfers, discipline, transition) handled on their legal clocks. The IEP is the core SPED document, so most compliance duties are IEP duties.

What are the big recurring SPED compliance deadlines?

Three cycles cover most of it: the IEP must be reviewed at least annually (34 CFR §300.324); reevaluation must occur at least every 3 years unless parent and district agree it's unnecessary (34 CFR §300.303); and progress on annual goals must be reported at the intervals the IEP promises — for most caseloads, every grading period (34 CFR §300.320(a)(3)).

What happens when a student with an IEP transfers in mid-year?

Services can't wait for paperwork. Under 34 CFR §300.323, the new district must provide services comparable to the incoming IEP — immediately for in-state transfers (until it adopts or replaces the IEP), and for out-of-state transfers until it completes its own evaluation if needed. 'We're still waiting on records' is not a legal reason for a service gap.

What is the 10-day rule in special education discipline?

Removals beyond 10 consecutive school days (or a pattern of shorter removals adding up) are a change of placement under 34 CFR §300.530 and trigger the manifestation determination review — the team must decide whether the behavior was caused by, or substantially related to, the student's disability before ordinary discipline can proceed. Case managers should be counting removal days from day one.