What is a student information system?
A student information system, usually shortened to SIS, is the system of record for a school. It holds the authoritative version of who is enrolled, which family each student belongs to, what courses they are taking, what grades they earned, whether they were in class, and — in many systems — what the family owes.
The important word is authoritative. Plenty of school software touches student data. An SIS is the copy everything else is supposed to agree with.
What an SIS typically covers
Student and family records. Demographics, contacts, guardians, siblings, medical notes, emergency contacts. One record per student, linked to one record per family.
Enrollment and admissions. Inquiries, applications, supporting documents, acceptance decisions, and the annual re-enrollment cycle.
Scheduling. Courses, sections, terms, and which students are in which section with which teacher.
Gradebook and reporting. Assignment scores, weighting, term grades, report cards, transcripts, and GPA.
Attendance. Daily or per-period presence, absence reasons, and the summaries a school has to produce for its accreditor or state.
Billing. Tuition plans, fees, payment schedules, and statements. This is the piece that varies most — some systems include it, some sell it separately, and some do not have it at all.
What an SIS is not
It is not a learning management system. An LMS is where teaching happens: assignments distributed, work submitted, materials posted, discussions held. An SIS is where the record of that lives. The two overlap at the gradebook, which is why they are so often confused, and why most schools end up running both.
It is also not an accounting system. An SIS tells you what families owe and what they have paid. A general ledger is a separate concern, and most schools reconcile between the two.
Why it matters which one you pick
Every other system a school runs reads from the SIS. Swap it out and you touch the LMS integration, the email directory, the lunch system, the accounting export, and every report the office produces. That is why schools stay on systems they have outgrown — the migration is genuinely disruptive, not because the current system is good.
Two things are worth weighing more heavily than feature checklists:
-
Can you get your data out? Not “is there an export button” but: can you export every entity, in a format you can open, without paying for it. This determines whether your next migration is a project or a crisis.
-
How much of the setup requires the vendor? If adding a grading scale or changing a term structure needs a support ticket, you will be waiting on someone else every August.
The fit problem for small schools
Most SIS platforms are built for districts and priced accordingly, or built as a gradebook that grew billing later. A school with two hundred students has the same structural needs as one with two thousand — enrollment, scheduling, grading, attendance, billing — with a fraction of the administrative staff to absorb the overhead of running the system.
That gap is the reason North Star SIS exists. If it sounds like your situation, try it out and tell us where your current setup breaks down.