Board hears lengthy ParentSquare presentation as staff recommend consolidating district communications
Get AI-powered insights, summaries, and transcripts
SubscribeSummary
District staff recommended adopting ParentSquare to replace multiple apps; presenters and a stakeholder rubric favored ParentSquare, but trustees pressed for more detail on privacy, account linking for students, training and contract terms before a March vote.
On Feb. 19, 2026 the Southern York County School District board received a detailed presentation recommending ParentSquare as a single platform to replace multiple district communication apps.
District staff said stakeholders — including coaches, counselors, teachers, parents and union representatives — evaluated several vendors and used an anonymous rubric. Staff reported a 14–3 stakeholder preference for ParentSquare and emphasized features they said matter to the district: mass notifications, two‑way messaging, real‑time translation into many languages, conference scheduling, read‑receipt analytics and a virtual phone option that gives teachers a district phone number rather than a personal line.
“ParentSquare really stood out in a couple areas, such as administrative overhead,” Dr. Hughes said during the presentation, adding that the vendor holds SOC 2 Type II and ISO 27001 certifications and an iKeepSafe student‑privacy endorsement. Staff said ParentSquare’s onboarding fee was lower (about $750) than comparable systems but estimated the first‑year platform cost at roughly $3,375 per student (the district estimate will vary with enrollment). Presenters said the vendor retains message records by default for seven years but that retention, auditing and private‑message settings would be set during onboarding.
Trustees pressed staff on specific operational and policy questions: whether phone calls and text transcripts sent through the platform would become official district records (staff: yes, they would be auditable), whether private messaging between staff and students could be disabled (staff: that is part of onboarding), how accounts are created and synced (staff: nightly sync from the district’s Sapphire SIS), whether parents must create accounts (staff: parents are uploaded and will get notifications without logging in), and how the district would handle a vendor price increase (staff described annual renewal terms and exit notice dates).
Board members also asked for more evidence about vendor reliability at high load, reports of account‑linking errors in other districts, and contract‑term safeguards. Multiple trustees said they wanted a concise menu of the sign‑up and account‑linking choices the district would use before approving a contract. Several directors recommended a phased rollout and a possible trial sandbox involving parents who have district email addresses.
Administration said the board would see a contract and implementation plan at the March meeting; staff also proposed delaying optional features such as the virtual phone until year two of implementation. No final contract vote was taken Feb. 19.
What happens next: staff will provide a written options menu for how parent/student account linking, message retention and virtual‑phone features would be set during onboarding; the board expects a formal contract and vote in March.
