Time cards

The shift they worked,
not the one you remember.

Somebody forgets to punch out. Three weeks later the hours are questioned and the only answer anybody has is a text message. Here is what replaces it.

The punch

Their own phone, or the
iPad already at the stand.

A valet clocks in from the phone in their pocket. On shared hardware the iPad is paired to a location by a manager, and everybody signs in with their own four-digit PIN, so a shared device never becomes a shared identity.

One shift

A punch is an event, not a field.

In, break, back, moved stand. Four things happened and the card is four things long. Nothing has been typed into it.

Then nobody clocked out

The record notices before you do.

The shift ended and he was still on it. That raises a flag with the shift behind it, and deliberately invents no time to close it with.

The fix

A correction is another event.

A manager supplies the time, with a name and a reason on it. The shift closes and the totals recompute. Nothing was edited in place.

What you can hand over

The line at the top is computed.

Six rows, in the order they arrived. Replay them again next month and you get the same shift, which is what makes it worth defending.

Approval

Approving is what locks it.

A period will not approve while a location still has cards waiting, and the server re-checks that itself. The button on the screen is advisory.

Owen DelgadoSat 22 Aug · Brickell Flatiron · scheduled 15:00–23:00OpenNeeds reviewApproved

15:0017:0019:0021:0023:0014:52break 28mGarage P2

14:52Clocked inFront driveOwen D.

18:10Break startedOwen D.

18:38Break endedunpaidOwen D.

20:05Moved standFront drive to Garage P2Owen D.

23:20Still clocked inshift ended, nobody punched outsystem

23:06Clocked outcorrection: forgot to punch outSofia M.

8h 14m

Gross

28m

Unpaid break

7h 46m

Net, to payroll

Nothing else at Brickell Flatiron is waiting.

Correction23:06Clock out

Sofia Marchetti

Reason: forgot to punch outAdded to the record. The flag above it stays where it is.

Why it holds up

Six events in.
One shift out.

The card is not a form somebody filled in and somebody else changed. It is a stream of events with a name on each, folded into one shift the same way every time it is read.

Punches stay event-sourced

Original events preserved

One computed shift

Breaks and overtime

The day ends at midnight.

A break is punched, and an unpaid one comes off the net by itself. Overtime is figured against your thresholds - daily, weekly, double time - and a shift that crosses midnight is split there, so its hours land on the day they were worked, in the timezone of the location that worked them.

Minutes already paid as daily overtime are then held back from the weekly threshold, so no minute is ever paid at an overtime rate twice.

On the ground

What actually keeps a punch honest.

Four controls, and every one of them holds on the server rather than in the app that draws the button.

The station belongs to a placeA manager pairs the iPad to a location, and it signs its own punches. Revoking it is one action.

A PIN, not a passed-around loginEvery person at a shared stand punches under their own four-digit PIN, and the PIN is never stored where it could be read back.

A location that is switched off takes no new shiftsRefused on the server, not hidden in the app. Shifts already open there can still be closed, because stranding one would be worse.

Punching somebody else is a manager's jobFrom a personal phone, only a manager may clock another person in or out, and every event carries who did it.

There is no GPS fence here, and we will not describe one. The apps show a valet how far they are standing from their stand. Nothing on the server decides a punch by reading a phone's location, so nothing on this page pretends it does.