Key takeaways
- Start two weeks out, while there is still time to log a few more honest data points.
- Every goal needs a baseline, a current level, and an on-track call before the packet is final.
- Write a one-page plain-language summary; the family should not have to read a data table to follow the meeting.
- Prep the team on one real question a family is likely to ask, and answer it from the logs.
Prepare for an IEP meeting in four passes. Two weeks out, confirm the data window and find the gaps. One week out, pull the evidence and export the progress report. Two days out, write a one-page plain-language summary. The day before, prepare the team. Each item below has a done-when standard, so you can tell a finished item from a started one.
Pass 1: two weeks out
| Item | Done when |
|---|---|
| Meeting date, type, and attendees confirmed | You know whether it is an annual review, a reevaluation, or an amendment, and who is invited |
| Reporting window set | Start and end dates for the data you will discuss are written down |
| Gaps in the window listed | Holidays, testing days, absences, and substitute days are noted next to each goal |
| Thin goals flagged | Any goal with fewer than about six data points in the window is marked, with a plan to log the next days honestly |
| Input requested | General education teachers, providers, and paraprofessionals have been asked what they have seen and what the team should know |
| Family preferences checked | You know the family's preferred language, whether an interpreter is booked through the district, and how they want to receive materials |
Pass 2: one week out
| Item | Done when |
|---|---|
| Goal data pulled in date order | Each goal's data points for the window are in one place, oldest first |
| Baseline and current level found | Every goal has both numbers written next to it |
| On-track call made | Each goal is marked on track, progressing but not on track, not progressing, or met |
| Context reviewed | ABC incidents, communication log entries, and schedule changes that explain a dip or a jump are noted |
| Accommodation evidence summarized | Each accommodation has a delivery count and a note on whether it helped |
| Service minutes checked | Delivered minutes are compared with the minutes on the IEP, and any shortfall has a reason |
| Progress report exported | The PDF is exported and annotated where a number needs context |
For the accommodation row, preparing accommodation evidence for the annual review has a per-accommodation summary format. For the minutes row, the free IEP minutes calculator converts weekly, monthly, and yearly mandates so the comparison is like for like.
Pass 3: two days out
| Item | Done when |
|---|---|
| One-page summary written | Each goal gets one or two sentences naming the baseline, current level, direction, and on-track call |
| Examples chosen | Two or three concrete moments that show the student's progress are picked, with dates |
| Draft ideas for next year listed | Goals to continue, revise, or retire are noted with the data reason for each |
| Materials sent if your district does so | Anything the family receives ahead of time has gone out in their preferred language |
Goal: during independent reading, will remain on task for 15 of 20 minutes on 4 of 5 days.
Summary line: "At the start of the year, Aisha stayed on task about 9 of 20 minutes. This quarter she averaged 16 of 20, and she met the goal on 4 of 5 days in each of the last three weeks. We recommend moving to a 25-minute block next year."
The daily notes to progress report guide has a table of data patterns and the sentence that matches each, including flat and variable data.
Pass 4: the day before
| Item | Done when |
|---|---|
| Team walked through the summary | Everyone presenting knows the on-track call for the goals they speak to |
| Likely questions answered from the data | For each goal, the team can point to the data points behind the summary line |
| Roles set | Someone leads, someone takes notes, and someone watches the time |
| Materials ready | Printed or shared copies of the summary, the report, and the full logs are ready for anyone who asks |
Preparing the team in 30 minutes
When several staff contribute to one meeting, a short prep session saves the meeting from turning into five people reading their notes aloud. Run it on the actual student, not a hypothetical.
- Read the one-page summary aloud, five minutes. Everyone hears the same on-track calls before adding anything.
- Each person names two or three pieces of evidence, ten minutes. Not a stack of logs. The few data points or dated moments that carry the student's story for their goal.
- Answer one likely family question from the data, ten minutes. For example, "How do you know the break card is helping?" Practice answering with the baseline, the current count, and one example, in plain language.
- Agree on next-year ideas, five minutes. Decide which goal changes the team will propose and why, so the family hears one plan.
A family question at the meeting is a good sign. It means they are following the data, and a team that has answered one out loud beforehand tends to answer the rest with the same calm specifics.
What a finished prep looks like
A finished prep is a one-page summary, an exported progress report, a short list of examples, and the full logs in reserve. To see how those pieces fit into a single document, look at the sample evidence packet. If you are building next year's collection plan at the meeting, the complete guide to IEP progress monitoring covers schedules by measurement type, and Evident sends meeting reminders 30, 14, and 7 days out so pass 1 starts on time.
Common questions
How far ahead should I start preparing for an IEP meeting?
Two weeks is a workable minimum. It leaves time to spot a goal with too few data points and log a few more days honestly, collect input from other teachers and providers, and send anything your district shares with the family ahead of time.
Should every daily log go in the meeting packet?
No. Use the logs as the evidence base, then bring a one-page summary per goal and two or three concrete examples. Keep the full logs available in case someone asks to see the data behind a number.
What if a goal has almost no data?
Say so plainly in the summary, give the reason (for example, a schedule change in weeks four and five), report what the available points show, and do not fill the gap with estimates. Then use the meeting to set a collection plan the team can actually keep.
Who should I ask for input before the meeting?
Everyone who works with the student on a goal: general education teachers, related-service providers, paraprofessionals who collect data, and the family. A two-question message (what have you seen, what should the team know) sent two weeks out is usually enough.