QR Code Staff Attendance with GPS: Stop Proxy Punches Without Another Machine

Every school has a version of this story. The biometric machine at the gate stops working in July. A replacement takes three weeks. Meanwhile staff sign a register, someone signs for a colleague who is "just parking", and at month end the accountant has two sets of records that disagree — and has to decide whose salary to cut.

Staff attendance is not hard because people are dishonest. It is hard because the systems schools use leave gaps: a machine that can fail, a register anyone can sign, and no clean way to fix a genuine mistake. This guide explains how QR code attendance with GPS closes those gaps, how it works alongside an eSSL fingerprint or face device, and how corrections and month-end locking keep payroll honest.

Why does staff attendance keep breaking in schools?

Staff attendance breaks at three points: how the punch is captured, how mistakes are corrected, and when the record becomes final. Most schools fix only the first one, by buying a machine, and then wonder why the arguments continue.

• Capture. A paper register can be signed by anyone. A single biometric machine is a single point of failure, and a queue forms at 7:55 every morning.
• Correction. A teacher forgets to punch out after a parent meeting. There is no proper way to ask for a correction, so it becomes a WhatsApp message to the principal that nobody can trace later.
• Finality. Punches keep arriving after salaries are calculated, and nobody knows whether the attendance report the accountant used is the one that exists now.

A good attendance system answers all three. The rest of this guide takes them in order.

How does QR code attendance with GPS work?

QR attendance works by showing a school-specific QR code on a screen at the gate; staff scan it with their own phone, and the system records the punch only if the code is valid and the phone is inside the school's boundary. No new hardware is needed beyond a tablet or an old phone for the display.

Two details make this safe enough to trust with salaries.

A QR code that expires

A school can use a static code, which never changes, or a dynamic code that refreshes on a short interval — every 30 seconds by default, and adjustable. With a dynamic code, a photo of the QR sent to a colleague at home is useless: by the time it is scanned it has expired, and the scan is refused with "QR code expired. Scan the new one." The code is also tied to one school, so a QR from another branch is rejected.

A location fence around the school

When GPS is required — it is on by default — the phone must share its location while scanning. The school sets its location once (standing at the gate and pressing "detect current location" gives the most accurate point) and chooses a radius between 10 and 5,000 metres. Every scan is measured against that point. Outside the circle, the punch is refused with "You are not at the school premises."

A screen at the gate that does only one thing

The display tablet should not be logged in as an administrator. LigiLearn lets you create a kiosk account for the receptionist: after login, the only screen it can open is the QR attendance display. If the tablet is left unattended, nothing else in the school's data is exposed.

QR or biometric: which should a school use?

Use both, and let each cover the other's weakness. A school chooses which modes are allowed — biometric, QR and manual — and can switch any of them off. Most schools are best served by keeping all three available.

How the eSSL device connects

LigiLearn works with eSSL biometric devices using the device's push protocol (often called ADMS or iClock). You register each device by its serial number, point the device's push URL to LigiLearn, and punches arrive on their own — no one exports files from the machine. You can choose whether a device accepts staff only, students only, or both.

Each device reports a heartbeat, so a device health report shows when a machine last checked in. That is how you find out a device is offline on the day it fails, not three weeks later. Punches from fingerprint, card, face, palm or PIN are all accepted, and break or overtime punches are recorded without changing the day's attendance.

How are late arrival and half day decided?

They are decided by rules the school sets once, not by someone reading the punch log each morning. The settings that matter are simple:

• Staff start and end time — for example 8:00 and 4:00.
• Arrival grace — how many minutes after the start time still count as on time.
• Early departure grace — the same idea at the end of the day.
• Half-day minimum hours — the hours needed for a day to count as at least a half day.

Because the rules are written down in the system, a late mark is no longer a matter of opinion. The late comers report and the staff hours report are built from the same rules, and each staff member sees their own month on a "My Attendance" page — so the conversation about a late mark starts from the same facts on both sides.

How do staff correct a missed punch without a WhatsApp message?

They send an attendance request inside the system. A staff member picks the day, asks for it to count as Present or Half Day, and writes the reason — forgot to punch, came late because of a board duty, worked on another day. The request goes to an administrator, who approves or rejects it. A rejection carries a reason the staff member can read.

The request has sensible limits built in, so nobody has to police them:

• Only today or an earlier date, and never before the staff member's joining date.
• A short reason is required.
• No request is needed — and none is allowed — for a day that already counts in full, as leave, or as a holiday.
• Only one pending request per day.
• Leave is not requested here; it needs an approved leave application.

For the administrator, there is also bulk regularisation: choose a staff member and a range of days in one month, see only the absent days and days with no record, and apply one status and one reason to all of them. The original device or QR punch times are never overwritten; the correction sits on top, and every request is written to the audit log.

What happens to attendance when payroll is approved?

Attendance becomes final. A day can be locked once it has been checked, and once a month is closed for payroll, requests can no longer be sent for it; any that are still waiting expire. This is the step most schools miss, and it is the one that ends the month-end arguments.

Real life still happens after the lock. A device that was offline may upload a week of punches after salaries were calculated. LigiLearn keeps those punches — nothing is thrown away — but they do not change locked attendance. They appear in a separate "late punches after payroll approval" list, so the accountant can see them and decide whether anything needs to be done next month.

A salary should be calculated from attendance that cannot change underneath it. Locking is not about control; it is about everyone trusting the same number.

Why we built staff attendance this way

Many school ERPs treat staff attendance as an import from the biometric machine and stop there. We built it from the problems schools actually described to us: the machine that fails, the colleague who signs for another, the forgotten punch that becomes an argument, and the punch that arrives after salaries were paid. Each part of the design answers one of those, at the root.

Nothing here needs a trained operator. The gate tablet shows one screen, staff use the phone they already carry, and corrections are a form, not a phone call. A school with a dozen teachers and a school with several hundred staff use exactly the same setup, and our team gives both the same attention. Setup and training are in Hindi or English — and if your office is more comfortable in Bhojpuri or Awadhi, our support team will talk to you that way. After you go live, we ask what is still slow, and we fix it.