Databus Logo
Blog Login →
The Faculty-Staffing Playbook for Coaching Academic Heads

Half the faculty are paid per class, half are salaried, and a substitute covered a batch on Tuesday. Who's owed what at month-end?

This is the playbook that keeps a mixed coaching roster straight — who's teaching which batch, who's on leave, who covered a substitute slot, and what each tutor is owed this month. Coaching staff HR, not school payroll; staff pay, not student fees.

For academic heads & centre directors · visiting + full-time rosters · leave & substitute cover · classes-taken as a fact, not a score.

See a month-end roster →
In plain English

Coaching faculty staffing is how an academic head runs a mixed roster of visiting tutors paid per class and salaried full-time faculty — knowing who teaches which batch, who's on leave, who covered a substitute slot, and what each tutor is owed this month. This page is the staffing playbook for that outcome; the underlying pay-calculation tool — per-lecture / per-hour / salaried computation, attendance, payslips — is the tutor-management feature. The roster reads from the batch timetable. K-12 school staff payroll (PF, ESI, TDS) is a separate SchoolDeck solution; student fees — the opposite money flow — are fee-finance. TutorDesk computes what's owed; the institute pays from its own account.

Visiting + salaried
one mixed roster
not two systems
Leave → cover
no batch left
without a teacher
Classes-taken
a factual count
never a staff score
Computes, not pays
institute pays from
its own account
A real month-end · CA/CS coaching · mixed faculty of 7 · the substitute Tuesday

One roster, visiting and salaried side by side — and the substitute who got credited.

Mr Bose runs a CA/CS coaching centre with three salaried faculty and four visiting tutors. This month one visiting tutor took two days' leave, and a colleague covered a Tuesday batch. Here's the month-end staffing statement — and the line that makes the mix honest.

Faculty staffing statement · CA/CS centre · month-end · 7 faculty Computed, for the institute to pay
TutorTypeBasis this monthOwed (₹)
Ms SenguptaFull-timeSalaried · full month, no adjustments
Mr Bose (self)Full-timeSalaried · academic head
Ms DuttaFull-timeSalaried · 1 LOP day adjusted
Mr IyerVisiting22 classes taken · per-class rateby rate
Ms NairVisiting18 classes taken (2 days' leave)by rate
Mr KhanVisiting20 classes + 1 substitute cover (Tue)by rate
Ms PillaiVisiting15 classes takenby rate
Whole rosterMixed3 salaried + 4 visiting · 1 leave, 1 cover, all accounted→ to pay tool
The line that matters is Mr Khan's Tuesday cover. Ms Nair took leave, Mr Khan stood in front of her batch, and the system credited the class to him — so the person who actually taught is the one paid for it, and Ms Nair's count reflects the leave. No rupee figures are invented here; the per-class rates and the final payslip are computed in the pay tool, and the institute pays from its own account.
Where mixed coaching faculty goes wrong

Four ways a coaching roster costs money and goodwill.

Two systems, one workforce

Salaried staff in one spreadsheet, visiting tutors' classes scrawled in a diary. At month-end nobody can see the whole teaching workforce or its real cost in one place, so both get errors.

The uncredited substitute

A tutor covers a colleague's batch at short notice and it's never recorded — so the absent tutor is paid for a class they didn't take, and the one who actually taught isn't. Do that twice and you've lost a good visiting tutor.

The batch with no teacher

A tutor's leave isn't tracked against the roster, so on the day, a batch turns up and there's nobody to teach them. Parents notice an empty class faster than almost anything else.

Pay disputes from a black box

A visiting tutor is told a figure with no breakdown of which classes it covers. Without a transparent count they can check, every month-end becomes an argument instead of a payment.

The playbook

Five steps, run every month.

1

Build the roster across batches

Lay out which tutor teaches which batch and subject across the week — visiting tutors paid per class alongside salaried full-time faculty — reading from the batch timetable, so the academic head sees the whole teaching schedule and any gap in one place.

2

Record leave and arrange cover

When a tutor applies for leave, it's recorded against the roster and a substitute is assigned to the affected batches — so no batch is left without a teacher, and the cover is logged so the substitute's class is counted.

3

Keep classes-taken as a factual record

Each tutor's classes actually taken — including substitute cover — accumulates as a transparent, factual record the tutor can see, not a composite quality score or a ranking of staff. It's a count of work done, used for pay and planning, not a judgement.

4

Produce each tutor's monthly statement

At month-end, produce a clear statement per tutor — visiting tutors by classes taken at their per-class rate, salaried faculty by fixed pay with any adjustments — so everyone can see how the figure was reached before it's paid.

5

Hand the computation to the pay tool

The detailed per-lecture, per-hour and salaried computation and the payslip are handled by the tutor-management tool. TutorDesk computes what's owed; the institute pays the salaries from its own account. TutorDesk does not hold or disburse the money.

The honest frame this runs inside

A factual count, a transparent statement, no black box.

Classes-taken is a fact, not a verdict

The platform records classes actually taken as a count of work done. It does not produce a composite "tutor quality score" or rank staff against each other — a teacher's effectiveness is a human conversation informed by data, never an automated label.

TutorDesk computes, the institute pays

The platform calculates what each tutor is owed and produces the statement; it does not hold or disburse salary funds. The institute pays its faculty from its own account. TutorDesk is the record and the calculation, not a payroll bank.

DPDP Act 2023 · Section 6

Staff records, including any identity documents collected for onboarding, are handled under DPDP Act 2023 Section 6 with consent. Staff data is kept for the staffing purpose, with access limited to those who manage the roster and pay.

Framework references: DPDP Act 2023 §6 (staff data consent). This page is coaching faculty staffing — distinct from K-12 statutory payroll (PF/ESI/TDS), which is the SchoolDeck staff-payroll solution. TutorDesk records and computes faculty pay; it does not hold or disburse salary funds. Figures shown are illustrative; per-class rates and payslips are set and computed in the tutor-management feature.

What this playbook owns · what it deliberately doesn't

Staffing playbook ≠ pay tool ≠ school payroll ≠ student fees.
This page owns the roster; the calc, the statutory payroll, and the fees live elsewhere.

TutorDesk keeps the staffing outcome and the pay-calculation tool as separate pages on purpose, and keeps coaching staff HR distinct from both school statutory payroll and student fees — so each ranks for its own job.

This page owns

  • The mixed-roster staffing playbook — visiting + salaried faculty on one view.
  • Leave + substitute-cover so no batch is left without a teacher.
  • Classes-taken as a factual record (not a staff score or ranking).
  • The per-tutor monthly staffing statement the academic head reviews.
  • The coaching-specific visiting-plus-salaried staffing model.

This page defers to

  • The pay-calculation tool — per-lecture/per-hour/salaried computation, attendance capture, payslip generation — lives in Tutor Management (feature). This page is the playbook; that page is the calc tool.
  • The batch timetable + clash engine the roster reads from — lives in Scheduling.
  • K-12 school staff payroll — PF, ESI, TDS, statutory salary processing — is a different problem in SchoolDeck Staff Payroll & HR. This page is coaching faculty only.
  • Student fees — the opposite money flow, what families owe the institute — lives in Fee & Finance. Staff pay and student fees are deliberately separate.
Three staffing realities in Indian coaching

The same playbook, three kinds of institute.

The roster is the same shape; the mix of visiting and salaried shifts with the institute.

Mostly visiting faculty

A subject-expert panel

A centre that runs on visiting subject experts paid per class needs the classes-taken count to be airtight, because almost the entire pay bill is per-class. Substitute cover and leave tracking are the difference between a clean month-end and a dispute.

Mostly salaried faculty

A full-time teaching team

An institute with a salaried core team uses the playbook mostly for leave, cover and the occasional visiting specialist — the value is in never having an uncovered batch and in a clean record of who taught what when a query comes up.

Multi-branch institute

Faculty across centres

An academic head across branches sees each branch's roster and the tutors who teach at more than one, so a visiting tutor's classes across two centres add up correctly into one monthly statement instead of two partial ones.

From the field

Kolkata, West Bengal · CA/CS coaching · 3 salaried + 4 visiting faculty.

"I run a CA/CS coaching centre, and my staffing is a mix — three of us are full-time and salaried, and we bring in four visiting faculty paid by the class. For years the month-end was a headache, because the salaried side lived in one place and the visiting tutors' classes lived in a diary, and the two never reconciled cleanly. The worst was substitutes: someone would cover a batch at short notice and it just wouldn't get written down, so the wrong person got paid and a good tutor felt cheated. Now it's one roster. When Nair took leave last month and Khan covered her Tuesday batch, the system credited the class to Khan — he taught it, he's paid for it, simple. What I value is that it doesn't pretend to score my teachers; it just tells me, truthfully, who taught how many classes. The actual pay calculation and the payslip sit in the tutor tool, and I pay everyone from our own account — the software just gets the numbers right so I'm not arguing about them."
Subhomoy Bose Academic Head · CA/CS coaching centre · Bhowanipore, Kolkata-700025, West Bengal
Mixed roster (3 salaried + 4 visiting) · leave & substitute-cover tracking · classes-taken as a factual record (§14.21) · computation handed to the tutor-management tool, paid from the institute's own account
Quick answers

Faculty staffing, asked and answered.

What every academic head and centre director asks before they change how faculty are staffed and paid.

What is coaching faculty staffing management?
It is how a coaching institute's academic head runs a mixed roster of visiting tutors paid per class and salaried full-time faculty — knowing who teaches which batch, who is on leave, who covered a substitute slot, and what each tutor is owed this month. This solution page is the staffing playbook for that buyer outcome; the underlying pay-calculation tool that computes per-lecture, per-hour or salaried pay and generates payslips is the separate TutorDesk tutor-management feature.
How is this different from the tutor-management feature?
The tutor-management feature is the tool — the per-lecture, per-hour and salaried pay computation, attendance capture, leave records and payslip generation. This solution page is the playbook — how an academic head actually runs a mixed faculty across a month: building the roster, arranging substitute cover, reading each tutor's classes-taken, and producing the monthly statement. If you want to see how pay is calculated, read the tutor-management feature; if you are the academic head responsible for the roster, this is your page.
Does it handle both visiting and full-time faculty?
Yes — that mix is the whole point. Many coaching institutes run a few salaried full-time faculty alongside a larger pool of visiting tutors paid per class, and the hard part is holding both on one roster. The playbook keeps visiting tutors (counted by classes actually taken at a per-class rate) and salaried staff (fixed pay with adjustments) side by side, so the academic head sees the entire teaching workforce and its cost in one view rather than two separate systems.
How does substitute cover work?
When a tutor takes leave, the affected batches are flagged and a substitute is assigned so no batch is left without a teacher. The substitute's class is logged as a class they actually took, so it counts towards their pay, and the original tutor's leave is recorded against the roster. The aim is that a last-minute absence becomes a recorded, covered slot rather than a scramble — and that the person who actually stood in front of the batch is the one credited for it.
Does it score or rank teachers?
No — and that is deliberate. The page keeps each tutor's classes-taken as a transparent factual record — a count of work done — not a composite "quality score" or a ranking of staff against one another. A factual count is useful for pay and for planning cover; a black-box score that purports to judge a teacher's quality is not something this page produces. If an institute wants to discuss a tutor's effectiveness, that is a human conversation informed by real data, not an automated verdict.
Is this for school staff payroll too?
No. This page is for coaching and tuition faculty — the visiting-plus-salaried mix a coaching institute runs. K-12 school staff payroll, with statutory PF, ESI and TDS salary processing run from biometric attendance, is a separate SchoolDeck staff-payroll-and-HR solution. The two are kept apart because a coaching institute's per-class visiting-tutor model and a school's full statutory payroll are genuinely different staffing problems, and conflating them helps neither.
Does TutorDesk pay the salaries or hold the money?
No. TutorDesk computes what each tutor is owed and produces a clear statement, but it does not hold or disburse salary funds. The institute pays its faculty from its own account, using the statement as the basis. TutorDesk is the record and the calculation, not a payroll bank or a money-routing service. Keeping that explicit matters: the platform's job is to make the figure correct and transparent, not to sit between the institute and its teachers' pay.
How is staff pay different from student fees here?
They are two opposite money flows and two different pages. This page is about money the institute owes its faculty — staff pay. Student fees, the money families owe the institute, are the separate TutorDesk fee-finance solution. They are kept distinct because the workflows, the people, and the compliance are different: faculty pay is a staffing and HR matter, while fee collection is a receivables and cash-flow matter. Conflating "pay" and "fees" is exactly the kind of blur that confuses an institute's books.
How does it connect to the timetable?
The roster reads from the batch timetable — which tutor is scheduled for which batch and slot — so staffing and scheduling stay consistent. The timetable and its clash-detection engine are owned by the scheduling feature; this page uses that schedule as the basis for the roster, leave and cover. So a timetable change flows through to staffing, and the academic head is not maintaining the teaching schedule twice in two places.

Stop reconciling a diary against a spreadsheet.
Run one honest faculty roster.

We'll walk you through a mixed visiting-plus-salaried roster, leave and substitute cover, the classes-taken record, and the month-end statement — in a demo built for your institute's faculty model.

Book the Faculty Staffing Demo →