Site clock-in terminal
A wall-mounted tablet where people clock in and out by tapping a card or entering a code, and a web platform that turns those events into timesheets a manager can approve and export.
A concept design under Example systems, and a semi-stack project: you buy the tablet, case and mount to our checklist, and we supply the kiosk app, the platform and a small card reader. Nothing here has been built, and no figure is a measured result.
An ordinary tablet, locked to one app
A common Android tablet in a rugged case is cheaper, easier to replace and faster to source than a custom terminal. The kiosk app is the only thing it runs: it shows the site and the time, takes a tap or a code, shows the person their name and the result, and goes back to ready.
With no network it keeps working, stores events on the tablet and sends them in order when the network returns. Android's lock task mode means the home and recent buttons do nothing, and a one-time code enrols the tablet to its site.
A small reader that sends a card number and nothing else
Many tablets have no NFC, or have it somewhere hard to tap. The reader is a small board on a short USB lead, mounted beside the tablet where people expect to tap. A microcontroller reads the card, ignores a repeat read within a short window, and passes the card number to the app as one line over a serial link.
It has no screen and no network, so the firmware stays small. It reads only, never writes to a card, does nothing until the app has checked its version and identity, and installs only firmware signed by us.
A platform that turns taps into timesheets
An intake service authenticates each tablet, accepts its events, removes duplicates and confirms receipt. Events are kept as they happened and never overwritten. A manager sees today at each site, who is in and who has not clocked in, and adds a correction with a reason, shown beside the original.
Hours per person per day are built from events and corrections, with missing clock-outs flagged. A manager signs off a period, and the platform writes a file the customer's payroll software accepts.
Our software and a small reader, on hardware you buy
- The platform only, for terminals you already run
- The reader only: board and firmware
- The kiosk app and the reader, on your tablet
- All three, on the tablet, case and mount you buy to our checklist
The heavy hardware is bought, not built, which is what keeps the cost down. The joints that cross from our work to yours, such as the export your payroll software accepts, are written down once and tested from both sides.
System overview
A wall-mounted tablet lets people clock in and out at a site by tapping a card or entering a code, and a web platform turns those events into timesheets a manager can approve and export. The tablet is an ordinary Android tablet in a rugged case on a wall mount. Our work is the kiosk app, the platform and a small card reader.
The design is semi-stack because the heavy hardware is bought, not built. The customer chooses and buys the tablet, case and mount to our written specification, and the only hardware we design is the reader, which is a small circuit board with its own firmware.
Why this design
- Off-the-shelf tablet. A common tablet in a rugged case is cheaper, easier to replace and faster to source than a custom terminal.
- A small separate reader. Many tablets have no NFC, or have it in a place that is hard to tap. A reader on a short USB lead sits where people expect to tap and works the same on any tablet.
- No biometrics. Cards and codes are enough for clocking in, and keep the system away from the most sensitive kind of personal data.
Who supplies what
| Layer | Who supplies it | What we do |
|---|---|---|
| Tablet | Customer, bought to our specification | Specify the minimum model, and test the app on the models they choose |
| Rugged case and wall mount | Customer, bought to our specification | Specify the fitting height, cable route and theft screws |
| Card reader | Us | Design the board and write its firmware |
| Kiosk app | Us | Build, test and maintain it |
| Platform and web application | Us | Build, host or hand over, and document |
| Payroll or accounting software | Customer | Produce an export file in an agreed format |
Requirements
The terminal records who arrived at which site and when, and gives a manager a record they can check and export. Each requirement can be tested, and the acceptance tests at the end say how.
| Ref | Requirement | Layer |
|---|---|---|
| R1 | Record a clock-in or clock-out when a person taps a registered card on the reader. | Reader, app, platform |
| R2 | Let a person clock in with a personal code when they have no card. | App, platform |
| R3 | Show the person's name and the result on screen for a few seconds, so they can see the right person was recorded. | App |
| R4 | Keep working with no network, store events on the tablet, and send them in order when the network returns. | App |
| R5 | Stamp every event with the time it happened, using a time source the platform checks. | App, platform |
| R6 | Stop a second tap by the same person within a set interval from creating a duplicate. | App, platform |
| R7 | Lock the tablet to the clock-in app, so staff cannot leave it or change settings. | App |
| R8 | Enrol a tablet to a site with a one-time code, and let an administrator disable it remotely. | App, platform |
| R9 | Show each manager the day's events by site and person, and let them add a correction with a reason. | Platform |
| R10 | Keep every correction and approval in an audit record that cannot be edited. | Platform |
| R11 | Produce a timesheet export in a format the customer's payroll software accepts. | Platform |
| R12 | Give each person, manager and administrator access only to what their role needs. | Platform |
| R13 | Accept signed firmware updates on the reader, and signed app updates on the tablet. | Reader, app |
| R14 | Be fitted by one person with ordinary tools, using the written fitting guide. | Mount, guide |
Tablet, case and wall mount
The customer buys these, so the specification says what to look for and what to avoid. It is written as a checklist the customer can take to a supplier.
| Item | What we specify | Why |
|---|---|---|
| Tablet | Current Android version with security updates still published, a screen of ten inches or larger, Wi-Fi, a USB-C port that supports a reader, and a battery that can run while on charge | The app needs a supported system, space for large touch targets, and a port for the reader |
| Power | Mains USB-C supply, with the lead run inside the mount or a cable cover | A tablet left on charge for months can wear its battery, so we also ask for a charge limit where the tablet offers one |
| Case | Rugged case with a corner guard, a screen cover and openings for the port and camera | Site walls and dust are harder on a tablet than an office |
| Mount | Fixed wall plate with a lockable cradle and tamper-resistant screws | Stops the tablet being lifted off or turned round |
| Position | Centre of screen at about 1.2 to 1.4 metres, away from direct sun and clear of door swing | Reachable standing, readable in daylight, and not knocked |
| Network | Site Wi-Fi with a signal check at the fitting point | Poor signal is the usual cause of delayed events |
Hardware outputs
A one-page hardware checklist for buyers, a fitting guide with drilling and cable steps, and a short list of tested tablet and case models once we have tried them. We do not supply or certify the tablet, case or mount.
Reader
The reader is a small board on a short USB lead, mounted beside the tablet. A microcontroller reads the card, checks it is readable, and passes the card number to the app over USB. It has no screen and no network, so the firmware stays small.
| Part | Job | Requirement |
|---|---|---|
| Card read | Reads the card's identifier from the NFC module and ignores a repeat read within a short window | R1, R6 |
| USB link | Presents itself to the tablet as a serial device, sends one line per read, and reports its own version | R1 |
| Feedback | Drives an LED and a buzzer: ready, read, rejected and fault | R3 |
| Update client | Installs only firmware signed by us, and keeps the previous image to go back to | R13 |
Rules the firmware follows
- It sends only the card identifier, never a name or any other personal data.
- It acts as a reader only: it cannot be told to write to a card.
- It restarts itself if it stops responding, and tells the app it did.
- It does nothing until the app has checked its version and identity.
Hardware for the reader
A microcontroller, an NFC reader module with its antenna, a USB-C connector, an LED and a buzzer, and a small plastic housing that holds the antenna against the front face. Schematic, layout, firmware source, a built prototype with test notes and a housing model are the outputs.
Android kiosk app
The app is the only thing the tablet runs. It listens to the reader, looks the card up, records the event and shows the person the result. It keeps working when the network is down.
| Screen or part | What it does | Requirement |
|---|---|---|
| Ready | Shows the site name, the time and "Tap your card" | R1 |
| Result | Shows the person's name, "Clocked in" or "Clocked out", and the time, then returns to Ready | R3 |
| Code entry | A large keypad for a personal code, with a limit on wrong attempts | R2 |
| Offline queue | Stores events on the tablet and sends them in order, removing each only after the platform confirms it | R4 |
| Clock check | Compares the tablet clock with the platform and flags a difference | R5 |
| Kiosk lock | Runs in Android's lock task mode, so the home and recent buttons do nothing | R7 |
| Enrolment | Pairs the tablet to a site with a one-time code, and stops working if an administrator disables it | R8 |
| Update | Checks for signed app updates outside working hours | R13 |
Rules the app follows
- The tablet stores card numbers and names for the site only, and nothing from other sites.
- Large type and high contrast throughout, with a sound and a colour for each result, so it works in glare and for people who cannot read the screen.
- An unknown card shows "Card not registered" and records nothing about a person.
- If the reader is unplugged, the screen says so and the code keypad stays available.
- A manager's screens are not on the tablet. They are in the web application.
Platform software
The platform receives events from every tablet, keeps them, and gives managers a day view, corrections and exports. It has an intake service, a store of people, sites and events, and a web application.
| Part | What it does | Requirement |
|---|---|---|
| Intake | Authenticates each tablet, accepts events, removes duplicates and confirms receipt | R4, R6, R8 |
| Event store | Keeps events as they happened and never overwrites them | R5, R10 |
| People and sites | Holds employees, cards, codes, sites and tablet enrolments | R2, R8 |
| Corrections | Lets a manager add a correction with a reason, shown beside the original event | R9, R10 |
| Timesheets | Builds hours per person per day from events and corrections, and flags a missing clock-out | R9 |
| Export | Writes a file for the customer's payroll software | R11 |
What the web application shows
- Today at each site: who is in, who has not clocked in, and tablets that have stopped reporting.
- A person's timesheet for a period, with each correction and who made it.
- Exceptions: missing clock-outs, events with a clock difference, and cards used at two sites close together.
- An approval screen where a manager signs off a period before export.
- Administration: people, cards, codes, sites, tablets and roles.
Accounts and access
There are three roles. A person sees their own hours, a manager sees the sites they manage, and an administrator manages people, tablets and exports. Every change to a role, card or tablet is recorded.
Platform outputs
The running service, source code and documentation, the event and export formats, and a plan for backups and for moving the service to another host.
Interfaces between the layers
Because this is a semi-stack project, several joints cross from our work to the customer's. Each is written down once, and tested from both sides.
| Joint | Between | What is agreed |
|---|---|---|
| Reader and app | Reader firmware, kiosk app | USB serial settings, the one-line read message, version and identity check, and the LED and buzzer commands |
| App and platform | Kiosk app, platform | Event format, enrolment, authentication, time, retry and confirmation rules |
| Platform and payroll | Platform, customer's payroll software | Export columns, date and time format, rounding rules and what a correction looks like in the file |
| Tablet and app | Customer's tablet, kiosk app | Minimum Android version, lock task permission and the update method |
| Installer and tablet | Person, tablet | Fitting steps, enrolment, and the checks that show it is reporting |
Example clock event
The values below are invented to show the shape.
{
"tablet": "example-site-01",
"event_id": "e-000457",
"type": "clock_in",
"method": "card",
"person": "p-0012",
"happened": "2026-01-01T07:58:12Z",
"sent": "2026-01-01T07:58:13Z",
"clock_difference_s": 0,
"queued_offline": false
}
Data protection
A clock-in record is personal data about an employee, so the design collects as little as it can and gives each person a clear view of what is held. This is design guidance, not legal advice, and the customer remains responsible for its own lawful basis and notices.
Built into the design
- No biometric data: no face, fingerprint or voice, only a card number or a personal code.
- The tablet camera and microphone are not used, and the app does not request those permissions.
- The reader sends a card number and nothing else. Names are held on the platform, not the reader.
- The tablet stores only the people at its own site, and clears its queue once events are confirmed.
- Codes are stored hashed, and wrong attempts are limited.
- Events are kept as recorded, and corrections sit beside them with a reason and an author.
- The customer sets how long records are kept, and the platform removes them at the end of that period.
What the customer must do
Tell staff what is recorded and why before the terminal goes live, decide how long to keep records, and decide who may see each site. People can ask to see their own record, and the platform can produce it.
Deliverables by stage
The baseline is semi-stack: we deliver the software and the reader, and the customer supplies the tablet, case, mount and payroll side. A full-stack variant is possible if the customer wants us to supply and set up everything.
| Stage | Semi-stack (baseline) | Full-stack variant |
|---|---|---|
| Specification | Requirements, interfaces, buyer's hardware checklist and test plan | The same, plus our own tablet, case and mount choice |
| Prototype | Kiosk app, platform and reader prototype, tried on the customer's chosen tablet | The same, on tablets we have chosen and fitted |
| Test | Tests against each requirement, with results written up | The same, plus a site trial |
| Handover | Source, reader design files, documentation, fitting guide and export format | The same, plus supply and fitting of units |
Indicative costs
These are the scale of costs for a project of this shape, excluding VAT. They are indicative, not a quote: a quote follows the specification, and parts prices move with quantity and supplier. Buying the tablet, case and mount off the shelf is what keeps the total down.
| Stage | Semi-stack (baseline) | What it covers |
|---|---|---|
| Specification | £1,500 to £2,500 | Requirements, interfaces, the buyer's checklist and the test plan |
| Prototype | £8,000 to £12,000 | Kiosk app, platform and a working reader, tried on your chosen tablet |
| Test | £1,500 to £2,500 | Every requirement tested and written up |
| Handover | £1,000 to £2,000 | Source, reader design files, documentation, fitting guide and export format |
| Design and build | £12,000 to £19,000 | The full-stack variant adds tablets, cases and mounts at cost, plus a fitting day per site |
Per site, bought by the customer
| Item | Indicative cost | Note |
|---|---|---|
| Android tablet | £150 to £250 | A current mid-range model that meets the checklist |
| Rugged case | £30 to £60 | With corner guard and screen cover |
| Wall mount | £25 to £50 | Fixed plate with a lockable cradle |
| Power supply and cable cover | £15 to £25 | |
| Card reader | £25 to £40 | Our board in its housing, at prototype quantities |
| Per site | £245 to £425 | Hosting the platform, where we host it, is in the order of £20 to £40 a month |
Acceptance tests and open decisions
Each requirement has a test that anyone can repeat.
| Ref | Test |
|---|---|
| R1 | Tap a registered card and check one event is recorded with the right person and time. |
| R2 | Enter a valid code, then a wrong one repeatedly, and check the limit applies. |
| R3 | Check the name, result and time show, then clear after the set interval. |
| R4 | Switch the network off, record events, switch it on, and check every event arrives once and in order. |
| R5 | Change the tablet clock and check the platform flags the difference. |
| R6 | Tap the same card twice inside the interval and check only one event is kept. |
| R7 | Try to leave the app with every button and gesture and check none works. |
| R8 | Enrol a tablet, then disable it from the platform and check it stops recording. |
| R9, R10 | Add a correction and check it shows beside the original, with author and reason, and cannot be edited. |
| R11 | Import the export into the customer's payroll software and check the hours match. |
| R12 | Sign in as each role and check each sees only what it should. |
| R13 | Install a signed update, then an unsigned one, and check the second is refused. |
| R14 | Have one person fit the mount from the guide, with ordinary tools, and time it. |
Open decisions
- Which payroll or accounting software the first export targets.
- Whether the platform is hosted by us or by the customer.
- Whether to support a second card type, or one only.
- How the tablet is managed in bulk: our own enrolment only, or an Android management service as well.
- Which tablet and case models to test first.
What this design does not claim
This is a concept design. It describes what we would build and how we would check it, not a product that exists.
- Nothing has been built or tested, and no figure here is a measured result.
- No certification is claimed for the reader, including radio and electrical approvals.
- The reader is not suitable for access control or for any use where a missed or false read could cause harm.
- A clock-in record shows that a card or code was used, not that a particular person was present.
- Rules on working time, pay and records vary, and the customer is responsible for meeting them.
- Part types and tablet requirements are examples, and are confirmed at the start of a real project.
Have a system like this in mind?
Tell us what it has to do, who will use it and which layers you already have. We will reply to arrange a conversation.