Web Clock-In Kiosk: Replace the Clipboard With Real Punch Times
Turn any shared tablet into a PIN-based clock-in kiosk so hourly staff punch in and out, a manager reviews and approves the day, and you export clean hours to payroll — no punch-clock hardware required.
A web kiosk where hourly staff tap a personal PIN to clock in and out, every punch is captured with a timestamp and device, a manager reviews the day's punch list (fixing odd punches), locks the day, and exports a per-employee hours CSV in the exact columns your payroll provider expects.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A shared tablet or computer for the kiosk
- An employee roster CSV/Sheet (name, employee ID, PIN, default location)
- Claude Code or any AI coding agent
The problem this kills
Hourly hours get written on a clipboard, scrawled on a whiteboard, or texted to a manager at the end of the night — and then someone re-keys them into payroll on Friday, squinting at handwriting and guessing whether "11–7" included a break. People forget to write their start time. Someone leaves and never writes down when. The 4 p.m. shift "rounds" itself to 4:00 even though they walked in at 4:18. By payday it's a negotiation, not a record.
Buying a real time-clock system means hardware, badges, contracts, and a per-employee monthly fee you don't want for a team of twelve. So you keep using the clipboard, and you keep paying for hours nobody can actually verify. You don't need a developer or a hardware vendor to fix this — you can build your own kiosk on a tablet you already own.
What you'll build
A simple web kiosk you open on a shared tablet by the door. Each employee taps their personal PIN to clock in, and taps it again to clock out — every punch is stamped with the exact time and the device it came from. Behind the kiosk is a manager view: a daily punch list showing who's in, who's out, and any punches that look wrong (a clock-in with no clock-out, a double clock-in, a shift that crossed midnight). The manager fixes the odd ones, applies your rounding policy if you use one, and clicks Approve & lock the day. Locking produces a clean hours-per-employee CSV in the exact column layout your payroll provider wants.
You start by importing your employee roster (a CSV or Google Sheet with name, employee ID, PIN, and default location). If you care about staff punching from off-site, you can turn on an optional geofence check that flags a punch made too far from the worksite — it warns the manager, it never blocks the worker.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how your team clocks in today, what your roster columns are named, whether you pay breaks, how (and whether) you round punch times, your overnight and split-shift cases, and the exact column layout your payroll provider expects — and then it tailors the data model, the punch rules, and every later step to your answers. This is not a generic template; the agent reads a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the roster import, the PIN kiosk screen, punch capture with the messy-punch guards, the manager review-and-approve screen, day locking, and the payroll CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today with no integration to your payroll system at all.
The governance it includes (this is the point)
This is a wage record, so it ships with the controls that keep it trustworthy: login so only your team (not the kiosk, which only takes PINs) can reach the manager and export screens, row-level security so you only ever see your own location's punches, a complete audit trail of every punch, edit, approval, and lock — who and when — and a hard human-approval gate so no hours are exported until a manager has reviewed and locked the day. Rounding is applied only on approval and never silently, so the raw punch time is always preserved next to the rounded one. Duplicate guards keyed on employee + punch time + device mean a double-tap can't create a phantom punch, and once a day is locked it can't be quietly re-edited.
Who it's for
Shift managers, restaurant/retail/warehouse owners, and office managers who run hourly teams without a punch-clock system and are tired of decoding a clipboard every payday. If you can describe how your crew clocks in today, you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll have staff punching a PIN on a tablet by the end of the weekend.