Skip to main content
Man in an e-waste bin labeled old equipment: Hey! I am not that old!

SDLA Compliance Resource

Notify CDE of Schools Not Complying with CSSP Requirements

The annual LEA-level exception report identifying schools that failed to meet Comprehensive School Safety Plan requirements—not a substitute for correcting the failure.

  • School Safety
  • CSSP
  • Public Accountability
Date(s)October 15, 2026
Applies toCalifornia K–12 public schools and responsible school districts/COEs, subject to applicable statutory structure

In Plain Language: Complete an all-school compliance reconciliation and notify CDE in writing by October 15 of every school that has not complied. Preserve the basis for inclusion/noninclusion and continue corrective action through adoption, approval, implementation, and evidence recovery.

Why this matters

Silence is not proof that every school complied. A willful failure to make the required report can lead to a state assessment, while the underlying missing plan remains a safety and audit risk.

Primary ownership

Primary owner: LEA school-safety/compliance lead. Partners: principals, CSSP committees, district/COE approver, governing board, emergency responders, labor/teachers, families/pupils, special education, facilities, legal, instructional continuity, and records staff.

From a school-by-school tracker to a CDE exception notice: the SDLA ITO workflow

The report identifies noncompliant schools, and each one still needs a dated corrective-action plan. This SDLA ITO (Input, Transformation, Output) graphic shows how each school's safety plan, adoption and approval evidence, and the required content become the compliance roster, the exception determination, and the CDE notice and corrective-action closure.

SDLA ITO: eleven steps from each school's safety plan, adoption and approval evidence, and the required content, through tracking, evidence testing, classification, and leadership review, to the compliance roster, the exception determination, and the CDE notice and corrective-action closure.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers tracking, evidence testing, classification, and leadership review; Output covers the compliance roster, the exception determination, and the CDE notice and corrective-action closure. Notify CDE in writing by October 15, 2026.

Open the full-size workflow graphic

Operational workflow

  1. Maintain a school-by-school compliance tracker covering committee/process, required content, public input, March 1 adoption, LEA approval, implementation, and public-file status.
  2. Collect and test evidence; do not rely only on principal attestation.
  3. Classify each school as compliant, incomplete, or noncompliant and obtain leadership/legal review.
  4. Send the required written October 15 notice identifying noncompliant schools through the CDE-authorized route.
  5. Retain delivery proof and execute a dated corrective-action plan for every exception.

Implementation pathway

All-school tracker
Evidence test
Classify/review
Notify CDE
Correct

Evidence to retain

  • All-school compliance roster
  • Plan/adoption/approval evidence
  • Required-content checklist
  • Exception determination and leadership approval
  • CDE notice and delivery proof
  • Corrective-action closure

Official guidance and help

Source review completed August 30, 2026. Verify current CDE, governing, Dashboard, school-plan, SARC, safety, instructional-materials, local-calendar, and legal instructions before acting.