DP Pano

Keeping a school's noticeboard current is nobody's actual job. The printed notice goes stale in a week, the duty roster is shifted along by hand every Monday, and the timetable lives in a spreadsheet that changes without anyone being told.

Schools that do put something on a screen hit a second problem: the teacher closes the full-screen page on the way into a lesson, nobody opens it again afterwards, and the system is dead by the second week. On top of that, the personal-data rules arriving in 2026 made showing a pupil's name and photograph on a public screen a problem from the outset.

Outside lesson time the board opens itself, full screen. The moment a teacher signs in, it steps back. Setting it up is a single step, and it asks the teacher to change nothing about how they work.

That is the whole answer to the second-week death: a system that needs somebody to remember it is a system that stops.

Separate screens are defined for the entrance hall, the staffroom, the canteen and the corridor. The content is held at school level and the screens differ only in layout: a notice entered once appears on every screen in that screen's own arrangement.

Updates are pushed from the server to the screen as they happen, over server-sent events. Nobody refreshes a page.

The timetable is built by a constraint solver that produces a clash-free schedule: teacher availability, block lessons, rooms and elective pools all enter the same calculation.

The duty roster is distributed automatically on a zone-by-day rotation and prints as landscape A4, ready for the wall. When a teacher is absent, their lessons are shared among the people free at that hour on a fair measure — that day's load, plus how many covers they have taken in the last thirty days.