Flexible scheduling
Build the week around how your institution really teaches: weekly lesson counts, explicit multi-period sessions for double periods, and classes that are either fully placed or not placed at all.
Create, manage and optimize schedules effortlessly. One flexible platform for schools, organizations and teams.
AnySchedule models the parts of a real institution — classes, teachers, rooms, periods and rules — and keeps them consistent, so a generated week is a valid week.
Build the week around how your institution really teaches: weekly lesson counts, explicit multi-period sessions for double periods, and classes that are either fully placed or not placed at all.
One deterministic engine turns your requirements into a week. The same inputs always produce the same timetable, so results can be reviewed, explained and reproduced.
A teacher, class or room can never be booked twice, lessons never land inside a break, and nothing is placed on a non-teaching day. Violations are reported instead of hidden.
Subjects, classes and streams, programmes, activity types and class kinds — plus the teaching assignments that decide who actually stands in front of each group.
Describe rooms by kind and features, then let a session require what it needs. If no suitable room is free, you learn why before anything is published.
Periods, breaks, operating days and reserved time shape the week. Publish a term to make it read-only, and unpublish it when something genuinely needs to change.
Most of the work happens once. After that, preparing a term is a short review rather than a rebuild.
Describe the school, the days it genuinely teaches and the terms you plan for. Everything later builds on this shape.
Capture what is taught, by whom and where — then describe the day in periods and breaks.
Generate the week, read the conflict panel, adjust what needs adjusting and publish the term when it is right.
AnySchedule treats constraints as facts that live in the engine and in the database — not as suggestions the interface politely hides.
A rule that prevents a double booking is checked by the scheduling engine and again by the database, so one buggy path cannot quietly produce an invalid week.
When a week cannot be built, the result says so explicitly and explains which requirement blocked it. Nothing is shortened, dropped or invented to produce a green checkmark.
Timetables belong to the institution. Deleting a personal account removes the person and their preferences — not the week that colleagues and students rely on.
AnySchedule is built for the people who have to make the timetable work, and for everyone who has to read it on Monday morning.