Running batches at a training institute

Ask an institute owner what they sell and they will say “courses”. Ask what they manage every day and the answer is “batches”. Confusing the two is the most common reason timetables, fees and attendance become tangled. This guide explains the difference, then covers scheduling and capacity in a way that works on paper or in software.

Course versus batch

A course is the reusable description of what you teach. It has a name, a syllabus split into modules or topics, a standard duration and usually a standard fee. A course has no dates. “Advanced Excel” is a course.

A batch is one scheduled run of a course. It has a start date, an end date, days and timings, a teacher, a room and a limit on the number of students. “Advanced Excel, weekday mornings, starting 4 November” is a batch. “Advanced Excel, Saturday evenings, starting 9 November” is a different batch of the same course.

Why keep them apart?

• You can run the same course many times without retyping the syllabus.
• Changing a batch’s timing does not alter the course.
• Fees, attendance and progress belong to a student’s place in a particular batch, not to the course in the abstract.

A student joins a batch; that link is the enrolment. Everything about a student’s journey, including what they owe, what they attended and how they are doing, hangs off the enrolment. If your records are a single flat list of “classes”, splitting it into these three ideas is the single best clean-up you can do. Our course catalog and enrollment pages describe how this looks in practice.

Designing your batches

Before you schedule anything, decide how you want to offer each course.

Choose a batch pattern

Common patterns at Indian training institutes include:

• Regular weekday batches, such as Monday to Friday, one hour a day.
• Weekend batches for working professionals.
• Fast-track batches with longer daily sessions over fewer weeks.
• Rolling or flexible batches where students can join at intervals.

Pick patterns that match who your students are. A school-going student and a working adult need different timings. Offer few patterns well, rather than many half-full ones.

Decide batch size

Capacity is a teaching-quality decision first and a room-size decision second. Practical courses, such as computer labs, are limited by the number of working systems, while theory classes are limited by comfortable seating and by how many students a teacher can follow. Write down a maximum for each course and batch. Two principles help:

1. Set a hard maximum. When the batch is full, new students go to the next batch instead of squeezing in.
2. Set a soft minimum. Decide in advance how many students make a batch viable, and by what date you will merge or postpone if it falls short.

Keeping a waiting list of interested students turns a full batch from a lost sale into the start of the next one. The admissions CRM can help you keep track of those interested leads and follow up when a seat opens.

Scheduling without clashes

A timetable is a set of constraints: a teacher cannot be in two places, a room cannot hold two batches and a student should not be booked into two overlapping batches. Clashes usually arrive through change, such as a teacher on leave or a batch moved, not through the original plan. Build habits that catch them.

A simple routine

1. Keep one master timetable. Whether it is a wall chart, a spreadsheet or software, there must be one place everyone trusts. Copies drift.
2. Check three things on every new batch: teacher availability, room or lab availability, and student overlap.
3. Record changes where everyone sees them. A verbal “class moved to 5 pm” that never reaches the master timetable is the source of most clashes.
4. Review the coming week every Friday. Look for batches starting, batches ending and any teacher leave.

Sessions and changes

Each batch is delivered as a series of sessions. Keep a light record of each one: date, time, topic and teacher. You will need it for attendance and for telling students what was covered. With Instione’s batch scheduling you set a weekly pattern and sessions are generated from it, one-off changes can be made to individual sessions, and clashes are flagged with conflict warnings. Calendar sync is not available yet.

Managing the life of a batch

Before it starts

• Confirm the teacher, room and material.
• Open enrolment, then close it when the batch is full or the start date passes.
• Collect the first instalment at enrolment so seats are committed.

While it runs

• Take attendance every session and review it weekly. Two or three absences in a row is the moment to call the student, not after a month.
• Track syllabus progress against the plan so a slipping batch is noticed early.
• Keep fee dues visible to whoever speaks to students, ideally the front desk.

When it ends

• Record completion and any assessment results.
• Issue certificates only after dues are cleared, if that is your policy. State this policy at admission.
• Ask for brief feedback from students. Their comments feed directly into the next batch’s timing and teacher choices.

Handling the awkward cases

A student wants to switch batches. Treat it as a transfer: end the old enrolment, create the new one, and carry the fees paid over rather than starting from zero. Keeping a record of the transfer avoids “where did my payment go” questions.

A student joins late. Decide your rule in advance. Some institutes allow late joiners within the first week with a catch-up plan; others only accept at the start. Either is fine if applied consistently.

A batch is oversubscribed. Offer the next batch, or open a second section if you have a teacher and room. Do not exceed the maximum, since quality drops and word of mouth suffers.

A teacher leaves mid-batch. Keep the syllabus and session records up to date so a replacement can pick up exactly where the last class stopped. This is a strong reason to keep records in a shared system instead of in one teacher’s notebook.

Running several branches

If you operate more than one centre, batches belong to a branch, but you can copy a course to another branch and publish later changes to it, so you describe each course once. Separate branch records also stop one centre’s staff from seeing or editing another’s students. See multi-branch for how this is handled, and student and staff management for who can see what.

A short checklist

• Courses describe what you teach; batches are dated runs; enrolments join students to batches.
• Set a hard maximum and a soft minimum for every batch.
• Keep one master timetable and record every change there.
• Check teacher, room and student overlap before confirming a batch.
• Review attendance weekly and follow up absences early.
• Keep a waiting list so a full batch feeds the next one.

If your current setup is registers and notebooks, our guide to moving your institute off paper shows how to bring batches across without disturbing classes that are already running.