Offline punch capture for unreliable timeclock setups

When the ADP website goes down mid-shift — and users say it goes down 'frequently in the middle of the workday' — the only fallback is paper and pen. Someone writes times on a notepad, and at some point an admin manually keys every punch into the system. That manual entry step is where errors multiply: handwriting is misread, someone forgets to submit the sheet, or punches get keyed into the wrong employee profile.

The reason this hasn't been solved cleanly is that it requires an independent system that employees already have on them and trust to work when the main system doesn't. That means a mobile-first offline mode. ADP has no incentive to build a robust offline fallback — doing so would mean admitting the primary product is unreliable, and it adds engineering complexity that benefits the customer but doesn't help ADP sell new seats.

What users are actually doing: physically writing times down, or hoping they remember their arrival time well enough to self-report later. One complaint describes needing to 'use paper and a pen to clock in' when the system is down. Another describes the site going down and requiring 'manual entry of all employee punches.' Both describe the same failure mode — no structured fallback means the data either gets lost or gets reconstructed from memory, neither of which is reliable for payroll.

This is a business because downtime events recur unpredictably and the cost of a single payroll correction is concrete — but more importantly, the compliance risk is real. In states with strict wage and hour laws, an employer who can't prove exact punch times is exposed. That exposure doesn't disappear just because the primary system came back online. The need to have a defensible record of when employees attempted to clock in — not just when the system recorded it — is a recurring legal and operational need, not a one-time setup.

What to build

Build a Progressive Web App that employees install once and use to log punches locally with a GPS-stamped timestamp when the primary HR system is unreachable, then automatically syncs those records to the employer's ADP account via API when connectivity is restored, with a manager review step before sync to catch conflicts.

Where to start

Target construction general contractors first — they already deal with field workers who have no reliable wifi, they're accustomed to paper timesheets as a backup, and the legal exposure from missing punch records on prevailing wage jobs is high enough that a safety net has obvious dollar value to justify a purchase conversation.

The hard part

Employees will use the offline backup app inconsistently unless it's dead simple and already installed before the outage — which means you need to sell adoption during normal operations, before anyone has experienced the pain, and that's a hard behavioral change to drive without a triggering event.

How it makes money

Per-employee per-month pricing at roughly $2–$4 per active hourly employee, billed to the employer, with the first 30 days free so adoption can be established before the first invoice.