EduGears AI SIS: Your Student Records Now Live Beside Your Courses

Ask a school office where a student is and you will usually get two answers. In the student information system they are a record: a number, an address, a guardian, a status, a fee balance. In the learning platform they are a roster line: a name in a classroom with some grades attached. Both are true. Neither is complete. And between them sits a nightly job that copies names from one to the other and, on a bad Monday, quietly does not.

We have spent the last stretch of development closing that gap rather than automating it. EduGears AI SIS is a student information system built into EduGears AI LMS — admissions, student records, attendance, report cards, timetables, fee records and a guardian portal, in the platform that already runs your courses. One platform, one login, and nothing in the middle to keep in step.

What does the sync layer actually cost?

More than the license for the second system, which is the part that gets budgeted. The real cost is that every question spanning both halves becomes a manual join, done by a person, under time pressure, usually with a parent on the phone.

Every one of those is an integration problem invented by having two systems. None of them is a question a school actually wanted to ask. When the record and the classroom live in the same platform, the join is not automated — it stops existing.

What joins the records to the teaching?

The cohort. It is the small idea that does most of the work here, so it is worth being precise about it. A cohort is a group of students moving through a year together — a class, a year group, an intake, a training cohort. Put a cohort on a course and the classroom is created for it, one per cohort and course, with that cohort's students already on the roster.

After that, enrollment stays in step by construction. Add a student to a cohort and they appear in the cohort's classrooms. Move them out and the rosters follow. There is no reconciliation step afterwards, because there was never a second copy to reconcile — the student record and the classroom enrollment are rows in the same database.

The same logic runs through the grades. The figure on the report card is the figure in the gradebook and on the transcript — the same category-weighted number the rest of the platform reads, not a copy that quietly drifted. We wrote about why one grade definition matters more than any dashboard in Student Progress Tracking: The Whole Learner on One Page; the SIS inherits that discipline rather than starting a second version of the truth.

What is in a student record?

Profiles, student numbers, and lifecycle status — with the history behind it. That last part is the one that matters in practice. A status field that only holds today's value can tell you a student is withdrawn; it cannot tell you when, or why, or who decided. Here every change is dated and carries the reason it was made, so the record answers the question an audit actually asks.

• Profiles and student numbers — the identity the rest of the school office refers to.
• Lifecycle status with full history — every change dated, with the reason it was made, rather than a single field overwritten in place.
• Guardians linked to students — the relationship is a record of its own, which is what makes the guardian portal possible later.
• An audit log of personal data — every read and every write of personal information lands in the log, not just the edits.
• Academic structure around it — academic years, terms, programs and cohorts give the year its shape, and the cohort is the unit timetables, registers and report cards all hang off.

Logging reads as well as writes is an unusual choice and worth defending. In a school, the sensitive event is rarely someone editing an address — it is someone looking at a home situation, a guardian arrangement, a fee balance. A log that only records changes cannot answer the question a family is most likely to ask.

How does attendance work, and what does it flag?

Attendance is a session register per cohort, taken where the day already happens. It can be switched on per cohort or for the whole organization, so a school that takes registers for some year groups and not others is not forced into all-or-nothing, and summary views roll the registers up by student and by session.

Then the registers feed the at-risk signals. An at-risk panel surfaces students who need attention, and — this is the part we care about — it explains in plain language why each one is flagged. Not a score. Not a risk percentile. A sentence a form tutor can read, disagree with, and act on.

What happens at report card time?

Per-term report cards carry grades and comments, and at sign-off they are frozen into a snapshot — so a published report never changes underneath you. That is the property schools ask us for most often and the one that is hardest to retrofit: if a report card is rendered live from current data, then a regrade in March silently rewrites what a family read in December. A frozen snapshot is what makes the document a record rather than a view. There is PDF export and there are print templates, because the paper copy is still the copy some families keep.

The AI part, stated precisely

Report-card comments can be drafted with AI. The drafts stay drafts: a teacher or registrar reads them, edits them, and saves them. Nothing is finalized, published or sent on anyone's behalf, and no comment reaches a family without a human having put their name to it.

We are being pedantic about this on purpose. A report-card comment is one of the few pieces of writing a school produces that a family keeps for years, and the value of a draft is that it removes the blank page, not that it removes the teacher. The same standard applies to the at-risk explanations: they tell you why the system raised a flag so that a person can judge it, not so that a person can skip judging it.

Does it handle admissions too?

Yes, from the first form to the enrolled student. There is a public application form for your school, pipeline stages with an audited timeline behind each application, offer letters as PDFs, and one click to turn an accepted applicant into a student with their record intact.

The one click is the point. In the two-system arrangement, an accepted applicant is retyped — once into the SIS, once into the LMS, occasionally into a spreadsheet in between — and every retype is a chance to lose a middle name, a guardian, or a date. Here the applicant record becomes the student record, and the audited timeline of how they got there stays attached to it.

Timetables and fees

Timetabling is a weekly schedule grid per cohort with clash detection across cohorts, teachers and rooms — the three ways a timetable actually breaks — plus a timetable view each instructor can open for their own week. Catching a double-booked room while you are building the grid is worth considerably more than a report that finds it afterwards.

Fees are invoices, part-payments, balances and issue-date views, kept as records. This is the school's book of what was billed and what has been received. It is a record of payments, not a way to take them: EduGears AI SIS does not process card payments and does not collect money. If your school banks through a payment provider today, it continues to — what changes is that the balance is visible in the same place as the attendance and the report card, and to the guardian who is being asked to pay it.

What do parents and guardians get?

Their own portal login — not a shared staff account, and not a PDF emailed once a term. A guardian signs in and sees the children linked to them, and nothing else. If they have three children at the school, that is one sign-in for all three, not one per child.

• A per-child overview: attendance, report cards, fee balances, and what the next school day holds.
• Coursework at a glance — what is due soon, what is overdue, and what has been marked.
• The weekly timetable for each child.
• School forms to read and fill in, per child.
• A messages inbox carrying what the school sends out.
• The same branding and the same 13 languages as the rest of the platform, right-to-left scripts included.

Guardian access is a role like any other on the platform: it opens a guardian's own children's records and stops there. It sits alongside the registrar role, and both slot into the owner, instructor and student roles you already use — so switching the SIS on does not mean learning a second permissions model.

Can we bring the students we already have?

Nobody starts a school year with an empty database, so this was designed before the features that depend on it. Students, guardians and rosters import from CSV against downloadable templates, and every import runs as a dry run first — you read what would be created before a single record is written.

You usually do not have to build the file, either. The format is detected from what you drop in:

And it all goes back out again. Records export to Moodle formats, to Canvas SIS Import, and to OneRoster 1.2 — for the timetabling, finance and reporting tools that read it, and for the institution that one day decides to leave. The exports matter as much as the imports: it is the only honest test of whether a system is holding your data or holding it hostage.

Courses come across separately and by their own routes — Moodle .mbz, Common Cartridge, SCORM — which is the older half of this story and covered in Migrating Courses to a New LMS: The Move, and What You Stop Maintaining. Between the two, a migration is people and content rather than people or content.

Who is this for — and what is it not?

It is built for small and mid-sized private schools, academies and training providers: organizations that teach, keep records on the people they teach, and would rather do both in one place than integrate two vendors. If you already run EduGears AI LMS, this is part of it — one platform, one login, one tenant, included with the LMS. There is nothing extra to host or install; an administrator switches it on and the student records appear beside the courses.

What it is not: a state-reporting system for public school districts. We do not position EduGears AI SIS for US public K-12 compliance reporting, and a district shopping for that should shop for that. The design goal here is a school office that can answer a parent's question in one screen — not a submission format.

Everything else the platform gives, the SIS inherits unchanged: 13 languages including right-to-left scripts, your brand from the sign-in page to the report card, and tenant isolation enforced with row-level security on every scoped table rather than by a filter someone can forget. It is not a bolt-on with rules of its own.

FAQ