Class Schedule Builder: A Timetable Without Clashes or Guesswork

How it is done today

Most coaching centres, training institutes and skill academies build the term timetable in a spreadsheet grid, once, before the term begins. It is printed, stuck on a wall, and then modified by hand as faculty change, batches fill and rooms are reallocated. Within a month the wall copy and the working reality have diverged.

The builder is not an attempt to automate judgement. Deciding who teaches what is a human decision. The work worth systematising is the checking: whether a slot is free, whether a room is big enough, how many sessions a batch has actually received, and who needs to be told when something moves.

Four record types, each with a small set of fields, related to one another.

• Batch code and course — the identity students and parents will use.
• Batch start date and total sessions — the two inputs behind a promised end date.
• Capacity, enrolled and waitlisted — the numbers a counsellor needs mid-conversation.
• Mode — in person, online or hybrid, since room constraints only apply to one of them.
• Faculty, subjects and availability — days, time bands and a weekly hour limit.
• Alternate faculty — named in advance, because absence is not an unusual event.
• Room or lab with capacity — including equipment where a session depends on it.
• Session day, start and end time — the slot itself, stored as real times.
• Session status — planned, delivered, cancelled, rescheduled, makeup.
• Sessions delivered and owed — derived, and the honest measure of progress.
• Attendance owner — who marks it, so it is marked.
• Fee status flag — visible next to enrolment, without duplicating the fee ledger.

Illustrative example only. The grid below shows the structure of a schedule rather than a timetable from any institute.

Read down the faculty and room columns for the same slot. That single check catches most timetable errors before they become an incident.

A single centre with six batches can survive on a printed grid and a good memory. Three centres with thirty batches cannot, because the person holding the memory is also the constraint on every change.

In a CRM the batch is a record that a counsellor, a faculty member and an administrator each see differently. Enquiries link to the batch they are being sold, sessions accumulate a delivery history, changes notify the batch, and end-of-term reporting comes out of the same data that ran the term.

Planning in weeks rather than sessions. Holidays and cancellations make week counts a fiction by the second month.

Leaving capacity out of the schedule. Enrolment then outgrows the room, and the fix costs more than the check.

Deleting cancelled sessions. The obligation to deliver them disappears with the row.

Announcing changes from personal numbers. The message history scatters, and so does the accountability.

Continue with WhatsApp CRM, lead management software, sales automation, CRM versus Excel, use cases, and the tools library.