Registers, fee slips and guardian calls everywhere? One system for your coaching centre

Admission forms are in a file, monthly fees are in a receipt book, attendance is on paper, and exam marks sit in someone's Excel sheet. Guardians call to ask whether their child came to class, how much is due and when results will be out. At the end of the month nobody is quite sure who has not paid. As you add batches or a second branch, the paperwork grows faster than the centre.

The answer is one system in which each student has one record, and admissions, fees, attendance and results all attach to it.

What the system should hold

• Students and guardians: name, class, school or college, guardian's name and phone number.
• Batches and teachers: subject, time, room and teacher for each batch.
• Fees: admission fee, monthly fee, exam fee, discounts and scholarships, and what is still due.
• Attendance: taken per class, per batch.
• Exams and results: marks for each test, with a simple view of progress over time.
• Notices: class changes, holidays, exam dates and dues, sent to guardians.

How the pieces connect

1. An admission form, at the desk or online, creates the student's record and assigns a batch.
2. The student's fee schedule is created automatically from your fee rules.
3. Each payment is recorded with a receipt, whether cash, bKash or Nagad. For mobile payments, staff note the transaction ID, or a licensed payment gateway records it for you.
4. Teachers take attendance on a phone in a minute at the start of class.
5. After each exam, marks are entered once and results are calculated.
6. Guardians get short SMS or WhatsApp messages about absence, dues and results.
7. You see one owner's view: dues by batch, attendance patterns and the month's collection.

Ready-made software or a custom build

Ready-made coaching software can get you running quickly and is worth trying first if your rules are fairly standard. A custom system makes sense when your fee rules, batch structure or reports do not fit, or when you run several branches and want one view across them. Before choosing either, check:

• Can it handle your real fee rules, such as sibling discounts, part payments and scholarships?
• Does attendance still work on a weak mobile connection or during a power cut, and sync later?
• Can each teacher see only their own batches?
• Can you export all your data whenever you want?
• Can messages to guardians go out in Bangla?

Mistakes to avoid

• Trying to move years of old records on day one. Start with current students.
• Building every feature before teachers have used the basics.
• Not checking guardian phone numbers, so messages reach the wrong people.
• One shared login for all staff, so nobody knows who changed a fee record.
• Publishing results with names and phone numbers for anyone to see. Many of your students are children; keep their data private and share results only with the student and their guardian.
• Keeping no backup of the system's data.

What you can do and where an expert helps

You can write down your fee rules, list batches and teachers, clean up the student list and decide what guardians should receive. A developer builds or configures the system, sets up messaging, payment records, user roles and backups, and trains your staff. This is part of the software and website development work I take on. I usually begin by sitting with whoever handles fees, because that is where most of the confusion lives.

The smallest useful first step

Pick one batch. For one month, keep its students, fees and attendance in a single shared spreadsheet, one row per student, and note every question guardians ask. That month shows what your system really needs to do. When you are ready to build it, get in touch.