A phase-by-phase checklist for walking into an IEP meeting with the evidence already in hand. It moves from confirming the reporting window, through collecting chart and incident evidence, to writing a plain-language summary, so the team is not scrambling for data while the meeting is underway.

Phase 1: confirm the window and the date

Verify the reporting start and end dates the team intends to discuss and confirm they match the meeting date. Check for holidays, testing days, absences, substitute days, and schedule changes inside that window. Knowing the gaps before anyone else points them out keeps the data credible.

Phase 2: collect chart and incident evidence

Pull the daily goal trends, any ABC incident notes, parent signatures, and communication logs that help explain what changed. You are not building a giant packet; you are making sure the story is backed by evidence instead of memory. Flag any missing logs so you can explain rather than hide them.

Phase 3: export the progress report

Export the PDF progress report before the meeting packet is finalized, and add team context where the numbers need interpretation. A report is strongest when trend data sits next to plain-language notes from the educators who know the student. Do this early so a last-minute export is not what holds up the packet.

Phase 4: prepare the plain-language summary

Write a short summary that says what the data suggests, what context matters, and what the team should adjust next. Bring interpretation, not just percentages, and a few concrete examples. If anyone asks a hard question, the daily logs, incidents, and signatures behind the summary are what hold it up.