Working Hours and Shifts in Restaurants Explained

What counts as working time and what a shift means

In my restaurant, working time is not only the minute spent with a guest. It is the actual time from the start of work to the end of work. That includes setup, mise en place, till handover, restocking a station and the closing work after the last table. A shift is the planned part of that working time, for example an early, middle or late shift. For adult employees in Germany, as of 30 September 2026, the basic rule is eight hours per working day, with up to ten only if the required averaging is observed; hours from multiple jobs are added together. That follows from Section 3 of the Working Hours Act and Section 2 of the Working Hours Act.

I explain this to new team members with a simple restaurant-evening example. If we open at 5:00 pm, a service shift often begins at 4:30 pm because glasses, station setup, reservations and handovers have to be prepared first. And it does not end with the last card payment if cutlery still needs topping up, open tables must be checked and the section has to be handed over cleanly. Anyone who looks only at opening hours underestimates the real deployment time. That is why I always separate opening hours, working hours and shift type clearly in the rota. It prevents later arguments about supposedly “missing” twenty minutes at the beginning or end.

Why shifts are more than times written on a rota

I do not organise shifts only by the clock, but by workload and responsibility. An early shift can feel calm and still contain a lot of preparation. A late shift is often harder even if it is the same length, because closing duties, cashing out and the final guests come with it. In many restaurants, a middle shift is not a half shift at all, but targeted reinforcement for the peak period. For example, from Monday to Thursday a small service team may be enough in the evening. On Friday I may need one extra person purely for drink runs and table turnover. Equal hours therefore do not automatically mean equal strain, and that is exactly how I explain my allocation.

A shift system becomes fair only when the unpleasant duties do not always land on the same people. So I look across several weeks at who has done weekends, late closes, terrace-heavy evenings or support for new colleagues. One team member may genuinely prefer late work, but not three closing shifts in a row. Another may handle Saturday night without complaint, but needs a reliable free Sunday morning in return. Differences like that belong in the planning. Otherwise the rota looks complete on paper but becomes unstable in practice. In my operation, fair shifts do not come from instinct alone. They come from workloads that are distributed visibly enough for everyone to understand.

Breaks are real interruptions, not theoretical gaps

Breaks are not a favour from the business. They are regulated by law. For adults in Germany, as of 30 September 2026, if working time exceeds six and goes up to nine hours, at least 30 minutes of break time are required; above nine hours, at least 45 minutes. Split breaks must each be at least 15 minutes, and working more than six hours without a rest break is not allowed. That is set out in Section 4 of the Working Hours Act. In daily practice, one point matters especially: a break is only a break if work really stops. If someone is still watching guests, polishing cutlery and staying available for questions, they have not had a genuine rest break.

That is why I do not schedule breaks as a hope, but as an operational task. In a typical Saturday shift, I decide before service starts who will cover reception from 6:15 to 6:30 pm so that the colleague on the first run can actually step away. The most common mistake in small teams is the sentence, “We’ll take a break when it gets quiet.” That often means the break is skipped completely or taken only halfway. A rush of guests does not cancel a legally required break. If I notice the plan leaves no room for one, then the problem was not an inflexible team. My staffing was too tight. For me, admitting that is part of organising shifts properly.

Rest time between two days is often the decisive point

Besides the break within a shift, the rest period between two working days matters just as much. The general rule is eleven uninterrupted hours of rest. In hospitality, this may be reduced to ten hours, but only if each reduction is compensated within the legal period by another rest period of at least twelve hours. That is regulated in Section 5 of the Working Hours Act. In practice, that means a long Saturday night and an early Sunday setup do not automatically fit together, even if each shift looks harmless on its own. Very often the last twenty minutes of closing work are what decide whether the legal rest period still works or has already slipped too short.

So I never check only the planned start time. I always look at the actual finish. For example, the late shift may officially end at 11:00 pm, but in reality the till is handed over, empties are sorted and the final open table is closed only at 11:25 pm. If that same person is supposed to return at 9:15 the next morning for setup, that is no minor oversight. It is a planning error. Bonzumo helps me here through verified time tracking with a time clock, personal sessions, exception handling and working-time accounts, because the actual hours worked can be recorded transparently and reviewed later with care. I do not blindly correct totals first. I start by checking the cause of the discrepancy.

Rota decisions and changes must fit professionally, not just spontaneously

For me, a rota is not a list of names. It is the link between contract, availability, qualification and the real course of business. I cannot assign working time however I like, but only within the framework of the contract, the law, any collective agreement and any works agreement, using equitable discretion. The key rule is Section 106 of the German Trade Regulation Act. Another point I explain openly because teams often mix it up: the well-known four-day notice rule in Section 12 of the Part-Time and Fixed-Term Employment Act applies to on-call work, not automatically to every normal restaurant rota.

When short-notice changes come up, I never decide them in my business only by asking who can jump in fastest. First I check the reason: sickness, an event, a reservation peak or simply flawed initial planning. Then I look at the task itself: who can actually cover the terrace, the till, reception or the closing service. Only after that do I check hours, rest periods and possible second jobs, because working time from multiple jobs has to be added together. A spontaneous swap between colleagues is therefore not automatically a valid solution. It becomes a real solution only when the task fits and the resulting hours remain lawful. Otherwise we are merely swapping the problem, not the responsibility.

Handovers and time entries prevent the usual small conflicts

Most disputes are not about whole hours, but about unclear minutes. Who waited for the delivery service, who had to resolve a complaint, who forgot to clock out after closing, and who assumed the night shift would handle the rest? That is why I treat time recording not as surveillance, but as a shared memory aid. Bonzumo verifiably offers a time clock, working-time accounts, exception references and separate role and editing permissions. That means a shift lead can clarify a forgotten clock-out case properly without automatically having free access to all HR data. This separation is exactly what makes corrections credible. It matters especially when one shared tablet is used by several people over the course of an evening.

I also work with a short fixed handover in every area. Five minutes are enough if the content is clear: open tables, special reservations, payments not yet completed, missing stock, any technical issue and the next break point. In service, the connection with the POS context is particularly useful. If someone later asks why table 14 was still open or where a tip was recorded, I can start from the specific transaction instead of relying on memory. For that I use the connected sales context in Keep every sale connected to the service around it and, for payment-related questions, Finish a good visit with a clear payment experience. That way, a shift handover does not turn into a search operation.

How I explain working hours fairly, including in relation to guests

I explain working hours to employees as early as possible, not only once a disagreement has started. I state clearly what counts as working time, when a shift practically begins, how breaks are organised, who approves changes and how forgotten time entries should be reported. I also set the limits clearly: guest pressure does not cancel breaks, an entry in the rota does not replace a working-time check, and a friendly swap between colleagues is uncertain without approval. If there is a works council, the timing and distribution of working hours, as well as technical systems used for monitoring behaviour or performance, may fall under co-determination; Section 87 of the Works Constitution Act is relevant there. Clear rules protect staff precisely from quiet pressure.

The same honesty helps in relation to guests. If we stop accepting a large menu at 10:30 pm, that is not a lack of goodwill. It is often the result of kitchen timing, closing work, breaks, handover and the next shift’s rest period. I would rather organise realistic last-order times than push my team heroically beyond the limit every time. From the outside that can look stricter, but in practice it is more reliable. I do not judge a good shift by whether everything was somehow still forced through. I judge it by whether the operation is closed down properly, the figures remain traceable, and the people return the next day able to work, respected and prepared.