Freelance project · SaaS
Admissions, attendance, fees and results in one system the whole school can use
The School Management ERP brings a school’s daily work into one place: admissions, attendance, timetables, fees, exams and parent communication. Each role sees its own view of the same data. I designed the role-based dashboards and the core flows for administrators, teachers and parents.
01The problem
Schools often run on a mix of registers, spreadsheets and messaging groups, so one student’s details live in several places. An ERP replaces all of that, but it serves people with very different jobs and very different comfort with software. The challenge was to keep a large system usable by giving each role only what it needs.
Who it’s for
School administrators
Need admissions, fees and records in order, with reports ready when they are asked for.
Class teachers
Need to take attendance, enter marks and see their timetable without admin work getting in the way.
Parents and guardians
Need to see attendance, fees due and results, and hear from the school in one place.
School principals
Need a picture of attendance, fees and results across the whole school.
02The main flow
01
Open today’s timetable
02
Take class attendance
03
Absences sent to parents
04
Enter homework or marks
05
Review class summary
03Structure
Students
Academics
Finance
Communication
Administration
04Key decisions
Decision 01
Marking every student present one by one is slow, and teachers do it every single day.
Considered
A list where each student must be marked present or absent.
Chosen
I made everyone present by default, so the teacher taps only the absent or late students and then confirms the register.
Why it works
Most students are in school on most days, so marking exceptions means far less tapping, while the confirm step still makes the teacher check the full list.
Decision 02
Opening the full system to parents would confuse them and expose internal detail.
Considered
Giving parents a trimmed-down version of the staff interface.
Chosen
I designed a separate, mobile-first parent view built around their child: today’s attendance, fees due, latest results and school notices.
Why it works
Parents have a handful of questions, and a view made for them answers those faster than any reduced admin screen.
Decision 03
A single outstanding amount leaves parents unsure what it covers and when each part is due.
Considered
A balance figure with a pay button.
Chosen
I showed fees as a term-by-term schedule with what is paid, what is due next and a receipt for each payment.
Why it works
A schedule answers the questions that would otherwise become calls to the school office, and it gives the admin team a clearer view of dues.
05What’s inside
One record holds a student’s details, attendance, fees, marks and documents.
Teachers mark only absent or late students, then confirm the register.
Fee schedules, collections, receipts and dues reports for the admin team.
Marks entered by subject feed report cards that parents can view and download.
Announcements and absence alerts reach parents in their own view.
06Outcome
Delivered
What I learned
In a large ERP, what each role doesn’t see matters as much as what it does.
Designing the student record first made every module easier, because they all had one place to point to.
Next step
Pick a time that suits you. You'll leave the call with a clear next step, whether we work together or not.
