Working Time vs Presence Time in a Restaurant

Working time is actual work; presence time is only being there

Working time and presence time are not the same. Working time is the period in which someone is actually working or carrying out an instructed activity that is necessary for the job. Presence time only means that someone is at the business or available on site for the business. So presence time can include working time, but it does not automatically equal it from start to finish. In hospitality, that distinction matters because a shift can contain visible quiet phases, waiting, preparation, and real breaks in the same room and within the same hour. In Germany, working time must be recorded; start, end, and duration have to be documented in a traceable way, as the Federal Ministry of Labour explains in its FAQ on working time recording, status 8 August 2025.

So if one of my team members asks whether “the whole time in the restaurant” automatically counts as working time, my answer is no, but every activity that is truly performed, instructed, or operationally necessary belongs in the assessment. If a guest asks why the crew is already there even though we are not open yet, the answer is just as clear: opening hours and the start of work often do not begin at the same moment. In my operation, I therefore do not separate time by gut feeling but by function. If someone is setting tables, preparing the coffee station, receiving deliveries, checking reservations for service, or attending a briefing, they are working. If they are in a genuine break and can use that time freely, they may be present, but they are not in working time.

A typical restaurant morning makes the distinction easy to see

Take a deliberately hypothetical example from a bistro with a lunch business. The door opens at 12:00, and a server arrives at 11:20. From 11:20 to 11:35, she polishes glasses, checks reservations, and sets up the terrace. From 11:35 to 11:45, the shift lead goes through the daily specials and allergen notes with her. From 11:45 to 11:55, she sits in the staff room, drinks a coffee, checks her phone privately, and can decide for herself what to do. From 12:00 onward, guest contact begins. In that example, the setup work and team coordination are working time; the free period before service is presence time, but not automatically working time. The key point is the content of each phase, not the fact that it all happens before noon.

This is exactly where misunderstandings start. Many restaurants say vaguely, “Be here by half past eleven,” even though that window may contain paid preparation, short internal walks, waiting for handover, and perhaps a private minute as well. I do not organise that with the sentence, “Just come in earlier.” I organise it with a clear instruction: which tasks start when, who is responsible, and from what point the person clocks in. That way, my team sees that I am not hiding necessary prep work inside unpaid time. At the same time, I avoid treating ten minutes of voluntary early sitting-around as if it were full work performance. The difference is not the clock time alone; it is what fills that time, what the person is expected to do, and whether the business is already using that time for its own purposes.

Preparation, changing clothes, and instruction are the usual borderline cases

Disputes often start around setup time. Necessary preparation and closing work can count as working time, for example setting up the till, stocking a station, or changing clothes if that is operationally required. Germany’s Federal Labour Court has made clear that payable working time can include required changing, the internal walks connected to it, and necessary cleaning, but the specific case, the employer’s instruction, and the legal basis still matter; not every voluntary change of clothes or every bit of personal grooming counts. That limited rule is reflected in BAG 5 AZR 212/23. In my restaurant, I therefore do not treat such time as paid or unpaid by reflex. I ask: was it required, work-related, and necessary on site, for example because a station cannot open without it?

Another clear case is instruction. If I brief new employees before their first shift on hygiene, equipment, or safety procedures, that takes place during working time in Germany under Section 12 of the Occupational Safety and Health Act. In practice, that means that thirty minutes on a new combi oven or on the drinks station is not some private learning phase; it is part of the job. I judge it differently if someone reads through the menu at home voluntarily because they want to feel more confident, without me requiring it. Then the operational instruction is missing as the decisive element. It only becomes fair when I name those differences in advance instead of arguing about them after the timesheet has already caused frustration, mistrust, or a preventable correction discussion.

Breaks make presence visible, but not automatically payable

Presence time is especially easy to confuse with working time when breaks happen in the same building. A server may sit in the staff room, stay physically nearby, and return to the floor twenty minutes later. What matters is not that the person is still inside the restaurant, but whether that phase was a real break. The verified basic rule for Germany is that presence time can include genuine breaks or private time and is therefore not identical to time actually worked. So if I expect someone to jump up at any moment and start taking payments again, that points away from a freely usable break. If the person can really switch off and decide for themselves how to spend those minutes, mere presence does not by itself become working time, even if the apron is still hanging on the chair nearby.

In practice, I use one simple test question: during that phase, could the person use their time freely, or were they still functionally on duty? Here is a hypothetical kitchen example. A cook eats at 15:00 in the restaurant, but is explicitly expected to keep an eye on the fryer alarm and jump in whenever an order comes through. Organisationally, that is not the same as an uninterrupted break. I do not solve those cases by intuition. I solve them with clear shift rules. Breaks are planned, responsibility for the station is handed over, and I only treat the time as a break if that handover has actually worked. That protects employees from fake breaks and protects the business from later arguments about supposedly “taken” recovery time, especially on split shifts or long service days.

For pay issues, timestamps alone are not enough

For everyday operations, one point is crucial: working time recording and pay claims are connected, but legally they are not exactly the same thing. Germany’s Federal Labour Court has stressed that timestamps alone do not prove every overtime pay claim; in a dispute, the employee still has to show the time worked and the employer-side instruction or causation behind it. That limited principle appears in BAG 5 AZR 359/21. For my restaurant, that means I should neither rely on memory alone nor pretend that a terminal solves every single case automatically. What matters is whether the recorded time fits the work that was instructed or tolerated and whether exceptions are checked properly by the responsible person rather than waved through at month-end.

That is why, when something is unclear, I do not ask for improvised estimates. I ask for a short, concrete record: date, actual start or end, break, task, and who can confirm the situation. If someone forgot to clock out, that does not automatically create an endless shift. The correction should be based on the actual activity, any note or shift coordination, and a responsible review; timely personal notes help as well. This approach is fairer for staff than blanket rounding down and safer for the business than blindly approving every gap. In hospitality, with late closes, cleaning, and handover after midnight, an explainable individual review matters more than any slogan about “being present,” because the decisive question is always what was actually done and why.

I separate the two in daily operations through rules, roles, and clean records

To make the distinction real, I need more than theory. For each shift, I define which setup tasks belong to the start, when the handover begins, who releases breaks, and which closing steps still belong to the shift. For the actual times, I use Bonzumo’s verified team tools: time clock functions, working time accounts, and exception handling, while roles and permissions help me ensure that corrections are reviewed by the right people rather than changed casually. Anyone who wants the operational framework behind that can look at Give your team a clear start to every working shift. The software does not replace my rules, but it gives them a visible and reviewable structure, so the discussion is based on recorded process instead of memory, mood, or hierarchy.

The order matters to me: first the rule, then the recording, then the review. I do not wait until payroll day to decide whether ten minutes of setup were “basically private.” Instead, my shift organisation might say: the early shift begins with checking the station and restocking receipt rolls; the closing shift ends after till handover and assigned cleaning. If a restaurant leaves those points vague, disputes about working time versus presence time follow almost automatically. It also helps to consider the whole day’s operating flow, not just the moment of clocking in. That is why I think in connected processes, as described on Connect the work behind every successful service: work begins where the operational task genuinely begins, not wherever confusion later becomes expensive or emotionally loaded.

It becomes fair when employees know in advance how their time is judged

A good rule must not only be legally careful; it must also be understandable to the team. So I put it in plain language: working time is everything you do on instruction, for the business, and within your role. Presence time is only the fact that you are there; it may include working time, a break, or simply arriving early by choice. I always add examples. Laying tables before opening counts. A mandatory instruction on a new machine counts. Waiting privately for a ride home after the shift does not. With concrete pictures like these, new employees understand faster why I do not value every minute in the same way and why that is not trickery but clean organisation. Even a small detail, such as whether the keys have already been handed over or a station has already been assigned, can change the classification.

Guests often notice the difference too. If the lights are already on and two people are moving through the dining room, that does not automatically mean service has started. One person may still be in working time doing preparation, while another may be on a real break. That is why I also explain the external effect to my team: being friendly and visibly ready is helpful, but unclear boundary cases should be handled by the shift lead, not by an individual server at the door. In that way, I protect employees from being pushed into unpaid in-between states simply because, from the outside, the operation already looks open. Clear language, visible responsibility, and documented processes matter more here than any abstract definition, because fairness starts before the first dispute, not after it.