IEP Meeting Prep Checklist for the Special Education Teacher

Quick Answer

Prepare an IEP meeting with current goal data, concise work samples, recent evaluations, implementation information, and student/parent/provider input. Draft PLAAFPs and goals as proposals, not fixed decisions. Use the prep window to close data gaps, identify unresolved team questions, and make sure the final—not draft—IEP reaches implementers afterward.

Meeting prep should make team discussion better, not make the decision before the team arrives. Bring current data, work samples, evaluation information, implementation evidence, parent concerns, and clearly labeled draft PLAAFP/goal/service language. Flag questions that still need team input. A strong prep packet helps the meeting move efficiently while preserving room to revise proposals based on discussion.

What a strong IEP meeting preparation includes

Meeting preparation organizes evidence and draft options; it should not pre-decide the IEP. Condition → Behavior → Criterion is useful when checking draft annual goals, but the preparation record itself should track data gaps, unresolved team questions, parent/student/provider input, documents to bring, and implementation issues that need discussion.

~2 weeks before — pull data, request missing input, flag gaps: Creates time to close evidence gaps. ~1 week before — draft PLAAFP/goals as proposals: Supports efficient review without fixing decisions. Several days before — organize agenda and participation: Centers unresolved decisions. Meeting day/after — revise, document, implement: Closes the loop from discussion to final IEP.

Build the meeting packet around decisions the team will actually have to make: current goal data, recent work samples and evaluation information, service/accommodation implementation evidence, parent concerns already raised, and draft language clearly labeled as draft. Preparation should make discussion easier, not predetermine the outcome. This checklist does not create a federal 'two-week' deadline; use state and LEA procedures for specific notice and timeline rules.

This is an educator workflow checklist.

For the documents that feed the meeting packet, use PLAAFP writing, Prior Written Notice, and measurable goal formula.

How to get a baseline

Two weeks before the meeting, audit the current IEP against the data you actually have. For each annual goal, pull the baseline, the most recent progress points, and one representative work sample or observation. For accommodations and services, check whether implementation records reveal recurring access problems or unclear wording.

Then list missing evidence. If a goal has not been monitored as written, do not hide the gap with a last-minute score. Collect what can still be collected validly, document the limitation, and bring the problem to the team. Recent teacher, provider, parent, and student input can add context, but it should not be used to fabricate a trend that was never measured.

Draft sections as working proposals. Mark them clearly as drafts and keep them editable so the meeting remains a team decision-making process rather than a presentation of a predetermined IEP.

Example IEP meeting-prep checkpoints

The examples in this section model meeting-prep decisions, not student performance standards. Use the student's current records and the team's unresolved questions to decide what belongs in the packet; do not turn a workflow example into a numeric IEP criterion. Any draft annual goal brought to the meeting still needs to be individualized from the student's current data and remains a team draft.

Two weeks before — Pull current goal data, work samples, service logs, attendance context, and teacher input; flag missing data early. (Condition: pre-meeting preparation window | Behavior: assemble current evidence | Criterion: enough time to close data gaps before meeting) How to measure: data packet checklist.

One week before — Draft PLAAFP and possible goals as proposals, label them as drafts, and leave room for parent, student, and team input. (Condition: drafting stage | Behavior: prepare proposed language | Criterion: avoid presenting decisions as already final) How to measure: draft review checklist.

Several days before — Confirm who needs to attend, gather student voice, and organize questions that require team decisions. (Condition: meeting logistics stage | Behavior: verify participants and open decisions | Criterion: meeting can address required topics efficiently) How to measure: meeting agenda.

Day before — Check that numbers in the PLAAFP match the units in proposed goals and that service/accommodation changes are supported by data. (Condition: final document review | Behavior: cross-check baseline, goal, and supports | Criterion: internal consistency) How to measure: document audit.

Meeting day — Use a visible agenda, summarize data briefly, invite parent and student input, and revise draft language as the team deliberates. (Condition: IEP meeting | Behavior: facilitate team decision making | Criterion: no predetermination) How to measure: meeting notes and revisions.

After meeting — Complete required documentation, communicate implementation responsibilities, and ensure staff have the final information they need. (Condition: post-meeting implementation | Behavior: close documentation and implementation loop | Criterion: responsibilities are clear) How to measure: final IEP and implementation checklist.

A two-week preparation timeline

About two weeks before: pull current annual-goal data, recent work samples, service logs, attendance information that affects interpretation, and the most recent evaluation. Ask gen-ed teachers and related-service providers for concise current input. Identify any goal that lacks enough recent data and collect what is missing.

About one week before: draft the PLAAFP and possible annual goals. Label them clearly as drafts. Cross-check every proposed criterion against the baseline unit. Review accommodations and services for implementation problems, not just whether they appear on the page. Gather parent concerns already communicated and plan how student voice will be included.

Several days before: organize the agenda around unresolved decisions, confirm required participants under your LEA process, and prepare a short data summary instead of a stack of unexplained printouts. If transition planning is involved, have current age-appropriate transition information ready.

Meeting day and after: present data neutrally, revise drafts as the team deliberates, capture agreed changes accurately, and make sure staff responsible for implementation receive the final information—not the pre-meeting draft.

Before closing your prep folder, run one consistency check: every number in a draft goal should be traceable to current data, every proposed support should connect to a documented need, and every unresolved question should appear on the meeting agenda. That single pass catches many avoidable meeting-time corrections.

Also confirm that draft dates, grade level, service names, and student identifiers are internally consistent. Small clerical errors can create confusion during implementation and later progress reporting.

Flag decisions that need team discussion before the agenda is full

As you review the file, mark questions that cannot be solved by editing a draft sentence: a service that is not producing the intended access, a goal with no comparable data, a parent concern that may require evaluation discussion, a transition need that has not been assessed, or accommodations that staff interpret differently. Put those items on the meeting agenda early enough that the team has time to discuss them.

Avoid using the preparation checklist to “finish” disputed decisions before the meeting. A strong draft reduces clerical work; it does not replace parent participation, provider input, student voice, or the IEP Team’s deliberation. Bring alternatives and the data supporting them rather than one polished option presented as already settled.

How to write the matching present level

Prepare each PLAAFP paragraph so the meeting can move from evidence to need to goal without hunting through separate documents. A useful prep note pairs the current metric with one sentence about educational impact and one question the team may need to resolve.

Example: “Current math problem-solving baseline: 40% correct on three comparable two-step word-problem probes with no more than one verbal prompt. Errors are concentrated in selecting the operation, not computation. Team question: should the annual goal isolate problem representation before adding multistep complexity?”

That is a draft analysis, not a pre-decided outcome. Bring the raw probes or summary sheet so team members can challenge or refine the interpretation.

Progress monitoring

After the meeting, replace drafts with the finalized IEP and distribute implementation information through the district’s approved process. Verify that gen-ed teachers, paras, and related-service staff who are responsible for implementation know the current goals, accommodations, supports, and service details relevant to their role.

Create the first data-collection dates before the paperwork disappears into the file. A strong meeting can still produce weak implementation if no one knows when the next probe, observation, or service review occurs.

Keep a short follow-up list for unresolved operational items: new data sheet, clarified accommodation wording, provider coordination, family copy, or staff training. Those tasks are not new IEP decisions; they are implementation steps arising from the final document.

Common mistakes

Most avoidable problems show up in one of these forms:

Presenting draft goals as final decisions. Bringing old data with no current baseline. Failing to reconcile conflicting service/accommodation information. Ignoring student or parent concerns received before the meeting. Using a giant data packet with no concise summary. Distributing a draft after the meeting instead of the final IEP.

Before the meeting, separate facts already established from decisions still open. Current goal data and evaluation results belong in the first group; proposed goals, service changes, placement questions, and unresolved parent concerns belong in the second. That distinction helps prevent a polished draft from being mistaken for a predetermined IEP and makes it easier to capture the team's actual decisions afterward.

FAQ

How early should a special education teacher start preparing for an IEP meeting?

A two-week preparation window can be a useful workflow because it leaves time to request teacher/provider input and close data gaps, but it is not a universal federal deadline. Follow state and LEA timelines for notices and meetings. Start early enough that current progress data, draft PLAAFP language, and student/parent input can be meaningfully reviewed.

Is it okay to draft IEP goals before the meeting?

Drafting proposed goals can make a meeting more efficient if they are clearly treated as drafts and remain open to team discussion and revision. The problem is predetermination—presenting a decision as fixed before meaningful parent and team participation. Bring data, explain the rationale, and be ready to change the wording, criterion, services, or supports.

What data should a case manager bring to an IEP meeting?

Bring current goal data, concise work samples, relevant evaluations, service and accommodation implementation information, teacher/provider input, and known parent/student concerns. Do not bury the team in paper. A short data summary that shows the baseline, current level, trend, and unresolved questions is usually more useful than a stack of unexplained printouts.

Should proposed services and accommodations be written before the meeting?

They can be drafted as proposals when current data support them, but they should not be treated as final before the team deliberates. Cross-check each proposed support against the documented need and implementation history. If the evidence is incomplete, label the issue as an open decision rather than filling the draft with a standard service package.

What should happen immediately after the IEP meeting?

Complete the required documentation, make sure final decisions match the discussion, provide or route notices and copies according to state/LEA procedures, and get the final implementation information to responsible staff. Remove or clearly archive pre-meeting drafts so teachers do not accidentally implement an outdated version of the IEP.

Need goals customized to your student?

Paste your assessment data and generate an IDEA-compliant, individualized goal in seconds.

Try it free →