Every staff punch, captured by a real device. Fingerprint, face, RFID — one register.

How most Indian schools track staff attendance today

At 7:48 a.m. the senior PRT teacher signs the paper register at the school gate. The PT teacher signs at 7:51. The Mathematics PGT signs at 7:56. By 8:00 the register has thirty-eight signatures; another twenty-six are still on the way. The peon writes 'L' against the late-comers in red ink — except for the head clerk's wife, who has been with the school nineteen years. The biometric machine on the office wall, the one bought from a local vendor in 2019, has been broken since Holi. The school is back on the paper register.

By month-end, the head clerk transcribes the register into an Excel sheet — working days, present days, late-comings, half-days, leaves — and emails it to the accountant for the salary run. The accountant raises four queries on the 3rd, the head clerk re-checks, two corrections go in by hand, and salary is processed on the 5th. Every month, the same loop. By April promotion week the school has lost the audit trail for at least two months.

The school bought the machine. The machine doesn't work for half the staff. The signatures keep coming back. Nobody trusts the data, but nobody has time to fix it either.

How Inkwelly Biometric works — three things, one register

Open Employee Attendance → Biometric and you land on a single page with two tabs: Devices and Fingerprints. The Devices tab is where every machine in your school is registered — gate-mounted ZKTeco for the main entry, an ESSL face-recognition unit at the staff room, an RFID reader at the back gate for the bus drivers. Each device has a deviceId (the serial number), a friendly deviceName, the location it sits at, the deviceType (FINGERPRINT, FACE or RFID) and an isActive flag. Add a device once and Inkwelly tracks the lastSeenAt timestamp every time it sends data — so the office knows in real time which gate is online and which has gone silent.

The Fingerprints tab is where each staff member is mapped to a locked slot on the device. The Mathematics PGT enrols her right index finger; Inkwelly assigns fingerprintId = 47, fingerName = 'Right Index', enrollmentStatus = PENDING, and pushes the slot to the device. The teacher walks to the gate, places her finger, and the device captures the template against slot 47. The status flips to active. The next morning her thumb on the gate device produces a punch record tagged with her employeeId — not 'unknown user 47', not 'guest punch', not a smudge that needs the office to map manually. The fingerprint slot is locked at the school level: nobody else in the school can be assigned slot 47. Duplicates are physically impossible.

For RFID and face devices, the flow is identical — the slot becomes a card UID or a face template, the mapping table records which staff member owns it, and the punch flows back the same way. From the first punch onwards, every entry lands inside the Daily Attendance view alongside manual and self-service punches, with the sourceIdentifier of the device that captured it preserved in the audit log.

If a teacher leaves the school, the office hits Deactivate on her fingerprint mapping. The slot frees up, the next joiner can re-use it the same day, and her historical punches stay attached to her old employee profile — never deleted, never reassigned. If a device is replaced, the old deviceId is decommissioned, the new serial number registered, and the existing fingerprint enrolments are pushed to the new machine in a single batch.

Walkthrough — the four screens of registering a device and enrolling a staff fingerprint

“Pehle har month dus minute ka calculation karna padta tha kis teacher ka thumb device pe nahi chala. Ab device offline ho jaye toh bhi pata chal jata hai morning mein hi. Salary clean nikalti hai 1st ko.”

Real-world scenarios Inkwelly Biometric handles every term

1. Replacing a broken device mid-session. The main gate ZKTeco unit dies on a Wednesday. The school orders a replacement Friday, fits it Monday morning. Open the device registry, mark the old deviceId isActive = false, register the new serial number, push the existing fingerprint enrolments to the new machine in a single batch. The teaching staff walks in Tuesday morning and the new device recognises every fingerprint without re-enrolment. Total office time: forty minutes.

2. A teacher resigns mid-term. The Hindi PGT submits her resignation effective 31 October. On her last working day, the office hits Deactivate on her fingerprint slot. Her slot 32 frees up. Her historical punches from the past three sessions stay attached to her profile and stay searchable for the salary register, the income tax computation, the appointment-letter audit, and any future verification request from her next employer. The slot itself is reassigned the next April when a new joiner needs it.

3. Bus drivers who can't enrol fingerprints. Three of the six bus drivers have abraded fingertips that the fingerprint device refuses to capture cleanly. Instead of forcing the issue, the office issues each of them an RFID card mapped to their employee profile via the same Fingerprints tab. The card UID is recorded as their fingerprintId-equivalent, the back gate RFID reader picks up the swipe each morning, and their daily attendance is identical to the teaching staff's — only the source device differs.

4. The face-recognition unit at the staff room during flu season. Every winter half the staff catch a cold; touching a fingerprint sensor with a wet thumb is a hygiene complaint. The school adds an ESSL face-recognition unit at the staff room door. Each teacher walks past once for enrolment — the device captures the face template, Inkwelly stores only the template ID and the mapping. From day two, the same teachers continue using the gate fingerprint AND the staff-room face unit; both punches roll into one daily record.

5. Pre-payroll reconciliation in five minutes flat. On the 1st of the month the accountant opens the Monthly Attendance Report and sees every staff member's working days, late-comings, half-days and leaves — sourced from biometric punches, manual punches and approved leaves. The report exports to CSV, lands in payroll, salary runs by the 5th. The head clerk no longer transcribes the paper register because there is no paper register.

See Biometric Attendance live with your school's existing devices

Bring the serial numbers of three of your existing biometric machines to a 25-minute demo — fingerprint, face or RFID. We will register them, enrol three test fingerprints, and show the punches landing in daily attendance — on your data, in front of you.

Limits, safety and the small print

One slot, one teacher, one school — until you say otherwise. A fingerprint slot is unique per school by database constraint. The system will not let you assign slot 47 to two staff members; the second initiateEnrollment call returns an explicit error. To re-use a slot, the existing mapping must be deactivated first — and the deactivation event is audit-logged with the user, IP and timestamp.

Vendor-agnostic, RD-service-friendly. Inkwelly does not lock you to a particular biometric vendor. Any Indian RD-service-compliant device — ZKTeco, ESSL, Realtime, Matrix, Mantra, eSSL — registers via the same deviceId field. The transport between the device and Inkwelly's PostgreSQL is your school's existing biometric integration server (or a managed bridge service we can recommend). Punch records flow in the standard EmployeePunchRecord shape regardless of source.

Data residency. Every fingerprint mapping, RFID card UID, face template ID and punch record is stored on the Mumbai-region PostgreSQL — never on overseas servers, never replicated outside India. Raw fingerprint and face templates remain device-side; Inkwelly stores only the mapping that says 'this teacher owns slot 47'. DPDP Act 2023 obligations — purpose limitation, consent recording, deletion-on-request within thirty days — are built in at the schema level.

Permissions, scoped to roles. Adding a device, initiating an enrolment, cancelling an in-flight enrolment, deactivating a mapping — each action is gated by an IAM permission that the school controls. The Principal's role usually grants all four; the Head Clerk's role grants enrolment and cancellation but not device add or deactivation. The default role pack ships configured for a typical CBSE / ICSE school — adjust per your trust's policy in five minutes.

No silent re-enrolment, ever. If a teacher's fingerprint slot becomes unreliable (cuts, burns, ageing skin), the office must deactivate the existing mapping and re-enrol against a new finger explicitly. The system never silently overwrites a template — every enrolment is a deliberate, audit-logged action. This is the difference between a biometric trail you can show a CBSE inspector and one you cannot.