A rule change doesn't rewrite last month
Policies are versioned. Change a meal window today and yesterday's shifts are still judged against the policy that was in force when they happened, not the one you just wrote.
The shift, hour by hour
A day, judged against the rules that were in force when it happened.
Most clocks record a start and an end. The expensive part of a California shift is everything in between, and what a claim turns on is which policy was live on the day.
- 8:00
Clock in
Location and device recorded on the punch, not on the timesheet afterwards.
- 12:45
Meal owed by hour 5
The window opened at 13:00. Clementime watches it approach; it does not lock the door.
- 13:04
Meal taken
Inside the window. Nothing is owed, and the record says why.
- 18:00
Second meal by hour 10
A ten-hour shift opens a second window. Judged against the policy in force today, not the one written next quarter.
- 18:30
Clock out
The shift closes against the policy version it began under.
Corrections leave a trail
Timecard corrections, punch overrides and lifecycle exceptions each have their own queue and their own record, so an edit is visible as an edit rather than as a number that quietly changed.
It never stops someone clocking in
A missed meal is flagged, recorded and surfaced to a manager. It is never a locked door in front of an employee who needs to start work, which is both what the law expects and what operators actually want.
One primary action. Never a wrong button.
The clock only ever offers the one action that makes sense next. There is no way to clock in twice or skip a break punch, so there is nothing to clean up later.
Break reminders, not break policing
The employee gets an advisory prompt before a meal is due. The compliance record is built from the actual punches when the shift closes — and reviewed by a person. It warns; it never decides pay.
California sick leave, at the current figures
One hour accrued per 30 worked, a 40-hour annual usage cap, an 80-hour accrual cap, and 90 days after hire before leave can be used — as the policy defaults, and every one of them versioned so you can change it.
Daily California split, then the period
Up to 8 regular, 8 to 12 overtime, over 12 double-time, per day — then rolled into the pay period with PTO and sick from the ledger. Hours and identifiers go to payroll; pay is computed there.
A ledger, not a number
A balance is built from every event behind it — accrual, use, carry-over — never a figure somebody can type over. Crediting the same accrual twice cannot happen.
Who is on the floor, right now
The Manager Console updates itself every five seconds: who is on, the headline numbers, and a force clock-out that records its reason. Nobody has to remember to refresh anything.
One AI feature: the staffing forecast
It reads your coverage history and suggests how many people you will need at peak. It explains patterns; it never approves, blocks or adjusts anyone's time.