Cookies, honestly. We'd like to see which pages actually help. Nothing measures you until you say yes. What we collect
Create the school timetable with AI: build the period grid per class and section with clash-blocking on teachers and rooms, and publish it so every teacher’s periods land on their own calendar.
A school timetable — or class schedule, or period plan — is built on a wall chart, checked by eye for clashes, and then copied by forty teachers into forty diaries.
Build it once, for each class and section, and publishing it puts every teacher’s periods on her own calendar.
Paperhint’s timetable is built in the school office per class and section, with hard clash-blocking on teachers and rooms, and reads its dates from the school calendar — terms, holidays, exam windows. Publishing it places every teacher’s periods on her own calendar automatically, and a change in the office is a change on her day. It sits alongside allotments (who teaches which class and section), so the timetable and the staffing agree.
Terms, holidays, events and exam windows in one school calendar that every other module reads dates from.
Periods by day, with clashes on a teacher or a room blocked as you go.
Every teacher’s periods appear on her own calendar. Nobody copies a row into a diary.
A swap or a cover made in the office is reflected on every affected teacher’s day.
Paperhint builds the timetable per class and section with clash-blocking on teachers and rooms, and publishes it to every teacher’s calendar. The office stays in control of the grid.
Yes. Publishing the school timetable places each teacher’s own periods on her calendar, and any change in the office updates her day.
Cover and swap are handled from the same place — a period is reallotted without rebuilding the grid, and the affected calendars update.
Yes. A teacher or a room cannot be in two places in the same period; the grid blocks the clash as it is built.