Timetable Constraints Explained for School Admins (Hard vs Soft)

Every school timetable is built around constraints - rules that the schedule must follow. Some rules are non-negotiable (a teacher can't be in two places at once), while others are preferences (Mrs. Sharma prefers not to teach on Saturday mornings). Understanding the difference between these constraints - and knowing how to configure them - is the key to generating a timetable that actually works. This guide explains timetable constraints in plain language for school administrators.

Common examples of hard constraints in schools:

• No teacher clash: A teacher cannot be assigned to two different classes in the same period.
• No class clash: A class cannot have two different lessons scheduled at the same time.
• No room clash: A room cannot be double-booked for two different lessons in the same period.
• Teacher availability: If a teacher is marked as unavailable on Wednesday afternoons, no lessons can be assigned to them during that time.
• Required periods per week: Math must be taught exactly 5 periods per week to Class 10A.
• Lab room requirement: Physics practical lessons must be scheduled in the physics lab.

Common examples of soft constraints:

• Preferred time slots: Schedule English in the morning hours when students are more attentive.
• Maximum consecutive periods: A teacher should not teach more than 3 consecutive periods without a break.
• Balanced day distribution: Spread a subject's lessons evenly across the week (e.g., not all 5 Math periods on Monday and Tuesday).
• Minimize gaps: Teachers should not have large idle gaps between their lessons.
• Maximum periods per day: A teacher should not teach more than 6 periods in a single day.
• Avoid last period: Avoid scheduling PE in the first period or theory subjects in the last period.
• Same-day clustering: Double periods (back-to-back lessons) for lab or project subjects.

The rule of thumb is: Only make a constraint hard if violating it would be physically impossible or against school policy. Everything else should be a soft constraint with a priority level.

• Availability (Hard): Days/periods when a teacher is not available (part-time, other commitments).
• Maximum periods per day (Soft): Limit teaching load per day to prevent exhaustion.
• Maximum consecutive periods (Soft): Ensure breaks between lessons.
• Minimum gaps (Soft): Avoid long idle hours between lessons.
• Preferred days/times (Soft): Teacher preferences for specific slots.

• No class clashes (Hard): A section cannot have two simultaneous lessons.
• Subject distribution (Soft): Spread lessons evenly across the week.
• Morning/afternoon preferences (Soft): Core subjects in the morning, electives in the afternoon.
• Maximum subjects per day (Soft): Limit the number of different subjects a class has in one day.

• No room clashes (Hard): A room cannot host two classes at the same time.
• Room type matching (Hard): Lab lessons in lab rooms, PE in the ground/gym.
• Room capacity (Soft/Hard): Class size should not exceed room capacity.
• Room proximity (Soft): Minimize travel time between consecutive lessons.

• Periods per week (Hard): Each subject must be taught the exact number of required periods.
• Double periods (Soft): Some subjects need back-to-back periods (labs, workshops).
• Not on consecutive days (Soft): Avoid scheduling the same subject two days in a row.
• Time slot preferences (Soft): Schedule physically active subjects (PE, sports) after breaks.

• Teacher availability: Set in the Teachers step - mark specific periods as unavailable.
• Class time-off: Set in the Classes step - block periods when a class has other activities.
• Room assignment: Set in the Lessons step - assign specific rooms to lessons that need them.
• Max periods and consecutive limits: Configured as soft constraints with priority weights.
• Subject distribution: The AI engine automatically distributes lessons across the week.
• Double periods: Specify in the Lessons step when creating the lesson entry.

For example, if you set "maximum 3 consecutive periods" as high priority and "preferred morning slot for English" as low priority, the engine will break the morning preference before it allows 4 consecutive periods. Configure priorities based on what matters most to your school.

• Check teacher availability: If too many teachers are marked unavailable during peak hours, there may not be enough teachers to cover all classes.
• Review periods per week: Make sure the total required periods don't exceed the available slots in the timetable grid.
• Relax non-essential hard constraints: Convert preferences to soft constraints. Does English really have to be in the morning, or is it just preferred?
• Check room bottlenecks: If you have 5 science classes but only 2 labs, the hard room constraint may be impossible to satisfy.
• Reduce double-period requirements: Double periods consume more scheduling flexibility. Consider making some optional.

• Hard constraints (7): No teacher clash, no class clash, no room clash, teacher availability for 5 part-time teachers, lab rooms for science, required periods per subject, PE only on the ground.
• Soft constraints (6): Max 5 periods/day per teacher, max 3 consecutive periods, even distribution across days, core subjects before lunch, minimize teacher gaps, double periods for labs.
• Result: The AI generates a timetable in under 2 minutes, satisfying all hard constraints and 94% of soft constraints. The 6% soft violations are minor (e.g., one teacher has 4 consecutive periods on Thursday).

Want to see how constraints work in practice? Sign up for TimetableMaster free and experiment with different constraint configurations to find the perfect balance for your school.