Google Classroom guardian email summaries and Kastr: what each one is for
Somebody in a board meeting will ask why the district needs a messaging platform when Google Classroom already emails parents. It is a fair question with a precise answer, and the answer is not that Classroom is bad. It is that guardian summaries are an opt-in coursework digest and a notification system is a different thing entirely.
| Classroom guardian summaries | Kastr | |
|---|---|---|
| Channels | Email only | SMS, voice, email |
| What triggers it | A scheduled digest of coursework | A person composing and sending |
| How a guardian is included | Invited by email, must accept | Derived from the roster; nothing to accept |
| Coverage | Only guardians who accepted | Everyone with a contact point in the roster |
| Language | Recipient's Google interface language | Per-guardian preference, DeepL, previewed before send |
| Emergencies | Not designed for it | Emergency flag bypasses quiet hours and channel preferences |
| Quiet hours | n/a | 21:00–07:00 by default, emergency-only bypass |
| Delivery evidence | None visible to the school | Per-recipient, per-channel outcome |
| Cost visibility | Free | Live per-channel estimate before you send |
| Audit trail | None | Hash-chained append-only log of every send |
Classroom wins the cost row outright and should. The rows that decide the question are coverage and emergencies: a system that reaches only the guardians who accepted an emailed invitation cannot be the system you use to tell a district that school is closed.
How a guardian actually ends up receiving a summary
The mechanics are worth walking through, because the gap lives in them rather than in any feature comparison.
A teacher or administrator invites a guardian by email address. Google sends an invitation. The guardian must open it and accept. Only then do summaries begin, and only for coursework in classes their student is enrolled in.
Every step in that chain is a place where coverage is lost. The email address in the SIS is wrong or stale. The invitation lands in spam. The guardian opens it on a phone, means to deal with it later, and does not. The guardian has no Google account and does not want one. The student changes classes and the association needs rebuilding.
The consequence that matters: an unaccepted invitation is a silent zero. The school sees a guardian who was invited. The guardian receives nothing. Nobody is told. Districts that measure this generally find acceptance well short of universal, and skewed in exactly the wrong direction — the families hardest to reach by email are the families least likely to complete an email-based opt-in.
Contrast the roster-derived model: a guardian is reachable because your SIS says they are the guardian and holds a phone number. There is nothing to accept and nothing to lose in an inbox. Each contact point carries a validationState and a consentState, so when someone genuinely is not reachable, that is a visible fact with a reason rather than an absence.
Classroom is not a roster source
Occasionally a district asks whether Kastr can take its contact list from Classroom. The answer is no, and the reason is topology rather than capability.
Classroom sits downstream. Your SIS is the source; Clever, ClassLink or Google's own tooling pushes rosters into Classroom; Classroom consumes them. Taking a comms roster from Classroom means going downstream to fetch data that was upstream a moment ago, having passed through a system that deliberately does not carry guardian phone numbers, restriction flags, language preference or educational rights.
The correct arrow is SIS → broker (optional) → Kastr, in parallel with SIS → broker → Classroom. Both consumers, one source. The Clever page covers the guardian-data caveat that applies to the broker leg, and the CSV page covers the direct route.
What each system should be used for
The boundary that most districts settle on, and that avoids paying twice for one job:
- Classroom: assignments, due dates, feedback on work, course announcements to enrolled students, and the weekly coursework digest for guardians who accepted the invitation. It is genuinely good at this and nothing here should be duplicated elsewhere.
- Kastr: closures, delays, emergencies, attendance outreach, building and district announcements, anything that must arrive on a phone, and anything that must reach a guardian who has never signed into anything.
The test that resolves ambiguous cases in one sentence: if the message needs to arrive whether or not anyone opens an app, it is not a coursework digest.
Being explicit about our side of that boundary: Kastr does not read Classroom grades, assignments or gradebook events, and does not send anything triggered by them. There is no missing-assignment alert and no grade-drop notification. Nor is there digest batching — no daily or weekly rollup exists in the send path. Every Kastr message is composed by a person and sent deliberately, which is a deliberate design position and also an accurate statement of what is built.
The cost question, since it is the real objection
Classroom guardian summaries are included with Google Workspace for Education, which for most districts means free. That is a genuine advantage and pretending otherwise would be silly.
What the free option cannot do is reach a family without an accepted invitation, send an SMS, place a voice call, respect quiet hours, bypass them for an emergency, translate per guardian with the sender able to preview it, or produce evidence of what was delivered to whom. Those are the capabilities a district is buying, and the honest framing is that they are additional to Classroom rather than a replacement for it.
On the number: $3.50 per student per year under 5,000 students, $3.25 to 14,999, $3.00 above — every feature included, no per-message fees, fixed for 36 months. A composer that shows the per-channel cost before you send tends to reduce the bill rather than inflate it, because people stop adding a voice call to a routine newsletter once they can see what it costs.
Questions people actually ask
Do Google Classroom guardian summaries cover school closures or emergencies?
No. They are a scheduled digest of coursework, delivered by email, only to guardians who accepted an invitation. There is no SMS, no voice, no priority handling and no delivery evidence. Using them for a closure means telling only the subset of families who completed an email opt-in.
Can Kastr use Google Classroom's guardian list as its contact list?
No, and it would be the wrong direction anyway. Classroom sits downstream of your SIS and carries no guardian phone numbers, restriction flags, language preferences or educational-rights information. Both systems should consume the same upstream roster rather than one feeding the other.
Does Kastr send a daily or weekly summary email like Classroom does?
No. There is no digest batching in the send path at all — every Kastr message is composed by a person and sent deliberately. If a weekly newsletter is what you want, someone writes and schedules one, with the audience resolved at send time rather than at schedule time.
What happens to guardians who never accepted their Classroom invitation?
They receive nothing, and nobody is told. That is the structural weakness: an unaccepted invitation looks like coverage from the school's side and is silence on the family's side. A roster-derived model has the opposite property — unreachability is a visible fact with a reason attached to the contact point.
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.