Prior Written Notice (PWN) Drafting — Reference Guide

Generated: 2026-05-10. Sources: 34 CFR §300.503 (federal binding), OSEP letters (federal guidance), state DESE/SDE/CDE templates (best-practice models), DCPS-specific language access requirements.

Use this doc when: drafting any PWN, especially for non-routine scenarios. The procedure docs in ../ (e.g., esy-pwn-decline.md) are Shannon's specific templates; this doc is the legal/professional foundation under them.

Part 1: Federal Requirements (34 CFR §300.503) — Binding

Source: 34 CFR §300.503 via IDEA.ed.gov | eCFR

Trigger — when PWN is required

Written notice must be given to parents a reasonable time before the LEA proposes or refuses to initiate or change:

1. Identification, evaluation, or educational placement of the child, OR
2. The provision of FAPE.

The seven required content elements

Every PWN must include:

1. Description of the action proposed or refused
2. Explanation of why the agency proposes or refuses to take the action
3. Description of each evaluation procedure, assessment, record, or report used as a basis for the proposed or refused action
4. Statement that parents have procedural safeguards protections and the means by which a copy can be obtained
5. Sources for parents to contact to obtain assistance in understanding IDEA
6. Description of other options the IEP Team considered and the reasons why those options were rejected
7. Description of other factors relevant to the agency's proposal or refusal

Language requirement

• Written in language understandable to the general public
• Provided in the parent's native language or other mode of communication, unless clearly not feasible

DC layer: Language Access Act

DCPS must provide written translations in Spanish, Amharic, and Mandarin Chinese for agency-wide documents. School-level documents must be translated into Spanish plus any language spoken by ≥3% of school population. Interpretation available in 240+ languages via Language Line.

For Spanish families: translation should be available within the school; do not send untranslated. For other languages: submit through DCPS Language Access Unit (languageaccess@k12.dc.gov, (202) 868-6508).

Part 2: Common Compliance Errors — What Reviewers Flag

Error 1: Boilerplate / cookie-cutter language

Most commonly flagged deficiency. Generic fill-in-the-blank notices that lack individualized explanation tied to the specific student's data. Reviewers specifically note when the same language appears across multiple students' PWNs.

Fix: Always cite student-specific data (assessment names + dates, specific data points, parent input received).

Error 2: "N/A," "See IEP," or blank fields

The PWN must be standalone — comprehensible without reference to other materials. Reviewers cite this as procedural violation even when the IEP itself contains the info.

Fix: Write it out, even if redundant with the IEP.

Error 3: Predetermination trap

Sending PWN before the IEP meeting (or making it appear the decision was made before) is a due-process red flag. Per OSEP: "providing prior written notice in advance of meetings could suggest...that the public agency's proposal was improperly arrived at before the meeting and without parent input."

Fix: PWN issues after the team meeting, before implementation.

Error 4: Implementing the IEP before issuing the PWN

"Negates the 'prior' in prior written notice." Notice must be provided after decision but before implementation.

Fix: Build a buffer between decision date and implementation date — some states (e.g., Connecticut) mandate 10 school days unless parent waives in writing.

Error 5: Language access failures

Federal violation if not translated/explained in parent's native language.

Fix: Submit translation requests through DCPS Language Access Unit BEFORE the PWN deadline. For Spanish: should be available in-school. For non-written languages: provide oral translation + document the parent understood.

Error 6: Pro-forma "options considered"

Leaving blank or writing "no other options were considered" without narrative.

Fix: Even if no alternatives were seriously weighed, name what would have been the natural alternatives and why they were ruled out (see Part 4 below for examples).

Error 7: Insufficient specificity in "basis for decision"

Listing test names without explaining what data drove the decision.

Fix: Cite specific assessment results by name + date AND specific data points (e.g., "classroom reading probe dated [month], showing X% accuracy").

Part 3: Field-by-Field Drafting Guidance

Element 1 — Description of the proposed/refused action

Be specific. Not "change in services" but "increase in OT direct services from 30 minutes weekly to 60 minutes weekly." Not "change in placement" but "from a co-taught general education setting for ELA/Math to a self-contained special education classroom for ELA/Math."

Element 2 — Explanation of why

The "why" is student-specific rationale tied to data, not policy boilerplate. Reference Endrew F.'s "reasonably calculated to enable a child to make progress appropriate in light of the child's circumstances" standard for placement-change rationale.

Element 3 — Basis for decision (data specificity)

What counts as evaluation procedure, assessment, record, or report:

• Formal assessments (psychoeducational, speech-language, OT/PT) — cite by name + date
• State assessments and district-wide assessments with dates
• Current and prior IEP goal progress data (cite goal area + current performance level)
• Classroom-based observations — note date + observer
• Progress monitoring data (cite tool, date range, result)
• Parent-provided information
• Teacher/related-service-provider reports
• Review of existing evaluation data (REED) — document explicitly

Critical for evaluation-related PWNs: Element 3 means what data did we use to decide whether to evaluate, not what tests we plan to administer.

Element 6 — Options considered and rejected

The most-commonly-underwritten element. Test for adequacy: could a stranger read this section and understand exactly what alternatives were on the table, and why each was rejected based on this student's individual circumstances?

Strong example pattern:

"The team considered maintaining [Student]'s current placement in a general education setting with additional classroom-based support. This option was rejected because [Student]'s most recent progress monitoring data from [date] shows [specific performance], indicating the level of support needed exceeds what can be provided in that setting without fundamentally altering the general education program."

What gets flagged: Identical bullet rejections across multiple students, "not applicable," boilerplate.

Element 7 — Other factors

Use this for things like:

• Parent declined a formally offered service (with date + mode of conversation)
• Parent unable to attend the meeting; document outreach was attempted (3 attempts / 3 days / 2 modes per DCPS due-diligence — see ../parent-communication-log.md)
• Cultural/family considerations the team weighed
• Connection to a hearing officer decision or settlement, if applicable

Part 4: Scenario-by-Scenario Guide

4A — Declined ESY (family offered, declined)

PWN required? Yes — Shannon's specific template is at ../esy-pwn-decline.md. Use it as primary; this doc is backstop.

Other ESY-related PWN scenarios where notice IS required:

• LEA determines ESY is not warranted for a student → PWN refusing ESY required
• Parent requests ESY and LEA declines → PWN refusing required immediately

Pitfall: Treating ESY determination as administrative checkbox. Courts have found PWN failures when LEAs documented ESY decisions only in IEP checkboxes without standalone notice.

4B — Compensatory Services

PWN required? Yes for any of:

• LEA proposing to provide comp services as part of IEP amendment → PWN documents the proposal
• LEA refusing requested comp services → PWN required

Content focus:

• Action: "Proposal to provide [X hours/weeks] of compensatory [service type] due to [brief description of service gap]"
• Basis: IEP service log, attendance records, provider reports documenting the gap period
• Options: Other comp formats considered (extended year, additional weekly sessions, outside provider)

Pitfall: Treating comp service agreements as informal. Without PWN, ambiguity about what was agreed; family can't invoke procedural safeguards if agreement falls through.

Note: Comp services are distinct from ESY — do not conflate. ESY prevents regression; comp services remedy past failure.

Shannon's template: ../comp-services-pwn-link.md (SharePoint share — recommend localizing).

4C — Proposed Change in Placement (LRE shift)

PWN required? YES — always. Any change in educational placement.

Includes:

• Moves between less-restrictive and more-restrictive settings
• Changes in school building
• Changes in program type (co-taught → self-contained)
• Some transportation changes when they constitute a program change

Pitfall: Assuming verbal communications at IEP meeting satisfy notice. They don't. Written notice must be provided after team decision and before implementation.

Content focus:

• Action: Specify current placement AND proposed placement with precision
• Rationale: Tie to specific IEP goal data, assessment results, disability impact
• Basis: Current FBA data, progress monitoring on academic/behavioral goals, observations
• Options: For LRE shift toward more restriction → name least-restrictive alternatives + why insufficient. For shift toward less restriction → note current placement's constraints.

4D — Proposed Change in Services (Frequency/Duration)

PWN required? YES — both increases AND decreases. Common error: drafting PWN only for service reductions, not increases.

Content focus:

• Current service (type, frequency, duration, provider, location) AND proposed service (all same fields)
• Rationale: Student-specific, citing progress data, re-eval findings, or clinical judgment with specific data
• Basis: Assessment or record driving change. For reductions: progress data showing goal attainment. For increases: assessment showing current level insufficient.
• Options: Whether maintaining current level was considered; if reducing, whether smaller reduction was considered

4E — Eligibility Determination (Initial or Re-eval)

PWN required? YES, for all of:

• Initial eligibility (finding child eligible)
• Initial eligibility (finding child NOT eligible) — refusal to identify
• Re-eval finds child no longer eligible (declassification)
• Re-eval confirms continued eligibility (typically required; some states embed in eval results notice)

Content focus for initial eligibility PWN:

• Action: "Proposal to find [Student] eligible for special education under [disability category]"
• Basis: Each evaluation administered (name, date, scores/findings), observations, parent input, existing records reviewed
• Options: Whether team considered other eligibility categories; for ineligibility, whether additional evaluation was considered

4F — Graduation / Aging Out

PWN required? YES + Summary of Academic Achievement and Functional Performance (SAAFP) per 34 CFR §300.305(e)(3).

Unique requirements:

• Provide PWN well in advance (spring of graduation year) for transition planning + due-process exercise time
• SAAFP must accompany — separate document but provided at the same time

Content focus:

• Action: "Termination of eligibility for special education services effective [date] upon graduation with regular high school diploma / upon reaching maximum age eligibility"
• Rationale: Basis for graduation determination (credits, requirements met) or age
• Basis: Transcript records, age documentation, IEP transition planning records
• Options: For aging-out, no alternatives. For diploma graduation, note alternatives (certificate of completion, continued enrollment) considered.

Pitfall: Issuing graduation PWN late or skipping the SAAFP. Both flagged in compliance reviews.

4G — Refusal to Evaluate (Parent Requests Evaluation)

PWN required? YES — clearest PWN trigger.

Timeline: Some states specify 15 calendar days; under federal "reasonable time," delay itself can be a procedural violation.

Pitfall: Verbal denials at IEP meetings without follow-up written notice. Compliance violation.

Content focus:

• Action: "Refusal to conduct [specific evaluation type] as requested by [parent name] on [date of request]"
• Rationale: Why LEA does not believe student meets evaluation criteria — cite existing data
• Basis: Existing evaluations, progress monitoring, teacher reports, prior eval results
• Options: Whether limited evaluation, records review, or other data collection was considered

Note on DC: Per OSSE Initial Eval Bulletin (Oct 2024), LEAs cannot delay or deny a referral to gather data, conduct screenings, implement pre-referral interventions, or because of limited English proficiency. If you're refusing to evaluate, the bar for justification is high.

4H — Proceeding Without Parent at IEP Meeting

PWN required? YES, for any decision the team makes at that meeting.

The two-track rule:

1. Document due diligence on meeting attendance per §300.322 (phone logs, written invitations, visit records, correspondence) in the IEP itself
2. Separately issue PWN for any proposal/refusal made at that meeting

What goes in PWN's "other factors" element: Fact that parent was unable to attend + reference to documented outreach.

Critical: Do NOT include parent-identifying specifics (home addresses, personal phone numbers) in PWN if it will be filed publicly. Outreach log belongs in IEP contact log; PWN should reference that outreach was documented.

Part 5: Quick-Reference Scenario Matrix

Part 6: State Templates Worth Studying

Part 7: Connection to DCPS-Specific Documents

• Shannon's template for declined ESY: ../esy-pwn-decline.md
• Shannon's link to comp services template: ../comp-services-pwn-link.md
• DCPS legal-timelines context: ../iep-legal-timelines.md
• DC translation form (NOT for progress reports): ../document-translation.md
• Memory feedback rules:
  • feedback_pwn_format.md — PWNs must be concise summary format, one short paragraph per section, NOT multi-paragraph narrative
  • feedback_pwn_service_rationale.md — Never justify service changes as "reflecting current delivery" (implies prior IEP was under-specified/overserviced)

Part 8: The OCR-Era Compliance Lens

Given OCR's March 2026 finding (see dcps-context-and-risks-2026.md), the PWN is now under heightened scrutiny as documentation of the LEA's decision-making process. Specifically, OCR flagged that DCPS allowed services to be "removed from IEPs when staff ran out of time."

Implication: Any service reduction PWN will be scrutinized for whether the rationale is genuinely about student need, or whether it's about staffing. Be honest about your basis-for-decision data. If a service is being reduced because of progress data → say so AND cite the data. If it's being reduced for any other reason, that's not a defensible PWN.

Sources

Federal/Binding:

• 34 CFR §300.503 — IDEA.ed.gov
• 34 CFR §300.503 — eCFR
• OSEP Letter to Anonymous, Aug 2 2018

DC-Specific:

• OSSE Special Education Process Handbook (Sept 2023)
• DCPS Language Access for Families
• Children's Law Center Language Access Guide

Third-Party Best Practice:

• Wrightslaw — PWN as Advocacy Tool
• Center for Parent Information & Resources
• Boardman Clark — PWN Reminders
• AALRR — PWN Fundamentals