When Do I Need to Clock In or Out at Work?

The short answer for a real restaurant shift

You need to clock in when your actual work starts; for time recording, the start, end, and duration of working time must be documented (BMAS FAQ on working-time recording). You clock out for a real break if your break is recorded that way, and you clock out at the end only after your last required task is finished. It is not automatically the moment you enter the building, not just the rota time, and not simply the point when the last guest has left; what matters is the real start, the real interruption, and the real end of your work.

I organise this from the daily reality of hospitality. For a server, work may start with the briefing, taking over a section, or the first setup task in the dining room. For a cook, it may start with mise en place, checking deliveries already waiting, or setting up the station. For a bartender, it may be restocking, preparing garnish, or opening the bar for service. In the same way, work does not end halfway through the closing routine. It ends after handover, reset, storage, and the last duty that genuinely belongs to the shift.

Arriving early does not automatically mean working time

A common misunderstanding is, "I am already here, so I must already be clocked in." In practice, that is too simple. If someone arrives early, hangs up a coat, has a coffee, chats privately, or waits for the shift to begin, that is not automatically working time. The key question is whether the person has already taken on a business task. Imagine a server arrives twelve minutes before the planned start, puts away a bag, and looks around the room. If no task has started yet, that is not a clean clock-in point. If a supervisor then says, "Please set up the terrace now," work has begun, and that is the moment to clock in.

To keep helpfulness from turning into unpaid grey time, I separate voluntary early arrival from actual assigned work. I do not tell my team, "Just come a bit earlier and see what needs doing." I define what is still personal time and what counts as the first operational task. That protects both sides. Staff do not have to start quietly helping and later argue about whether those minutes mattered. I can also explain fairly why simply being present before the shift, without any task, is not yet the start of recorded work. Clear language prevents more conflict here than later corrections ever can.

What the first real task looks like in service, kitchen, and bar

The difficult part is usually not the rule itself but the first concrete action. I treat work as having started when someone is available for the business and takes over an intended task. A typical example from evening service is a briefing at 4:55 pm for a 5:00 pm shift because a large wave of reservations is expected. If attendance at that briefing is part of the role, the person clocks in before it starts. Another example is a cook who is already in the kitchen at 10:50 but does not begin station setup until 11:00. In that case, 11:00 is the correct clock-in moment. Presence alone is not the same as work, but assigned activity is.

I make this predictable by giving role-specific examples instead of leaving every employee to guess. Service starts when the section is taken over, the briefing begins, or the first setup task is assigned. Kitchen starts with actual preparation at the station, not with merely standing in the room. Bar starts with the opening steps that belong to that station. If we use Bonzumo, the time clock helps us capture these working times in a traceable way, and exceptions can later be reviewed instead of guessed. But software does not replace management. I still need to define the operational start clearly so that "just helping for five minutes" does not disappear from the record week after week.

Breaks only count as breaks when the person is truly free

The same logic applies to breaks: clocking out only fits when the interruption is genuinely free; for working-time recording, what matters is the real interruption, not just a break entered on paper (BMAS FAQ on working-time recording). If someone only quickly drinks water in the back room but still remains approachable, has to hear the phone, or is called straight back out when it gets busy, that is not an organisationally genuine free break. A realistic example is a bartender sitting in the staff room for twenty minutes, eating, serving no drinks, and being covered by a colleague. Then clocking out for the break is clean; if that same person keeps answering orders or briefly handles a delivery, the interruption was not a real break after all.

I organise breaks around availability and cover, not only around the number of minutes. When someone is on break, they should know whether they are truly out or merely under less pressure for a moment. Restaurants often create frustration by recording breaks on paper while the employee remains effectively on call. That is unfair to staff and it also gives me poor time data. My solution is simple: the shift lead states who covers whom, whether the person is fully released, and what happens if the break is interrupted. That makes later questions much easier to answer and prevents "breaks" that were never really free in the first place.

Clocking out at the end means after the last required duty

You do not clock out just because the last guest has paid or the kitchen has received its final ticket. In hospitality, every shift usually includes closing work. In service, that may mean resetting the station, sorting glassware, returning the card terminal, checking for open issues, or handing information to the late team. In the kitchen, it can mean securing chilled items, labelling containers, cleaning surfaces, and leaving the station ready for the next shift. At the bar, stock return, till-related steps, and a proper shutdown may still be part of the role. The right clock-out moment is therefore after the last mandatory step, not after the last visible guest contact.

One of the biggest fairness mistakes a business can make is to treat closing work as if it were optional lingering. I avoid that by defining what belongs to the shift for each area and what is private time after release. If two employees stay behind to chat after the handover is complete, working time has already ended. If waste routes, storage, reset, or a documented handover are still pending, they stay clocked in until those duties are actually finished. That distinction matters because time records are only useful when they reflect the real shift instead of an idealised version of it. The broader operational picture behind that sits in Connect the work behind every successful service.

What to do if someone forgets to clock or the recorded time is wrong

If you forget to clock in or out, report it immediately. The longer a case sits, the more memory turns into approximation. A typical example would be a cook who starts preparation on time, then notices only after the first orders that no active session was started. Another would be a server who finishes the shift, gets pulled into a final reservation question, leaves, and notices at home that the session was never ended. The right response is not to guess roughly at some later date. The right response is to reconstruct the case quickly: when the first real task began, when the last duty ended, whether there was a genuine break, and what caused the recording error.

I handle corrections through a clear exception process instead of through vague trust or vague suspicion. Bonzumo supports personal sessions, exception-related review, working-time accounts, and role-based permissions, so I can keep responsibilities clear when a time needs correction. In practical terms, that means not everyone changes everyone else's times. The employee reports the issue, the shift lead or office reviews it, and the correction is made in a traceable way. If mistakes repeat, I first inspect the process itself. Maybe the shared device is placed badly, maybe the briefing starts too abruptly, or maybe the team lacks one clear routine. Good organisation prevents more errors than a stricter tone ever will.

Why the rota is only the plan and the time record is the reality

The rota answers only part of the question. It shows when someone is scheduled. Time tracking shows when the person actually worked, paused, and finished. In a restaurant, that difference matters every day. A shift may be planned from 5:00 pm to 11:00 pm, but a pre-service briefing starts at 4:50 because a coach party is due, and the final handover finishes at 11:14. Or the reverse happens: a counter shift is scheduled to start at 11:00, but because a delivery problem delays meaningful setup, real work begins later. The plan remains important, but it does not replace the real sequence of the shift.

That is why I link planning and time capture without treating them as the same thing. The rota is my intended staffing, the time record is my factual working time. Only with both can I talk fairly about extra time, missed breaks, early helping, or idle waiting. My practical rule for the team stays simple: clock in immediately before the first real task, clock out for a genuine free break, clock back in when work resumes, and clock out finally after the last required duty of the shift. The biggest pitfall is inconsistency. If managers silently expect early work, record breaks that were not free, or sometimes count closing work and sometimes do not, no time system will feel fair. That is why I build the routine clearly in the shift organisation itself, supported by Give your team a clear start to every working shift.