SMS / iMessage (Plain Text Messaging): SB 848 Governance Analysis

What SMS / iMessage Is (and Isn’t)

SMS and iMessage are device-level text messaging systems built into mobile phones. While they differ technically—SMS being carrier-based and iMessage using Apple’s end-to-end encrypted messaging—both function as direct, user-owned communication channels outside institutional control.

Despite this, SMS and iMessage are still commonly used for:

• Coach–athlete communication
  
• Quick logistics (“practice moved,” “bus is late”)
  
• Informal coordination outside official platforms
  

This analysis evaluates SMS and iMessage (plain text messaging) against the governance capabilities a district would need to enforce the limits on staff–student electronic communication defined under Education Code § 32100(b)(1)(B) as amended by SB 848.

Summary: Where SMS / iMessage Stands

SMS and iMessage lack the institutional governance capabilities needed to enforce defined limits on staff–student electronic communication.

While they are convenient and familiar, both provide no institutional ownership, no administrative visibility, no retention guarantees, and no oversight capability. Any oversight relies entirely on voluntary compliance and after-the-fact reconstruction.

Environment & Governance Context

Institution-Governed Communication Tenant

SMS and iMessage do not provide an institution-governed tenant. Messages are exchanged directly between individual devices and phone numbers owned by users, carriers, or device manufacturers.

Official vs Unofficial Spaces

There is no concept of an “official” environment. School-related texts are visually and functionally indistinguishable from personal conversations.

Parallel/Unmanaged Groups

Anyone can create group texts with any combination of participants. Schools have no awareness of, or control over, these conversations.

Matrix alignment

• Institution-governed communication tenant: No
  
• Official vs unofficial environments visually distinguishable: No
  
• Parallel unmanaged team or group creation prevented: No
  
  

Communication Controls

Staff–Student 1:1 Messaging

SMS and iMessage are inherently one-to-one (or small-group) communication tools and cannot be disabled, restricted, or governed by role at the school or district level.

Group Messaging and De Facto Private Messaging

Group texts are explicitly designed to function as private conversations among a limited set of participants. There are no constraints preventing these threads from acting as de facto private messaging channels.

Matrix alignment

• Staff–student 1:1 messaging can be disabled or restricted by role: No
  
• Group messaging constrained to prevent de facto private messaging: No
  
  

Records & Auditability

Centralized Message Logging

SMS and iMessage messages reside on individual devices and, transiently, with carriers or platform providers. There is no centralized, institution-enforced logging.

Administrative Search & Retrieval

Schools and districts have no ability to search, retrieve, or review SMS or iMessage conversations across users, teams, or time without collecting devices or screenshots.

Message Retention

Messages can be deleted by users at any time. Retention varies by device settings, backups, and carrier or platform policies and is not under institutional control.

Audit Trail

Neither SMS nor iMessage provides an institution-owned or defensible audit trail. Any reconstruction months or years later depends on voluntary disclosure, screenshots, or incomplete third-party records.

Notably, iMessage’s end-to-end encryption further limits institutional access and does not improve governance, retention, or auditability.

Matrix alignment

• Centralized message logging enforced at organization level: No
  
• Administrative log search and retrieval across users, teams, and time: No
  
• Message retention independent of user deletion or account changes: No
  
• Audit trail defensible months or years later: No
  

Administrative Visibility

Admin Visibility into Messages

There is no administrative visibility into SMS or iMessage conversations. Institutions cannot view staff–student communication without reconstructing it through external investigation or individual cooperation.

Matrix alignment

• Admin visibility into all staff–student messages without reconstruction: No
  

Governance

Routine Proactive Message Review

SMS and iMessage offer no mechanism for proactive or routine review of messages.

Review Logging & Outcomes

There is no concept of message review, reviewer identity, or review outcomes within either system.

Active Supervision Across Time, Teams, and Seasons

MS and iMessage do not support sustained, institution-level oversight across time or organizational boundaries.

Pattern-Based Risk Review

There are no tools for detecting grooming patterns, boundary erosion, or longitudinal risk across conversations.

District-Level Governance & Escalation

Districts have no roles, controls, or escalation workflows within SMS or iMessage.

Matrix alignment

• Routine proactive message review support: No
  
• Review actions logged with reviewer, date, and outcome: No
  
• Explicit review outcomes supported: No
  
• Active supervision (governance spanning time, teams, and seasons): No
  
• Longitudinal pattern-based risk review supported: No
  
• District-level governance and escalation supported: No
  
  

What This Means for SB 848

SMS and iMessage operate outside institutional control. Even well-intentioned policies (“don’t text students privately”) rely entirely on individual compliance and are unenforceable in practice.

From an SB 848 perspective:

• Oversight is reactive and investigative, not routine
  
• Schools cannot demonstrate meaningful institutional control
  

Final Takeaway

SMS and iMessage are familiar and convenient, but they lack institutional governance capabilities. Because SB 848 requires districts to adopt policies that define limits on staff–student digital contact, a tool that cannot support enforceability, visibility, and retention makes it difficult — if not impossible — to demonstrate compliance in practice.

Any reliance on SMS or iMessage places the burden of compliance entirely on individual behavior and ad-hoc reconstruction, rather than on systems that support enforceable limits and meaningful oversight.

‍

‍