The time clock that proves who clocked in.

Every clock-in is the credential your team already wears — a badge tap, or a QR code on the name tag — plus a framed photo. The tap or scan proves the credential was there; the photo shows who was standing at the clock and whether the tag was worn — a person reviews it, and On Post never uses facial recognition. Anything that needs a second look, such as a PIN typed instead of a badge or a clock-in with no photo, is flagged for a manager rather than passing quietly into a timesheet.

Any modern tablet or desktop computer with a camera, on a wall or at a counter, is the shared clock. PINs need nothing else. QR codes need a printer: each person’s code downloads at print size and goes on the name tag. Badge tap adds a USB badge reader (13.56 MHz), a card for each tag holder, and a tablet that takes USB accessories, such as an iPad or the Samsung Galaxy A series; Amazon Fire tablets cannot use the reader. There is no app to install — the clock, the manager side and the team app all run in a browser.

Badge taps and QR codes keep working. Each clock-in is saved on the tablet the instant it is tapped and sends itself, exactly once, the moment the tablet has any connection — the store wifi or a phone hotspot held near it. A PIN needs a connection, because a PIN is a secret the tablet never stores. On the manager side, a clock quiet for half an hour is named on the board and in Attention, and an email goes out if it stays quiet for two hours during the day, so nothing waits unnoticed until payroll.

Only if you allow it, per person, at one of three levels: the shared time clock only (the default), their phone within a geofence around your location, or anywhere — for a driver who finishes after close. A phone clock-in from outside the fence is recorded and flagged, never silently accepted.

As your policy says. Where breaks are paid and not clocked, each shift earns its break by length and the clock shows no break button — a button no one should press is how missing clock-outs happen. Where meal and rest breaks are clocked, each kind is paid or unpaid as you set it, time past the allowance can go unpaid, and a required break that was not clocked is noted on the timesheet.

Pay periods run weekly or biweekly from the start day you choose. Overtime follows the federal 40-hour workweek, or California’s daily rules where you have a location there. Paid time is exact by default, or rounded to the nearest 5, 6 or 15 minutes — always the nearest, never down. Timesheets and the payroll file carry regular and overtime hours already split.

Timesheets export per pay period as the file your payroll provider imports, or as a CSV, carrying each person’s payroll file number and legal name. A provider file will not build while someone with hours has no file number, and it says who, so no one’s hours are silently dropped.

Yes. Import, under Settings, reads the time cards and the team list your previous provider exports — a CSV or an Excel file that names a person, a clock-in and a clock-out, as it comes. Time cards become real records on each person’s timesheet, with hours, overtime and breaks worked out under your own settings, and people are matched to anyone already on your team. Wages, tips and PINs are not imported.

Every new business gets 30 days of the whole product, with no card to enter. When the trial ends you are on the Free plan unless you choose another — free, with no time limit, and nothing you recorded is removed. What each plan includes is on the pricing page, and you can change plans whenever you like.

Your timesheets export as payroll files or CSV for any pay period, and closing your account keeps your records readable for as long as the law requires — they do not vanish. Time records are append-only by design; a correction records who changed what, when, and both the before and the after, so what you export is what actually happened.