SDLA Compliance Resource
Review, Update, and Adopt Each Comprehensive School Safety Plan
The annual site planning process for evaluating risks, consulting required partners, updating mandated procedures, inviting public input, adopting the plan, forwarding it for LEA approval, and implementing it.
2027 law and source-version check
The March 1 annual CSSP review/update requirement remains. AB 2496 section 2 removes the separate annual July school-safety-plan status report formerly required in the SARC under EC 32286; this change takes effect January 1, 2027. Continue school safety planning, consultation, approval and implementation duties.
AB 2496, Chapter 615, Statutes of 2026. Authority and source-version register.
In Plain Language: By March 1, each school reviews, updates, and adopts its CSSP through the required committee and public process, includes all current statutory elements—including instructional continuity and immigration-enforcement notification procedures—and forwards it to the district/COE for approval.
Emergency instructional-continuity clocks
The ICP must provide pupil/family engagement as soon as practicable and within five calendar days, including two-way communication and support for pupil needs. Instructional access must begin as soon as practicable and within ten instructional days; remote instruction must align with the applicable independent-study provisions.
For J-13A events on or after July 1, 2026, retain the required ICP/implementation certification and explain any prevented implementation and services actually offered.
- Activate Instructional Continuity After an Emergency
- CDE instructional-continuity authority
- CDE J-13A certification guidance
Coverage addition reviewed October 21, 2026.
Why this matters
A copied plan with a new date is not an annual safety process. Missing consultation, public presentation, required content, adoption, LEA approval, or implementation can create audit findings and weaken real emergency readiness.
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 the planning committee to an adopted Comprehensive School Safety Plan: the SDLA ITO workflow
Each school's plan is reviewed, updated with required partners and public input, adopted, then tested during the year. This SDLA ITO (Input, Transformation, Output) graphic shows how the planning committee, incident and risk evaluations, and the required-content checklist become the updated plan, the public meeting and adoption record, and the implementation evidence.
Operational workflow
- Convene/verify the required planning committee and consult law enforcement, fire, emergency, labor, staff, families, pupils, and other required partners.
- Assess current crime, climate, emergency, facility, accessibility, and continuity risks and evaluate prior implementation/incidents.
- Update every required procedure, including disability adaptations, instructional continuity, immigration-enforcement notification, and current policies.
- Present plan goals for public input, then complete school adoption by March 1 and forward for district/COE approval.
- Train, implement, test, maintain the public/redacted file, and track corrective actions throughout the year.
Implementation pathway
Evidence to retain
- Committee and consultation evidence
- Risk/incident evaluation
- Required-content checklist and updated plan
- Public meeting and adoption record
- District/COE approval
- Training/drills/implementation and public-file evidence
Official guidance and help
- CDE CSSP GuidanceMarch 1, October 15, content, and process
- CDE Safe Schools PlanningCompliance tool and resources
- CDE Instructional Continuity PlanRequired CSSP component
- Education Code 32280–32289.5Statutory authority
Targeted authority/source review: October 21, 2026. Targeted AB 2496 SARC/CSSP transition review; this is not a revalidation of every separate safety or SARC provision. See the source-version register. Other source history is retained in the publication record.

