Klock turns any tablet or laptop into a time clock that recognises your staff by face. No cards to lose, no PINs to share, no buddy punching. Timesheets, overtime, unpaid breaks and leave are worked out for you.
Set up in about ten minutes. Works on the hardware you already have.
No installation, no server to look after, no proprietary terminal to buy.
Each person looks at the camera once and turns their head. It takes about fifteen seconds. You record their consent at the same time, because that is what the law expects for biometric data.
Open the kiosk page and leave it running. Staff step up, get recognised, and are clocked in or out. Anyone the camera struggles with can use a PIN instead.
Hours, overtime, deducted breaks and leave, as a Sage import file — or a branded PDF per employee to sign, or Excel and CSV for your accountant.
The awkward parts of time and attendance are not the clocking. They are the rules around it, and getting them wrong costs real money in both directions.
A shift starting at 18:00 and ending at 05:00 stays on the day it began, and is paid as one shift rather than split across two dates.
Set lunch as 12:00–12:40. Someone who clocks out at 12:20 loses the twenty minutes they actually took, not the whole forty.
Daily overtime first, then the weekly threshold on what is left. Defaults follow the BCEA — nine hours a day, forty-five a week — and you can change both.
Payroll packages do not import “hours worked”. They import transactions: a quantity against an earning code, for an employee identified by payroll’s own number. Klock produces that file directly.
Sage VIP and Payroll Professional, Sage Business Cloud, Sage 300 People, or a plain all-columns file for anything else. Earning codes are yours to set, because every installation renames them.
The number on the floor and the number in payroll are rarely the same. Klock keeps both, refuses to reuse one, and tells you who is unmapped instead of quietly leaving them off the run.
A push carries an idempotency key and a checksum of its contents. Re-running a period that has already gone through is refused rather than paid again.
Open shifts, people with no payroll number, hours that are missing rather than zero — shown before you export, not discovered on a payslip.
The useful thing a model can do here is read a period and tell you what to look at first. The dangerous thing is arithmetic. Klock lets it do the first and structurally prevents the second.
A prioritised read of the period’s exceptions — open shifts, people with no payroll number, a spike in manual punches — ranked by what would actually cost money if it went out unnoticed.
Your question becomes a query and Klock runs it. Every figure comes from the same place the timesheet does, so it matches. The query is shown alongside the answer, so you can see the question was understood before you trust it.
Paste a sample from your payroll system and Klock proposes which codes to export against, quoting the line it read each one from. Nothing is applied until you enter it yourself.
An owner switches it on per workspace. Klock then sends employee codes rather than names, and puts the names back before you read them. Face templates are never sent — there is no code path that can read them.
Every plan includes an amount of AI usage, and every call is metered against it. When the allowance runs out Klock stops and says so. You set the ceiling; nothing is spent past it.
Who is on shift right now, who has forgotten to clock out, who is missing, and who is on leave. Hours by day and by person.
Annual, sick, family responsibility, unpaid and public holidays. Recorded, so a legitimate day off never looks like a no-show.
Bad light, an injury, a bandaged face. Anyone the camera cannot match can still clock in, and the timesheet records that it was a PIN.
Bring your own identity provider over OIDC — Microsoft Entra, Google Workspace, Okta — or use an email and password.
Every enrolment, erasure, manual correction and settings change, with who did it and when. Manual punches are marked as such.
Your logo, company name and registration number on the timesheets you hand to staff and send to payroll.
The door tablet gets its own address with nothing to navigate to, so it can be locked to one screen. The office can use the admin app at the same time without disturbing it.
A weak face template is worse than none — it fails at the door and gets fixed with a manual punch nobody trusts. Enrolment scores itself and refuses to save anything below the bar you set.
When the kiosk refuses someone it says how close it came and what it needed. Adjust how strict matching is against those numbers rather than a hunch — and it warns you when you have gone too far.
Klock has no roster, so it will not tell you someone was absent. It tells you which working days have neither a punch nor leave, and lets you decide what that means.
Excel, CSV and PDF at any time, on any plan. If billing lapses the workspace goes read-only and stays readable — payroll records are a legal obligation, not leverage.
This matters enough to be blunt about. Enrolment produces a list of 128 numbers that describes a face. That is what gets saved. The image is discarded in the browser and never reaches our servers, and the numbers cannot be turned back into a picture of anyone.
Under POPIA, biometric data is special personal information. Klock records explicit consent per person, lets you withdraw it and erase the template at any time, and keeps the punch history separate so erasing a face does not destroy a payroll record.
Fourteen days free, all features, no card. If it does not suit you, walk away — and take your data with you, in Excel.
Create your workspace