Where Digital Communication Environments Break Down Under SB 848

A Practical Diagnostic for SB 848 Changes to Ed Code § 32100

Scope: 

This diagnostic tool helps school leadership evaluate whether their staff–student electronic communication practices can be reasonably defended under the recent SB 848 amendment of California Education Code § 32100, including the requirements to:

• “Establish appropriate limits on contact…” via social media, internet platforms, text messaging, and other forms of electronic communication, and

Under SB 848, schools must define limits on staff–student electronic communication and adopt policies addressing both classroom and nonclassroom environments. When digital tools are used in athletics and activities, schools must consider how those environments support visibility, governance, and enforceability of those defined limits.

This article does not address mandated reporting, training requirements, physical safety, SafeSport, or Title IX obligations. It is not a policy guide or product comparison.

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

What Makes Communication Practices Defensible

Schools often assume they’re compliant because they have a written policy prohibiting inappropriate contact. But § 32100 compliance is not measured by policy intent alone. It is evaluated by whether the digital environments where staff and students communicate can be:

• reasonably governed
• credibly explained when something goes wrong.

In practice, a defensible environment for staff–student electronic communication typically provides:

1. Institutional Visibility – Communications are accessible to authorized administrators, not just individual staff
2. Governed One‑to‑One Messaging – The school can define, control, and restrict private messaging
3. Reliable Retention and Export – Records can be produced without relying on individual cooperation, screenshots, or personal accounts.
4. No Unsupervised Side Channels – Private conversations cannot bypass established oversight
5. Timely Auditability – Records can be reviewed quickly in response to complaints or inquiries

*These criteria are an operational translation of SB 848 / Ed Code § 32100’s requirements to establish appropriate limits on contact, not the statute’s verbatim language.

In practice, schools must operationalize those policy limits through systems and procedures that function consistently in real use. These criteria reflect the common structural conditions schools may consider when evaluating whether communication can be governed consistently at the institutional level.

If a communication practice fails any one of these criteria, the school may struggle to demonstrate that "appropriate limits" were meaningfully established—even if staff are acting in good faith and no misconduct has occurred.

The scenarios below show where common staff–student communication practices break down.

‍Common Compliance Failure Scenarios

‍

Scenario 1: Direct Texting via Personal Phones

Fails: Institutional Visibility, Reliable Retention and Export, No Unsupervised Side Channels

What happens
Staff text students using personal phone numbers (SMS, iMessage) for logistics, reminders, or quick coordination around practices, events, or assignments.

Why this fails

• Messages live only on personal devices; administrators have no direct access.
• The school cannot retain, export, or centrally store these texts.
• During an inquiry, the only way to see messages is to ask staff to produce them.
• One‑to‑one contact occurs entirely outside any school‑governed system.

Bottom line
In this model, one‑to‑one staff–student communication does not occur within a digital environment the institution can reliably govern or review without relying on individual cooperation. It depends on individual devices and cooperation, not institutional control.

Scenario 2: Consumer Messaging Apps with Private Channels

Fails: Institutional Visibility, Enforceable Limits on One‑to‑One Contact, Reliable Retention and Export, No Unsupervised Side Channels

What happens
Teams, clubs, or classes use apps like GroupMe, Instagram, Discord, WhatsApp, Snapchat, or similar platforms. Group chats feel transparent, but the platform also enables private DMs between participants.

Why this fails

• Staff–student DMs are invisible to administrators and other group members.
• The school cannot technically prevent or govern private messaging inside the app.
• Message history and deletion are controlled by individual users, not the institution.
• Even “official” accounts are user‑controlled; the school has no direct export or audit path.

Bottom line
The platform guarantees unsupervised one‑to‑one channels between staff and students. Even with good policies, this digital nonclassroom environment cannot be described as being in institutional control.

Scenario 3: Manual or Delayed Access to Communication Records

Fails: Institutional Visibility, Reliable Retention and Export, Timely Auditability

What happens
The school uses tools where records exist but are slow or difficult to access—for example, requiring user‑level exports, IT tickets, vendor requests, or ad hoc help from staff.

Why this fails

• When a concern arises, it takes days or weeks to assemble relevant messages.
• Exports may be incomplete due to user deletions or platform limits.
• Access often depends on staff participation (e.g., initiating exports, sharing credentials).
• The school cannot routinely spot‑check or review communication patterns.

Bottom line
An environment that can only be pieced together through slow, manual processes may be retrievable, but it does not support consistent institutional visibility during routine operations. SB 848 focuses attention on whether defined limits can function in day-to-day operations — not only during investigations.

Scenario 4: Inconsistent or Optional Tool Adoption Across Sites and Programs

Fails: Enforceable Limits on One‑to‑One Contact, Timely Auditability

What happens
The district recommends or approves tools for staff–student communication, but adoption varies. Some programs use the approved system; others use personal phones, consumer apps, or a mix of channels. Enforcement is loose or left to local discretion.

Why this fails

• There is no single, consistent standard for how staff communicate with students.
• Administrators cannot see or audit communication across the full organization.
• Written policies about “approved tools” are not reflected in day‑to‑day behavior.
• Different groups normalize different one‑to‑one channels, many of them unsupervised.

Bottom line
Without consistent use of school‑governed tools, the district cannot credibly claim that staff–student communication—including one‑to‑one—takes place in environments that enforce appropriate limits.

Bringing It Together: The Real SB 848 Question

The patterns in these scenarios don’t come from bad intent. They come from normal behavior operating inside systems that were never designed to give schools reliable, institution‑level supervision over staff–student communication—especially one‑to‑one.

Across all of them, three themes repeat:

• Necessary 1:1 communication has no consistently governed home. Direct messages live on personal phones or in consumer apps the school doesn’t govern.
• Oversight depends on people, not environment. Visibility relies on staff memory, screenshots, or cooperation, rather than on systems that keep communication observable by design.
• Supervision happens, if at all, after a concern. Records can sometimes be reconstructed, but the environment itself may not support consistent institutional visibility.

SB 848 does not ask schools to eliminate staff–student communication. It asks a different question:

Can you show that the digital environments where staff and students communicate — especially one-to-one — are environments your institution can easily govern and review as part of normal operations?

If the honest answer is:

• “It depends on staff sharing messages from their phones,”
• “We could pull records if we had enough time,”
• “Some programs use our system; others do their own thing,”

then the gap is not in policy language—it is in system design.

A practical next step is to:

• Audit what is actually in use across teams, clubs, and activities.
• Map each tool to the five criteria—with special attention to how it handles one‑to‑one messaging.
• Standardize on environments where necessary direct messages can occur inside a school‑governed system.

The goal is not to remove all risk or all discretion. It is to ensure that when staff and students communicate—especially one‑to‑one—they are doing so inside digital nonclassroom environments your school can see, explain, and stand behind under SB 848.