How to Write Prior Written Notice (PWN)
Prior Written Notice is not a generic meeting summary. When 34 CFR §300.503 is triggered, document the action proposed or refused, why, the evidence used, alternatives considered and rejected, other relevant factors, procedural-safeguard information, and help resources. Follow state procedures for format and timing without inventing a universal federal day count.
PWN is triggered by an agency proposal or refusal involving identification, evaluation, educational placement, or FAPE—not simply because an IEP meeting occurred. Draft from the actual decision: what the agency proposes or refuses, why, which evaluations or records support it, which alternatives were considered and rejected, and what other factors mattered. The notice must also carry the required procedural-safeguard and assistance information under §300.503.
What a strong Prior Written Notice includes
PWN is a procedural notice, not a measurable student goal. Do not force Condition → Behavior → Criterion into the notice. The useful structure is action proposed/refused → why → evidence relied on → options considered/rejected → other relevant factors → procedural-safeguard/help information, written so the rationale matches the actual record.
Federal anchor: 34 CFR §300.503 sets the PWN trigger and required notice content; state procedures may add form or timing details.
Action — what the agency proposes/refuses: State the actual decision. Reason — why the agency made that decision: Connect reason to student-specific evidence. Basis — evaluations/records/reports used: Name the evidence. Alternatives — other options considered + why rejected: Shows the decision path. Other factors — relevant context: Include only what influenced the decision.
Draft PWN from the decision record, not from memory after the fact. Pull the actual proposal or refusal, the evaluations/assessments/records/reports relied on, the reasons for the decision, the alternatives the team considered and rejected, and other factors that truly influenced the agency's action. PWN is required for the proposal/refusal triggers in §300.503; it is not a generic meeting recap for every unchanged item.
PWN is easier to draft accurately when you also have the underlying meeting and amendment record, so use IEP meeting preparation, IEP amendments, and PLAAFP writing.
How to get a baseline
For PWN, “baseline” is the decision record that exists before the agency writes the notice. Gather the parent request or agency proposal/refusal, relevant evaluations, assessments, records, reports, classroom data, and the options the IEP Team actually considered. Do not invent new rationale after the decision simply to make the notice sound complete.
Identify the trigger first. Under 34 CFR §300.503, PWN is required a reasonable time before the public agency proposes or refuses to initiate or change the identification, evaluation, educational placement, or provision of FAPE. State procedures may specify forms or additional timing details, so check local requirements rather than quoting a made-up federal day count.
Create a one-page drafting sheet with seven boxes: action proposed/refused; why; evaluations/records used; other options considered; why rejected; other relevant factors; procedural-safeguards/help information. If one box cannot be filled from the record, the writer has found a documentation gap that should be resolved before finalizing the notice.
Example PWN decisions and documentation
These PWN models are drafting examples, not legal templates for a particular student. Any annual-goal language mentioned in a notice still has to be individualized from that student’s data and IEP Team decisions.
PWN examples should read like documentation of an agency proposal or refusal, not like annual goals. The three models below are illustrative only; teams must use the student's actual record, the action under consideration, and the evaluations, records, alternatives, and other factors relevant to that decision. State forms may add fields, but the federal content requirements remain the floor.
Three compact PWN models
Model 1 — proposing an added service. The LEA proposes to add 30 minutes per week of direct specialized reading instruction beginning on the date identified in the IEP. The team proposes this change because three recent reading probes remain below the expected goal trajectory despite documented changes in instructional grouping and practice opportunities. The team relied on the probes, classroom work samples, teacher data, and the current evaluation. It considered continuing the current service level and increasing only accommodations; those options were rejected because current data show a need for additional specially designed instruction. The notice should also include the required procedural-safeguards statement, sources of parent assistance, and any other relevant factors.
Model 2 — refusing a parent request. The LEA refuses the request to discontinue all small-group math support at this time. The team considered current unit assessments, three problem-solving probes, classroom independence data, and parent and teacher input. Although accuracy has improved, the student continues to require explicit problem-solving instruction and prompting to complete multi-step grade-level tasks. The team considered reducing the support immediately and a gradual reduction with additional data collection; it rejected immediate removal because the current data do not show independent performance at the level described in the IEP. Include procedural-safeguards information, assistance sources, and other relevant factors on the required form.
Model 3 — proposing reevaluation. The LEA proposes a reevaluation in the identified areas because existing classroom, progress-monitoring, and prior evaluation data do not provide enough current information to determine the student’s educational needs and whether changes to services are warranted. The team considered relying on existing records alone but rejected that option because key questions remain unresolved. The notice should identify the specific records and assessments used as the basis for the proposal, describe other considered options, and include all remaining §300.503(b) elements in understandable language.
A seven-part drafting check
Before sending PWN, read the notice once for each required element. First, can a parent identify the exact action proposed or refused? Second, does the notice explain why? Third, does it name the evaluations, assessments, records, or reports used as the basis? Fourth, does it contain the procedural-safeguards statement and explain how to obtain a copy when applicable? Fifth, does it list sources for help understanding IDEA? Sixth, does it describe other options the IEP Team considered and why they were rejected? Seventh, does it describe other relevant factors?
Then do a plain-language pass. Replace internal abbreviations with understandable terms, remove vague phrases such as “based on team consensus,” and make sure the rationale matches the actual data discussed. PWN should show the path from evidence to decision without overstating what the evidence proves.
Make the notice understandable to someone who was not in the meeting
A useful PWN should stand on its own. Read the draft as though the reader did not hear the team discussion. The notice should make clear what the LEA proposes or refuses, why, which evaluation procedures or records were used, what other options were considered, why those options were rejected, and what other factors mattered. Avoid shorthand such as “team agreed” or “data support the decision” without identifying the actual decision and evidence. The goal is not to recreate meeting minutes; it is to create a concise record that explains the agency’s action in a way a parent can follow later.
How to write the matching present level
A PLAAFP belongs in PWN only when current educational performance is part of the reason for the proposal or refusal. Do not force a present-level paragraph into notices about issues that turn on other evidence.
Example: if the agency proposes adding specialized reading instruction because three probes show persistent decoding errors, the PWN can cite the current reading data as part of the evidence used. If the agency refuses a request for a particular device because functional trials show equal access with an existing support, describe those trials accurately instead.
Keep the notice consistent with the IEP and evaluation record. A PWN that gives a rationale different from the team’s actual discussion creates confusion and weakens the audit trail.
Progress monitoring
PWN itself is not a progress-monitoring instrument. The follow-up task is to verify that the proposed/refused action, the final IEP language, and the implementation record stay aligned.
For an accepted service or goal change, confirm the effective IEP language and then monitor the student outcome through the normal goal/service system. For a refusal, preserve the evidence and explanation supporting the decision and follow any required local procedural steps.
Use a quality check before sending: could a parent who did not attend the meeting understand what the agency decided, why, what evidence it relied on, what alternatives were considered, and where to get help understanding procedural safeguards? If not, revise the notice for clarity rather than adding legalistic filler.
Common mistakes
For Prior Written Notice (PWN), these errors most often break the link between the data sheet and the decision the IEP Team needs to make:
Using PWN as a generic meeting recap. Leaving out the evaluations/records used as the basis. Writing 'team decided' without explaining why. Failing to describe alternatives considered. Using boilerplate procedural language unrelated to the student. Inventing a state-specific timeline without checking state rules.
Read the finished PWN as a parent who was not part of the staff conversation. The action proposed or refused, the reason, evidence relied on, options rejected, other relevant factors, procedural-safeguards information, and sources of assistance should all be identifiable from the notice itself. Then verify any state-specific form or timing requirements without replacing the federal 'reasonable time' rule with an invented day count.
FAQ
Paste your assessment data and generate an IDEA-compliant, individualized goal in seconds.
Try it free →