Staggered lunch: how to timetable split lunch breaks
4 min read
If your canteen seats 300 and your school has 1,200 students, lunch is a timetabling problem. Most schools in that position split lunch into two or more sittings. Done well, it shortens queues, calms corridors and frees up dining space. Done badly, it creates clashes, lost teaching time and staff who never get a break.
Common models
Fixed sittings by year group
The simplest model. Years 7 to 9 eat first, Years 10 to 13 eat second, and the timetable for each half of the school is built around its lunch slot.
It's easy to explain and easy to supervise. The downside is rigidity: any lesson that mixes year groups, such as a combined sixth form class or a vertical tutor group, can't happen across the lunch boundary.
Teaching through lunch
The school day has a longer middle section. While one half of the school eats, the other half is taught, then they swap. This keeps total teaching time the same but means one lesson for each group is split around, or moved by, lunch.
It makes the best use of space, but it's the hardest to timetable, because a teacher with classes in both halves needs to be free at some point for their own lunch.
Flexible sittings by lesson
Rather than fixing lunch by year group, lunch falls wherever each group's timetable leaves a gap in the middle of the day, within a lunch window. This spreads numbers most evenly, but it needs software to do well, and it can be harder to communicate to students and parents.
Decide what you're balancing
Before choosing, be clear what matters most for your site:
- Dining capacity: how many students the canteen and outdoor space can take at once
- Serving time: how long it takes to serve a sitting, which sets a minimum length for each one
- Supervision: how many staff are needed on duty for each sitting
- Movement: whether corridors near the canteen become a bottleneck during changeover
Write down the maximum number of students you want at lunch at once. That single number turns a vague goal ("less crowded lunch") into something you can check every version of the timetable against.
The knock-on effects
Staggering lunch touches the rest of the timetable in ways that are easy to miss:
- Teacher lunch breaks. In England, teachers are entitled to a reasonable break between sessions. A teacher with lessons on both sides of a split must still get one.
- Shared staff. A teacher who teaches both lower and upper school needs their lessons arranged so the lunch boundary doesn't strand them.
- Practical rooms. Labs and workshops may need clean-up time if a lesson finishes just before a lunch sitting.
- Clubs and interventions. Lunchtime clubs need students and staff free at the same time, which is harder when lunch is split.
- Bells. More sittings means more bells. Check your bell system can handle the pattern before committing.
Making it a soft goal, not a hard rule
It's tempting to make "no more than 400 at lunch at once" a hard rule. Often it works better as a strong preference. As a hard rule, it can make the timetable impossible when combined with everything else. As a goal, the timetable keeps numbers as low as it can while meeting every genuinely hard rule, and you can see how close it got.
That's the same principle we cover in hard and soft constraints: be strict about which rules really can't bend.
Check it before you publish
Once the timetable is built, look at lunch in three ways:
- Peak numbers at each lunch slot, against your capacity
- Each teacher's day, to confirm everyone has a break
- A few sample student days from each year group, to check lunch falls at a sensible time and doesn't create long gaps either side
How Timez helps
Staggered lunch is one of the goals Timez works towards. Within your school day, it spreads lunch breaks so canteens and corridors don't jam, while meeting every hard rule. Because each project keeps its own settings, you can compare lunch arrangements side by side before you decide.
For what else to check before you sign a timetable off, see how to build a school timetable.