Workforce

Hours that hold up in an argument

Everything about time in DineStack is built for the conversation three weeks later, when somebody says their hours are wrong. Nothing stores a total, nothing is edited, and every correction has a name and a reason on it.

  • Certified offline clocking
  • Corrections keep the original punch
  • Included in the price

Clocking

Two ways to clock, one timeline

Both produce the same clock events on one employee timeline. A punch carries how it was made, which is evidence rather than a change to the hours.

Default

The restaurant clock

A staff clock on the counter tablet. Nobody needs to own a phone to use it, which is why it is the default rather than the fallback.

Clocking checks in as it happens, so unlike the till it needs the connection. If the restaurant is offline the clock says so and the punch waits, rather than recording an hour nobody can stand behind.

Opt-in

The employee’s own phone

Off unless a restaurant turns it on. When it is on, the server checks where the phone was: inside the workplace area, with a fresh enough fix, accurate enough to mean something.

The phone reports what it observed and never its own verdict. A device deciding whether it is allowed to clock in is a device somebody can talk into it.

A manager reviewing hours sees “restaurant clock” or “mobile, geofence verified” beside the time — not because it changes the hours, but because it is what the hours rest on.

Managing

One screen, read in seconds

Who is working, who is on break, who is late, who is close to overtime, and what needs a decision.

A live board

What labour is costing right now, beside who is on the floor. One screen rather than a report run after the fact.

Timecards with the punches under them

Daily and weekly totals, with the events they came from. A correction sits beside the original punch rather than replacing it.

A weekly rota

Plan the week, publish it, copy it forward. Schedule against actual shows late arrivals as facts — there is no punctuality score, and there is not going to be one.

Overtime before it happens

Worked hours plus rostered hours, projected. Overtime a manager hears about on payroll day is a cost they could not avoid; on Thursday it is a rota change.

Tips by where the money physically is

Card tips are in the bank. Cash tips are already in a pocket. Pooling divides by allocation, so what comes out of a pool equals what went in — to the cent.

One attention queue

Missing clock-outs, breaks nobody came back from, unplanned shifts, disputed hours. Grouped by kind, never tallied against a person.

Overtime

Your policy, not our guess

Overtime rules differ by state, by province, sometimes by contract, and they change. DineStack does not know your labour law and does not pretend to.

Stage 1

You record the thresholds

The work-week start, the weekly and daily thresholds, double time if it applies, and what each is multiplied by.

Stage 2

The policy is versioned

With effective dates, so correcting a threshold today does not silently restate every week you have already paid.

Stage 3

Hours are divided by it

Regular, overtime and double time — from the punches that were actually recorded, never from a stored total.

Stage 4

It reads back the same

A June timecard reprinted in October reads June’s policy, because the version is part of the record.

What we will not say. DineStack does not claim your configured policy is lawful anywhere. It says “your configured labour policy, applied to the hours we recorded” — and the arithmetic is what we stand behind.

Payroll

Payroll-ready, not payroll

DineStack is not a payroll provider. It does not calculate tax, withholding or net pay, and it is not going to.

Hours per person, per shift
Split into regular, overtime and double time by your own policy.
Breaks and corrections
Corrections listed rather than baked in, so the file shows what changed.
Tips broken out by where the money is
Card and cash separately, with the currency stated on every row.
CSV or JSON
The file your bookkeeper or your payroll provider needs, in either shape.
It will not say Ready while it is not
An open shift, a disputed timecard or a row nobody can put a name to keeps the period out of Ready. You can still export it — and if you do, the file records that you chose to.
Get started