Quiet Hours for School Notifications
Every district in a snow state sends a message before 06:00 several times a winter. Almost none has ever checked what that rests on, and the check takes twenty minutes. This page is that check, plus a default policy you can adopt as written.
| Message | Governing window | Basis relied on | Record to retain | Confidence |
|---|---|---|---|---|
| Lockdown or evacuation alert, any hour | None — sent regardless | Emergency purpose | Authoriser, time, incident reference | High |
| Weather closure, 05:00–06:00 | None — emergency reasoning | Safety, delay defeats purpose | Authoriser, conditions relied on, decision time | High |
| Two-hour delay, 05:30 | None — emergency reasoning | Same | Same | High, weaker than closure |
| Mid-day early release | Within normal hours anyway | School-related | Standard send record | High |
| Scheduled maintenance closure known days ahead | Federal 8am–9pm applies | Not time-critical | Standard send record | High |
| Attendance notification | Federal 8am–9pm applies | School-related, not urgent | Standard send record | High |
| Event reminder or survey | Federal 8am–9pm applies | School-related | Standard send record | High |
| Any send to a family in another timezone | The recipient's local clock | Called-party time governs | Timezone of record per contact | Verify with counsel |
| Any state with a narrower window | The narrower of the two | State telemarketing statute | State check, dated | Verify — varies and changes |
General information, not legal advice. The federal baseline commonly cited for calls and texts is 8:00am to 9:00pm in the called party's local time. Several states narrow the evening boundary or add day-of-week restrictions through their own telemarketing statutes; whether those apply to a public school district's operational messaging is exactly the question to put to your counsel, in writing, once, and then never again.
The 05:00 closure message, analysed properly
Two conditions make the early send defensible, and both are things the district controls.
Condition one: the message is genuinely about health and safety, and delay would defeat its purpose. A closure driven by ice, snow, flooding, extreme cold, a building failure or an air-quality event meets this comfortably. Families need the information before they put a child on a road or at a bus stop. A closure for a scheduled boiler replacement, a professional development day added late, or an administrative decision made the previous week does not, and should be sent the evening before during normal hours.
Condition two: the district can show it was a decision, not a habit. Retain, for each early send: who authorised it, the time of the decision, the conditions relied on, and the time of the send. This is four fields and it converts an argument into a record.
The failure mode is a district that flags everything as an emergency because the emergency flag is the only way to get past its own configured quiet hours. That is a workflow defect that becomes a compliance defect. If your platform makes emergency override the path of least resistance, expect your staff to take it.
Kastr's quiet hours default to 21:00–07:00 and only an explicitly emergency-flagged send bypasses them. The flag is gated on a capability rather than granted to every user, and each use writes to the per-district append-only, SHA-256 hash-chained audit log. The friction is intentional: it means the 05:00 send has a name attached to it.
The multi-timezone district
Not an edge case. Districts near a timezone boundary routinely enrol students whose home address is in the neighbouring zone, and every district has families who moved away mid-year and kept the number, plus military families and split-custody arrangements spanning states.
The principle generally applied is that the called party's local time governs, not the sender's. That produces three practical problems:
- Area code is not location. Mobile numbers keep their area code across a move. A 907 number may be in your district. A local area code may be three timezones away. Inferring timezone from area code is wrong often enough to matter.
- Address of record is better but still imperfect for a family with two households in two states.
- The safe practice for non-urgent sends is to send within a window that is inside 8am to 9pm across every timezone you plausibly touch. For a district on a boundary that means 09:00 to 20:00 local, which costs you nothing operationally.
For genuinely urgent safety messages the analysis does not change: emergency reasoning applies regardless of clock, and the record you keep is the same record.
A default quiet-hours policy you can adopt
Adapt the names and adopt the rest. This is written to be pasted into a board policy or an administrative regulation.
- Standard window. The district sends no automated voice or SMS message before 08:00 or after 20:00 in the recipient's local time, except as provided below. The platform is configured to enforce this by default.
- Early operational window. Messages concerning a closure, delayed start, early release or transport disruption caused by weather, a building failure or an external hazard may be sent from 05:00. They are authorised by the superintendent or a named designee.
- Emergency window. Messages concerning an active threat to the health or safety of students or staff may be sent at any hour, on any channel, to any contact point of record, including contact points that have revoked consent for routine messaging. Authorised by the superintendent, a named designee, or the incident commander.
- Authorisation record. Every send under paragraphs 2 or 3 records the authorising individual, the time of decision, the time of send, and a one-line statement of the conditions relied on. The record is retained for [PERIOD] and is available to the board on request.
- Annual review. The communications lead reports annually to the cabinet on the number of sends made under paragraphs 2 and 3. A rising count under paragraph 3 is treated as a governance question, not an operational one.
- Vendor configuration. The district's platform is configured so that bypassing the standard window requires an explicit action by a user holding the relevant permission, and so that each bypass is logged.
Paragraph 5 is the one that matters over a five-year horizon. Emergency overrides do not get abused in a single decision; they drift, one convenient send at a time, until a district is sending event reminders at 06:40.
Questions people actually ask
What time can a school legally text or call parents?
The commonly cited federal baseline for calls and texts is 8:00am to 9:00pm in the called party's local time, and some states narrow the evening boundary through their own statutes. Whether a state telemarketing statute reaches a public district's operational messaging is a question for your counsel. Emergency safety messages are analysed separately.
Can a school send a snow day message at 5:00am?
Districts do, and the reasoning is the emergency purpose: a health-and-safety message whose value would be destroyed by waiting. That reasoning is strong for hazardous conditions and weak for a closure decided a week earlier for administrative reasons. Keep a four-field record — authoriser, decision time, conditions, send time — and the argument is straightforward.
Do quiet hours apply to emergency school notifications?
An active safety incident is the clearest case for sending regardless of hour, and platforms including Kastr let an explicitly emergency-flagged send bypass quiet hours and per-family channel preferences. The discipline is keeping the flag rare, permissioned and logged, so it still means something in year five.
Which clock applies when a family lives in a different timezone from the district office?
The recipient's local time is the one generally applied. Do not infer timezone from area code — mobile numbers keep their area code across a move. For non-urgent sends, use a window that is inside 8am to 9pm across every timezone you plausibly touch, which for a boundary district means roughly 09:00 to 20:00 local.
Should a district configure quiet hours in its platform or rely on staff judgement?
Configure them. A default that has to be deliberately overridden produces a record and a decision; a convention that lives in someone's head produces neither. Kastr defaults to 21:00–07:00 with the override gated on a capability and written to an append-only audit log, which is the shape to look for whatever you buy.
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.