Duplicate identities
The same child appears under three spellings across fee, transport, and class lists.
One student record. Every stakeholder. Zero duplicate files.
The Student SIS Directory is the system of record after admission — identity, guardians, health, documents, and academic history that every other ScholarERP module trusts.
1
canonical profile per student across campuses
100%
emergency contacts reachable from any module
0
spreadsheet copies of the master roster
The problem
Why campuses drown in parallel student files
Without a true SIS, admissions, fees, transport, and teachers each keep their own list — and none of them match on exam day.
Missing guardians
When an emergency hits, staff scramble for a phone number that is not on the register.
Health blind spots
Allergies and medical notes live in paper files the PE teacher never sees.
Broken history
Transfers, promotions, and prior grades are hard to reconstruct when a student changes section.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Unified student profiles
Photo, demographics, roll/GR numbers, house, section, and program — one card used everywhere.
Guardian & family graph
Link parents, siblings, and emergency contacts with relationship and pickup permissions.
Health & medical notes
Capture allergies, conditions, and doctor contacts with role-gated visibility.
Document vault
Store birth certificates, transfer certificates, and ID scans against the student record.
Academic history timeline
Promotions, section changes, and prior term outcomes stay attached to the same ID.
Custom fields & tags
Add board, medium, scholarship flags, or trust-specific attributes without custom code.
Role-aware access
Teachers see assigned classes; parents see their children; admins see the full directory.
Clean handoff from admissions
Confirmed applicants become SIS records with documents and fee plans already attached.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Enroll
Admission confirmation creates or updates the canonical student profile.
-
02
Enrich
Staff complete guardians, health notes, documents, and custom attributes.
-
03
Operate
Attendance, fees, transport, and portals read from the same directory.
-
04
Lifecycle
Promote, transfer, alumni-archive — history stays intact under one ID.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
Admin / Registrar
Owns creates, merges, promotions, and cross-campus visibility.
Teacher
Sees profiles and contacts for students in assigned sections.
Parent / Guardian
Updates contact details and views profile data via the parent portal.
Counselor / Nurse
Accesses health and counseling notes under stricter permissions.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
1 source
of truth for identity across campus tools
Minutes
to find a guardian contact in an emergency
Cleaner
audits when boards or trusts request records
“We stopped maintaining five Excel rosters. If a phone number changes once, every bus, fee, and class list updates with it.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Can one student belong to multiple campuses in a trust?
Yes. Trust deployments can keep a single identity with campus/program affiliations so transfers do not create duplicate profiles.
How does SIS connect after admission?
When an applicant is confirmed, ScholarERP provisions the SIS record with documents, guardians, and fee plans already linked.
Who can see medical information?
Health fields are permission-gated. Typical setups limit them to admin, nurse, and designated counselors — not every teacher.
Can we import legacy student lists?
Yes. CSV/Excel import utilities map roll numbers, contacts, and sections during onboarding with validation for duplicates.
See your roster as a living SIS directory
Book a demo with sample student, guardian, and health profiles for your institution type.