Foundational

What data does an SIS
actually store?

A modern SIS holds detailed information about every student in the district. Understanding what's in it - and what isn't - is the foundation of both privacy and effectiveness.

Talk to Alma
The short answer

An SIS stores student demographics, enrollment and attendance, grades and academic records, scheduling and course data, discipline and behavior records, health information, special population identification (special education, EL status), family contact information, and communication history. It does not store detailed educational content (that's the LMS) or financial and business records (that's the ERP).

The scope of student data

Understanding what's stored is the start of understanding what's at stake.

The SIS is one of the largest concentrations of student data in a district. Parents, boards, and privacy advocates increasingly want to know what's actually in it. Districts should be able to answer clearly.

Categories of data typically stored in an SIS:

  • Demographic: Name, birthdate, gender, race and ethnicity, address, phone, email, primary language, citizenship or residency status where required
  • Family and guardian: Guardian names, relationships, contact information, custody arrangements
  • Enrollment: Grade level, school assignment, enrollment date, entry codes, withdrawal codes, transfer history
  • Attendance: Daily and period-level attendance, tardiness, absences, reasons where recorded
  • Academic: Current gradebook data, historical grades, transcripts, GPA, class rank, credits earned
  • Scheduling: Current schedule, historical schedules, course assignments
  • Discipline and behavior: Incidents, referrals, actions taken, restorative practices notes
  • Health: Immunizations, allergies, medical alerts, medications administered at school
  • Special populations: Special education status (indicator only in most SIS platforms), EL status, gifted status, free/reduced meal eligibility, homeless status
  • Communication: Messages exchanged between school and family, notification history
  • Assessment: State assessment results, benchmark data, universal screener scores

Common questions, answered directly.

Usually not the full documents. Most SIS platforms indicate whether a student has an IEP or 504 plan, but the detailed plan documents live in a specialized special education management platform (SEAS, Frontline, Skyward SPED, or district-built systems). The SIS is where you note the accommodation exists; the specialized platform is where the plan is developed and stored.

Basic health indicators yes: immunizations, allergies, medical alerts, medications administered during school hours. Detailed medical records, physician notes, or protected health information typically live elsewhere. Nurse notes vary - some districts keep them in the SIS, others use a specialized nurse management platform.

Some do, some don't. States vary in requirements. Where SSNs are stored, they should be encrypted, access-controlled, and typically limited to registrar-level users. Many districts have moved away from storing full SSNs in the SIS due to privacy risk, using state-assigned student IDs instead.

Not directly. The SIS typically stores free/reduced meal eligibility status (yes or no) rather than actual family income. The determination is made elsewhere - through the free/reduced meal application system - and the eligibility flag flows to the SIS for program participation and reporting purposes.

Most modern SIS platforms support student photos, though whether they're used varies by district. Photos help with identification for substitute teachers, security staff, and lunch service. Districts should have clear policies on who can access photos and how they're managed. Some states have specific rules on student photo consent and retention.

Varies by data type and state requirements. Academic records (transcripts, historical grades) are often retained indefinitely - a student may need their transcript decades after graduation. Attendance and discipline records typically follow state retention rules (often 5-7 years). Current-year operational data is retained as long as needed for reporting cycles. Districts should have documented retention policies aligned with state requirements.

Access is controlled by role and legitimate educational interest (a FERPA concept). Teachers see students in their classes. Building administrators see students in their building. Counselors see their caseload. District administrators see broader data. Registrars and specific administrators see sensitive data (health, discipline, special populations). Families see only their own students. Students of appropriate age see their own records.

Alma enforces these boundaries through granular role-based permissions down to individual data fields - ask to see the permission structure directly during your evaluation rather than taking a general description at face value.

Alma encrypts data at rest and in transit, enforces role‑based access control, maintains comprehensive audit logs, undergoes SOC 2 Type II auditing, and provides districts with data ownership and portability. Ask specifically about the data types your district cares about most and the controls that apply.

Districts should ask any SIS vendor to walk through the specific data types stored, who accesses each, and how that access is controlled.

Ready to see how Alma handles this?

Get straight answers to the questions this guide raises. Schedule a walkthrough with Alma.

Schedule a Demo