Tutoring centre scheduling in India is a three-body problem: batches must respect school timings, teachers must not be double-booked, and parents must manage drop and pick-up around their own work. Add a board-exam batch that needs extra sessions in February, a shared classroom and one star faculty member, and most centres discover their timetable has been held together by the front desk's memory. This guide builds the grid properly -- classes, teachers, rooms and parent communication -- so collisions get designed out rather than negotiated daily.
Key takeaways
- Design the timetable from fixed constraints first -- school hours, teacher availability and room count -- before taking admissions.
- Slot batches by class and subject with explicit buffers, because back-to-back endings guarantee a crowded hallway every evening.
- Track teacher load openly so one star faculty member does not silently carry the whole centre.
- Solve the parent pick-up queue with staggered batch endings, not with more staff at the door.
- Send batch changes and attendance on WhatsApp -- parents in India read those messages within minutes.
Why batch timetables break at coaching centres
Most Indian coaching timetables fail for predictable reasons. They are built around ideal conditions -- a teacher who stays for six hours, classrooms that never need cleaning between batches, students who arrive exactly on time -- so the first real-world perturbation cascades. A batch that ends at 6:00 p.m. overlaps the next one's arrival at 6:00, parents waiting outside block the corridor, and the next class starts twelve minutes late every day for a year.
The deeper issue is that the timetable is treated as a product of demand rather than a design. Every new admission becomes a new batch squeezed wherever space appears, until the grid contains three batches sharing one teacher in the same hour. Centres that sit down once a term and design the grid from constraints -- rather than assembling it admission by admission -- report far fewer daily fires.
Build the batch grid from fixed constraints first
Start with what cannot move: school timings in your locality (which differ between morning and evening schools), teacher availability windows, room count and the board-exam calendar. Everything else -- new admissions, extra doubt sessions, trial classes -- arranges itself around those fixed blocks. The grid is a table of room x time x teacher, and no cell may hold two batches without an explicit, written exception.
- Fix batch endings on staggered times -- 5:30, 6:00, 6:30 -- so arrivals and departures never hit the corridor together.
- Build a 10-minute buffer between batches in the same room for cleaning, questions and the teacher's transition.
- Cap batch strength at a number you can actually teach, not a number that fills the room; overfull batches quietly become two bad batches.
- Reserve two floating slots per week for doubt sessions, retests and trial students instead of squeezing them into existing batches.
- Mark exam-season blocks in advance -- February and March need revision slots that exist before the panic, not during it.
- Publish the grid as the source of truth -- front desk, teachers and parents all read the same version.
Teacher load and backup planning
Indian coaching centres run on a small number of strong faculty members, and the timetable often reflects that reality badly: the star teacher ends up with ten batches, no preparation time and no substitute if they fall ill. Make teacher load visible as numbers -- hours per week, batches per person, gaps between batches -- and set a written ceiling. A teacher running six consecutive batches is one illness away from six cancelled classes.
Backup is a scheduling artifact, not a personality: each batch should have a named substitute from the same subject pool, briefed on the syllabus position, and the grid should show that assignment. Centres that add a floating teacher for two afternoons a week find that absences stop cascading into refunds and angry parent groups -- a single backup slot protects far more revenue than it costs.
- Publish weekly teaching hours per faculty member as a visible number, with a written ceiling.
- Give every batch a named subject-matter substitute, briefed on the current syllabus position.
- Keep one floating teacher slot free each evening for absence cover and doubt sessions.
- Protect preparation time on the grid; a teacher with no gap is a teacher producing tomorrow's class in tonight's hurry.
Parent pick-up and drop queues
The corridor outside a coaching centre at 6 p.m. is a queue problem, and staggered batch endings are its solution. When every batch ends simultaneously, thirty families converge on one door with two-wheelers double-parked across the lane; when endings are spaced fifteen minutes apart, arrivals and departures flow instead of collide. The other half of the fix is visibility: a whiteboard or a message showing when the batch actually ends today (doubt sessions routinely overrun) saves parents from waiting outside for a class that finished late.
For centres running weekend batches with heavy pick-up traffic, a numbered handover -- parent arrives, reception matches token to student -- prevents the worst outcome of all: a child released to the wrong person in a crowd. The same discipline applies at larger scale in coaching batch timings and parent pick-up queues.
Communicating batch changes to parents
Every timetable change currently travels by word of mouth through students, which guarantees distortion by the third retelling. A single WhatsApp broadcast channel per batch -- created at admission, with the teacher and centre admin in it -- carries schedule changes, festival holidays, exam-season slots and attendance notices with zero distortion. Indian parents read WhatsApp within minutes; SMS and printed notices do not get read at all.
Keep the channel one-directional by design: announcements from the centre, replies to a personal number, so the broadcast does not drown in twenty questions. Reminder discipline matters too -- a message the evening before a rescheduled class, and a short confirmation at admission of the batch timing, handle most of the daily confusion. The message structure that works is set out in WhatsApp reminders, adapted here from services to classes.
- One broadcast group per batch, created at admission with the teacher and centre admin inside.
- Announcements only in the group; replies routed to a personal number so the thread stays readable.
- Evening-before message for any rescheduled class, and a confirmation at admission of the batch timing.
What to review each term
Four numbers per term: batch utilisation (students attending against seats filled), teacher hours against the agreed ceiling, classes started more than five minutes late, and parent complaints about timing. Together they show whether the grid is serving the timetable or the timetable is serving habit. A batch at 40% utilisation and a teacher at 110% load tell you exactly what to change before next admissions.
Review before the term's timetable is published rather than after it breaks, because changing batch timings mid-term is the single most disruptive act a centre can perform. The scheduling logic transfers broadly from other batch-based businesses; the same principles run through queue management strategies for Indian businesses.
Frequently asked questions
How far in advance should a coaching centre publish its batch timetable?
A full term ahead, with exam-season blocks marked, and with two floating slots reserved for doubt sessions and trials. Publishing the grid as the single source of truth for front desk, teachers and parents eliminates the daily renegotiation that quietly eats teaching time in most Indian centres.
What is a good batch size for tuition classes?
The number you can actually teach, not the number that fits the room. Many Indian centres run effective batches of 15-30 depending on subject and level; beyond that, doubts go unanswered, weaker students disengage, and parents compare. Cap seats and keep a waiting list rather than diluting every batch.
How do I stop batch timings from overlapping at arrival and departure?
Stagger batch endings by 15 minutes and insert a 10-minute buffer between batches sharing a room. Arrivals and departures then flow instead of colliding in one corridor. Also publish the actual end time -- doubt sessions run late -- so parents stop gathering outside twenty minutes early.
Should teachers be allowed to take extra batches beyond a limit?
Set a written ceiling on weekly hours and publish teacher load as numbers. Star faculty carrying ten batches are one illness away from six cancelled classes, and exhausted teachers produce visible quality decline within a term. One floating substitute slot per week protects more revenue than it costs.
Which channel works best for communicating schedule changes to parents?
WhatsApp, as a one-directional broadcast per batch -- created at admission, announcements sent by the centre, replies routed to a personal number. Indian parents read WhatsApp messages within minutes, and a single controlled channel removes the telephone-game distortion that handwritten notices and student relays inevitably produce every term.
See SWIQ in action
SWIQ holds the batch grid, sends WhatsApp schedule notices and tracks attendance per batch -- so the timetable runs itself instead of running the front desk.
Launch the SWIQ web app