What looks like a school website is really three systems: a shop window for those choosing, a portal for those already enrolled, and a task manager for those doing the work.
The task
A private lyceum in Mykolaiv, twenty-five years old, years one to eleven. The brief looked like “a school website” and turned out to be three briefs for three different people.
A parent choosing a school needs to understand terms and fees. A parent whose child already attends needs something else entirely — grades, timetable, payments, contact with the teacher. And the staff need somewhere the work actually lives: tasks, deadlines, owners.
One shop window cannot serve all three. Usually nobody tries: the school gets a website, a separate parent chat, and separate spreadsheets for internal work — and all of it lives apart.
The approach
Three systems on one foundation. The public site, the parent portal and the staff task manager share an account and a database. A parent signs in where they first came to look at the school, not on a separate portal with another password.
The parent portal. Everything that used to go into messages and get lost there now sits in one place, available around the clock. This lifts more load off the office than it appears to: a large share of calls to a school are questions whose answers already exist.
A task manager for staff. Internal work stops living in a messenger where a task sinks under newer messages. There is a deadline, an owner and a status.
Enquiry tracking for applicants. An application is a record, not an email — you can see who got in touch, where the conversation stands and how it ended. Admissions arrive in waves, and without this some enquiries are lost simply through workload.
Mandatory transparency covered in full. Statutes and founding documents, governance structure, regulatory basis, anti-corruption policy, vacancies, fees. Ukrainian education law requires openness, and this is a case where compliance also builds trust: a parent sees figures and documents instead of “call us to find out”.
Independent analytics instead of external trackers. Visit statistics are counted on the lyceum’s own server: visitor data does not go to third parties or feed anyone’s advertising profiles. Where children are involved, that is the correct default rather than an extra.
The result
The lyceum does not have a website, it has a working system: the public part brings new parents in, the portal serves current ones, the task manager holds the internal work together.
This is exactly the difference between building a website and building a system. A website can be ordered anywhere. A system has to be designed around how the institution really runs.