Timetable and batch scheduling for coaching institutes: avoiding the 6pm clash

Every coaching institute has the same structural problem: school ends at 3pm, dinner is at 9pm, and every parent wants their child taught in the six hours between. Rooms sit empty all morning and three batches want the same room at 6pm.

You cannot fix that by wanting it fixed. You can stop it turning into a weekly crisis.

Schedule the scarce thing, not the convenient thing

Most timetables are built around student preference, which is why they collapse. Build around whichever resource is genuinely scarcest in your institute — usually one of three:

• Rooms, if you have fewer rooms than simultaneous batches at peak.
• Teachers, if one Physics teacher covers four batches. This is the most common real constraint and the most often ignored.
• Peak hours, if both of the above are fine but everyone wants 5pm–7pm.

Identify yours, timetable that first, and let everything else arrange itself around it. A timetable built around the wrong constraint looks fine on paper and breaks in week two.

Spread demand instead of fighting it

Some peak pressure is genuinely movable, and shifting even one batch out of the crush pays for itself:

• Droppers and repeaters can take mornings. They have no school. This is the single biggest lever most institutes have and the one they use least.
• Weekend long sessions can absorb an entire subject that otherwise needs two weekday evening slots.
• Staggered start times — 4:45 and 5:15 rather than both at 5:00 — halve the arrival crush at the door and at attendance.

Leave deliberate slack

A timetable with every room full at every peak hour has no capacity to absorb anything going wrong, and something goes wrong most weeks. One free room and one free teacher slot at peak is not waste — it is what lets you move a class when a teacher is ill instead of cancelling it.

Institutes that run at theoretical 100% utilisation spend their week rescheduling. The slack costs less than the chaos.

What actually goes wrong, and the fix

• A teacher double-booked across batches. Almost always because the timetable lives in one person's head or a spreadsheet only they edit. Fix: one shared source of truth that shows teacher-wise, not just batch-wise.
• Two batches sent to the same room. Fix: schedule rooms explicitly rather than assuming.
• Students not told about a change. The most damaging one, because it wastes a parent's trip. Fix: schedule changes should notify the batch automatically — see WhatsApp automation.
• A cancelled class never rescheduled. Fix: track owed sessions per batch. Parents remember what you owe even when the institute does not.

When a teacher calls in sick

This is the stress test. Decide the policy once, in advance, so it is not improvised at 4pm:

• Can another teacher cover? Only if someone maintains a current view of who is free at which slot.
• Can it swap with a later topic? Often yes, and less disruptive than cancelling.
• If cancelling, notify before students travel. The difference between a minor annoyance and a complaint is roughly two hours' notice.
• Log the owed session immediately. Not in someone's memory.

Where scheduling meets money

A batch running at half capacity in a peak slot is occupying your scarcest resource while contributing least. That is a scheduling decision with a financial consequence, and you cannot see it without per-batch numbers — which is what batch-wise profit & loss is for. Sometimes the right answer is merging two thin batches rather than finding a third room.

Once the schedule holds, the next thing that breaks at 6pm is attendance — covered in registers, biometric or QR.