One question, one answer
Outstanding balances, attendance and enrolment are read from the same student record instead of being reassembled.
Education · Internal management system and member portal
Music school
A management system replacing scattered spreadsheets for students, attendance, lessons, workshops and payments, with a portal so parents can find information instead of asking for it.
The operational challenge
A basic question about the business took an hour to answer.
Student records, attendance, payments and parent communication lived in separate files and chat threads. Each was accurate on its own, but nobody could answer “who has not paid this month?” without assembling the answer by hand, so the answer was usually an estimate.
Leadership and scope: Mihail led discovery of the real teaching and administrative workflow, then owned product definition, architecture and delivery of the management system and the parent-facing portal.
The delivered system
One record for every student, from enrolment to attendance and payment.
- Brought students, groups, rehearsals and attendance into one structure instead of parallel files.
- Tracked payments, recurring expenses and outstanding balances against the same student record.
- Handled private lessons and workshops with their own attendance and payment flows.
- Added a member portal where parents access programmes, materials and notifications directly.
- Applied role-based access so staff, administrators and parents each see only what they should.
How the work moves
What it changes day to day
Where the system earns its place.
Fewer repeated questions
Parents see schedules, materials and notifications themselves, which removes a large share of daily admin replies.
Access matched to the person
Staff, administrators and parents each see only what their role allows, which matters when the data concerns children.
Why spreadsheets stopped working
Spreadsheets fail at the point where two facts must agree.
A spreadsheet is excellent at holding a list and poor at holding a relationship. Once attendance, tuition and enrolment must agree about the same student, keeping several files consistent becomes a daily manual job that quietly grows with the school.
Modelling the student once, then attaching attendance, lessons and payments to that record, removed the reconciliation rather than speeding it up.
Reducing the administrative load
The portal exists to prevent questions, not to add a feature.
A large share of administrative time was spent answering questions that a parent could answer themselves: when a session is, what to prepare, what is outstanding.
Publishing that information once, in a place parents can reach, converts repeated individual replies into a single update.
What changed operationally
to answer who has outstanding payments, instead of an hour
for students, attendance, lessons, workshops and payments
portal for parents, reducing repeated administrative questions
Published without naming the school. Student data, family details and financial records remain private and are never used as marketing material.
What can be verified
A system handling personal data describes its structure, not its contents.
This system holds information about children and families, so nothing from it is shown publicly. Access is restricted by role, and the case study describes the workflow rather than the data.
For a comparable organisation, the transferable evidence is the model: one student record, attendance and payment attached to it, and a portal that removes repeated questions.
When the team runs on spreadsheets and memory