- Confirm the reporting window and meeting date.
- Review missing logs, unusual schedule days, and incident context.
- Export progress reports before the meeting packet is finalized.
- Bring plain-language interpretation, not just percentages.
- Walk in with timestamped evidence that holds up if the meeting turns tense.
IEP meetings go better when the team can find the evidence quickly. Use this checklist to review daily logs, incidents, parent signatures, and progress reports before the meeting window closes.
Review the reporting window
Start by confirming the start and end date your team intends to discuss. Missing logs, holidays, testing days, absences, and schedule changes should be understood before the data is summarized.
Collect chart and incident evidence
Look at daily goal trends, parent signatures, ABC incident notes, and any communication logs that help explain what changed. You are not trying to overload the packet, just trying to avoid relying on memory.
Prepare a plain-language summary
A useful progress summary explains what the data suggests, what context matters, and what the team should adjust next. Percentages are helpful, but they rarely tell the whole story by themselves.
Avoid the common prep mistakes
The most common mistake is summarizing from memory the night before. By then the details that explain an outlier day have faded, and a parent who remembers that week clearly will notice the gap. Pull the actual logs and let the timestamps do the work. A second mistake is cherry-picking the good weeks. If you show only the stretch where the trend looked strong, you have built a packet that crumbles the moment someone asks about the months you left out.
Watch for the silent reframe too. Phrases like seems better or having a rough patch feel honest, but they invite debate because they are opinions. Replace them with what the chart shows: requested a break independently on nine of fifteen days, up from three the month before. When the number sits next to the claim, there is far less to argue about.
Finally, do not wait until the packet is locked to notice a reporting gap. If a goal has only a handful of data points, that is worth knowing a week out, while there is still time to log a few more days honestly or to frame the limited window as preliminary rather than conclusive.
Prepare for a meeting that turns adversarial
Most meetings stay collaborative, but some do not, and the ones that turn tense are exactly the ones where preparation pays off. When a parent arrives with an advocate or attorney, the question shifts from how is the student doing to can you prove it. Objective, timestamped daily logs answer that question in a way a remembered impression never can. Each entry shows what was scored, on which date, against a goal that was defined in advance.
Build the packet so it stands on its own. Export the progress report as a PDF, keep the ABC incident notes attached to their dates, and have the communication log ready to show what was shared with the family and when. The point is not to win an argument; it is to make the record so clear that there is little left to dispute. FERPA, role-based access, and your district data agreement are the floor here, so confirm that what you bring to the table matches what the family has already been able to see.
Frequently asked questions
Should every daily log be included in the meeting packet?
Usually no. Use daily logs as the evidence base, then include a clear summary and relevant examples.
What if there are missing days?
Do not hide them. Note why data is missing when you know the reason, and avoid over-interpreting a short window.
Can parent signatures be part of the review?
They can help show communication history, but they should be interpreted carefully and in context.
How early should I start prepping the evidence?
Begin about a week out. That gives you time to spot a thin reporting window, log a few more honest days if needed, and export progress reports before the packet is finalized, rather than reconstructing everything the night before.
What is the single most defensible thing I can bring?
An exported progress report backed by timestamped daily logs. It shows what was scored, on which dates, against goals that were set in advance, which is exactly the kind of record that holds up if a meeting gets tense.