Resources / Special Education / Prior written notice

How do school districts document prior written notice for special education decisions?

The short answer

Prior written notice is the notice a district must give a parent before it proposes or refuses to change a student's identification, evaluation, placement, or provision of FAPE. The notice itself carries no signature requirement. That's a separate question from consent: a parent's actual sign-off is still required before an initial evaluation and before the first delivery of special education services, and treating notice and consent as interchangeable is where districts get into trouble. Because prior written notice generates nothing signed, "the parent sent it back" was never available as proof it went out. If a placement decision is ever challenged, the district is the one that has to produce the record: what was sent, when, to whom, by what method, in what language. Nothing comes back to hand that record over. It has to already exist.

On this page

Why the systems you already have do not cover this How districts handle it now Where it goes wrong

What doing it well actually requires Common questions How Flow Forms handles it

Why the systems you already have do not cover this

The IEP platform is where the notice usually gets written. It holds the student's plan, it produces the document, and that part works. What it does not do is get the document into a parent's hands and show you that it arrived. Delivery happens outside the platform: someone prints the notice and mails it, sends it home in a backpack, or attaches it to an email and hopes the address is current. The platform knows a notice exists. It does not know whether the parent ever saw it.

The student information system has the same shape from the other side. It knows the student, but the notice is not its document and the delivery is not its job. So the most compliance-sensitive routine document in special education travels the least tracked path in the district: out of a printer, into an envelope, and into silence.

How districts handle it now

In most offices, prior written notice runs on the copy machine and the mail. The notice gets drafted in the platform, printed, copied for the file, and mailed or sent home with the student. A paper copy goes into the student's folder, or a scan goes into a shared drive if someone has time. If the office tracks delivery at all, it is a spreadsheet or a checklist someone updates by hand, and it records that a notice was sent, not that it was received.

What varies is what districts ask for in return, and the variation is the district's own choice, because federal law requires nothing back. Some districts add a signature line to the notice asking the parent to confirm they received it, an acknowledgment of receipt rather than an approval of the contents. Others send the notice plain and keep only their own record of the mailing. Procedural guidance points every version toward the same conclusion: since no signed copy is coming back on its own, the district should maintain its own system for documenting that notice was provided. However a district chooses to run it, the burden of proof lands in the same place, on the district's own records.

This is not carelessness. It is what the tools at hand actually support. The office is doing everything the process allows it to do, and the process still ends at the mailbox.

Where it goes wrong

The volume is what breaks it. Prior written notice is not an occasional document. Every proposed evaluation, every placement change, every service adjustment, every refusal generates one, for every affected student, all year. Each one takes the same walk to the printer and the same trip through the mail, and each one leaves the same question behind: did it get there?

Most of the time nobody asks that question, so the gap stays invisible. Then a parent says they never received a notice, or a student transfers and the new district asks for the file, or the office needs to confirm what was sent before an annual review, and the answer has to be assembled from a folder, a spreadsheet, an email search, and someone's memory of a mailing that happened months ago. The record exists in pieces. Nobody planned for the day it would have to be produced whole.

What doing it well actually requires

Delivery through a channel the parent actually sees. Mail assumes a current address and an opened envelope. A portal assumes a login parents remember. Delivery that works goes to the phone the parent already carries and the email they already use, as a direct link, with nothing to install and no account to recall. The point is not that digital is newer. It is that the notice's legal purpose is informing the parent, and a channel the parent does not check cannot do that job.

A send record created at the moment of sending. Because nothing is required to come back, the proof of provision is the district's to create, and doing this well means the record of what went out, to which parent, through which channel, and when, exists because the sending created it, not because someone remembered to log it. When delivery and recordkeeping are the same act, the record has no gaps to explain.

One place the whole stream lands. A year of notices for a caseload should be answerable as a search: everything sent for this student, in order, with dates. When each notice files itself alongside the rest of the student's paperwork, producing the history takes minutes, and it looks the same whether the request comes from a parent, another district, or a state reviewer.

The stream treated as routing, not as events. An office that handles each notice as its own small project will always be behind the volume. Handled as routing, the notice moves the way every other routed document moves: it goes out through the defined channel, its status is visible while it is out, and it files itself when the process completes. What stays with the office is the part that needs a person: the decision itself, and the explanation the notice has to carry. What leaves is the tracking.

The proof shows up differently depending on whether anything has to come back. For forms that need a parent's response returned, delivery method is measurable as a return rate: Sweetwater County School District #2 sent meeting notices requiring a response by paper mail and got back around 10%; delivered as a direct link to parents' phones and email, returns rose to 81%. A prior written notice has nothing to sign, so the same delivery machinery does a quieter job. The system's own record confirms each notice was sent, through which channels, and when, for every notice, as a byproduct of sending it. That record is the proof of provision a district otherwise keeps by hand, and it exists whether or not anything ever comes back.

Common questions

Questions we hear from every special education office

Do parents have to sign a prior written notice?

No. Prior written notice informs; it does not ask permission. Consent is a separate requirement with its own forms, and the two are often confused because they travel together. Some districts do add a receipt line asking the parent to sign and return the notice, but that is local practice for the district's own records, not a federal requirement, and signing it acknowledges receipt rather than agreement. Either way the delivery problem remains: the district needs to show the notice was provided, which means the record of sending matters even when no signature comes back.

Can prior written notice be delivered electronically?

IDEA allows notice by electronic means where the parent has agreed to receive communications that way, and states add their own rules on top. Check your state's requirements and your district's documented practice. The operational answer is the same either way: whatever channel you use, the delivery has to be one your parents actually receive, and the record of it has to exist somewhere you can find.

What do we have to produce if a parent disputes what they were told?

The notices themselves, and the account of when and how each was provided. A dispute is rarely about whether a document was written; it is about whether the parent received it before the decision took effect. An office that can produce the notice, the send date, and the delivery channel from one record answers that in minutes. An office reconstructing it from a mail log and a file folder is proving a negative with paper.

How Flow Forms handles it

School districts already run parent notice delivery through Flow Forms. Where a notice gets sent matters for a reason separate from compliance: a notice can be fully compliant and still land somewhere nobody checks. Flow Forms sends every notice by text and email together, not one channel and a hope for the other, as a direct link to the phone and email parents already use, with the send record and the filed document created automatically as part of the process. If notice delivery and tracking is a problem your office is carrying by hand, this is the kind of process we build.

This is proven in the field. At Sweetwater County School District #2, moving meeting notices from paper mail to a direct link sent to parents' phones and email lifted returns from about 10% to 81%.

See how it would work for your district →