Worked scenario
Working out what to pay visiting faculty takes a day and still gets disputed
Per-session pay is simple arithmetic on data nobody captured cleanly, which is why it consumes a day and produces arguments.
3 min read
Visiting faculty are paid for sessions taken. The timetable says what was planned. What actually happened includes substitutions, cancelled sessions, doubled-up classes and one week when the batch was on a break.
Three sources, no truth
The timetable, the attendance register and somebody's WhatsApp messages about who covered what. Reconciling them at month end is slow, and where they disagree the institute usually pays what is claimed, because it cannot prove otherwise.
Record the delivery, not the plan
The fix is marking a session as delivered, by whom, at the time it happens — a few seconds by whoever is running the batch. Everything else follows from that one record.
Why a checkable statement matters
Faculty disputes are rarely about money in principle. They are about not being able to verify a number handed to them. A statement listing sessions and dates ends most of them before they start, and costs nothing once the delivery record exists.
What changes
- Sessions recorded as delivered, including substitutions, at the time
- Cancellations distinguished from no-shows, because they pay differently
- Faculty payable calculated from the record rather than reconstructed
- A statement the faculty member can check themselves
Questions about anything here, or a situation this does not cover? contact@anantatechhub.com

