Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Education Technology 6 min read

Multi-branch coaching centre operations: a step-by-step guide

A practical sequence for standardising admissions, fees, batches, attendance and reporting across coaching centre branches without losing local flexibility.

E
EncryptTechBD · 0 comments
Student taking notes beside an open laptop
Photo: Startup Stock Photos / StockSnap

A coaching centre with one branch runs on memory and a WhatsApp group. A centre with four branches runs on the same habits until the first month-end, when the fees collected at one branch do not match the receipts, a teacher has been scheduled at two locations at the same time, and the owner cannot answer a simple question: how many students are actually active this month?

Multi-branch operations are not a bigger version of single-branch operations. They need a shared definition of a student, a batch, a fee and a result, plus a reporting rhythm that lets each branch run locally without inventing its own rules. This guide sets out the sequence, the evidence to collect and the mistakes that cost the most time.

Prerequisites

  • A branch list with an owner for each. A branch without a named manager will not adopt a standard process.
  • One course and fee catalogue. If every branch prices the same course differently, consolidation starts with a commercial decision, not software.
  • A student identifier that survives a branch transfer. Phone number alone is not an identifier; families share numbers and students change them.
  • Connectivity and devices. Decide which tasks must work offline, and test the chosen tools on the phones and laptops the branches actually use.
  • A data protection position. Student records include guardians' contact details, attendance and results. The Personal Data Protection Act, 2026 makes it sensible to document why each field is collected, who can see it and how long it is kept.

Step 1: define the operating model

Write down what is decided centrally and what is decided at branch level. Central: course catalogue, fee structure, admission rules, result publication, branding and reporting definitions. Branch: class timing, teacher allocation within the approved pool, local events and parent meetings. Without this split, every branch becomes a separate business and consolidation becomes a negotiation.

Step 2: build one course and batch catalogue

Give every course a code, a level, a duration, a fee plan and a syllabus version. A batch is then a course plus a branch, a schedule, a teacher and a start date. This sounds bureaucratic until you need to compare performance across branches; then it is the only way to know that "HSC Physics Batch A" means the same thing in Dhaka and Chattogram. For school and higher secondary courses, record which national curriculum version the syllabus follows, because a batch that starts before a revision and one that starts after it are not comparable.

Step 3: standardise admissions

Use one admission form, one document checklist and one approval step. Capture the student, guardian, course, batch, fee plan and consent at the point of admission. Issue a student ID immediately. If admissions are still paper-based, photograph the form and enter the record the same day; a backlog of paper is where duplicate students and missed fees begin.

Step 4: centralise fee collection and receipts

Fees arrive as cash, bKash, Nagad, bank transfer and occasionally a cheque. Define which methods each branch accepts, who can collect, and how a receipt is issued. Reconcile daily, not monthly, and separate the person who collects from the person who confirms the bank or wallet settlement. A shared spreadsheet is better than nothing, but a receipt number that is unique across branches is the minimum control.

Step 5: design batches and teacher allocation

Build a weekly timetable with room, teacher and batch, then check for clashes across branches before publishing. Teachers who travel between branches need travel time in the schedule. Publish the timetable to students and guardians through one channel, and keep a change log so a room change does not become five different WhatsApp messages.

Step 6: run attendance and make-up classes

Attendance should take less than two minutes per batch. Mark it at the start of class on a phone or tablet, and define what happens for late arrivals, absences and make-up classes. Attendance data is only useful if it is reviewed: a student at risk of dropping out often shows a pattern of absences before the fee reminder.

Step 7: control exams, marks and results

Standardise the exam schedule, mark entry and moderation. Decide who can enter marks, who can change them and who approves publication. Publish results through a consistent channel, and keep a record of the version that was released. Parents remember a wrong mark longer than they remember a good result.

Step 8: make parent communication predictable

Use approved templates for admission confirmation, fee reminders, attendance concerns, exam schedules and results. WhatsApp Business can handle routine messages, but the templates must be reviewed and the opt-out respected. Keep a record of what was sent, to whom and when.

Step 9: set a branch reporting rhythm

Agree a short monthly pack: active students by course, new admissions, withdrawals, fee collection against dues, attendance rate, exam completion and teacher utilisation. One page per branch, defined the same way everywhere. The owner reviews exceptions, not every row.

Step 10: roll out in waves

Pilot in one branch for a full admission and fee cycle. Fix the process before adding the second branch. Then roll out one branch at a time with a named champion, a training session and a two-week support window. Do not switch off the old process until the new one has produced a complete month-end.

Evidence checklist

  • Signed operating model and branch decision rights.
  • Course, batch and fee catalogue with version history.
  • Admission form, document checklist and student ID register.
  • Daily collection report matched to bank and wallet settlements.
  • Weekly timetable with clash checks and a change log.
  • Attendance and exam records for a complete month.
  • Monthly branch pack reviewed by the owner.

Common mistakes

  • Letting each branch keep its own course names and fee plans.
  • Collecting fees without a unique receipt number.
  • Scheduling teachers without travel time between branches.
  • Publishing results before moderation is complete.
  • Buying software before agreeing the operating model.
  • Giving every branch manager full access to every student record.
  • Treating WhatsApp as the system of record.

Metrics to report

  • Active students by branch and course.
  • Fee collection rate and days of dues outstanding.
  • Attendance rate by batch, with the lowest five named.
  • Student withdrawal rate and reasons.
  • Teacher utilisation and timetable clashes.
  • Time to publish results after the last exam.

Where this fits in our work

We build coaching centre operating systems under Education Operations, covering admissions, batches, fees and parent communication. The pricing page explains how a branch rollout is scoped. For the data protection side, read how student data privacy obligations change year by year.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes