Are School Text Messages Public Records? What Determines the Answer
Every state has a public records law, every school district is a public body under it, and almost no district has thought carefully about what that means for text messages. The answer does not turn on which app was used or whose phone it was. It turns on content, and the practical problem is not legal exposure but retrievability — a record you cannot find is a record you cannot produce.
| Factor | Does it decide the answer? | Why |
|---|---|---|
| Content relates to district business | Largely, yes | This is the test in most states, in some form |
| Which device it was sent from | No | Personal devices do not create a private category for public business |
| Which app or platform was used | No | Same reasoning; the medium is not the test |
| Whether it names a student | It changes the exemption analysis | Education-record protections engage, usually meaning redaction rather than withholding |
| Whether the district can retrieve it | Not legally — but it decides everything practically | An unretrievable record is a compliance failure in waiting |
| Retention schedule | Yes, for what still exists | Lawfully destroyed records need not be produced; destruction during a hold is a different matter |
| Whether it was sent to one family or thousands | No | Volume affects the redaction burden, not the status |
| Whether a parent replied | The reply has its own status | Inbound content is also a record and is often forgotten entirely |
State records laws differ substantially in their exemptions, their fee structures and their response deadlines. What is broadly consistent is the first row and the second: content decides, and the device does not. Confirm your own state's test and exemptions with your records officer and counsel.
The three failure patterns
The record that exists nowhere. A principal texts forty families from a personal phone about a bus delay. Those are district records. They exist on forty handsets and one personal device, and the district cannot search any of them. When a request arrives, the district either produces nothing and asserts nothing exists, or asks a staff member to hand over their personal phone. Both outcomes are bad, and neither is fixed by a policy prohibiting the practice, because the practice happened for a reason.
The over-disclosure. A request arrives for “all communications about the reorganisation”. Someone exports the send log and hands it over, complete with guardian phone numbers, email addresses and home languages. That is a privacy incident produced by a compliance process, and it is more common than the opposite failure.
The forgotten inbound. Two-way messaging means families reply. Those replies are records too, they frequently contain health and family information, and in many districts nobody has ever considered where they live or how long they are kept. Ask your vendor what happens to an inbound message and for how long.
Building for retrievability
The records-friendly system is not the one with the strictest policy. It is the one where the easy path produces a searchable record by default. Five properties to look for:
- One place for outbound family communication, easy enough that staff use it instead of their phones. This single property does more for records compliance than any amount of training.
- A searchable send history covering recipient, channel, language, timestamp and delivery outcome, retained on a schedule you set rather than one the vendor chose.
- Inbound message capture in the same place, with the same retention treatment.
- Export that produces something a records officer can work with. This is where we have to be honest: Kastr's export is a contract right under clause 7.1, exercised by asking us, and the self-serve tooling does not exist yet. For a district with a heavy records load that is a real weakness, and vendors who have shipped that tool have an advantage over us today.
- A tamper-evident record. Where a produced record may be challenged, being able to show that the log is append-only matters. Kastr's is: per-district, hash-chained with SHA-256 so each entry covers the previous one, with UPDATE and DELETE revoked at the database role in addition to insert-and-select-only policies.
A retention position you can actually defend
Retention for communications is usually governed by your state's records retention schedule, administered by a state archives or library agency, and those schedules rarely address text messaging directly. That leaves districts to reason by analogy, which is legitimate if you write the reasoning down.
A workable approach:
- Classify by content, not by channel. A truancy notice is a truancy notice whether it went by post or by SMS, and it takes the retention of the underlying record type.
- Set a default for everything unclassified, and make it short enough to be honest and long enough to be useful. Most districts land between one and three years for routine operational messaging.
- Suspend on hold. Whatever the schedule says, a litigation hold or an open request stops destruction. Make sure the person who administers the platform knows how to do that, and that they are told when a hold exists.
- Write down what the platform holds. One page, given to the records officer, listing artefact types and retention periods. Kastr publishes retention defaults per record class, and we will tell you the uncomfortable part: there is no automated purge job behind them today, so treat them as policy and contract rather than as an enforced mechanism.
The exercise worth doing before a request arrives. Pick a real question — “every message the district sent about the September bus route change” — and try to answer it with the systems you have. Time it. Note which systems you had to touch and which you could not search at all. Most districts discover the answer is four systems and one personal phone, and that discovery is dramatically cheaper in a quiet week than during a statutory response deadline.
This page describes what a statute asks of a vendor. It is not legal advice, statutes are amended, and section numbering moves. Confirm the current text with your own counsel or your state education agency before you rely on any of it in a contract or a procurement file.
Questions people actually ask
Are teacher text messages to parents public records?
In most states the test is whether the content relates to public business, not which device or app was used. A message about district business is generally a district record wherever it lives, which is why the practical risk is retrievability rather than status.
Can a district refuse a records request for messages naming students?
Education-record protections and other exemptions generally apply, but the usual result is redaction rather than blanket withholding. That means someone has to review the material, which makes exportability and searchability a procurement question rather than an administrative afterthought.
How long should a district keep text messages to families?
Classify by content and apply the retention of the underlying record type, with a defensible default for anything unclassified. Your state records retention schedule governs; most were written before mass texting and require reasoning by analogy, so write the reasoning down and have counsel review it once.
Do parent replies count as records too?
Yes, and they are the most frequently forgotten category. Inbound messages often contain health and family information, they are held somewhere by default, and in many districts nobody has decided how long. Ask your vendor what happens to an inbound message and for how long it is retained.
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.