Streamlining the Prior Written Notice (PWN) workflow

When Prior Written Notice is required

Under 34 CFR § 300.503(a), a district must give written notice to parents a reasonable time before it proposes, or refuses, to initiate or change the identification, evaluation or educational placement of the child, or the provision of a free appropriate public education to the child. The word "refuses" matters. When a parent asks for an evaluation, a service, an aide or a placement and the team says no, that refusal requires PWN just as much as a proposal does.

In file reviews, PWN problems tend to fall into three groups: notices that were never issued, usually for refusals or for changes made outside a meeting; notices issued but missing required content; and notices issued so late that they no longer serve as notice. All three are fixable with a defined workflow.

• Proposing or refusing an initial evaluation or reevaluation
• Proposing or refusing a change in eligibility or identification
• Proposing or refusing a change in services, goals or placement
• Exiting a student from special education, including graduation with a regular diploma

The seven required elements

Section 300.503(b) lists what the notice must contain. A PWN that omits any element is defective, even if the decision it describes was entirely appropriate. Use this list as a checklist on every notice before it leaves the building.

Pay particular attention to elements three and six. Element three requires a description of each evaluation procedure, assessment, record or report the agency used as a basis for the action, not a general statement that the team reviewed data. Element six requires a description of other options the team considered and why they were rejected. If the team considered nothing else, that is itself a problem worth noticing.

• 1. A description of the action proposed or refused by the agency
• 2. An explanation of why the agency proposes or refuses to take the action
• 3. A description of each evaluation procedure, assessment, record or report used as a basis
• 4. A statement that the parents have protection under the procedural safeguards and, if this is not an initial referral for evaluation, how a copy of the safeguards description can be obtained
• 5. Sources for parents to contact for assistance in understanding Part B
• 6. A description of other options the IEP team considered and the reasons those options were rejected
• 7. A description of other factors relevant to the proposal or refusal

Language and readability requirements

Section 300.503(c) requires the notice to be written in language understandable to the general public and provided in the parent's native language or other mode of communication, unless it is clearly not feasible to do so. If the native language or mode of communication is not a written language, the district must take steps to translate the notice orally or by other means, ensure the parent understands it, and keep written evidence that those requirements were met.

In practice, that means no unexplained acronyms, no pasted assessment jargon, and no single-sentence explanations like "per team decision." A parent reading the notice at home should understand what will change, why, and what they can do if they disagree.

A weak PWN explanation, rewritten

Before: "Action refused: 1:1 aide. Reason: not needed per team."

After: "The district refuses the parent's request, made at the October 14 IEP meeting, for a full-time one-to-one paraprofessional. The team reviewed classroom behavior data from September 8 to October 10, the September functional behavioral assessment, and teacher reports. These show that Maya is engaged during 78% of observed intervals with the current supports and that incidents requiring adult intervention have dropped from 6 to 2 per week since the behavior intervention plan began. The team considered a full-time aide and rejected it because the data show Maya is making progress with less restrictive supports and because constant adult proximity could reduce her independence goals. The team also considered adding paraprofessional support during transitions and lunch, which is included in the proposed IEP. The team will review behavior data again in eight weeks."

The rewrite names the request and who made it, identifies each data source, gives a reason rooted in the data, describes the alternative considered, and explains what happens next. Pair it with the procedural safeguards statement and assistance contacts, and the notice is complete.

Building a workflow that does not miss notices

The root cause of missed PWNs is usually ownership. If everyone assumes the case manager will issue it and the case manager assumes the meeting summary covers it, nobody does. Assign PWN issuance to a named role for every meeting and every out-of-meeting change, and make it a required step before an IEP can be marked final.

Draft the notice during the meeting, not after. The facilitator or note-taker should capture each proposal and refusal as it happens, along with the data cited and the options discussed. Reconstructing the reasoning from memory three days later produces exactly the thin explanations reviewers flag.

Remember that PWN applies outside meetings too. An amendment made without a meeting under § 300.324(a)(4), a decision to deny an evaluation request received by email, or a change in placement during a discipline process all trigger notice.

Auditing your notices

Pull a random set of IEP files each semester and check every PWN against the seven elements, the timing and the language requirements. Count refusals specifically; if your files show proposals but almost no refusals, it is likely refusals are being decided without notice.

TPA Ventures generates a PWN draft from the meeting record with each of the seven elements as a required field, and flags any proposal or refusal captured in the notes that has no corresponding notice. The district's staff still review and issue every notice, because the explanation has to reflect the team's actual reasoning.