Paying coaching institute staff: per-hour, per-student and fixed salary models

Teacher pay is the largest cost in most coaching institutes and the least systematised. A typical institute runs three models at once — a couple of full-time teachers on fixed salaries, visiting faculty on hourly rates, and someone on a per-student share — and calculates all three by hand on the last day of the month.

Each model behaves differently as you grow. Choosing badly is expensive; changing later is awkward.

Fixed monthly salary

The same amount regardless of batches taught or students enrolled.

• Works when the teacher is core to the institute, teaches a full load, and you want them invested rather than counting hours.
• Cost behaviour: fixed. Excellent when batches are full, painful in a thin season — this is the model that hurts if admissions dip.
• Watch for: a teacher whose load quietly halves while pay does not. Without per-batch costing you will not notice.

Per-hour or per-session

Paid for sessions actually delivered. The default for visiting faculty.

• Works when a teacher covers one or two batches, or a specialist subject you cannot fill full-time.
• Cost behaviour: variable, and it tracks delivery — the safest model when you are new or seasonal.
• Watch for: disputes over cancelled sessions. Decide in advance who bears a class cancelled by the institute versus by the teacher, and write it down. This is the single most common payroll argument in coaching.
• Also watch: hours claimed versus sessions actually held. If nobody records delivery against the timetable, you are paying from memory.

Per-student share

A fixed amount per enrolled student, or a percentage of the batch fee.

• Works when the teacher genuinely drives admissions — parents come for them by name.
• Cost behaviour: scales with revenue, which makes it the safest model on paper and the most volatile for the teacher.
• Watch for: what happens with mid-course joiners, leavers and unpaid fees. Does the teacher earn on a student who enrolled but never paid? Answer it before it happens, not during a disagreement.
• Also watch: it can create pressure to over-fill batches past the size the teaching quality supports.

Where payroll quietly goes wrong

The failures are boringly consistent across institutes:

• Sessions paid from memory. If delivery is not recorded against the timetable, the month-end calculation is a negotiation.
• Cancellations never resolved. An owed session that is neither delivered nor deducted just accumulates as a disagreement.
• Per-student payouts computed on enrolment, not collection. You pay out on a fee you have not received. Over a season this is a real hole — the fix is to compute on collections, or explicitly decide to carry the risk.
• Advances handed out and forgotten. Especially in cash. Every advance should reduce a specific future payout in writing.
• Teacher cost never allocated to a batch. Which makes batch profitability guesswork — see batch-wise profit & loss.

Statutory obligations

Once you employ staff rather than engaging visiting faculty, obligations follow — TDS on salaries above the applicable limit, and PF and ESI once you cross the employee-count thresholds. The line between an employee and an independent contractor is about how the work is controlled, not what the agreement is titled, and getting it wrong is expensive retroactively.

This is genuinely a question for a CA rather than an article. What matters operationally is that you keep records clean enough to answer it: written engagement terms, payments through the bank, and a payout record per person per month.

What to fix first

In order of return:

1. Record sessions delivered against the timetable, automatically. Everything else depends on it.
2. Write down the cancellation rule. One line, agreed once, ends a recurring argument.
3. Pay through the bank. Cash payroll is the most common reason an institute cannot reconstruct its own costs.
4. Allocate teacher cost to batches, so you can see which batches actually earn.

Teacher cost and room time are the two inputs that decide whether a batch is worth running. Once payroll is recorded per batch, the P&L in batch-wise profit & loss becomes genuinely usable rather than an estimate.