Punch from anywhere it makes sense
Phone or laptop for people with an email, a shared kiosk with a PIN for people without one. Both obey the same rules — the kiosk is never a side door around a schedule.
Track time, catch everything that deviated from the schedule, approve the week and export payroll-ready numbers. Every figure traces back to a real punch and the person who approved it — months later, in front of anyone who asks.
Free to set up · takes about a minute
Attendance is only useful if the numbers survive an argument. Everything here is built so a figure can be traced, explained and defended long after the week it came from.
Phone or laptop for people with an email, a shared kiosk with a PIN for people without one. Both obey the same rules — the kiosk is never a side door around a schedule.
Late arrivals, absences, forgotten clock-outs, correction requests and time off land in a single list. Resolve it or accept it with a reason — nothing is silently swept away.
Fixed shifts, flexible days or a weekly target, each with its own grace period. Change a schedule and the past is never quietly recalculated behind you.
Managers approve their own team. Locked means locked — reopening is owner-only, always audited, and everyone affected is told what changed.
Hours, paid leave, worked holidays and pay rates roll into a summary and a CSV your payroll system can read without a spreadsheet in between.
Assign a person to a manager’s team and that manager gets their queue, their board, their timesheets, their PINs and their leave balances — and nothing outside it.
Each person’s week is one screen: what they were expected to do, what they actually did, what was corrected and by whom. Breaks are already deducted. Paid leave is already separated from worked time.
| Day | In | Out | Worked | Note |
|---|---|---|---|---|
| Mon | 08:58 | 17:04 | 7:36 | 30 min break |
| Tue | 09:12 | 17:00 | 7:18 | Late — accepted |
| Wed | 08:55 | 17:02 | 7:37 | |
| Thu | — | — | 0:00 | Annual leave |
| Fri | 09:00 | 16:31 | 7:01 | Corrected 16:31 |
| Total | 29:32 | + 7:36 paid leave |
Not everyone has a work email, and pretending otherwise is how attendance systems quietly stop reflecting reality. People with an account punch from their own device. Everyone else uses a shared kiosk with a personal PIN.
The same eight hours, seen by everyone who touches them. Scroll on.
Swipe across →
One button on her phone. The server stamps the time the moment it arrives; her device clock is recorded beside it so any gap between the two is visible rather than hidden.
Never overwritten. A punch is an event, not a field. Nothing that happens later edits it.
She was due at 09:00 with five minutes of grace, so 08:58 is simply present. Had it been 09:20, the day would surface as late — against the pattern that was in force on that date, not the one in force today.
The past is judged by the past. Editing a schedule never recalculates a week that has already closed.
The overnight job closes the shift at the rule, not at midnight, and flags it. Priya proposes the real time herself with a note; it goes to her manager as a correction rather than an argument.
Both numbers survive. The correction is a new row pointing at the original. The record shows what the clock said and what was agreed.
Two items, both his own team. He approves the correction and accepts a late arrival with a reason. His name and that reason are stored with the day, permanently.
Nobody is scored. There is no punctuality ranking anywhere in the product, by design.
Priya submits, Manny approves, the period locks. Payroll gets payable minutes, unpaid break, paid leave and holiday worked as separate columns — the shape a payroll run needs.
Reopening leaves a mark. Only an owner can, only with a reason, and the reason sits next to the original approval.
Setup is front-loaded on purpose. Once the calendar and the schedules are right, the weekly routine is just clearing a queue and pressing approve.
Country, timezone and workweek in one screen. Those choices set the defaults everything else inherits.
Import your country’s public holidays in one click, then create the schedules that define what “late” means.
Anyone with an email is invited automatically. Anyone without one gets a kiosk PIN instead. Assign them to a manager’s team.
People clock in and out, exceptions collect in one queue. Clear it, approve each timesheet, lock the period, export payroll-ready hours.
Every decision that touches someone’s pay is written down as it happens: who did it, when, and the reason they gave. The trail is append-only, so a record can be added to but never edited away.
Most of the product adapts to how you work. These six do not — they are the reason the numbers are worth anything.
Once a pay period is locked, nothing inside it can move. Reopening is an owner-only act, it records a reason, and it notifies every person whose numbers are back in play.
Corrections add a new row and keep the original visible next to it. You can always answer “what did this look like before, and who changed it?”
When a late arrival is fine, you accept it with a reason. It leaves the queue but stays on the record, attributed to you — and it can be revoked.
There are no productivity ratings, no rankings and no league tables. It records what happened against what was expected, and stops there.
Public holidays cover everyone, but they never block a punch. If someone works one, they clock in, confirm, and the day is recorded as worked holiday — payable, and visible in reports.
A manager requesting a person outside their team gets “not found”, not a greyed-out button. The boundary lives in the database, not in the interface.
Nobody sees pay rates they should not. Managers are scoped to their own people, and the person who locks a period is never the person who can reopen it.
Everything an admin can do, plus the only role that can reopen a locked pay period and transfer ownership.
People, schedules, holidays, pay rates, kiosk setup and locking the period. Sees the whole organisation.
Their own team: the exception queue, the live board, approvals, schedules, kiosk PINs and leave balances — plus their own timesheet like anyone else.
Their own hours. Clock in and out, take breaks, ask for a correction, request time off, see the week so far.
The entry is closed automatically at the end of the day and flagged as auto-closed rather than counted as a full shift. The person is asked to confirm the real time, and the confirmation is recorded next to the original.
Yes — that is what the kiosk is for. Give them a PIN and they punch from a shared tablet at the door. They still get schedules, timesheets and exceptions like anyone else.
They are one calendar for the whole organisation. Import your country’s published days, or add your own, and every person inherits them — there is no per-person holiday list to keep in sync. Anyone who does work that day is recorded as working a holiday.
A manager can approve a correction, and every correction keeps the original time visible with a reason and their name against it. Nobody, including an owner, can silently overwrite a punch.
Only the people on their team. Their queue, board, timesheets, schedules, PINs and leave balances. Pay rates stay with admins and owners.
Every report exports as CSV — attendance summary, payroll summary and raw time entries — with the same figures you see on screen, for the same date range.
More detail, including every term the product uses, is in the product guide.
Create an organisation, import your holidays, add one person and clock in. You can have a real record inside five minutes.