For mid-size districts: big enough to need governance, small enough that nobody has time for it
Between roughly 2,500 and 10,000 students a district acquires all the governance problems of a large one and none of the staffing. This is the band where the question of who may send district-wide stops being obvious and starts being a real decision.
| Who | Can send to | Enforced by | Logged |
|---|---|---|---|
| District communications | Everyone, any school | Org-level role on the district record | Hash-chained audit event per send |
| Principal or building admin | Their own school's families | Row-level security — a building account cannot resolve rows outside its school, regardless of the URL | Yes, with resolved audience size |
| Front office | Individual families in their building | Same row-level boundary; student selection expands to guardians | Yes |
| Teacher | Families of their own students | Enrolment-derived audience | Yes |
| Emergency send | Bypasses quiet hours and channel preferences | Capability gate, not a checkbox | Yes, flagged as emergency |
| PTA or volunteer group lead | Their group's members only | Group governance with no district-console access at all | Group identity shown, true author recorded |
| Anyone, to a grade or bus route | Not supported | Grade, school-preset and route targeting do not resolve today | — |
| Anyone, with an approval step | Not supported | No approval workflow exists; enforce with policy | — |
The governance question that actually bites
In a district of 800 students, everyone who can send is in one room. At 8,000 there are forty people with send rights across nine buildings, and the person who owns the district's voice has met perhaps a third of them.
The failure this produces is not misuse. It is volume. Families in a mid-size district commonly receive messages from the district, the school, two teachers, the athletics department and the PTA in the same week, none of which coordinate, and the result is that they stop reading all of it. By the time you need them to read one — a closure, a lockdown, an attendance escalation — you have trained them not to.
The technical part of the fix is scoping, so that district-wide sending is genuinely restricted. The important part is a message calendar that nobody has time to maintain, which is why the practical version is a rule rather than a schedule: one district-wide message a week unless it is operational, and building messages do not duplicate a district message.
Cost across the band transition
The published rate is $3.50 per student below 5,000 and $3.25 from 5,000 to 14,999, which means crossing 5,000 students reduces your per-student rate. The arithmetic:
- 2,500 students: $8,750 a year, $26,250 over the locked 36 months.
- 4,900 students: $17,150 a year, $51,450 locked.
- 5,100 students: $16,575 a year — less than at 4,900, because the band changed. $49,725 locked.
- 7,500 students: $24,375 a year, $73,125 locked.
- 10,000 students: $32,500 a year, $97,500 locked.
Yes, a district of 5,100 pays less in total than a district of 4,900. That is what happens when bands are published as flat rates rather than negotiated, and we would rather have the odd artefact than a price you have to ask for. Enrolment is set at contract signature and does not re-price mid-term, so growth inside the term does not cost you more.
A rollout plan for a district with no project manager
Eight weeks, part-time, with named owners. The dates matter less than the ordering.
- Week 1 — technology director. Start 10DLC brand and campaign registration. This is two to six weeks of waiting and it is the critical path.
- Week 1–2 — technology director. Decide the system of record for contact data, and get one roster POST working against
/api/v1/roster/sync. Count guardian coverage per school. Expect one building to be materially worse than the others; it always is. - Week 3 — communications director. Decide the scoping model using the table above, and write the emergency-flag policy. Two sentences, approved by the superintendent.
- Week 4 — both. Import history if you are migrating. Our ParentSquare importer validates the export and produces a signed receipt; the row load is done with us, not self-serve.
- Week 5 — principals. One hour of training per building, delivered by the communications director, not by us. The content is the cost preview, send-test-to-me, and the quiet-hours rule.
- Week 6 — pilot. Two buildings send real messages. Nothing district-wide.
- Week 7 — go/no-go. The decision criteria are guardian coverage above your threshold, 10DLC approved, and both pilot buildings reporting fewer than three "I never got it" calls.
- Week 8 — district-wide. First district send, in a quiet week, not the week before a holiday.
Leaving mid-contract, honestly
The arithmetic that decides it. If your current agreement has eighteen months to run at $22,000 a year, walking away costs $33,000 in unrecoverable licence plus roughly 80–150 staff hours of migration. Switching to save $4,000 a year does not pay for itself inside the remaining term. Switching because the platform is failing your families does, and it is a different conversation.
The two moments when the arithmetic works are at natural expiry and immediately after a renewal increase, because the increase is what changes the denominator. If a renewal email has just landed, read the negotiation guide before you do anything else — a substantial share of increases are soft, and finding that out is free.
If you are switching regardless, mid-year versus summer covers what actually breaks in each path.
Questions people actually ask
What does this cost at 6,000 students, and what changes when we cross 5,000?
$3.25 per student above 5,000, so 6,000 students is $19,500 a year and $58,500 across the locked 36 months. Crossing 5,000 lowers your per-student rate rather than raising it, so a 5,100-student district pays less in total than a 4,900-student one. Nothing about the product changes at any band — every feature is included at every size.
Can building staff send without district approval, and can we turn that off?
Scope is configurable, and the boundary is enforced with row-level security rather than by hiding buttons — a building-scoped account cannot resolve an audience outside its own school. What does not exist is an approval workflow with routing and hold states, so "the principal may send but the communications director must approve" is enforced by policy and the audit log, not by the software.
How long does a mid-year rollout take?
About eight weeks part-time, and the compressible part is smaller than it looks. 10DLC brand and campaign registration takes two to six weeks and cannot be shortened, so it goes in week one. Roster, scoping decisions, training and a two-building pilot fill the rest. Going district-wide before the pilot is where mid-year rollouts fail.
What do we lose by leaving our current vendor mid-contract?
The remaining licence, which is usually unrecoverable, plus 80 to 150 staff hours. Also, in practice: saved distribution lists, message history unless you export it deliberately, consent records if the outgoing vendor's export omits them, and staff muscle memory for a term. Ask your outgoing vendor for the export in writing before you give notice, not after.
Do we need a dedicated communications platform administrator?
Not full time at this size, but you need a named one. The failure mode in mid-size districts is not that the work is heavy, it is that it belongs to nobody, so guardian coverage decays quietly and nobody notices until a closure day. Half a day a month, owned by one person, is enough.
One price. Every feature. Locked for three years.
$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.