Use cases
The way shift work actually runs.
Formclock is pre-launch, so these are illustrative scenarios. They describe what the shipped product does for each kind of operator, not customer quotes.
Sunday scheduling drops from hours to minutes. The coverage agent does the first pass and the GM just approves it.
Kiosk verification photos stop buddy-punching, so recorded hours match reality and payroll stops leaking.
Staff are shared across stores instead of over-hiring, so labour stays in budget without slamming anyone.
A no-show no longer stalls the dock: standby coverage is lined up before the shift even starts.
Fair-rotation numbers are visible to everyone, so on-call stops being an argument.
When occupancy jumps, the front desk staffs up to demand in minutes.
Setup takes an afternoon and the team is on the kiosk the same day.
The outcomes the product is built to move.
No measured customer results yet, so no invented ones. These are the design targets: the four outcomes the product is built to move for an operator.
Staff to traffic, share across stores
Traffic-based staffing and shared staff across locations, without over-hiring.
Standby coverage before the dock stalls
Standby coverage lines up the moment someone is a no-show.
Rotation everyone can see is fair
On-call stops landing on the same people; the whole team can see it's even.
Clean publishes, every time
Overtime and availability are checked before a schedule ever goes live.
See it with your own schedule
Set up a workspace, add your team, and build a week. It takes about ten minutes and costs nothing.
Start free