Every few months we get an inquiry from a school that spent €15,000 on a Learning Management System, deployed it for a full year, and then contacts us because they still do not have a way to track attendance, manage enrollment, or communicate with parents. The LMS is doing exactly what it was designed to do. The school bought it expecting it to do something different.
The confusion between Student Information Systems and Learning Management Systems is widespread enough that it consistently shapes buying decisions in ways that leave schools with tools that do not solve their actual problems. This post is an attempt to be definitive about the distinction, with enough specificity to be useful rather than just categorical.
What a Student Information System does
A Student Information System (SIS) is the operational database of a school. Its primary function is to hold, organize, and make accessible the official records of every student, teacher, and administrative interaction that the school produces. The canonical data in an SIS includes: enrollment records, attendance, grades and assessments, health and medical information, behavioral incidents and pastoral notes, timetables, and billing and fee payment records.
The defining characteristic of an SIS is that it produces the official record. When an inspector asks for attendance data, the school produces it from the SIS. When a parent asks for their child's academic record, the school produces it from the SIS. When the national ministry requires enrollment statistics, the data comes from the SIS. The SIS is the source of truth for institutional data about the school's students and staff.
An SIS does not deliver learning content. It does not host course materials, assignments, or video lessons. It does not provide a discussion board or a collaborative workspace. It records that a student was assessed and what the result was, but it does not contain the assessment instrument itself. The boundary is between record and content.
What a Learning Management System does
A Learning Management System (LMS) is a content delivery and assignment management platform. Its primary function is to host course materials, distribute assignments, collect student submissions, and — in some implementations — provide automated assessment tools. The canonical data in an LMS includes: course content (videos, documents, presentations, interactive exercises), assignment specifications and deadlines, student submissions, feedback from teachers, and in some cases automated quiz scores.
Popular LMS platforms in European schools include Google Classroom, Microsoft Teams for Education, Moodle, and Canvas. What these platforms have in common is that they are built around the teacher-student-content relationship. They facilitate learning activities. They do not manage the operational and administrative life of the school.
An LMS does not manage enrollment. It does not track attendance in the official sense (though some have attendance widgets that generate unofficial records). It does not manage fee billing. It does not hold the student's medical record, safeguarding notes, or family contact information. Most critically, an LMS does not produce the kind of structured, auditable data that compliance reporting and inspection frameworks require.
Where the confusion comes from
The confusion has two sources. The first is that both systems have grade-related functionality. An LMS grades assignments. An SIS records grades in the official transcript. These look like the same thing to a school director who is not already familiar with both systems, especially because the word "grade" is used in both contexts. They are not the same thing: one is the teacher's record of a learning event, and the other is the official academic record that the school certifies and the student carries forward to university applications or employment.
The second source of confusion is that both systems have some attendance functionality during pandemic-era implementations. Google Classroom and Microsoft Teams both acquired attendance features during the 2020-2022 period when schools needed to track student presence in virtual classes. These features gave many school administrators the impression that their LMS handled attendance. They handled attendance for virtual classes during distance learning. They do not handle the official attendance register that national curricula require, and they do not integrate with the billing, parent notification, and compliance reporting workflows that attendance data needs to feed.
What happens when schools buy an LMS expecting SIS functionality
The most common failure pattern is this: a school adopts Google Classroom or Microsoft Teams because it is free (or included in a Google Workspace / Microsoft 365 subscription), uses it successfully for content delivery, and then assumes that because the platform handles learning it handles school management. The SIS function — enrollment tracking, official attendance, billing, compliance reporting — stays in spreadsheets or a legacy system that nobody maintains.
This works until it does not. The moment when it stops working is usually either an inspection (when the school cannot produce the structured data the inspector requires from a coherent system), a staffing change (when the person who maintained the spreadsheets leaves and the institutional knowledge leaves with them), or a compliance event (when a parent makes a GDPR data access request and the school discovers that the data is scattered across Google Drive, Excel, and the memory of a former administrator).
A school running Google Classroom for content delivery and Kinderpedia for operational management has the right tool for each function. A school running Google Classroom for everything has a content delivery system that is excellent and an operational management system that is absent. The gap is not visible during the sale. It is very visible during an inspection.
What happens when schools buy an SIS expecting LMS functionality
The reverse failure is less common but happens in schools that spend significant budget on an enterprise SIS expecting it to replace their content management workflow. Enterprise SIS platforms — the kind used in large US school districts, like PowerSchool or Infinite Campus — are excellent at managing operational data at scale. They are not designed to be content delivery platforms. Their assignment management features, where they exist, are typically rudimentary compared to purpose-built LMS tools.
In the European private school context, schools that purchase an expensive SIS with the expectation that it will replace their need for a platform like Google Classroom are consistently disappointed by the content management experience. The SIS manages records at the cost of content workflow. The correct answer is to use both, connected where the data needs to flow between them (grade synchronization, student roster synchronization), and separate where the functions are genuinely different.
How the two systems connect
In a well-configured school technology setup, the SIS and LMS are not competitors — they are connected. The connection points are: the student roster (the SIS is the source of truth for who is enrolled, and the LMS gets its class lists from the SIS), grade data (grades entered in the LMS for individual assignments can feed into the SIS's official gradebook), and single sign-on (teachers and students log into both systems with the same credentials, managed through the SIS's identity management).
Kinderpedia integrates with Google Classroom through a data sync that pushes student roster information to Google Classroom classes automatically when enrollment changes in Kinderpedia. Grade data flows in the opposite direction: assignment grades entered in Google Classroom can be imported into Kinderpedia's gradebook for inclusion in progress reports. This means the teacher does the work once — entering grades in the LMS where they manage content — and the record appears in the SIS where it feeds compliance and reporting requirements.
The integration is not frictionless in the sense that the two systems look identical to the user. They are different products with different interfaces. But the data they hold does not need to be entered twice, and the choice between them is a question of which function is being served — content delivery or official record — not which product to buy instead of the other.
A practical test for what you actually need
If your primary unsolved problem is: "We cannot produce attendance records for an inspection," "We do not know which parents have paid their fees for this month," "Our student medical records are in a spreadsheet that one administrator controls," or "We have no central record of which students have safeguarding flags" — you need an SIS, not an LMS.
If your primary unsolved problem is: "Teachers are distributing assignments through personal email," "Students do not have a central place to access course materials," "We cannot collect and grade homework submissions efficiently," or "Teachers have no way to share resources with each other" — you need an LMS, possibly in addition to an SIS you already have.
Most schools that contact Kinderpedia have the first set of problems. A few have both. The answer for both sets is the same: start with the SIS, because the operational data management is the foundation that everything else depends on. Content delivery without an operational foundation is a building without a structure. It looks functional until something structural is needed.
What to ask before buying either
Before committing to any platform, ask the vendor to demonstrate three things: how the system handles a subject access request under GDPR (this tests whether the data structure is coherent and the export function works), how the system produces the monthly attendance summary for the class that has the most students (this tests whether the data entry workflow is realistic at scale), and what happens to the school's data if the contract is terminated (this tests data portability, which matters because switching costs in school management software are high). A vendor who cannot answer all three questions confidently is a vendor whose product you should not trust with your school's operational data.