Reading and Responding to a Draft IEP Before the Meeting
Case managers who send drafts out early and actually welcome feedback before the meeting will find validation, and a few pointed reminders, in the staff section below.
The email lands on a Tuesday, usually with a subject line as bureaucratic as everything else about this process — “IEP Draft for Review” — and a PDF attached that runs anywhere from eight to thirty pages. Somewhere in there is a description of your child that will shape their education for the next year. Most parents open it, skim it once, feel a familiar tightening in the chest, and close the laptop until the meeting itself. Understandable. Also a mistake with real consequences.
A draft IEP arriving before the meeting is not a courtesy copy. It’s an invitation to negotiate, and most families never take it.
Why the Draft Exists in the First Place
Under IDEA, districts aren’t required to send a fully finished document before the meeting, but many do, and increasingly it’s considered good practice — some states have moved toward requiring it outright. The logic is straightforward: a meeting where everyone’s seeing the proposed goals, services, and placement for the first time in real time is a meeting where genuine collaboration is nearly impossible. Nobody can process eight pages of present-levels data, service minutes, and goal language while simultaneously being asked to react to it out loud in front of five professionals who’ve had weeks to prepare.
The draft is the school showing its hand before betting. Not reading it before the meeting means you’re playing the same game blind.
That’s the entire purpose of getting it early: to shift you from reactive to prepared. A parent who’s read the draft twice, marked it up, and arrived with three specific questions is participating in the meeting. A parent seeing the language for the first time as it’s read aloud is attending it.
What “Draft” Actually Means, Legally
Here’s a distinction worth sitting with, because schools sometimes blur it, intentionally or not: a draft IEP is a proposal, not a done deal. The team, which includes you, has not yet finalized anything. If a draft arrives that reads like a finished product — polished, definitive, with no bracketed placeholders or obvious room for input — that’s worth naming in the room. You can say, plainly, that the document reads as though decisions have already been made outside the team process, and ask for that to be corrected on the record. A true draft should feel unfinished. If it doesn’t, something happened before you were looped in that shouldn’t have.
This matters because IDEA is explicit that parents are equal participants in developing the IEP, not reviewers of a decision already reached. A draft that arrives as a fait accompli quietly violates that principle even when nobody intends it maliciously. Sometimes it’s simply institutional momentum — the team met without you to “get a head start,” and nobody flagged that as a problem. Flag it as one anyway.
Reading the Present Levels Section First
Most parents jump straight to goals and services because that’s where the action seems to be. Start earlier than that. The Present Levels of Academic Achievement and Functional Performance section is the foundation everything else stands on, and if it’s wrong, everything built on top of it will be wrong too, no matter how well-crafted the goals sound.
Read this section asking one question of every sentence: does this match what I actually see at home? If the draft says your child “demonstrates increasing independence in multi-step directions” and you’re watching them melt down over a two-step bedtime routine, that’s not a minor wording quibble — that’s a data mismatch that will justify a lower level of support than your child needs. Present levels drive service minutes. An inflated present-levels section is often the quiet mechanism behind a service reduction nobody explicitly argued for in the room.
Write down the specific discrepancies with dates and examples. “On June 3rd, homework took ninety minutes with constant redirection” is usable. “He struggles more than this makes it sound” is not. Specificity is what makes your objection show up in the final document instead of dissolving into “parent expressed some concerns” in the meeting notes.
Testing Every Goal Against Three Questions
Goals are where vague, well-intentioned language does the most damage, because they sound reasonable and often are reasonable — just not ambitious enough, specific enough, or connected to your child’s actual needs. For every goal in the draft, run it through three questions before the meeting.
Is it measurable in a way that doesn’t rely on someone’s subjective impression? “Will improve reading comprehension” measures nothing. “Will answer four out of five literal comprehension questions after reading a grade-level passage, in three of four consecutive trials” measures something specific, and someone can either verify it happened or can’t.
Does the timeline match the need? A goal addressing a skill that’s actively regressing shouldn’t be written with a full annual timeline and no interim benchmarks. If your child is losing ground right now, the draft should reflect urgency, not the standard cadence.
Is this goal actually connected to your child, or is it boilerplate? Districts sometimes recycle goal language across students with similar disability categories, and it shows. If a goal reads like it could apply to any child with the same diagnosis rather than yours specifically, say so, and ask what data generated this particular goal for this particular kid.
Service Minutes: Where the Real Negotiation Happens
Everyone feels the goals section, but the service minutes section is where the actual resources get decided, and it deserves the same scrutiny as a contract, because that’s functionally what it is.
Compare the proposed minutes against what your child received the previous year, and if there’s a reduction, ask for the specific data that justifies it before the meeting, not during it. A reduction should be backed by evidence of mastery or reduced need, documented and dated. “The team feels he’s ready for less support” is a feeling, not a data point, and you’re entitled to ask what generated that feeling.
Also check the delivery model, not just the number. Thirty minutes of speech services delivered in a small group of four kids is not equivalent to thirty minutes one-on-one, and a draft can quietly shift from individual to group delivery without anyone flagging it as a substantive change. It is one. Note it as one.
Writing Your Response Before the Meeting
Once you’ve marked up the draft, don’t wait to raise your concerns live in the room where you’ll be processing everyone else’s reactions in real time too. Send a written response before the meeting — even a short one — listing your specific questions and proposed changes. This does two things. It gives the team time to actually prepare answers instead of improvising them, which sometimes gets you further than a live confrontation would. And it creates a paper trail showing exactly what you raised and when, which matters enormously if you ever need to dispute the final document later.
Keep the tone factual rather than heated. “I noticed the present levels describe increasing independence with multi-step directions; at home, two-step routines still require consistent redirection. Can we discuss this discrepancy and its impact on the proposed goals?” does more work than any version of the same point delivered with visible frustration, however earned that frustration is.
For Facility Staff and Case Managers: Sending Drafts That Actually Invite Response
If you’re the one drafting and circulating these documents, the instinct to send something polished and near-final is understandable — nobody wants to hand a family something sloppy. But a document that reads as finished discourages exactly the kind of engagement the law intends. Consider building in visible signals that this is genuinely a draft: bracketed notes indicating where the team still wants family input, present-levels language pulled directly and visibly from recent data rather than generalized summary, and a cover note that explicitly invites written questions before the meeting rather than just attaching the file silently.
Families who send detailed written responses before the meeting aren’t being difficult. They’re doing exactly what the process was designed to elicit, and a team that treats that engagement as friction rather than participation is misreading its own job. If a parent’s written response arrives with specific data-based objections, take the time to prepare a substantive answer before the meeting rather than fielding it live and improvised — it makes for a shorter, more productive meeting for everyone in the room, staff included.
Bottom Line
A draft IEP sitting unopened in your inbox until the night before the meeting is a chance at real participation, quietly wasted. Read the present levels against what you actually see. Test every goal for whether it’s measurable, urgent enough, and actually about your child. Scrutinize the service minutes like the resource allocation they are. And put your response in writing before you ever sit down at that table, because the version of you that’s had time to think clearly will always negotiate better than the version of you reacting in real time to language you’re seeing for the first time.