Student Information System for Boarding Schools

Hostel management software is built around room allocation, mess billing and occupancy reporting for transient residents. A student information system for boarding schools is the academic record of the child first, with residential life layered on top. It links lesson attendance, marks, parent communication, exeat, medical events and safeguarding into one longitudinal file that travels with the student from admission to leaver. Hostel tools cannot evidence pastoral care to an inspector; a boarding SIS is designed to.

Yes. The pastoral and safeguarding module is designed around the evidentiary expectations of the UK Independent Schools Inspectorate (ISI), the Council of International Schools (CIS) accreditation protocol, and the Ofsted National Minimum Standards for Boarding Schools. Every incident has a timestamped author, named DSL reviewer, action plan, review date and immutable audit log. Inspectors can be shown a chronological pastoral history for any current or recently departed student inside the platform, rather than reconstructed from email.

Yes. Each guardian relationship carries its own approval rights. A parent overseas can authorise a weekend exeat to a named host; the local UK or US guardian can be required to co-sign for long-leaves; the house-master receives a queued approval with travel details and expected return time. Every approval is captured with IP, timestamp and the contact channel used, so the school can demonstrate informed consent if anything goes wrong.

International students get a dedicated section for passport number and expiry, visa type and expiry, CAS or I-20 reference, UK or US guardian contract on file, and travel itineraries each holiday. Expiry alerts run to the registrar months in advance; a missing or out-of-date document blocks term enrolment until resolved. The same record stores home-country emergency contacts, language preferences and any cultural or religious considerations for housing.

Clinical notes are visible only to the nurse and named medical staff. Boarding and academic staff see derived welfare flags — for example, asthma, EpiPen location, allergies relevant to dining, or a 'no contact sport' note — without seeing the underlying consultation history. Access is granted by role and audited; every view of a sensitive record is logged. This separation lets the school meet GDPR, HIPAA-adjacent local rules and inspector expectations without crippling day-to-day operations.

Yes. The same student file simply omits the residential block when a child is a day pupil, or activates it on the day they convert to boarding. Mixed schools run weekly boarders, flexi boarders, full boarders and day pupils side by side without duplicate records, and historical conversions remain visible on the student's timeline for fee, pastoral and safeguarding continuity.