Attendance Software for Schools — Built for Staff, Not Students

A school runs two attendance systems that get called one thing. Student attendance is roll-call: a class register, period-wise marking, parent notification, minimum-attendance percentages, and reporting into a board or university format. Staff attendance is employment: who taught, who was on leave, who covered a substitution, what goes to payroll, and what an inspector sees in the register.

Workclave is the second one. It handles the staff side thoroughly and does not do student roll-call at all — no student records, no class rosters, no parent SMS, no LMS or ERP integration for learners. Most school ERPs are built the other way round: strong on student data, with staff attendance as a thin module bolted on. If your student system is already in place and the staff side is still a register on the principal's desk or a spreadsheet the accountant chases each month, that gap is what this fills.

The teaching day does not fit an office attendance model. A teacher's day is periods, not a single in-and-out: six teaching periods, a free period used for correction, an unplanned substitution for an absent colleague, exam invigilation, a parent-teacher meeting after hours. A biometric punch at the gate records two events and says nothing about any of it.

That is why the substitution ledger is usually a separate notebook, why extra-duty claims at term end are argued from memory, and why the monthly payroll input is reconstructed rather than recorded. The information existed all along; nothing captured it in a form anyone could total up.

A session is a block of work attached to what it was for. For a teacher that means the period, the substitution, the invigilation slot or the admin duty is its own record with its own start and end. The head of department or the principal approves them, and the approval is kept with the session permanently.

The consequence is that everything downstream is a total of records that already exist rather than a reconstruction. Substitutions taken this term are a number, not a recollection. Extra duty is evidenced when it is claimed. The register a state inspector asks for and the payroll input the accountant needs come from the same approved data, so they cannot disagree with each other.

• Teaching periods, substitutions, invigilation and admin duty recorded separately.
• Approval by the head of department or principal, recorded with the approver's name.
• Substitution and extra-duty totals available at any point in the term, not just at the end.
• One approved dataset behind the register and the payroll input.

A school year is term dates, a mid-term break, exam weeks, state-specific holidays, institution-specific days and the vacation period when administrative staff are working and teaching staff largely are not. Running that on a generic corporate calendar produces attendance percentages that are wrong for everyone, every term.

Calendars, holidays and leave types are configured per workspace here, so the working days are the institution's actual working days. Teaching staff, administrative staff, lab and library staff and housekeeping can follow different patterns in the same system without one of them being forced into the wrong shape, and each group's attendance percentage is computed against the calendar that actually applies to it.

A trust running three schools, a college with distributed departments or a coaching institute with branch centres has the same problem repeated per site: each location keeps its own register, and the head office sees them only when someone emails a spreadsheet. Comparisons are impossible and the consolidated view is always stale.

Because every site runs the same session record in the same system, the consolidated view is live and the per-campus view is a filter on it. Approvals stay local — the head of department who knows the staff approves the sessions — while visibility is central. No one is emailing registers at month end.

Fingerprint and face-recognition readers are the default recommendation for school attendance, and they carry obligations most institutions have not priced in. Under the DPDP Act, 2023 the standard is notice, purpose limitation, minimisation and deletion — and minimisation is the hard part, because if a login and an approval prove the same fact, a biometric template collects more personal data than the purpose needs. A template store is also a breach liability that a login-based record simply does not create.

Workclave captures no fingerprints, no face templates and no Aadhaar numbers. For an institution that teaches privacy and consent as part of its own curriculum, running staff surveillance hardware is a contradiction worth avoiding — and shared readers at a school gate are a hygiene question too, one that has not gone away.

Stated plainly, because a school evaluating this deserves it before a demo rather than after: Workclave holds no student records, no class rosters, no marks, no fee data and no parent contacts. It does not mark student attendance, does not send absence SMS to parents, and does not integrate with student ERPs or learning management systems. If student roll-call is what you are shopping for, this is the wrong product and a school ERP is the right category.

What it replaces is the staff register, the substitution notebook and the spreadsheet the accountant rebuilds each month. Institutions that get value from it already have their student system sorted and are tired of the staff side being the part nobody owns.

Pricing is per staff member, with no hardware. Free for up to 3 users, then ₹199 per user per month, no base platform fee and no seat minimum — so a twenty-teacher school pays for twenty staff and a three-campus trust pays for its actual headcount. Students are never counted, because they are not in the system.

Compare that against the per-device cost of readers across campuses plus annual maintenance, and the arithmetic usually favours dropping the hardware — particularly for a trust replacing ageing units at several sites at once.