Prior Written Notice (PWN) in Special Education: What It Is and What It Must Include

Prior Written Notice (PWN) is the school district's formal explanation when it proposes, or refuses, to change your child's special education program. It is a federal procedural safeguard, not optional. PWN must be in writing, must explain why, and must list what the district considered.

Take a third grader with autism whose IEP team proposes to remove the 1:1 aide because the school says she is doing better. Federal law requires the district to put that proposal in a written Prior Written Notice that explains the data the team relied on, the alternatives considered, and the procedural rights you have to disagree. The PWN is the document that turns the conversation in the IEP meeting into a procedurally clean record.

This guide walks through what PWN must contain per the federal regulation, when the district must issue one, an autism-specific scenario showing PWN in practice, what to do when the notice is missing or vague, and how PWN timing varies state by state.

What a Prior Written Notice Must Contain

Federal regulation 34 CFR §300.503(b) lists 7 specific pieces of information the school district must include in every PWN. A notice missing any required content is procedurally defective on its face.

The 7 required contents:

1. A description of the action proposed or refused. The PWN names exactly what the district is doing or declining to do (changing placement, denying an evaluation, modifying related services).
2. An explanation of why the agency is proposing or refusing the action. The PWN explains the reasoning, not just the outcome.
3. A description of each evaluation procedure, assessment, record, or report the agency used as a basis for the proposed or refused action. The PWN names the data: which evaluations, which test scores, which observations.
4. A statement that parents of a child with a disability have protection under the procedural safeguards. The PWN reminds parents that procedural-safeguard rights apply (34 CFR §300.500).
5. Sources for parents to contact to obtain assistance in understanding the provisions of Part B. The PWN lists where parents can get help (parent training and information centers, state advocacy organizations).
6. A description of other options that the IEP team considered and the reasons why those options were rejected. The PWN documents the alternatives that did not get picked, not just the chosen path.
7. A description of other factors that are relevant to the agency's proposal or refusal. The PWN can include anything else relevant to the decision (state policy, district capacity, parent input).

These 7 contents are not optional; 34 CFR §300.503(b) requires every PWN to include each one. The notice must also be written in language understandable to the general public and provided in the native language of the parent or another mode of communication used by the parent unless clearly not feasible (34 CFR §300.503(c)).

When the District Must Issue a Prior Written Notice

PWN attaches to a specific set of district actions. Under 34 CFR §300.503(a), the district must issue PWN a reasonable time before it proposes or refuses to initiate or change the identification, evaluation, educational placement, or provision of a free appropriate public education (FAPE) to a child with a disability. The statutory anchor for the same rule is 20 USC §1415(b)(3), which makes written notice one of the procedural safeguards Congress built into IDEA itself.

In practice, the most common PWN trigger events are: starting or refusing an initial evaluation, finding or not finding the child eligible for special education, drafting or changing the IEP, changing placement along the continuum, adding or removing related services, and graduating or exiting the child from special education. Any of these triggers PWN. A casual hallway conversation does not, but a written or verbal commitment by the district to take or refuse one of these actions does.

The PWN trigger events overlap with the least restrictive environment decision (any placement change triggers PWN) and the present levels (PLAAFP) evaluation cycle (any new evaluation data prompts PWN). Because PWN sits on top of the broader IDEA procedural safeguards framework at 34 CFR §300.500, every parent walking into an IEP meeting should expect a PWN to follow any decision the team makes that fits the trigger list. If the district resolves something at the meeting and never sends a written notice, the procedural record is incomplete.

Federal regulation does not define "reasonable time" in days; states may. Pennsylvania defines it as 10 calendar days under 22 Pa. Code §14.162; most other states leave it as the federal default. The state callout below names the state DOE policy document for CA, TX, FL, NY, and PA. PWN also connects to the bigger question of FAPE: every PWN is implicitly a statement about whether the proposed or refused action is consistent with the district's FAPE obligation, and parents who want to anchor a disagreement to the FAPE standard can do so within the PWN response. For a foundation walkthrough of how the IEP itself is structured, see what an IEP is.

An Autism-Specific Example: Proposed Removal of a 1:1 Aide

Take a third grader with autism whose IEP currently includes a 1:1 aide during academic blocks. Mid-year, the team observes the child managing transitions and writing tasks with fewer prompts, and the district proposes to remove the aide. Under 34 CFR §300.503, the proposal triggers a PWN.

The PWN must explain that the district proposes to remove the 1:1 aide (action), describe the observations and progress data the team relied on (basis), list the alternatives the team considered like reducing the aide's hours instead of removing entirely or assigning a shared aide across two students (other options), state the parent's procedural rights to disagree, and describe any other relevant factors (transition planning, regression risk, state policy). If the PWN says only "the team has decided to remove the aide" without naming the data, the alternatives, or the rationale, the notice is procedurally defective on its face under 34 CFR §300.503(b).

A defective PWN is not just a paperwork issue. The notice is the parent's procedural anchor for any disagreement that follows; if the notice is missing required content, the parent's response can name that gap and ask the district to issue a compliant PWN before any change takes effect. In the 1:1 aide scenario, the parent might respond by requesting that the aide remain in place pending an amended PWN, by asking for the specific data observations and dates the district relied on, and by listing the alternatives the parent believes the team should have considered (a fade plan over a semester, a shared aide rather than full removal, an itinerant behavior consultant in lieu of a dedicated aide). The conversation moves from a yes-or-no to a documented analysis grounded in the procedural framework.

What to Do When the PWN Is Missing, Vague, or You Disagree

When a Prior Written Notice is missing, vague, or you disagree with the proposal, the path forward is documentation, not confrontation. Document the absence or the disagreement in writing; ask the district to issue a compliant PWN under 34 CFR §300.503(b) if the original is incomplete; keep dated copies of every notice and every response. The written record is what every later procedural option (mediation, state complaint, due process hearing) depends on.

Procedural-safeguard violations are a recognized basis for state complaints and due process hearings under 34 CFR §300.151 and 34 CFR §300.507; talk to a special-education attorney before pursuing either formal route. State complaints are filed with the state DOE and trigger a written investigation; due process hearings are formal adjudications before a hearing officer. Both routes have technical procedural rules and short timelines, which is why early documentation matters.

The IEP Advocacy Letter Builder drafts a written request that names the procedural gap, cites the regulation, and gives the district a clean ask to respond to. The letter is the documented step that anchors every later option. Parents who also have a 504 plan should review the 504 Accommodations for Autism guide for the parallel civil-rights procedural framework under Section 504, and the IEP vs 504 Plan walkthrough to clarify which framework governs the proposed change before drafting a response.

Free legal help is available in every state through Parent Training and Information centers; you can find yours at the Center for Parent Information and Resources. Most state-level disability rights organizations also offer free consultations on procedural questions. The advocacy letter step almost always comes first; documenting the procedural gap in writing strengthens every later route.

How Prior Written Notice Timing Varies by State

Federal IDEA leaves PWN timing as "a reasonable time before" the proposed action; the federal regulation does not name a specific number of days. Several states define timing more precisely. Pennsylvania requires PWN at least 10 calendar days before the action under 22 Pa. Code §14.162; the state-specific timing is stricter than the federal default and is documented in the state callout below. Connecticut requires PWN 5 school days in advance; Massachusetts requires it 10 days in advance within a 30-day window. Most other states (California, Texas, Florida, New York) leave the timing as the federal "reasonable time before" default.

The state callout below names the state-DOE policy document for California, Texas, Florida, New York, and Pennsylvania. If your state is not listed, the federal "reasonable time" standard at 34 CFR §300.503(a) governs, and your state DOE procedural safeguards notice will clarify whatever local detail applies. State services for autistic children also intersect with PWN: California's Lanterman Act and Regional Center system operates under its own procedural-notice rules that parallel federal IDEA procedural safeguards. Reading the state procedural safeguards notice front-to-back once is worth the time; it lays out the timing, the dispute-resolution routes, and the contact points specific to your state.

A Quick Recap for Parents

Before any IEP meeting where the team might propose a change, keep these five anchors in mind:

• PWN is a federal procedural safeguard at 34 CFR §300.503, not optional and not waivable by district policy.
• PWN must contain 7 specific pieces of information per §300.503(b); a notice missing any required content is procedurally defective.
• Federal timing is "a reasonable time before"; some states define it more precisely (PA: 10 calendar days).
• The PWN is the documented record the parent uses to anchor any later disagreement; keep dated copies.
• When the PWN is missing or vague, the path forward is a written request, not a confrontation.

For more on navigating special education, see the IEP vs 504 Plan walkthrough, the least restrictive environment guide, the present levels (PLAAFP) explainer, and the 504 Accommodations for Autism guide, or use the IEP Advocacy Letter Builder to draft a written request when a PWN is missing, vague, or you disagree with the proposal.