The SB 848 Resource Center

California Senate Bill 848 — formally the School Employee Misconduct: Child Abuse Prevention Act — is a state law that extends statewide child-safety obligations to private and religious K-12 schools for the first time. It also expands the mandated-reporter pool to include volunteers, board members, and contractors who have direct contact with students.

The law operates through five California code sections that work together:

Most existing California education law focused on public schools. SB 848's headline shift is that it pulls private schools, religious schools, and church-operated schools into the same statutory framework — and includes everyone with recurring student contact, not just credentialed teachers.

SB 848 reaches further than most prior California school-safety statutes. Coverage extends to:

Standalone organizations not affiliated with a school (e.g., independent club sports leagues, standalone church youth programs without a school) generally fall outside SB 848's direct scope but may still be subject to SafeSport, federal CIPA, or local jurisdiction rules.

How enforcement is likely to surface

SB 848 does not establish a single enforcement agency or audit schedule. In practice, exposure typically surfaces through:

• Incident triggers.When something happens, the first question from attorneys, insurers, and parents is "what was the school's written policy, and can you prove it was being followed?"
• Insurance review. Liability carriers are already asking California schools about SB 848 readiness in renewal paperwork.
• Certificate discipline. Individual educators face certification consequences if found to have violated the communication policy or failed to report.
• State agency inquiry.Routine investigations may request the school's written policy, training records, and safety plan as part of their review.

The operational obligations under SB 848 reduce to six distinct deliverables:

1. Adopt a written communication policy(EC §32100) limiting staff-student communication outside parent-inclusive channels. The policy must be enforceable and provable — having it on paper is not enough; the school must be able to demonstrate compliance.
2. Expand the mandated-reporter program to include volunteers, board members, and contractors per Penal Code §11165.7. This is already in effect (January 1, 2026).
3. Deliver annual training (EC §44691) to the entire expanded mandated-reporter pool. Topics typically include grooming recognition, mandatory-reporting timelines, and the communication policy itself.
4. Adopt a comprehensive safety plan (EC §32281.5) with documented supervision and protection procedures.
5. Document reporting procedures(EC §44030.5) so that — when an incident occurs — the school can produce timestamped evidence of who knew what, when they reported it, and how it was escalated.
6. Coordinate with insurers on best practices (SB 848 §6). Liability carriers are increasingly tying renewal terms to documented SB 848 readiness.

EC §32100 doesn't prescribe a specific platform or vendor. It requires a written policy that limits staff-student electronic communication occurring outside parent-inclusive channels. To operationalize that policy, schools generally need to address four pieces:

What "parent-inclusive channel" means in practice

The statute leaves the specifics to schools. Common interpretations:

• School-issued email accounts with automatic archival to the district
• Learning-management-system messaging with parent-account access
• Group channels where every minor's parent or guardian is included on the thread
• Purpose-built monitored-messaging platforms with parent visibility by default and full audit logs

Each approach has trade-offs in usability, cost, and adoption. The common requirement is that the school can demonstrate the channel provides parental visibility — or that parents can request the record — and that staff are not having unmonitored 1:1 contact with students.

Schools that meet the spirit of SB 848 — not just the letter — tend to share the following operational habits. None are required by the statute itself, but each strengthens the school's ability to demonstrate compliance when scrutiny arrives.

School athletics sit at the intersection of SB 848 and SafeSport. Most K-12 sports programs are school-affiliated— meaning coaches are school staff or contractors, athletic directors report to school administration, and parent communications flow through school channels. That places them squarely under SB 848.

Where SB 848 is stricter than SafeSport MAAPP

• Scope of the reporter pool.MAAPP's training requirements cover Adult Participants in a National Governing Body chain. SB 848 covers all volunteers, board members, and contractors with student contact — not just those tied to an NGB.
• Annual training is a hard requirement. MAAPP requires annual training but enforcement varies by NGB. SB 848 makes annual training a state-statutory requirement for the expanded reporter pool.
• The policy must be written and adoptable. MAAPP's expectations sit in NGB policy. SB 848 requires the school itself to adopt, publish, and enforce a written policy.

Where SafeSport is stricter than SB 848

• Two-deep communication is explicit in MAAPP.SB 848's §32100 requires parent-inclusive channels but leaves the "two adults on every thread" structure to the school's implementation. MAAPP is more prescriptive.
• Specific platform prohibitions. MAAPP explicitly calls out disappearing-message platforms (Snapchat) as non-compliant for Adult Participant - Minor Athlete communication. SB 848 leaves that to school policy.

Practical guidance for athletic departments

School athletics programs benefit from documenting alignment with both frameworks simultaneously. An AD who can demonstrate SafeSport MAAPP compliance and a §32100 written policy is well-positioned for both insurer review and parent confidence.

SB 848 expressly extends to church-operated schools — meaning K-12 schools operated by a church, religious denomination, or faith-based organization. That's a meaningful shift: many of these schools previously sat outside California's public-school statutory framework on operations.

What it doesn't change: doctrine and curriculum. SB 848 doesn't affect a school's religious standards, hiring criteria related to faith, or what is taught. It imposes statewide child-safety obligations on operations — mandated reporting, training, communication boundaries, hiring vetting.

Specific implications for church-operated schools

• Same §32100 policy obligation. Religious schools must adopt a written policy on staff-student electronic communication.
• Same expanded mandated-reporter pool.Volunteers — including parent volunteers, youth-group leaders running programs through the school, and contracted faith-formation instructors — are mandated reporters under §11165.7.
• Annual training applies. The same EC §44691 requirements that cover public-school staff cover religious-school staff and volunteers.

And for standalone churches and youth ministries?

Churches operating youth ministries that aren't formally part of a school are not directly regulated by SB 848. But:

• Many denominations are voluntarily aligning their youth-protection policies with SB 848's framework for consistency and to simplify training for staff who serve in both school and ministry contexts.
• Parents who experience SB 848-aligned operations at their school will start expecting equivalent standards from the church youth ministry their child attends.
• Insurers covering churches are increasingly asking about communication-policy practices that mirror SB 848 requirements, regardless of statutory obligation.

The §32100 policy's emphasis on parent-inclusive channels reshapes the role of the parent or guardian in school operations. What parents can expect:

What parents should ask their school

1. Has the school adopted a §32100 communication policy?
2. Which platforms are approved for staff-student communication?
3. How can I see communication between staff and my child?
4. What training has the staff received this year?
5. Who do I contact if I notice off-channel contact?

The samples below illustrate the structure of policy language most schools are adopting. They are not a substitute for legal review. Work with your school attorney to adapt them to your state, school structure, religious considerations, and existing policy framework.

Sample §32100 policy elements

A compliant written policy typically includes:

• A statement of intent (e.g., "The school is committed to ensuring that staff-student electronic communication occurs through channels that include parental visibility...")
• Definitions of "staff," "student," "electronic communication," and "approved channel"
• The list of approved channels for staff-student communication
• Prohibited platforms (personal SMS, personal email, social-media DMs, disappearing-message apps)
• Process for obtaining written parent consent for non-default channels
• Off-channel-contact reporting requirements for staff
• Consequences for violations, including certificate-discipline referrals where applicable
• Annual review and adoption schedule

Sample coach/club-advisor communication addendum

• Two-adult rule for all 1:1 coach-athlete communication
• Parent inclusion on all team-wide group messages
• No disappearing-message platforms (Snapchat, etc.)
• Required reporting of any off-channel contact within 48 hours
• Annual SafeSport-aligned training requirement

Sample parent communication transparency notice

For inclusion in parent handbooks at the start of each school year:

"[School Name] adopts and enforces a written staff-student communication policy aligned with California Education Code §32100. Communication between staff and students occurs through approved parent-inclusive channels listed in the appendix. Parents may request a record of any communication involving their child at any time. Staff who receive off-channel contact from a student are required to report it within [X] hours of receipt. Any parent who observes off-channel contact is asked to notify [administrator role] at [email]."

Use this checklist as a structured walkthrough of your school's readiness. Each item maps back to a specific code section.

Have a question we haven't answered? Email hello@safeteam.io and we'll add it to the Resource Center.