Restaurant Shift Handoff Without Messy Hours

It is 3:45 on a Saturday. Two servers from the lunch crew are wiping down tables and want to leave. The dinner cook just walked in the back door. The host for tonight is tying an apron. All of them are about to touch the same tablet by the pass within about ten minutes of each other. Get the order of taps wrong and you end up with a server whose clock-out never happened, a cook whose shift starts fifteen minutes late on paper, and a report you have to fix by hand on Monday.

Here is the sequence that keeps every entry honest during that overlap, using the shared-tablet kiosk. No logins, no app, just names on a screen.

Before the handoff: what should already be true

The tablet is mounted or propped where both crews pass it, usually by the kitchen door or the pass. It is on the kiosk screen showing the full name list, not locked and not on some other app. If you run one tablet for the whole restaurant, that is fine; the list holds everyone regardless of role.

Each worker's name is spelled the way they will recognize it fast. "Maria S." beats "Maria Sanchez" if there are two Marias and one of them is quicker to spot. This matters more than it sounds, because a rushed person tapping the wrong name is the most common way hours get crossed. If you have not set up the roster yet, walk through tracking part-time and shift staff hours first and come back.

The lunch crew clocks out first, one at a time

Do not let the outgoing crew wait for the incoming crew to arrive. As soon as a lunch server is actually done, they walk to the tablet, tap their name, and confirm the clock-out. The screen shows the entry closing. That worker is now off the clock at the real minute they stopped.

A few concrete rules for this step:

• One person at the tablet at a time. A line of two forming is normal at 3:50; a scrum of five is how the wrong name gets tapped.
• Clock out when the work stops, not when the paperwork idea occurs to someone twenty minutes later in the parking lot.
• If a server is helping seat early dinner guests, they are still on the clock. They tap out when they hand off, not before.

If you want the precise mechanics of closing an entry, the glossary entry for how a clock-out is recorded spells out what gets saved.

The dinner crew clocks in as they arrive

The incoming cook, host, and servers each tap their own name and confirm they are on. There is no reason to wait for the lunch crew to finish first. Two entries can happen within the same minute: a lunch server closing at 3:52 and the dinner host opening at 3:52. Those are two separate records tied to two separate names, and they will not collide.

This is the whole point of names-on-a-tablet rather than one shared punch. Every tap is attributed. When you pull the report later, you see exactly who overlapped and for how long, which is what you want to see during a handoff, not something to hide.

If your entrance and your pass are far apart, a second clock-in method helps. Some restaurants post a QR code by the back door so arriving cooks scan in on their own phone before they even reach the line. You can print one with the QR sign-in poster generator and skip the tablet crowd entirely for arrivals.

Label the overlap so reports stay filterable

If you track lunch and dinner as separate cost centers, use tags on entries so you can split them later. A tag like dinner on the incoming crew's entries lets you pull dinner-only hours for a week without eyeballing timestamps. Worker groups do the same job for people: a kitchen group and a front group let you report labor by area.

You do not have to tag during the rush. Tags can be applied to entries afterward from the dashboard. The rush job is only the clock-in and clock-out; the labeling is a two-minute cleanup pass whenever you have a breath.

What happens when someone forgets to clock out

Someone will forget. A lunch server gets pulled into a birthday table, then leaves through the front without touching the tablet. Their entry is still open at midnight.

This is where the auto-close behavior protects your numbers. A stale open entry gets closed at its start time plus your cutoff, not at the current time. So a shift that started at 11:00 with a four-hour cutoff closes at 15:00, not at 2:00 the next morning. A forgotten clock-out never inflates the hours you report. You will still want to correct the exact minute if you know it, but the default will not hand you a fourteen-hour lunch shift.

Closing the day and pulling the numbers

At end of night, open the dashboard and confirm nobody is still shown as on the clock who has actually gone home. Fix any obvious open entries. When the pay period ends, export the data. The CSV keeps the same columns every time, including a distinct-worker count, so payroll does not break because a header moved.

If you pay hourly, you will likely convert those clock times into decimal for payroll. The decimal and HH:MM hours converter handles that without a spreadsheet formula. From there the hours are ready to hand off to whoever cuts the checks.

Set the tablet up once, teach the crew the one habit (tap your own name, in and out, at the real minute), and the lunch-to-dinner handoff stops being a source of correction work. Want to see the tap flow before you commit? Try the live kiosk demo and run a fake handoff yourself.