IEP due date tracker: build it from the deadlines the law actually creates
Search “IEP due date tracker” and you get spreadsheets to buy. What almost none of them tell you is which dates belong in the sheet and where each one comes from — and that is the part that decides whether the tracker holds up. A due-date tracker is not a calendar; it is a map of the deadlines IDEA and your state impose on the IEP, with a lead time in front of each one. Below: the seven deadline types with their citations, the eight columns worth keeping, and the two mistakes — storing the wrong anchor date and sorting by due date — that make most SPED trackers quietly useless by October.
The seven deadlines that belong in it
| Deadline | What the rule requires | Citation | Lead time | The trap |
|---|---|---|---|---|
| Annual review | Periodically, but not less than annually | 34 CFR § 300.324(b)(1)(i) | ~30 days | Track the IEP's effective date, not the last meeting date — and remember § 300.323(a): an IEP must be in effect at the start of each school year. |
| Triennial reevaluation | At least once every 3 years; not more than once a year unless the parent and agency agree | 34 CFR § 300.303(b) | 60–90 days | The deadline is the reevaluation, not a meeting. Consent has to go out months earlier. |
| Initial evaluation | 60 days from parental consent, or the state's timeframe if the state set one | 34 CFR § 300.301(c)(1) | Start immediately | Check your state's unit. Calendar days and school days produce very different dates across a winter break. |
| Progress reports | As often as the IEP itself says — quarterly or other periodic reports, concurrent with report cards | 34 CFR § 300.320(a)(3)(ii) | Full grading period | The IEP sets this deadline, so it varies student to student. Copy the promised schedule into the tracker at the annual review. |
| Reevaluation on request | When the parent or a teacher requests one | 34 CFR § 300.303(a)(2) | Same week | The trigger is a request, not a form. Log the date you received it, in writing, the day it happens. |
| Transfer student | Comparable services immediately upon enrollment, until the new IEP is adopted or developed | 34 CFR § 300.323(e)–(f) | Day of enrollment | In-state and out-of-state transfers follow different paths; both start the day the student walks in. |
| Transfer of rights notice | Beginning not later than one year before the child reaches the age of majority under state law | 34 CFR § 300.320(c) | One IEP cycle | The age of majority is a state question — 18 in most states, 19 in Alabama. Compute from the student's birthday, not the grade. |
Notice how few of these are annual reviews. The annual review is the deadline everyone tracks, and it is the one districts miss least often. The overdue triennial, the progress report that never went home, the transfer student served on comparable services for two months with no new IEP — those are the findings, and they are the ones a tracker built only from meeting dates cannot see.
The eight columns
| Column | Why it’s there |
|---|---|
| Student / ID | Initials or district ID, not full names — the tracker travels between your desk, your bag and a meeting table. |
| Deadline type | Annual, triennial, progress report, initial eval, transfer, rights notice. The type determines the lead time, so it has to be a column, not a note. |
| Legal due date | The date the regulation or state rule actually sets. This one never moves to be convenient. |
| Unit (calendar / school days) | For anything computed from a trigger. States split on this and the difference can be weeks. |
| Start-by date | Due date minus the lead time for that deadline type. This is the column you sort by. |
| Trigger date | Consent signed, enrollment date, parent request received. Needed to prove the clock started when you say it did. |
| Status | Not started / notice sent / scheduled / held / documents filed. Held is not the same as filed, and audits check the second one. |
| Notice sent | The date the meeting notice went out, so the notice-period requirement is provable without opening the file. |
Two of these are the ones the store-bought sheets leave out. Start-by date is due date minus lead time, and it is the column you sort by — a triennial due in April is a February problem, and a tracker sorted by due date will show it to you in April. Trigger date is what makes a computed deadline defensible: if the clock runs from parental consent, the tracker should say what day consent arrived, because that is the fact in dispute if the timeline is ever questioned.
The anchor-date mistake, and why it costs you weeks
Most trackers store one date per student: the last IEP meeting. That is the wrong anchor for two of the seven deadline types. The annual review runs against the IEP’s effective period — 34 CFR § 300.324(b)(1)(i) requires review “periodically, but not less than annually,” and § 300.323(a) separately requires that an IEP be in effect for each child at the beginning of each school year, which is a second constraint the meeting date alone will not catch. The triennial runs from the date of the last evaluation, not the last meeting, and those two dates can be a year apart on a student who had an amendment or a late eligibility determination.
The fix is boring and it works: store the IEP effective date, the last evaluation date, and the meeting date as three separate fields, and compute each deadline from its own anchor. If your district system exports them, export all three. If it does not, pull them once per grading period during your file review pass rather than trying to keep them current continuously.
State rules change the arithmetic, not just the number
Federal law sets the initial evaluation at 60 days from parental consent, then explicitly yields: “or, if the State establishes a timeframe within which the evaluation must be conducted, within that timeframe” (34 CFR § 300.301(c)(1)). States took that invitation in genuinely different directions, and the unit matters as much as the number:
- Nevada — 45 school days from informed written consent (NAC 388.337), so the clock pauses over every break, and the Superintendent can extend it by up to 15 more school days on request.
- Alabama — 60 calendar days to evaluate plus 30 more to determine eligibility, with the rule stating the timeline runs regardless of scheduled interruptions in the school year or summer vacation (Ala. Admin. Code r. 290-8-9-.02).
- Kentucky — a single 60-school-day clock that covers evaluation, eligibility and the IEP meeting together, which changes where the internal milestones have to sit.
This is why the tracker needs a unit column. A 45-school-day deadline and a 60-calendar-day deadline set from the same October consent date land almost two months apart. Check your own state page — the state guides cover the clock, the unit, and whether it runs through breaks — before you write a formula.
Working the tracker across a year
- Week 1 of the year: build the recurring rows. Every student on the caseload gets an annual-review row and a triennial row with real anchor dates pulled from the system, plus the progress-report schedule each IEP actually promises. This is a one-time cost of a couple of hours and it is the whole game.
- Every Monday: sort by start-by date, not due date. Anything whose start-by date has passed is this week’s work regardless of how far away the legal deadline looks.
- The day a trigger happens: add the row immediately. Consent signed, transfer enrolled, parent request received. Triggered deadlines are the ones that get missed, because nothing on a calendar prompts you to create them.
- End of each grading period: reconcile against the district system. Amendments, transfers and late eligibility determinations move anchor dates. A side tracker that has drifted from the record of truth is worse than none.
- Close the loop on status. “Held” and “documents filed” are different states. Compliance monitoring looks at the file, not the meeting.
If your caseload is large enough that this feels like a second job, that is a real finding rather than a personal failing — the caseload management guide deals with triage when the tracker is honest and the numbers still do not work, and the SPED paperwork organization guide covers the wider system this one sheet sits inside.
Frequently asked questions
What dates should an IEP due date tracker contain?
Six recurring ones and three triggered ones. Recurring: the annual review date (34 CFR § 300.324(b)(1) — periodically but not less than annually), the triennial reevaluation date (§ 300.303(b)(2) — at least every 3 years), the progress-report dates you promised in the IEP itself (§ 300.320(a)(3)(ii)), the ESY decision point, the transition-age triggers, and the transfer-of-rights notice date. Triggered: initial evaluation clocks from the date of consent (§ 300.301(c)(1)), transfer-student comparable-services clocks (§ 300.323(e)-(f)), and any reevaluation requested by a parent or teacher (§ 300.303(a)(2)). The recurring dates go in the tracker at the start of the year; the triggered ones get added the day the trigger happens.
Is the IEP annual review due on the anniversary of the meeting or the anniversary of the IEP start date?
The safe answer is: on or before the anniversary of the date the current IEP took effect, which is why your tracker should store the IEP's effective date and not just the meeting date. 34 CFR § 300.324(b)(1)(i) requires the IEP Team to review the IEP periodically but not less than annually, and § 300.323(a) requires an IEP to be in effect for each child at the beginning of each school year. Many districts and states set an internal deadline earlier than the anniversary to build slack for rescheduling. Track both dates and drive the reminder off the earlier one.
Does the triennial reevaluation deadline mean the meeting or the evaluation?
The reevaluation must occur at least once every 3 years (34 CFR § 300.303(b)(2)), which means the evaluation work and the eligibility determination — not just a meeting on the calendar. Because consent, testing windows, and report writing all sit in front of that date, a working tracker carries a second column: a start-the-process date set well before the legal deadline. A triennial due in April with a consent request sent in March is a deadline you will miss.
How far ahead should an IEP due date tracker warn you?
Different lead times for different deadlines, which is the reason a single 'due date' column is not enough. Annual reviews need roughly 30 days (notice, scheduling, drafting). Triennials need 60 to 90 days (consent, assessment windows, report writing, eligibility). Progress reports need whatever your grading period requires for data collection, which usually means starting on day one of the period. Building a lead-time column and sorting by start date rather than due date is the single change that turns a tracker from a record of what you missed into a plan for what to do this week.
Do the evaluation timelines count calendar days or school days?
It depends on the state, and getting the unit wrong is one of the most common tracker errors. Federal law sets 60 days from parental consent for the initial evaluation but explicitly defers to a state-established timeframe (34 CFR § 300.301(c)(1)). Nevada, for example, uses 45 school days (NAC 388.337), so its clock pauses over breaks. Alabama uses 60 calendar days plus 30 more for eligibility, and its rule says the clock runs through summer vacation (Ala. Admin. Code r. 290-8-9-.02). Store the unit alongside the number in your tracker, and check your own state's rule before you compute a single date.
What happens if an IEP due date is missed?
It becomes a compliance issue for the district, and how serious depends on what was missed and whether it affected the child's education. States monitor timeline compliance as part of IDEA general supervision, and missed annual reviews and overdue reevaluations are among the most commonly cited findings. The practical response is the same in every case: hold the meeting or complete the evaluation as soon as possible, document the reason for the delay contemporaneously, and — where services or content changed — consider whether prior written notice is owed. A tracker's real value is that it makes the near-misses visible while they are still fixable.
Should the tracker live in a spreadsheet or in the district IEP system?
Most district systems store the dates but do not surface them the way a case manager needs — they show one student at a time, not the next six weeks across a caseload. The workable pattern is to treat the district system as the record of truth and keep a lightweight caseload view (a spreadsheet or a printed sheet) that you drive your week from, rebuilt from the system's dates each grading period. Never let the side tracker become the only place a date exists.
Related guides
- IEP compliance checklist — what has to be true inside each IEP, once the dates are under control.
- SPED documentation checklist — every form the IEP process generates and who it goes to.
- Annual IEP review checklist — the work that fills the 30 days between start-by and due.
- IEP service log template — the minutes side of the compliance record.
Getting the due date right in the first place
A tracker is only as good as the date you enter, and the date depends on which kind of day your state counts. The evaluation timeline by state chart shows the clock, the day type, and the finish line for 29 states, so you can set the tracker from the rule rather than from habit.