Check-in that works where there is no signal

Most attendance products quietly assume two things: the employee's phone has a connection, and its clock is correct. Both assumptions fail at exactly the sites where attendance matters most—a dairy shed, basement, remote yard, cool room, or gate at the edge of coverage. An offline attendance system needs to preserve an honest event without pretending the network is always available.

Why offline punches are harder than they look

When a phone loses signal, the punch has to queue locally. The trap is storing whatever the phone clock said and treating it as truth. A slow clock shifts the punch and everything downstream with it: late rules, expected hours, overtime, and payroll inputs. A fast clock can make an honest punch appear to come from the future.

A stronger record carries several pieces of evidence together: the device timestamp, the device's known clock offset, the capture method, the site or kiosk identity, and the time the server eventually received the event. The system can correct ordinary clock drift while preserving the original evidence for review. It should never silently replace one timestamp with another.

Four attendance patterns for unreliable sites

No single check-in method fits every frontline environment. The practical options are:

• Mobile GPS check-in when the worker has a connected phone and location evidence is appropriate.
• A printed site QR code when the priority is a simple, low-cost checkpoint at a stable location.
• A rotating kiosk QR code when a connected shared screen can issue short-lived codes that resist photo reuse.
• An offline worker code scanned by an online kiosk when the worker's phone cannot connect or its clock should not be trusted.

The last pattern reverses the usual kiosk. The worker's phone creates a short-lived signed code without a network connection, and a fixed kiosk scans it. Physical presence is established at the kiosk, while the recorded attendance time comes from the connected server path. The worker's phone connection and local clock no longer determine the payroll event.

What managers and payroll need to see

Offline support is not complete when the app merely says that a punch will sync later. Supervisors need to distinguish a normal queued event from a duplicate, expired code, rejected location, corrected clock, or event awaiting review. Payroll needs the final accepted time, the rule version applied to it, and a trace of any approved correction.

A good implementation also defines what happens when two devices submit the same event, when a phone stays offline for several days, and when a kiosk itself loses connectivity. These are operating rules, not edge cases to leave until rollout.

Crewtide supports multiple attendance methods per site so an operation can choose the trust model that matches its conditions. The objective is simple: capture the work honestly at the point it happens, preserve the evidence, and make exceptions visible before hours move to payroll.