Working hours in hospitality: is this normal?

Common does not automatically mean acceptable

Yes, irregular and late working hours are normal in hospitality. What is not normal is a setup that only works through constant stress, missed breaks, last-minute extensions, or shifts that are routinely stretched far beyond plan. If a server asks me whether ten consecutive late days, constant call-ins, and no reliable finishing time are “just hospitality,” my answer is clear: this profession has unusual hours, but that does not remove limits or the need for fair organisation. Precisely because our business has rush periods, I have to plan properly instead of romanticising overload.

Anyone who works in restaurants sees genuine peaks: a packed weekend, a weather shift that fills the terrace, or a group that all wants to pay at once. That explains pressure, but it does not excuse a weak basic structure. One late evening can be normal; a work culture built on permanent improvisation is not. I therefore do not only ask how long someone stayed yesterday. I look for patterns across weeks: do the same people always absorb the overtime, do breaks regularly disappear, or does the early shift start too soon after a late close? That is where demanding hospitality stops and avoidable overstrain begins.

The legal baseline in Germany is brief, but clear

For Germany, the framework is clear in the Working Time Act. The basic rule is generally eight working hours per workday; up to ten is only allowed if the legally required averaging adjustment is made so the average comes back down. Legally required breaks cannot simply be cancelled because guests are busy. For more than six and up to nine working hours, at least 30 minutes of break time are required; for more than nine hours, 45 minutes. Split breaks must each be at least 15 minutes. That follows from section 3 of the Working Time Act and section 4. A break must be a real interruption of work, not just an automatic deduction on a list.

Rest time between working days matters as well. The general rule is eleven hours; in hospitality it may be shortened to ten only with the legally required compensation, so it is not something I can use as a permanent convenience. The basis is section 5 of the Working Time Act. So if someone closes very late and returns early the next morning for setup, I do not first ask whether that person is “resilient.” I ask whether our rota was workable in the first place. That is not legal hair-splitting. It is basic operational management. Young workers and some other protected groups can have additional rules, so I check those cases separately.

How I recognise when things are no longer normal

I do not judge working hours by gut feeling. I look for repeated warning signs. One example: a front-of-house colleague is officially planned until 10 p.m., but in four out of five shifts stays until 11:30 p.m. because cashing up, resetting tables, and spontaneous groups were never realistically built into the rota. In that case the colleague is not “too slow”; the shift plan is understating the actual work. Another warning sign is when the kitchen supposedly takes its break “somewhere between tickets,” but nobody ever truly steps away from work. As soon as operations only function through silent self-exploitation, I do not have a staff problem. I have a leadership problem.

The team’s language tells me a lot too. If sentences like “we take breaks when it gets quieter” or “leaving on time is unrealistic here anyway” become normal, the line has already moved. It is normal for a Saturday night to be intense. It is not normal if nobody would be surprised when a planned eight-hour shift becomes eleven. That is why I check three very concrete points: planned versus actual finishing times, the concentration of short-notice call-ins, and shifts that repeatedly sit too close together. The most revealing moments are often the half hour before opening and the half hour after the last guest leaves, because hidden extra work is often buried there.

Fair working hours are created before the shift begins

The biggest mistake is to talk about working time only once somebody is already exhausted. Fair working hours start with the shape of the shift itself. If I know that Fridays between 7 and 9 p.m. are where the bar starts to buckle, I do not just staff the guest-facing area. I also plan for closing tasks, replenishment, and payment bottlenecks. One practical decision might be this: instead of two people from 5 to 11 p.m. plus a vague hope that it will quiet down, I schedule one extra person from 7 to 10 p.m. specifically for clearing, water runs, runner routes, and support at payment time. That lowers pressure and prevents the same end-of-night extension from repeating again and again.

It is just as important to distinguish honestly between opening hours and working hours. Guests may only see 6 to 10 p.m., but for the team that often includes mise en place, cleaning, cash closing, or putting goods away. If I do not plan those times visibly, I automatically create “surprise overtime.” That is why I discuss the real work arc for each role: who needs 20 minutes of preparation, who needs 45, and whose work does not end with the last ticket but only with a proper handover point? That kind of clarity fits well with Give your team a clear start to every working shift, because planning and responsibilities are considered together there.

How I handle exceptions without turning them into the permanent model

Of course there are evenings when a coach party arrives late or a storm pushes every terrace guest indoors at once. Then a shift can run longer without that automatically meaning abuse. The real question is how I deal with it. I do not wait until 10:05 p.m. to tell the team that “today will simply run longer” if the trend was obvious by 8 p.m. I address early what extension is likely, who can take it, and which task can be dropped if necessary. Fairness does not mean everyone has to carry everything. It means the exception is consciously organised and then properly balanced afterwards.

This is exactly where documented actual times help more than heroic stories. In Bonzumo, I can use shift planning and time tracking so planned shifts, the real start, the real end, and exceptions remain understandable later. In practice that means the server clocks their time, the shift lead reviews striking deviations, and we discuss not only the total but also the reason. Was the terrace understaffed, did checkout take unusually long, or did someone call in sick? The benefit is tangible: I correct the next rota based on real strain instead of memory. You can see that connected operational setup in Connect the work behind every successful service.

Late, split, and changing shifts need clean rules

Many conflicts do not arise from the total number of hours alone, but from how those hours are distributed. A split shift may suit some life situations and be nearly impossible for others. A late shift is not automatically unfair, but it becomes a problem when the same person always closes and is also the one constantly asked to cover weekends. Night work is also more nuanced than many people assume: a late restaurant evening is not automatically the legal case of a night worker. What matters are the contract situation, the rota, and the legal framework on night time and compensation in section 2 of the Working Time Act and section 6.

In practice, that means I define openly in the team who can regularly close, who needs certain time windows for family reasons, and how we distribute weekends. In Germany, weekend work does not automatically create a statutory Sunday or public holiday premium; such claims can arise from a contract, collective agreement, or workplace rule. Sunday work does, however, generally require a substitute rest day under section 11 of the Working Time Act, and the Federal Labour Court has made clear that the Act itself does not automatically create a Sunday or holiday pay premium in every case, as seen in BAG 5 AZR 431/16. That is precisely why internal rules must be clear, understandable, and explained equally to everyone instead of being improvised from one shift to the next.

What I honestly tell staff when they ask whether this is normal

When someone asks me whether working hours in hospitality are normal, I say this: inconvenient hours, yes; permanent boundary-crossing, no. Anyone in this profession has to expect evenings, weekends, and changing levels of demand. Nobody has to accept breaks that exist only on paper, rest periods that are systematically squeezed, or a complete loss of personal predictability. Good hospitality is not the art of keeping people endlessly available. It is the art of organising reliably despite a lively and unpredictable service. That is why I never hear this question as complaining. I hear it as an early warning sign about leadership, staffing, and culture.

My fair solution is rarely one dramatic lever. It is several clean decisions working together: realistic shift lengths, visible setup and closing times, documented actual hours, clear rules for stepping in, understandable distribution of late duties, and an open conversation before frustration hardens. If a team member shows me a recurring pattern, I do not just try to improve the mood. I change the process. In hospitality, “normal” should mean demanding, lively, and sometimes long. It should not mean opaque, exhausting, and constantly at the limit. From the perspective of a well-run operation, that distinction is exactly what matters.