← IndexMALIK HADI — Case StudyHire me
02Web · SystemDesign + Dev

School Mgmt. System

A role-based school portal — admissions, fees, results and attendance for admins, teachers, students and parents in one system.

Landing page
(01)The Problem

The school ran on registers, spreadsheets and WhatsApp. Fees were tracked by hand, results took weeks to compile, and parents had zero visibility until report-card day. They needed one system for four very different kinds of users.

(02)The Process

Mapped every workflow with the staff first, then built a role-based portal: admins manage admissions, classes and fee schedules; teachers mark attendance and enter results; students and parents get read-only dashboards of exactly what concerns them. Built on Next.js with an Express/MongoDB backend and strict role-based access control.

(03)The Result

Result compilation went from weeks to the same afternoon, fee defaulters surface automatically instead of by audit, and parents check progress from their phones. The office staff's spreadsheet era is over.

0Roles — admin, teacher, student, parent
0Modules from admissions to results
0Office hours saved per week (est.)
(++)Under the hood
01Next.jsOne app, four role-scoped experiences
02Express · MongoDBFees, results and attendance with a full audit trail
03RBACRoute- and API-level role enforcement

Results that took our office weeks now go out the same day.

School AdministratorClient