SB 848 / Ed Code 32100 — What’s Required vs. What’s Assumed

SB 848 — titled the School Employee Misconduct: Child Abuse Prevention Act — strengthens student safety by reinforcing professional boundaries between school personnel and pupils. As part of that framework, Education Code §32100 now requires governing boards to establish appropriate limits on staff–student electronic communication.

Most schools agree with that objective.

The challenge is not defining the goal, but translating statutory limits into systems and practices that hold up under real-world conditions.

This article explains what SB 848 actually requires, what it leaves unresolved, and why that gap is where most compliance failures occur.

Terminology
In this article, schools refers collectively to public school districts, charter schools, and private schools subject to SB 848 and Education Code §32100.

What the Law Clearly Requires

SB 848 amends Education Code § 32100 in two key ways that apply directly to digital communication:

• § 32100(b)(1)(B) requires governing boards to:
  “Establish appropriate limits on contact, during or outside of the schoolday, between pupils and school employees, volunteers, and school contractors via social media internet platforms, text messaging, and other forms of communication that do not otherwise include the pupil’s parent or guardian.”

1. Limits on digital contact
The statute recognizes that staff sometimes need to communicate with students, but it requires boards to define limits on that contact via electronic channels.

2. Policy without prescription
The law does not prescribe specific technologies or platforms. It requires districts to articulate limits and governance expectations in policy.

This means schools must answer questions such as:

• What counts as appropriate limits?
• How will the district ensure policy intentions translate into practice?
  ‍

What the Law Does Not Define — and Why That Matters

The most important compliance challenges stem less from what SB 848 says and more from what it leaves open‑ended. Those gaps are where leadership must make clear, defensible choices.

1. What “appropriate limits” mean in practice
The law requires limits on contact via social media and text, especially where parents are not included. But it does not specify:

• When is a one‑to‑one message acceptable?
• What counts as necessary logistics versus inappropriate familiarity?
• How should exceptions (illness, transportation issues, emergencies) be handled?

Schools must define these boundaries in policy and practice—especially in extracurricular and individualized contexts where one‑to‑one contact is often necessary for the program to function.

2. How digital communication environments are governed
The statute does not define:

• What tools or platforms are required;
• How oversight must occur;
• Whether monitoring must be real-time, periodic, or complaint-driven.
  

It does not establish supervision obligations in statutory language. These are choices a district must make to implement limits effectively.

3. Monitoring vs. reconstruction
The law requires limits — it does not mandate a specific oversight model. Districts must determine whether policy expectations are met:

• Continuous monitoring?
• Sample review?
• Post-event reconstruction?

Schools must determine whether their model is proactive—or based on reconstructing events after something has gone wrong.

4. Auditability and timely access
Similarly, auditability and timeliness are not quantified:

• How quickly should relevant records be accessible in a complaint or investigation—minutes, hours, days?
• Who needs direct access (e.g., site administrators, HR, legal, Title IX)?
• Can users alter or delete messages in a way the institution cannot see?

In all of these areas, SB 848 establishes the outcome—appropriate limits in digital channels that can be goverened. Schools must fill in the operational details.

The Assumptions That Undermine Compliance

Common assumptions in school practice often fail when measured against the statute’s outcomes:

Assumption #1: group chats reduce risk. 

Group messaging can still enable private side conversations outside of institutional visibility.

Assumption #2: copying parents equal oversight. 

Including parents increases transparency in individual exchanges, but it does not centrally govern records.

Assumption #3: records can be retrieved if needed. 

Systems that allow unrestricted deletion or require manual reconstruction make retrieval unreliable under pressure.

Assumption #4: policy alone governs behavior. 

Most staff act in good faith. That does not make policy self-executing. Under normal constraints—time pressure, habit, convenience—behavior tends to follow the path of least resistance:

• the app everyone already uses
• the channel that produces the fastest response
• the tool that works best on a personal phone

Unless systems are designed to support and reinforce expectations, policy will inevitably be outpaced by practice. Under SB 848, that disconnect is no longer just an operational issue; it is a compliance and governance issue.

SB 848 Was Not Written as a Technology Law — But It Assumes Technology

SB 848 does not mandate a specific platform, vendor, or technical implementation. That has led some schools to treat it as primarily a policy exercise: update handbook language, restrict one-on-one communication, and reference an “approved” tool.

That approach misses a critical reality.

That approach misses the point: the statute requires Boards to define limits, and districts to operationalize them.

• unsafe behavior is hard to sustain, and
• concerning patterns are easy to detect and address.

Policies describe expectations.

Systems determine whether those expectations hold up in real use.

Why Platform Choice Is a Governance Decision

Because SB 848 is often framed as a compliance or safety issue, platform selection is sometimes treated as a technical decision or delegated primarily to IT teams. While IT plays a critical role, this framing is incomplete.

IT teams are well-positioned to evaluate security, integrations, and uptime. SB 848 compliance, however, hinges on governance: who has visibility into communication, who controls access, who owns records, and how quickly administrators can intervene when concerns arise.

A platform can be technically secure and still fail compliance expectations if administrative visibility is limited, audit access is delayed, or enforcement controls vary by role or department. These are not merely feature deficiencies — they are governance failures.

Choosing communication tools is, in effect, choosing where staff–student communication will occur, and whether that environment can be supervised at the institutional level.

A More Practical Compliance Standard

Rather than asking whether a policy or platform technically satisfies the statute, schools should ask a more practical question:

Does this system allow the district to enforce the limits it has defined under Ed Code §32100(b)(1)(B)?

A defensible approach to SB 848 compliance typically includes communication that is:

• Centralized rather than scattered – Staff–student messages live in school‑governed systems, not across personal devices and consumer apps.
• Visible at the institutional level – Authorized administrators can see who is communicating with which students, and how, without relying on individual cooperation.
• Auditable without delay – Relevant records can be reviewed quickly when concerns arise.
• Supportive of necessary one‑to‑one contact – Direct messages can occur where they are needed, but only inside environments the school can govern.
• Resilient to normal human behavior – Oversight continues to function as staff, tools, and habits change over time.

Anything less does not eliminate risk—it merely obscures where the risk lives.

The Question Schools Should Be Prepared to Answer

Every school should be able to answer the following without hesitation:

If an issue arose tomorrow, could we clearly demonstrate that staff–student electronic communication—group and one-to-one—where the district can enforce the limits it has defined?

If the answer depends on good intentions, manual reconstruction, or policy language alone, there is work left to do.

Meaningful compliance with SB 848 begins when oversight is built into the environments where communication actually happens—not simply assumed through behavior or policy.

‍