Prior Written Notice: What It Is and Why Schools Often Skip It
This post also speaks directly to facility staff and case managers, since Prior Written Notice is one of the most commonly violated — and most easily fixed — compliance requirements in special education.
Picture the meeting. A case manager says, almost in passing, “We looked at adding the extra pull-out session, but the team felt the current supports were sufficient.” Heads nod. The meeting moves on to scheduling. Nobody writes anything down beyond a line in the minutes. Three months later, the parent wants to know exactly why that request was denied, wants to see what data the team actually reviewed, and discovers there is nothing — no letter, no explanation, no record of the reasoning beyond a sentence someone half-remembers from a meeting that ran long.
That gap is not a small oversight. It’s a specific, named, legally required document that simply never got sent. Prior Written Notice is one of the most consequential rights under IDEA, and it is also, without much competition, one of the most routinely skipped. Not because schools are hiding something, usually. Because it’s easy to treat a verbal explanation in a meeting as good enough, when the law is explicit that it isn’t.
What Prior Written Notice actually is
Prior Written Notice, often shortened to PWN, is a written document a school district is legally required to provide to parents any time it proposes to initiate or change — or refuses to initiate or change — the identification, evaluation, educational placement, or provision of FAPE to a child. That’s a wide net. It covers decisions to start an evaluation and decisions to refuse one. It covers a change in placement and a refusal to change placement when a parent requested it. It covers a new service being added and a requested service being denied.
The notice has to be given a reasonable time before the school implements the proposed action — not after, not simultaneously, before. And it isn’t a blank explanation. IDEA specifies what must be in it: a description of the action proposed or refused, an explanation of why the district is proposing or refusing it, a description of each evaluation procedure, assessment, record, or report the district used as a basis for the decision, a statement that parents have protection under procedural safeguards, sources for parents to contact for help understanding the law, and a description of any other options the team considered along with the reasons those options were rejected.
PWN is the document that turns “we decided” into “here’s exactly why, based on exactly what” — and its absence is the single easiest procedural violation to prove, because a missing document doesn’t require interpretation.
That last clause — other options considered and why they were rejected — is the part that gets skipped almost universally, even in notices that technically exist. A form letter that says “the team decided a 504 was not appropriate” without naming what alternatives were on the table and why they were dismissed is a PWN in name only. It fails the actual requirement while looking, on the surface, like compliance.
Why this document exists at all
It’s worth understanding what PWN is actually for, because that context explains why it matters even in cases where the outcome would have been the same either way. Special education decisions involve an enormous amount of professional judgment, made by people with more training in the subject than the parent sitting across the table. That imbalance is real and, in most cases, appropriate — that’s what the expertise is for. But an imbalance of expertise without a corresponding transparency requirement becomes an imbalance of power. PWN is the mechanism that keeps professional judgment accountable to something other than itself. It forces a team to articulate its reasoning in a form that can be reviewed, questioned, and — if necessary — challenged.
It also does something less obvious but just as important: it creates a contemporaneous record. Memory is unreliable, and disputes over what was “actually said” in a meeting six months ago are almost impossible to resolve without documentation. PWN removes the ambiguity. Either the letter exists, describing the decision and its basis, or it doesn’t. There’s no room for competing recollections about a document that was either sent or wasn’t.
Where it gets skipped, and why
In practice, PWN gets bypassed in a few predictable ways, and none of them are usually intentional deception — which doesn’t make them acceptable, but does explain why they’re so common. The most frequent is the “verbal explanation as substitute” pattern: a decision gets discussed and explained out loud in a meeting, everyone nods, and the team treats that conversation as sufficient because it felt thorough in the room. It isn’t sufficient. The law requires the written document regardless of how clear the verbal explanation was.
The second pattern is the generic form letter — a template PWN that gets filled in with minimal specifics, technically sent, but missing the actual substance the law requires: what data was reviewed, what alternatives were considered, why they were rejected. This is compliance in form without compliance in function, and it’s often harder to catch than an outright missing notice because something did arrive in the mail.
The third is simple case-load overwhelm. A case manager tracking dozens of files, running multiple meetings a week, treats PWN as one more form in a stack of forms and lets it slip, not out of disregard for the family but because the system rewards speed and nobody built in a hard stop that prevents a meeting from closing without it.
None of these explanations change the legal reality. A parent is entitled to that notice regardless of why it didn’t arrive, and “we were busy” is not a defense that holds up in a state complaint.
What to do when PWN doesn’t show up
If a decision was made — a service denied, a placement changed, an evaluation refused — and no written notice followed, the response doesn’t need to be an immediate escalation to due process. Start with a direct, dated written request: an email or letter simply asking for the Prior Written Notice regarding the specific decision, referencing the date of the meeting where it was discussed. This does two things at once. It gives the school a straightforward chance to correct an oversight, and it creates your own written record showing you asked, with a timestamp, regardless of what happens next.
If that request goes unanswered or gets brushed off, that’s the point where a state complaint becomes a genuinely useful tool, since PWN failures are exactly the kind of procedural violation state complaint processes are built to address quickly, without requiring an attorney or a hearing. Reference the specific decision, the date it occurred, and the fact that no written notice was provided within a reasonable time. This isn’t an aggressive move. It’s using the system as designed.
For staff and case managers: build PWN into the workflow, not the exception
The single most effective fix for chronic PWN gaps isn’t more training on what the law requires — most case managers already know, in the abstract, what PWN is. The fix is structural: no meeting closes, no decision gets implemented, without the PWN drafted the same day, before the file gets set aside for the next case. Treat it the way a clinic treats a discharge summary — not optional documentation completed if time allows, but a required step that blocks the process from moving forward until it’s done.
It also helps to build the “other options considered” section into your actual planning process rather than writing it retroactively. If a team is discussing alternatives during a meeting — and a well-run meeting always should be — capture that discussion in real time. It becomes both a better internal decision record and a PWN that will actually hold up if it’s ever reviewed by a hearing officer or state investigator. The teams that get burned by PWN complaints are almost never teams that made bad decisions. They’re teams that made reasonable decisions and then couldn’t prove it.
What to actually do with this
If your child’s IEP has changed in any way in the last year — a service added, removed, a placement shifted, an evaluation refused — go back and check whether a Prior Written Notice actually arrived, and whether it contained real substance: the data reviewed, the alternatives considered, the reasoning behind the choice. If it didn’t, ask for it in writing this week, dated, specific, and calm. This is not a confrontation. It’s a document you were always entitled to receive.
Bottom line
Prior Written Notice isn’t a bureaucratic afterthought tucked into a folder of paperwork — it’s the legal record of why a decision about your child was made, and its absence is one of the clearest, most provable violations in special education law. If it didn’t arrive, ask. If it doesn’t come the second time, file. The document exists precisely for that moment.