Clocking in from inside a radius you set
Pin each office on a map and set how far out still counts. A clock-in from outside that radius is recorded as outside it, with the distance, rather than silently accepted or silently refused.
One moment
Staff
An attendance management system with a geofence
Most attendance software answers the wrong question. It records that somebody pressed a button, which tells you nothing, because the button can be pressed from anywhere. The question worth answering is whether the person was at work, and the only honest way to answer it is to check where the phone was when they said they arrived.
No card, no demo call, unlimited staff accounts on every plan.
Before the software
A register that everybody knows is fiction
A paper register signed at the end of the week is filled in from memory and rounded generously. A punch app without a location is pressed on the bus. Either way the figures that reach payroll are wrong, and everybody in the office knows they are wrong, which is worse than not measuring at all because it makes the honest staff feel foolish.
What it does
Built, not on a roadmap
Everything below is in the product today. Open a free account and you will find it there.
An away day carries a reason
Staff are legitimately out: a university visit, an education fair, a bank. Clocking in from elsewhere is allowed and asks why, so the record shows a reason rather than a gap that gets argued about at month end.
Attendance feeds payroll, in the Nepali month
Payroll runs on the Nepali month because that is the month salaries are actually paid in, and it reads the days genuinely clocked rather than a figure typed in afterwards. SSF, PF, TDS and CIT are handled.
A front desk clock for shared devices
Not everyone carries a phone they will install something on. A tablet at reception, a PIN each, and the same record.
Who is in today, per office
The home screen shows who has clocked in and who has not, per branch. Head office sees every branch at once without asking a manager to send anything.
Salaries stay out of the CRM
The staff list shows a band, not a figure. Exact salaries sit behind payroll's own permission, and opening payroll is recorded. Nothing in the system deletes that trail.
The actual screen
Not a mockup
This month, by person: days in, hours, and which ones were clocked from outside the office radius.
Why it fits
Why the Nepali month matters
Attendance software built elsewhere runs on calendar months, so a Nepali payroll built on it is either wrong or maintained by hand in a spreadsheet beside it. Asar is not July. Running the month the salary is actually paid in removes a reconciliation nobody should be doing.
Questions owners ask
- Can staff clock in from home?
- They can press the button anywhere, and the record will say where they were. A clock-in from outside the radius you set is recorded as outside it, with the distance, and asks for a reason. Nothing is silently accepted.
- Does it work without a smartphone for every member of staff?
- Yes. There is a front desk clock for a shared tablet, where each person has a PIN. The record is the same.
- Is there a free version?
- There is a free tier that includes attendance with a geofence, so you can run a real office on it before paying anything. Nothing is charged until you ask to be invoiced.
- Does attendance connect to payroll?
- Yes. Payroll reads the days actually clocked rather than a number retyped from a register, and it runs on the Nepali month.
- What if somebody is genuinely out of the office?
- They clock in and give a reason, which is recorded against the day. A university visit is not absence, and a system that cannot tell the difference produces figures nobody trusts.
- Can a branch manager see only their own office?
- Yes. How far somebody sees is set separately from what they can do, so a branch manager sees their office and head office sees all of them.