The rule for catching batch conflicts (same teacher/room/student in two batches at once): write the three constraints — teacher, room, student — in separate matrices and reconcile before the week starts. Batch routines on paper do not reveal conflicts; they surface when a student has been sitting and waiting.

What to verify: identifying teacher, room and time constraints

Keep these fields in the week matrix:

Constraint Question Conflict example
Teacher same teacher, same slot, two batches? Sir-A: Physics-A and Chemistry-B both at 7
Room same room, same slot, two batches? Room-2 for two batches at 7
Student same student, same slot, two subjects? Student-21 in Physics and Maths both at 7

The third is the most common — one student taking multiple courses is normal in coaching; the conflict is caught when the batch is built, while fixing it is still cheap.

A usable sample: the empty conflict matrix

Fill this table at week start:

Slot Batch Teacher Room Students Conflict flag
9 AM SSC-A Sir-1 Room-1 18 —
7 PM HSC-A Sir-1 Room-2 22 teacher ✓ (different slots)
7 PM SSC-B Sir-2 Room-2 15 room conflict

Reconcile the matrix and fill the last column — conflicts become visible before batches go live. With software, the system should warn at entry time — create a deliberate conflict in the demo to see.

Batch time conflicts: workflow steps and limitations

  1. Fill the matrix in one meeting before batches launch — later splitting becomes endless.
  2. On a conflict, three fixes: change slot, change room, change teacher — never on anyone’s assurance.
  3. Student-level conflicts are resolved with the guardian informed — what the student reports after sitting is not enough.
  4. Limitation: the matrix is not one-time — batches added or times changed mid-month require filling it again.

Time conflicts: questions to ask before your demo

  • Does the system warn at entry time?
  • Is the batch routine printable on one page?
  • Does a student’s routine auto-update after a batch change?

See the coaching page for routine and batch structure; the attendance module and attendance documentation for the roll-call connection.

Time conflicts FAQ

Is the matrix rebuilt weekly?

No — at the start, plus on any batch/time change. A quick reconciliation each week-start is a good habit anyway.

If the software lacks conflict warnings?

Keep the matrix running — the duty is the institution’s, not dumped on software. It also becomes a vendor-comparison score.

How common are student-level conflicts?

Very common among multi-course students — and they suffer the most; catching them saves them.