Every tap counts,even offline
One tap records attendance in under a second — stored on the device, synced the moment your connection returns. No internet, no excuses, no lost records.
- Sub-second tap
- Works fully offline
- Clone-proof cards
Attendance hardware and software built for sites where the network cannot be trusted, engineered to stay
Everything attendance should have been from the start
Five parts, each one built so that a failure somewhere else does not stop a tap from counting.
Three steps, then it runs without you
- 01Step 1
Import your people
Upload a roster or connect the system you already run. Groups, shifts, and schedules come across as they are.
- 02Step 2
Hand out the cards
Each card pairs to one person in seconds. Readers need nothing beyond power to start accepting taps.
- 03Step 3
Read the day
Attendance appears as it happens — and keeps appearing when the internet does not.
Anywhere people show up and someone has to know





The claims, and the mechanism behind each one
The network is the one part you cannot control. So nothing waits for it.
A tap is committed to local storage before anything is sent. Sync is a background job, never a precondition.
0
Readers accept taps through a full outage.
1
One tap is the entire interaction. No PIN, no signature, no queue.
Queued records replay in the order they happened.
Duplicates collapse on identity and time rather than on arrival, so two readers recording the same person produce one record.
Attendance data is personnel data — treat it that way
Four properties that hold whether or not the site is online.
Encrypted at rest and in transit
Records are encrypted on the reader, on the device, and on the wire between them.
Challenge-response cards
Cards authenticate with a rotating challenge, so reading a card does not let you replay it.
Append-only history
Corrections are new entries, never overwrites. The original record stays auditable.
Scoped access
A supervisor sees their own group. Nobody browses the whole organisation by default.
Get in line for the first rollout
Pre-registration is a place in the queue, not a contract. Tell us where you are and what you run, and we will come back with a phase and a timeline.
Questions worth asking before you commit
Stop losing records to a dropped connection
Put your roster on a system that keeps counting when the line goes down.


