Kiosk
Clocking in without a phone: a tablet, a PIN, and nothing else on screen
For the warehouse, the site and the shop floor, where nobody carries a company phone. Open a link on an old tablet, fix it to the wall and it is clocking people in: no app to install, no session to expire, and no list of who came in today on display.
A shared device cannot have a session
That is the decision everything else follows from. A tablet on a wall is used by thirty people a day. If it needed a login, the session would belong to somebody, and that somebody would end up clocking in for everyone else without meaning to. So the kiosk has no session, no user account and no password for anyone to remember.
What it has is an address of its own. When you create a kiosk you give it a name, tie it to a work centre if that applies, and out comes a link with a forty-character random code. That link is the credential: which account the kiosk belongs to comes from its own row and never from the address, so changing one character does not land you in the account next door — it lands you nowhere.
There is a QR code to download, which is how it goes up in two minutes: print it, scan it with the tablet, save it to the home screen. And if the link ever leaks, rolling the code is one click and the old one dies immediately.
A PIN says who you are, and you do not set your own
Four to eight digits, one per person. It is set by whoever administers the team, from that person's record, not by the person standing at the kiosk: on a shared device, letting anyone choose a PIN is letting anyone choose somebody else's.
- Stored hashed — like a password. Nobody can read it back, not even the person who set it. If somebody forgets theirs, you set a new one.
- Unique across the account — checked against every other PIN when it is assigned. Two people sharing a PIN is one of them clocking in as the other.
- None of the famous four — 1234, 0000, 1111 and 4321 are rejected, and not out of pedantry: on a keypad everyone can see, those are the first four anybody tries.
- Eight wrong tries in a row and the screen stops for two minutes — enough that guessing is not worth it with a queue of people waiting behind you.
One button, and the server decides the rest
You type the PIN and one button appears. If the day is open it closes it; if not, it opens it. There is no choosing between «in» and «out», which is precisely the mistake people make in a hurry and somebody has to correct by hand afterwards.
If the kiosk is tied to a work centre, that centre overrides the one on the person's record and the entry is marked as made on site: the device is what attests to where somebody clocked in, not whatever a phone claims.
When the day closes, the minutes go straight into the project if that person has exactly one live assignment. With several, the entry comes in without a project and is split afterwards: asking somebody which of their four projects this was, on their feet with people behind them, is asking for the first answer that comes to mind.
And if they are dragging an open day from earlier in the week, it tells them as they come in.
What the kiosk does not show, and why that is deliberate
The screen never shows a list of people or anybody's hours. A device on a warehouse wall is read by everyone who walks past, including people who do not work there. Who came in today and at what time is not corridor information.
After clocking in, and only then, that person sees the clock, the name of the centre and their own hours for the day. Nobody else's.
- No corrections from the kiosk — those are requested from a phone or a computer, and they leave a trail.
- No time logged against projects, no time off requested.
- No picking a project by hand.
- No break button: in and out only. Breaks are clocked from the app.
How many kiosks, and where
As many as you need, each with its own link and its own centre. A warehouse with two doors is two kiosks, and every entry knows which door it came through. A kiosk can be switched off without being deleted, and it records when it was last used — which is how you find out the tablet in the stores has been dead for three weeks.
The kiosk is part of the time tracking module: if the account does not clock in, the kiosk does not exist and its link goes nowhere. How the modules work.
Frequently asked questions
Do I have to buy a terminal?
No. Anything with a browser will do: an old tablet, a spare phone in the office, the computer on reception. There is no app to install and no hardware to buy, which also means there is nothing to fall out of support in three years.
What happens if the internet drops in the warehouse?
The kiosk needs a connection: it is a page, not a device with a memory of its own. If it drops, people clock in from a phone or ask for the correction afterwards, which records that it was a correction and who made it.
Can somebody clock in for a colleague if they know their PIN?
Yes, in the same way they could hand over a badge. A PIN is not biometrics and does not pretend to be. What you do get is one hashed, unique PIN per person, a lockout after eight wrong tries, and a centre tied to the device, so the entry says where it was made.
How many digits is the PIN?
Between four and eight, your choice when you set it. Four is fine for a workshop of twelve; with a large headcount it is worth going longer, because the same pool of combinations is being shared out among more people.
Does the kiosk work for a headcount of three hundred?
It works, but a bare PIN starts to strain: with that many people the sensible setup is a kiosk per centre, each checking against its own roster, rather than one device on the main door.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.