Blog Time and attendance
Clocking in where nobody carries a company phone
In an office people clock in from their computer and there is no debate. In a warehouse, on a site or in a shop there are thirty people, no company phones and one door they all come through inside ten minutes. There the options are three.
The real problem is the five-to-eight minute
Any system works with one person standing in front of it. What separates them is the queue: thirty people arriving inside ten minutes, in gloves, with dirty hands or in a hurry. If clocking in takes eight seconds a head instead of two, the queue reaches the street, and by the third day people clock in «later», which is the same as not clocking in at all.
So the question is not which one is most secure. It is which one survives the rush without anybody deciding to skip it.
The card
Fast, familiar, and with a problem everybody knows and almost nobody says out loud: cards get lent. Whoever is running late asks a colleague to swipe theirs, and the record says they were in at eight.
It also carries a running cost. Cards get lost and demagnetised, readers have to be bought, and the day the manufacturer drops support for the model you replace the whole estate. And what you are left with at the end is a file you have to export and reconcile against something else before it means anything.
Fingerprint and face
It solves the lending problem and opens a much larger one. Under the GDPR — and the UK GDPR, which reads the same way here — biometric data processed for the purpose of uniquely identifying someone is special category data under Article 9. That means you need a lawful basis under Article 6 and, on top of it, a separate Article 9 exception. Employee consent rarely does the job, because the imbalance of power between employer and employee is usually taken to mean it is not freely given, and several European supervisory authorities have taken enforcement action against fingerprint-based attendance systems on exactly that reasoning. This is not small print: it is the kind of decision you put in front of whoever handles data protection for you before you buy the hardware, not after.
And in practice, fingerprint readers fail precisely where they are most needed: hands with plaster on them, with oil, in gloves, in the cold. Every failed read is one more attempt in the queue.
The tablet on the wall
Any screen with a browser, sitting on the kiosk page. You type a PIN and a button appears. Two seconds.
What makes it different from the other two is not the speed, which is much the same: it is that there is no separate file. The clock entry lands in the same place the projects and the hours live, so when the day closes those minutes can go straight onto a project. There is no export to reconcile at month end.
- It costs whatever the tablet costs — and an old one will do. No terminal to buy, no licence per device, and no model that ends up out of support.
- It is set up in two minutes — print the kiosk QR code, scan it with the tablet, save it to the home screen.
- There is no session — and on a shared device that is the point: a session would belong to somebody, and that somebody would end up clocking in for everyone else.
- It is tied to a site — the entry knows which door it was made at, which is more than a phone tells you.
What a kiosk does not solve, and you should know before you buy
None of the three options is magic, and anybody selling you theirs without saying this is selling it badly:
- A PIN can be lent. Exactly like a card. It is not biometrics and it does not pretend to be. What you do get is one PIN per person, four to eight digits, encrypted, unique across the whole company, with the obvious ones refused and a lock-out after eight failed attempts.
- It needs a connection. It is a web page, not a device with memory. If the line goes down in the warehouse, people clock in from a phone or ask for the correction afterwards, which leaves a visible note that it was a correction.
- It does not replace corrections. People forget to clock out under every system ever built. What matters is that fixing it is easy and leaves a trail. How a missed clock-out gets fixed.
The decision rule, in one line
If what you need is a record that is good for more than compliance, the criterion is not the hardware: it is where the minutes end up. A reader that leaves you a file has solved one problem and created another. How the PIN kiosk works.
Frequently asked questions
How many kiosks do I need?
One per door people come in through. Two doors means two kiosks, each with its own link and its own site, so every entry knows where it was made. Putting a single one at the main entrance of a building with two ways in guarantees a queue at one and late entries at the other.
Can breaks be clocked at the kiosk?
No: the kiosk does clock in and clock out. Breaks are recorded from the app. It is a real limitation and we would rather say so.
What about somebody with no phone who has never used a tablet?
Typing a few digits and pressing one button is everything on the screen, and the screen shows nothing else. It is deliberately as close to an alarm keypad as we could make it.
Can I run the kiosk and phones at the same time?
Yes, and that is the normal setup: the warehouse clocks in on the tablet and the field team from their phones with location. Same working day, same record.
All of this is built into Fichaloto. See how it works.
Keep reading
How to choose
Twelve questions worth asking before you sign
None of these twelve questions is technical. Every one of them is answered in a sentence, and you can ask for the answers in writing before signing anything.
Compliance
A clocking record that cannot be quietly rewritten
Most time-tracking tools store hours in a table anyone with database access can edit. That is fine until the day somebody asks you to prove a number.
Capacity
Planned, clocked, charged: three numbers that should match and usually do not
Most companies can tell you what they planned and what they invoiced. Very few can tell you, for a given week, whether those two things are related.