Restaurants are the hardest place in the small-business world to run a clean timesheet. Front-of-house punches in for the lunch rush, kitchen never punches out, the host swaps shifts twice in one Saturday, the new server forgot to clock out at midnight, and California meal-break rules want a fifth opinion. Here’s how to set up time tracking that actually fits a restaurant — kiosk at the door, geofences that cover the patio, OT rules that match your state, and exports that don’t lose tipped wages.

The 30-minute restaurant setup

Most restaurant owners over-engineer the first version. Start small, then layer. Here’s a clean 30-minute setup that covers 80% of the cases.

1. Add the location and draw the geofence

Pin the address. Default radius is 100m, which usually covers the dining room and parking lot. For restaurants with a patio across the street or a dumpster down the alley, push to 150m. The cost of a too-tight geofence is a kitchen lead failing to punch in after taking out the trash; widen by 50m before going live.

2. Set up kiosk mode

Park a tablet at the staff entrance — any iPad or Android tablet works. Open the kiosk URL, enable always-on display, plug it in. Each employee gets a 4-digit PIN. Kitchen staff especially appreciate this; nobody wants a personal phone with food-prep oils on it.

3. Build the schedule

Recurring templates for common shifts (Sat lunch, Sat dinner, Sun brunch). Open shifts for callouts. Shift swaps with manager approval. Conflict detection catches the “double-booked Maria” case before it happens.

4. Configure compliance rules

California: 30-minute unpaid meal break before the 5th hour, second 30-minute break before the 10th. New York: 30-minute meal break for shifts over 6 hours. Massachusetts: 30 minutes for shifts over 6 hours. Configure the rule once per location; violations route to the exception inbox automatically.

5. Add overtime thresholds

Federal default is 40 hours/week. California adds daily OT after 8 hours, double-time after 12. Configure the rule per location, and the engine flags violations the moment they cross.

Kiosk vs personal phones — which fits a restaurant?

Almost every restaurant ends up using both:

Kiosk for kitchen and dishwashers. Tablet at the door, PIN entry. No phones in the line.
Personal phones for FOH managers.They’re floating, opening, closing — phone-based GPS keeps them flexible.
Personal phones for delivery drivers. Per-trip GPS, geofences at the restaurant and at delivery zones if you operate a fleet.

Handling overtime and meal-break compliance

Restaurants are the highest-violation industry for meal-break rules — partly because shifts run long, partly because the line gets slammed and breaks slip. A real compliance engine does three things:

Flags violations as they happen, not at end-of-week when payroll runs.
Routes them into one inbox the GM clears each shift change.
Keeps an audit trail per rule, so you can prove compliance if a state agency asks.

Tips, hours, and the payroll export

Tips don’t belong in the time clock. The time clock’s job is hours worked. Tips — declared, pooled, distributed — are a payroll-side concept that varies by state. Best practice:

Export hours from ClockOut at end-of-period.
Enter tips in your payroll provider per employee per shift.
Run gross pay; provider handles tip-credit math per state.

Most restaurant owners we talk to use Gusto or Square Payroll for tip handling. Both accept ClockOut’s hour exports directly.

Shift swaps without text-message chaos

Restaurants have the highest swap rate of any small business. The default — managers fielding swap requests by text on a Saturday morning — costs everyone time and breaks half the coverage gaps.

Configure shift swaps in-app: employee A posts the shift, any eligible employee B can claim it, manager sees the request, approves with one tap. Eligibility rules (qualified for the role, no overtime trigger, available per their availability record) prevent 90% of bad swaps automatically.

Restaurants in numbers

~15% of restaurant workers report having buddy-punched in the last year.
~40 minutes of average daily timesheet drift per FOH employee on paper systems.
~$38B annual U.S. restaurant labor-cost overrun attributed to time-tracking errors and OT mismanagement.

FAQ

What’s the best time clock for a small restaurant?

One that supports kiosk mode at the door, geofencing for FOH managers, and a compliance engine that handles meal breaks. ClockOut, Homebase, and 7shifts all qualify; pricing model is the main differentiator.

Do I need a separate app for tips?

No — tips are handled in payroll. The time clock tracks hours; payroll providers (Gusto, Square Payroll, Toast Payroll) handle tip declaration and tip-credit math.

How do I track minor (under-18) hours?

Configure per-employee hour caps and shift-end limits in the rules engine. Most states require under-18s to stop work by 9 or 10 PM on school nights — set the rule once per state, the engine enforces.

Can the kitchen and FOH share one schedule?

Yes, but split into roles. One schedule, multiple role lanes — kitchen doesn’t see FOH’s open shifts, FOH doesn’t see kitchen’s. Cleaner than two separate schedules.

Time Tracking for Small Restaurants: A Practical Setup Guide