Skip to main content

SDLA Compliance Resource

Provide the Full Procedural Safeguards Notice at Every Required Event

A trigger-based distribution control for supplying a current, understandable rights notice and practical assistance without mistaking delivery for comprehension or consent.

  • Special Education
  • Procedural Safeguards
  • Parent Notice
Date(s)At least once per school year and again at specified triggers: initial referral/parent request for evaluation, first state complaint, first due-process complaint, disciplinary change of placement, and parent request; California may require additional delivery with assessment plans
Applies toParents and educational rights holders of children with disabilities or children referred for IDEA evaluation

In Plain Language: Give the parent the complete current safeguards notice at the required events, in an understandable language and accessible format. Explain where to ask questions and how to use the rights; do not hide the notice in a portal or substitute a summary for the full notice.

Why this matters

The notice covers evaluation, records, consent, IEE, complaints, due process, stay put, discipline, private placement, attorneys' fees, and other protections. Timing matters because families need it when decisions arise.

Joint ownership

Owner: special education compliance/case staff. Partners: assessment intake, discipline, complaint/due-process staff, records, language/access services, and parent support contacts.

From a notice trigger to the full safeguards notice delivered: the SDLA ITO workflow

Delivery of the full notice is tied to specific events, and delivery alone does not prove understanding. This SDLA ITO (Input, Transformation, Output) graphic shows how the current notice versions, the pupil's trigger events, and the parent's access preferences become the version control record, the trigger log, and delivery and access evidence.

SDLA ITO: eleven steps from the current notice versions, the pupil's trigger events, and the parent's access preferences, through trigger checks, delivery in an accessible language and format, and recording access, to the version control record, the trigger log, and delivery and access evidence.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers trigger checks, delivery in an accessible language and format, and recording access; Output covers the version control record, the trigger log, and delivery and access evidence. Provide the full notice at least annually and at each trigger; do not substitute a summary or hide it in a portal.

Open the full-size workflow graphic

Operational workflow

  1. Maintain a trigger matrix and current controlled safeguards versions/translations.
  2. At each event, verify whether the annual notice has already been provided and whether the event independently requires another copy.
  3. Deliver through the parent's accessible preferred method and language; include help contacts and offer explanation.
  4. Record version, trigger, date, method, recipient, access confirmation, and follow-up.

Federal trigger map

Once each school year
Initial referral or parent request for evaluation
First state complaint in the school year
First due-process complaint in the school year
Disciplinary change of placement
Whenever the parent requests a copy

Evidence to retain

  • Current version/translation control
  • Pupil-level trigger log
  • Delivery and access evidence
  • Interpreter/explanation support
  • Correction of failed or stale delivery

Official guidance and help

Source review completed August 30, 2026. Verify current federal and California law, court or OAH instructions, local SELPA procedures, individual circumstances, and the exact service and records state before acting.