TCPA Compliance for School Districts
Districts have run automated calling for two decades on the assumption that schools are exempt. The assumption is roughly right and dangerously imprecise. There are two separate exemptions, they cover different things, they both have edges, and the messages districts most want to send — fundraising, partner promotions, ballot measures, vendor offers — are on the wrong side of every one of them.
| Message type | Classification | Reasoning |
|---|---|---|
| Lockdown or evacuation alert | Emergency purpose | Health and safety, delay defeats the purpose |
| Weather closure or delay | Emergency purpose | Safety-driven, time-critical |
| Building failure closure (power, water, heat) | Emergency purpose | Same reasoning where students are affected that day |
| Scheduled maintenance closure, known a week ahead | School-related, not emergency | No time criticality; send in normal hours |
| Early release for weather | Emergency purpose | Custody of a child changes within hours |
| Same-day absence notification | School-related | Transactional, about the recipient's own child |
| Attendance pattern outreach | School-related | Operational, individual, non-commercial |
| Scheduled attendance nudge campaign | School-related — document it | Campaign-shaped; carrier rules also apply |
| Health office pickup request | School-related | Individual and operational |
| Communicable disease exposure notice | School-related | Public health, non-commercial |
| Immunisation compliance deadline | School-related | Statutory obligation of the district |
| Bus route change or delay | School-related | Operational, affects the child's day |
| Testing week reminder | School-related | Instructional operations |
| Registration or enrolment window | School-related | Enrolment administration |
| Parent-teacher conference scheduling | School-related | Individual and instructional |
| Grade or missing-assignment alert | School-related | About the recipient's own child |
| Meal balance reminder | School-related — watch state law | Non-commercial, but state lunch-shaming statutes constrain wording |
| School event reminder | School-related | Non-commercial school activity |
| Athletics schedule change | School-related | Operational |
| District survey | Consent advisable | Not operational; low value on voice or SMS anyway |
| PTA or booster fundraising appeal | Do not send | Solicitation, outside the exemptions |
| Bond or levy campaign message | Do not send | Advocacy; separate state electioneering rules also apply |
| Third-party vendor or photographer offer | Do not send | Commercial, and a family-data-use problem regardless |
| Message to a number never given to the school | Do not send | No consent record; also a 10DLC filtering risk |
This is general information for planning purposes, not legal advice, and it is a classification framework rather than a determination. Your counsel decides. The value of the table is that it forces the district to sort its own message inventory before a complaint does it for you.
The two exemptions, and where each one stops
The emergency-purpose reasoning covers messages made necessary in a situation affecting the health and safety of the recipients, where a delay would defeat the purpose. It is the strongest ground a district has and it is genuinely narrow. A lockdown alert at 06:00 is squarely inside it. A 06:00 call about picture day is not, and sending one erodes the argument for the next real one.
The school-related informational reasoning covers the ordinary operational traffic between a school and the families it serves: absences, closures, transport, health office, enrolment, instruction. Three edges matter:
- It does not cover solicitation. A fundraising appeal is a fundraising appeal whether the PTA or the district sends it.
- It does not cover third parties. The moment a message promotes an outside organisation — a photographer, a tutoring service, a sponsor — the character of the message changes even if the district composed it.
- It does not survive revocation. A family that has asked you to stop has asked you to stop, and "we are a school" is not an answer to that.
The practical district test, applied before every non-routine send: would this message exist if the school had no relationship with an outside organisation, and would a reasonable parent describe it as school business about their own child? Two yeses and you are on solid ground. One no and it needs consent or should not go.
Consent, and the record you should be able to produce
Districts collect phone numbers at registration and then treat every number as equally consented. That is the single most common defect. The record you want, per contact point, is:
- The number itself, normalised to E.164 so that the same number is not stored four ways.
- Source — registration form, online enrolment, SIS import, front-office correction, parent portal.
- Validation state — has anything ever confirmed this number reaches this household.
- Consent state, separately — did this household agree to receive messages on it, and for what.
- Timestamp and the exact wording shown at the point consent was captured.
- Rank — which number is primary, so a district is not choosing at random between three mobiles.
- Revocation, if any, with its date, channel and scope.
Kastr stores validation state and consent state as two separate fields on every contact point, along with source and rank, precisely because collapsing them into one boolean is how an audit trail is lost. That is a data-model claim, not a compliance claim: the fields exist and are populated; whether your consent posture is adequate is a question for your counsel.
The two-household problem. Consent is a property of a person and a channel, not of a student. A district that stores "texting consent" against a student record will get it wrong for every two-household family: one parent consents, one does not, and both are attached to the same child. Kastr models one person with many effective-dated roles, so consent attaches to the adult and their contact point rather than to the child, which is the only structure that answers the question correctly. Whatever platform you use, ask this question in the demo and watch what happens.
Revocation, and the emergency contact who said stop
When a parent asks you to stop, four things must happen and most districts do one of them.
- The request is honoured on the channel it was made on, immediately and automatically. A STOP keyword must work without a human in the loop.
- The request is recorded against the person, not against a list. Otherwise the next campaign built from a different list re-adds them.
- The scope is captured accurately. "Stop texting me about lunch balances" is not "stop contacting me". Districts routinely over-apply, then wonder why a family missed a closure.
- The district decides in advance whether revocation propagates across channels. A parent who texts STOP has not opted out of voice calls, and a system that silently applies the opt-out to every channel has made a policy decision on the district's behalf.
The hard case: the only reachable adult for a child has opted out, and there is a lockdown. The emergency-purpose reasoning is generally understood to survive an opt-out for genuine safety messages, and that is how mass-notification platforms are built — Kastr's emergency flag bypasses per-family channel preferences and quiet hours, and it is capability-gated rather than available to every user. Two things follow. First, the flag must be rare enough to mean something. Second, a district should have a written policy stating who may set it and on what grounds, and should be able to show the audit entry afterwards. Kastr's audit log is per-district, SHA-256 hash-chained and append-only at both the database role and the row-security policy, so that entry is tamper-evident rather than merely stored.
Eleven questions to ask a communications vendor
Most of these cannot be answered by a salesperson, which is the point. Ask them in writing.
- Are validation state and consent state stored as separate fields, or is there one flag?
- Is consent attached to a person and a contact point, or to a student record?
- When a parent texts STOP, what exactly is suppressed — that number, that person, that channel, or everything?
- Does an SMS opt-out propagate to voice and email, and is that behaviour configurable by the district?
- Can an emergency send override an opt-out, who is permitted to do that, and is the override logged?
- What is the audit record for a send — who authorised it, what audience it resolved to, what each recipient's consent state was at that moment?
- Can that audit record be edited or deleted by anyone, including your own staff?
- Where does the district's data live at the end of the contract, and by what mechanism does it come back?
- Is the district's data ever used to market to families, by you or by anyone you sell to?
- What happens to the district's messaging if you are acquired?
- What are your quiet-hours defaults, and what bypasses them?
Our own answers, so you can hold us to them: separate fields; consent on the person and contact point; STOP suppresses the contact point and is recorded against the person; cross-channel propagation is a district decision rather than a silent default; emergency override is capability-gated and audit-logged; the audit log is append-only at two independent layers and cannot be edited by us either; export is a contract right at clause 7.1 — and to be exact about it, that is a contractual obligation on us, not a self-serve button in the product, because the export tooling is not built yet; clause 9.4 prohibits marketing or selling to district families and any family-facing subscription revenue, permanently; clause 11.2 gives you a 90-day exit with export and a prorated refund on a change of control; quiet hours default to 21:00–07:00 and only an emergency-flagged send bypasses them.
Questions people actually ask
Does the TCPA apply to school districts?
Yes. Public entities are not categorically outside it, and the practical position for schools rests on exemptions rather than on non-application. Two matter: the emergency-purpose reasoning for safety messages, and the school-related informational reasoning for ordinary operational traffic to families who provided their numbers. Both have edges, and solicitation is outside both. General information, not legal advice.
Are school emergency calls exempt from the TCPA?
Emergency-purpose messages — those made necessary by a situation affecting health and safety where delay defeats the purpose — are the strongest ground a district has, and that is what a 05:15 closure call or a lockdown alert rests on. The exemption is narrow by design. Using it for event reminders weakens the argument and, more immediately, teaches families to ignore the alerts that matter.
Do schools need parent consent to send text messages?
Two regimes apply at once and districts commonly satisfy only one. The TCPA analysis rests on the exemptions plus the fact that the family provided the number. Separately, carrier 10DLC rules expect a documented opt-in for the registered campaign, and unregistered or undocumented traffic is filtered silently. Capture consent explicitly at registration, store it as its own field, and get counsel's position in writing.
What happens if a parent revokes consent but the school needs to reach them in an emergency?
Genuine emergency safety messages are generally understood to survive an opt-out, which is why mass-notification platforms provide an emergency override. The obligations that come with it are a written policy on who may use it, a narrow definition of what qualifies, and an audit record afterwards. A district that flags routine sends as emergencies has both spent the argument and trained its families to ignore the flag.
Is a district liable if its communications vendor sends a non-exempt message?
Assume the district's name is on it and plan accordingly, because the family whose phone rang did not contract with your vendor. Practically this means the district owns the message inventory: know what is being sent, on whose authority, and under which classification. Ask the eleven vendor questions on this page before signing, not after a complaint.
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.