Live founding pilot
Every punch gets an honest receipt.
Record work even when identity, location, or connectivity is uncertain—then route the exception to the right person before payroll closes.
For 10–100-person restaurants, cleaning firms, retail, care, events, schools and multi-site teams. Audit free; no payment today.
01 / Product system
Four layers between a punch and clean payroll.
Capture the original event, surface the exception, assign a decision and preserve the export trail. Each layer is visible; none silently overwrites the one before it.
02 / Resolve
Resolve the exception before it reaches payroll.
Select a node to inspect what happens there. Drag empty space to pan, use the controls to zoom or fit, and follow the highlighted exception path when the happy path breaks.
Read the workflow as a list
- Punch attemptThe attempt is recorded immediately instead of being erased by weak GPS, identity or connectivity.
- Local receiptThe employee receives a timestamped, device-local receipt and can see whether it has synchronized.
- Evidence contextSchedule, device, network and location confidence are attached as evidence, not treated as a verdict.
- Exception classifierMissing out-punches, offline events, overlaps and geofence uncertainty receive distinct states.
- Manager decisionThe manager accepts, corrects or rejects with a reason while the original event remains intact.
- Payroll exportOnly resolved time enters the payroll CSV, accompanied by a decision and acknowledgement trail.
- Exception queueThe employee and manager see who must respond, why the item is blocked and when payroll closes.
Workforce timekeeping
Capture first. Resolve uncertainty before payroll.
Each app starts with a workflow customers already pay for and repeatedly describe as fragile. The live product boundary is deliberately narrow enough to validate before expanding.
Capture the punch
Create a local receipt even when the network or location check is uncertain.
Name the exception
Late, offline, geofence, identity and schedule mismatches get distinct states.
Ask for context
Employee and manager add evidence without editing the original event.
Close before payroll
Acknowledgements and corrections export with a visible decision trail.
Complaint-first product design
Built from repeated failure patterns.
Counts come from one-to-three-star US Apple App Store reviews collected on 2026-07-30. Themes may overlap; app spread matters because a problem repeated across competitors is harder to dismiss as one bad release.
Read methodology and limitations →| Recurring complaint | Reviews | Apps |
|---|---|---|
| Clock-in, punch and timecard failures | 203 | 8 / 8 |
| Schedule, shift and availability friction | 195 | 8 / 8 |
| Updates that break frequent actions | 184 | 8 / 8 |
| Sign-in, logout and access failures | 102 | 8 / 8 |
| Geofence clock-in failures | 50 | 6 / 8 |
First boundary
What belongs in the pilot.
- Schedule import
- Punches and offline receipts
- Correction requests and acknowledgements
- Exception inbox and payroll CSV
Not claimed
What stays outside.
- Payroll-tax filing
- Hiring or benefits
- Face recognition
- Surveillance or full HR claims
Founding offer
A real price, before a big commitment.
Start with a free workflow audit. If the problem and scope fit, reserve a small founding pilot with transparent boundaries.
Workflow audit
Free
One anonymized broken workflow, mapped into states, exceptions and a proposed pilot boundary.
- 30-minute working session
- Flow map and scope recommendation
- No product or purchase required
Founding Pilot · one time
€199
One location, up to 20 active workers, setup and a 90-day pilot.
- Direct onboarding and workflow setup
- Founding feedback channel
- Optional planned continuation: €39/month
No payment today. The one-time pilot fee becomes payable only after a usable pilot matching the written scope is ready for your team. Any continuation is optional and agreed separately.
Clear answers
Before you raise your hand.
Is Clockstead a payroll system?
No. The first scope prepares clear timekeeping evidence and corrections for payroll export; it does not calculate or file payroll taxes.
What happens when GPS is uncertain?
The punch attempt is preserved with its location confidence and routed for resolution. Imperfect GPS does not automatically erase the event.
Can managers edit punches?
The live pilot preserves the original record and attaches requested changes, reasons, decisions and acknowledgements.
Is there a working product?
Yes. A limited founding-pilot PWA is live at /app/ with schedule import, offline punch receipts, corrections, acknowledgements, manager resolution and payroll CSV.
Complaint wanted
Bring us the workflow that broke.
Show us the last exception that cost time, trust or money. Start with the free audit or reserve the clearly scoped founding pilot.
Compare the two starting options →