Employee attendance app · 09:02:14 IST, the punch
A mobile attendance app for small teams. People punch in from their phone's browser, the office fence is checked once at that moment, and a punch made with no signal keeps the time it was made.
Works today in the phone's browser, with nothing to install. A native mobile app is coming soon.
Included in LekhaHR Operations: ₹79 per employee per month on annual billing for the first 25, no minimum; GST extra. See every band
Tue 29 SepShift 09:00–18:00
Punched in
09:02:14
Koramangala office
Paiteq Technologies · Tue 29 Sep 2026
Asha Rao · office
09:02 in · location read18:14 out · location read
Rohan Das · remote, no signal
kept at 09:18:07, the time it was made
Design preview · sample data · Paiteq Technologies
No. 02
Join by code
A shop-floor team shouldn't need an IT person to get started.
Meenal invites the team from LekhaHR. Asha opens the link on her phone, types the six-digit code from her email, and she is in. Each later sign-in sends a fresh code to her email.
Paiteq Technologies
Hi Asha, you're invited
Meenal Joshi added you to Paiteq on LekhaHR. Check your leave, punch in and get your payslips here.
We sent a 6-digit code to your work email.
Join PaiteqNo password to remember. Each time you sign in, we email you a fresh code.
because the person is already on the record, so they only confirm, never retype
because a code in the inbox is harder to share than a password on a sticky note
because it works today in the phone's browser, with nothing to install, and can sit on the home screen. A native mobile app is coming soon.
because the first job is to confirm the details HR imported
No. 03
One read, at the punch
because attendance needs to know where a punch was made, not where a person went.
If your policy asks for location, the phone reads it once when the punch button is pressed, checks it against the office geofence and stops. The same single reading happens at punch out. Nothing is recorded between the two punches: no background tracking, no route and no travel history.
because the punch is stamped when it is made
because 40 m from the office pin
because a weak reading is kept and flagged, never silently trusted
because it is kept privately with that one punch
Your location between punches
Routes, distance or travel history
Location while LekhaHR is closed
Contacts, messages, photos or other apps
The person, whoever approves that punch, and the HR roles you allow. Nobody else.
The phone asks for location only when a punch needs it. LekhaHR never needs “always”.
A selfie, where your policy asks for one, is evidence for one punch, not a login.
Design preview · sample data
No. 04
A weak network
Queued is a visible state, never a spinner that quietly gives up.
Rohan punches in at 09:18:07 from home with no signal. The phone holds the punch and says so. At 09:31:40 the signal returns and the punch syncs, still at 09:18:07.
on the phone, with no network
with a one-time id, so a retry can't count it twice
as soon as the signal came back
Design preview · sample data
The honest limit
A held punch syncs the next time LekhaHR is open with a signal. We don't promise a sync while the browser is fully closed on every phone, and clearing the browser's data before it syncs removes the held punch. That is why the screen keeps saying Queued until the punch is safely recorded.
because a state you can see beats a punch that vanished without a word.
No. 05
Outside the fence
because a field visit or a day at home is work, and the punch should say so.
Rohan works from home on Tuesdays. His punch lands 6.1 km from the Koramangala office, so the phone offers a remote clock-in instead of an error. Priya is on leave, so Meenal, who covers her approvals, approves it from her phone at 09:40.
Set the pin and a radius from 50 m to 2 km for each location.
Your policy says who may ask for a remote clock-in, and who approves it.
Tell your manager when you left, before the cutoff. The day is never guessed.
Punch in09:18:07
You're 6.1 km from the Koramangala office.
Ask Meenal (covering for Priya) for a remote clock-in? Your punch keeps its time either way.
Reason
Working from home, as every Tuesday
Ask MeenalApproved by Meenal Joshi · 09:40
No. 06
Approve on the go
A question keeps the request open, and the reply stays on it.
At 10:14, Meenal's phone has two things waiting: Vikram's missed punch-out from Mon 28 Sep, and Asha's leave. Each shows what happens if she says yes.
To do2 waiting for you
Vikram Nair
Regularisation · filed 09:55
“Missed punch-out. On a client call until 18:30.”
if approved: Present, out 18:32
ApproveReject
Ask a question
Asha Rao
Casual leave · Fri 16 – Mon 19 Oct · 2 days
because the manager sees the status the day becomes, before approving
because the working is done before it reaches the approver
because the manager decides with the facts on one card
because late marks and missing punches arrive with their rule
No. 07
An honest note
because the right tool for your team matters more than one more sign-up.
Written for you if
Talk to us first if
No. 08
Questions
It should record each punch with the time and, if your policy asks, the location at that moment only; keep working on a weak network; let people fix a missed punch with a reason; and send paid days straight to payroll. LekhaHR does this from the phone's browser, for teams from two people.
LekhaHR works today in the phone's browser, with nothing to install. A native mobile app is coming soon. It is not in the Play Store or App Store today. People open LekhaHR in the browser they already have, can add it to the home screen, and punch, fix a missed punch or approve from there.
No. Location is read once when you punch in and once when you punch out, and only if your company's policy asks for it. Nothing is recorded between punches, and there is no route, distance or travel history. Each reading stays with its own punch.
Yes. The punch is held on your phone, keeps the time you made it, and syncs when the signal comes back, with a one-time id so a retry can never count it twice. The screen says Queued until it has synced.
The punch is not thrown away. If it lands outside the office geofence, you can ask your manager for a remote clock-in from the same screen, with a reason, if your policy allows remote or field days. Your manager approves it from their phone.
No. There is no face matching, and LekhaHR does not connect to biometric or face-recognition devices. If your policy asks for a selfie with some punches, it is stored privately with that one punch and used only to review it.
LekhaHR does not claim to detect fake-location apps. Each punch keeps how accurate its location reading was, and punches outside the fence or with a weak reading go to the manager to review, so an odd punch is seen rather than silently accepted.
No more than opening a map once. Location is read only at the two punches, in and out. Nothing runs in the background between them, so there is no background location, no background battery use and nothing to keep switched on through the day.
No. 09 · By invitation
because the bill is sized to the team you have. We reply to every request by email.