School Management System
Features
Modules & records
Several schools
Several schools are overseen from one place, each with its own classes and a weekly timetable that gives every period its time, its lesson and its classroom.
Student enrolment
Every student is enrolled through one complete form: their personal details and medical notes, the contacts of their parents or guardians along with whether each may be contacted, and any notes. Each record also carries a status of active, inactive or graduated.
Cascading assignments
Students and teachers are assigned to schools, then to classes, then to lessons, through pickers in which each choice narrows the next, and anyone can belong to several of each.
Student and staff catalogues
Students and staff are listed in searchable catalogues that sort and filter by status, school, class and lesson. Any record can be edited right in its list, and a deleted one is kept so that it can be recovered.
Lesson records
Choosing a school, a class and a lesson lays out every session by its date, showing whether classwork and homework were set and how many of the enrolled students attended. Each session then records the work set and, for every student, their attendance, completed exercises, dictation scores, test grade and notes.
Tests
Tests are defined for each lesson as part of its course material, and every session can be linked to the test that was held in it.
Teacher schedules
Every teacher has a schedule for each day of their week, showing the school, the class and the subject of each lesson, its start and end times, and the classroom along with its place in the school.
Security and data integrity
Protection & integrity
Prepared statements throughout
Every query that carries user input runs as a native prepared statement through PDO, with emulation turned off, so the input can never be read as part of the SQL itself. Sorting and filtering accept only values from a fixed allow-list.
Encrypted staff records
Teachers' personal details are encrypted field by field with AES-256, each record with its own random IV, and sealed with an HMAC-SHA256 that is verified in constant time before anything is decrypted. The keys are kept outside the code, and without them the data is all but impossible to read.
Password hashing
Passwords are never stored as they are typed: teachers' are kept as Argon2id hashes and students' as bcrypt hashes, and both are checked with PHP's password_verify.
Sessions
The session cookie is Secure, HttpOnly and SameSite=Strict, with a limited lifetime, and a screen left idle locks itself and signs the teacher out.
Sign-in protection
Every sign-in passes a reCAPTCHA, which is verified on the server rather than trusted from the browser.
Validation on both sides
Every form is checked twice. The browser checks each field against patterns that accept both Greek and Latin letters, and the server then escapes the text and checks email addresses, lengths, password strength and the type of every identifier, so a harmful entry is refused rather than forwarded to the database.
Data integrity
A change that touches several tables runs as one transaction and is rolled back whole if any part of it fails, so the data is never left half-written. Deleted records are only marked as deleted, never erased.