ParentSquare — SAFE Communications Score

Platform evaluation for staff-student supervision and institutional governance.
Download ParentSquare PDF

Full framework and scoring methodology: SAFE Communications Score

0 — No controls

1 — Token / incidental capability

2 — Partial / workaround only

3–4 — Functional with gaps

5 — Full institutional control

Maturity tiers: Limited 0–25% · Developing 26–50% · Moderate 51–75% · Advanced 76–100%

Institutional Control

5/5

Staff-Student Messaging

1/5

Cross-Role Access Controls

3/5

Records & Retrievability

4/5

Administrative Visibility

3/5

Review & Incident Workflow

0/5

Longitudinal Monitoring

2/5

District-Level Governance

3/5

This evaluation assesses institutional supervision and governance capability in school settings. Platforms designed for general consumer use may serve other communication needs effectively while lacking the oversight controls this framework measures.

Institutional Control 5/5

Deployed as a true district or school tenant — no individual can create unauthorized communication spaces outside institutional control.

Staff-Student Messaging 1/5

DM exists and logs are immutable, but the on/off switch is tenant-wide — disabling it for coaches also disables it for all classrooms, making program-level control architecturally impossible.

Cross-Role Access Controls 3/5

Parents cannot message students directly. Staff-to-student messaging is configurable but role controls are coarse — granting coach access requires granting it to all staff roles.

Records & Retrievability 4/5

Logs are immutable and searchable at the district and site-admin level. The AD must typically escalate to a principal or higher to access records — visibility is siloed at the top of the hierarchy, contrary to the spirit of the school's duty of supervision.

Administrative Visibility 3/5

District and site admins have real-time, architecture-enforced visibility across all communications. Visibility does not extend to the director or program level without manual configuration — the AD must add themselves to each team individually.

Review & Incident Workflow 0/5

No native flagging, escalation path, or documented outcome workflow. Incident response relies entirely on manual reconstruction outside the platform.

Longitudinal Monitoring 2/5

District and site admins can search all messages involving a staff member or student across conversations. Full context requires multiple windows. The AD cannot conduct this review independently.

District-Level Governance 3/5

District settings cascade to schools and roles are centrally managed. Permission controls are blunt — targeted athletic program governance is difficult without unintended consequences for other roles.