Scheduling rules

School timetable constraints explained

A timetable is only as useful as the rules behind it. Separate requirements from preferences before you ask a generator to place lessons.

Start free trial See the live demo

School timetable constraints describe when a lesson can happen, who can teach it and which resources it needs. A requirement such as a teacher being unavailable on Friday differs from a preference such as teaching Maths in the morning. Treating both as compulsory can turn a workable week into an impossible scheduling problem.

Start with a single agreed list of rules. Record the owner of each rule and whether it is a requirement or a preference. This gives the timetable coordinator a way to resolve competing requests without silently changing the curriculum or a teacher’s contract.

Hard constraints: what must never overlap

A teacher, class or room cannot be in two lessons in the same period. A teacher’s unavailable time must remain unavailable. If Chemistry requires the science lab, another lesson cannot book that lab at the same time. These rules define whether a placement is valid.

Weekly teaching hours are another feasibility check. In a five-day week with six teaching periods per day, a class has 30 slots. A curriculum requiring 32 periods cannot fit unless the week changes or the requirements are revised. A generator cannot solve a shortage of teaching time by rearranging lessons.

Soft constraints: what you want to improve

Preferences include spreading a subject across the week, reducing gaps in a teacher’s day and avoiding too many demanding lessons consecutively. They help compare valid timetables, but may compete with one another. A morning preference for every subject cannot be satisfied simultaneously.

Agree priorities before generation. For example, preserve part-time availability as a hard rule, then prefer fewer gaps, then prefer early periods for a particular subject. Review the actual result with staff rather than assuming a high overall score means every teacher’s week works well.

A worked example: the shared science lab

Suppose four classes each need two lab periods per week. Demand is eight lab periods. If the lab is available for ten periods, the room has enough capacity in total. But if the only qualified teacher is available for six of those periods, staffing is the bottleneck. Check the overlap between teacher and room availability, not just the separate totals.

Resolve the shortage with the person responsible for staffing or curriculum. Possible changes include another qualified teacher, more lab availability or a revised lesson requirement. Do not relax safety, qualification or contractual requirements simply to fill the grid.

Try the rules before moving to a school-wide system

Use the free timetable generator to explore class, teacher and room clashes with a small setup. The browser demo supports day-level teacher availability and a limited school size; it is not a model of every scheduling rule your school may need.

For a real implementation, compare your requirements with Skoolia’s AI timetable capabilities. Bring your hardest rules to a demo and ask to see how the system validates them before publication.

Before you generate

Confirm weekly subject periods for every class
Record qualified teachers and their availability
List specialist rooms and shared resources
Separate compulsory rules from ranked preferences
Check capacity before changing any rules

Frequently asked questions

What is a hard timetable constraint?

A rule a valid timetable must obey, such as no teacher double-booking or no lesson during a teacher’s unavailable time.

What if no timetable satisfies the rules?

Check class hours, staffing and room availability for shortages. Resolve the conflicting requirements with the responsible staff member, then regenerate.

Generate your school timetable with AI

Start a 14-day free trial on Skoolia — no credit card, cancel anytime.

Start free trial

14 days free · No card required · Clash-free timetables in minutes