Schoology Learning and Kastr: where parent contact data actually lives
Districts reasonably assume that if 8,000 parents have Schoology accounts, those accounts contain 8,000 reachable phone numbers. They almost never do. This page sets out the four routes by which a Schoology parent account comes into existence, what each one actually populates, and why the roster for your emergency messages should come from your SIS instead.
| Provisioning route | Who creates it | Email present | Mobile phone present | Relationship verified | Coverage of your families |
|---|---|---|---|---|---|
| Parent access code | The parent, self-service | Whatever they typed | No | By code possession only | Whoever bothered |
| SIS-driven provisioning | Automated from the SIS | Yes, from the SIS | Rarely carried | Yes | High |
| Rostering broker (Clever, ClassLink) | The broker | If guardian sharing is enabled | Usually withheld | Yes | Depends on share config |
| Manual admin creation | A staff member, one at a time | Yes | No | Whatever was typed | A handful |
The mobile-phone column is the point of this page. An LMS is built to identify a person so it can show them a gradebook. It is not built to reach a person on a phone during a closure, so it does not systematically collect or carry the field that makes that possible. Every row here is No or Rarely, and no configuration change turns that column green.
Why the LMS is the wrong roster source
Three structural reasons, none of which are criticisms of Schoology as a learning platform.
Self-selection. Parent access codes produce accounts for the families who were motivated enough to redeem one. That population skews exactly the way you would expect, and it is close to the inverse of the population you most need to reach during a closure or an attendance escalation. A roster with a participation bias is not a roster.
No phone number. The account exists to authenticate someone into a gradebook. There is no operational reason for it to hold a verified mobile number, so it generally does not. Without a mobile there is no SMS, and Kastr's SMS-to-voice failover has nothing to fail over to.
No withdrawal signal. When a student leaves the district, the SIS knows on a specific date. LMS accounts frequently linger for a term or longer, and a parent account can outlive the enrolment that justified it by considerably longer than that.
Add the ordinary consequence: two sources of truth for a contact detail, with no rule for which wins. The SIS answers all three of those problems by design, because those are the things a system of record is for. If your district runs PowerSchool SIS alongside Schoology — a very common pairing — both are downstream of the same upstream data, so take the roster from the SIS and let the LMS be the LMS. The PowerSchool SIS route is the one to build. The same reasoning applies to Canvas and Google Classroom, which are covered separately for the same reason.
The ownership boundary: which system sends what
Districts that run both without an explicit split end up sending everything twice, which trains families to read neither. The workable division is by scope and by consequence of being missed.
- Course-level, non-urgent, one teacher to one class — assignment posted, project deadline moved, rubric shared, gradebook updated. Schoology. It has the context, the audience is already there, and the material belongs next to the work.
- Building or district-level, time-sensitive, must arrive — closure, delayed start, lockdown, reunification instruction, bus route change, immunisation deadline, meal-balance notice. Kastr, over SMS and voice, because those need to reach a phone whether or not anyone opens an app.
- The ambiguous middle — a whole-grade field trip reminder, a class event needing a signature. Decide once, publish the rule to staff, and stick to it. The specific rule matters far less than its consistency.
The test that resolves most cases: if a family missing this message has a consequence measured in a grade, it belongs in the LMS. If the consequence is measured in a child standing somewhere unexpected, it belongs in the notification platform.
Explicitly, what Kastr does not do with Schoology. Kastr reads no course data, no assignment data, no gradebook data and no submission data, and it sends nothing triggered by any of them. There is no missing-assignment notification, no grade-drop alert and no low-score trigger, because there is no rules engine that fires: rules can be configured and nothing runs them. There is no Schoology connector, no partnership, no SSO and no LTI integration — magic link is the only authentication Kastr has, for staff and families alike.
What a Schoology parent account is, and what a Kastr guardian record is
They are different objects solving different problems, and the confusion between them is the reason districts over-estimate their reach.
A Schoology parent account is a login. It authenticates an adult so a platform can show them their child's coursework. It is associated with a student, it may or may not be verified, and it holds whatever the provisioning route happened to populate. Its purpose is completed when someone signs in.
A Kastr guardian record is a person with an effective-dated guardian role and a set of contact points. Each contact point carries a channel type, a validation state and a consent state — the last mattering for 10DLC and TCPA purposes — plus a source and a rank. A guardian record does not require the adult to have ever signed in, ever downloaded anything, or ever known Kastr exists, which is the entire design goal. The measure of a login is activation. The measure of a guardian record is whether a message reaches a human at 5:40am on a snow day.
That difference is also why one identity carries many roles. An adult who is a guardian at two schools and a substitute teacher is one person with three effective-dated roles rather than three accounts, so a district-wide send reaches them once.
The count worth running before you sign anything, with any vendor. Take your active student list from the SIS. Count how many have at least one guardian with an SMS-capable mobile number. Then count how many have none at all. In most districts that second number is one to four per cent, and nobody knows it until somebody counts it. Kastr's dry run produces that list for you: the diff engine hashes and classifies every record without writing anything, and the zero-contact list falls out of it. It is the most useful thing a roster exercise produces, and it is worth more than any feature comparison.
Questions people actually ask
Can Kastr pull guardian phone numbers from Schoology parent accounts?
Not reliably, because those numbers are usually not there. Schoology parent accounts exist to authenticate an adult into a gradebook, and none of the four provisioning routes systematically collects or carries a verified mobile number. Take guardian contact detail from your SIS, which holds it because reaching families is what a system of record is for.
We use PowerSchool SIS and Schoology — which should feed Kastr?
The SIS, without hesitation. Both are downstream of the same upstream data, and only the SIS holds verified guardian phone numbers, authoritative school assignment and a real withdrawal date. Schoology stays your LMS; PowerSchool SIS becomes your roster source. Building it the other way gives you a self-selected population with email at best.
Does Kastr replace Schoology course updates?
No, and it should not. Course-level material belongs next to the coursework, where the context lives and where the audience already is. Kastr covers building and district messages that must arrive on a phone regardless of whether anyone opens an app: closures, delayed starts, protocol activations, transport changes, deadlines. The dividing test is whether a missed message costs a grade or costs a child standing somewhere unexpected.
What is the difference between a Schoology parent account and a Kastr guardian record?
An account is a login, measured by activation. A guardian record is a person with an effective-dated role and contact points carrying channel type, validation state, consent state, source and rank, measured by whether a message reaches a human at 5:40am. A guardian record works whether or not the adult has ever signed into anything, which is the whole point of it.
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.