The Results
| Metric | Result |
|---|---|
| Weekly time saved | ~10 hours of manual scheduling work eliminated |
| Growth enabled | School scaled to 3× its original size |
| Schedule distribution | Automated to all students and teachers via portal + email |
| Curriculum database | Still in active use today |
The Challenge
A performing arts college in Germany with around 300 students and a dozen teachers had been managing their class scheduling by hand in Excel. For years, this worked fine — the school was small enough that one person could map it all out manually.
But the school was growing. Multiple year groups, overlapping teacher availability, room assignments, and an increasingly complex curriculum made manual scheduling unsustainable. Each new term meant days of painstaking spreadsheet work, and mistakes — double-bookings, missed classes, scheduling conflicts — were becoming more frequent.
They evaluated off-the-shelf scheduling software, but found it too rigid and cumbersome. A performing arts curriculum doesn't fit neatly into the templates that standard school software assumes. They needed something built around the way their school actually operates.
The Solution
I built a custom web application, hosted on a dedicated server, that replaced the entire spreadsheet-based workflow:
Automated schedule generation: The system handled the complex logic of assigning classes across multiple year groups while respecting teacher availability and room constraints — work that previously took days of manual effort.
Schedule distribution: Once generated, schedules were published through a portal and automatically emailed to both students and teachers. No more printing, no more chasing people down with updates.
Teacher hours tracking: The system logged hours per class and per teacher, giving the school accurate data for labour cost estimation and budgeting — replacing guesswork with real numbers.
Curriculum database: A persistent record of what each teacher taught, per subject, per year. This gave the school a living knowledge base of their curriculum history — still in active use today.
Key Takeaway
This is a textbook case of a system that worked — until growth broke it. The school didn't need software when they were small. But what was manageable for 100 students became impossible for 300. Rather than forcing them into generic scheduling software that didn't fit their curriculum, we built exactly what they needed. The result: a system that removed the bottleneck, enabled the school to keep growing, and is still serving them today.