Do I have to work overtime just because it’s busy?

No, overtime is not automatically mandatory

No, you do not have to work overtime in a restaurant just because the place is full or someone called in sick. In Germany, whether I can require extra hours depends on the employment contract, any collective agreement, any works agreement, and my right to issue instructions, which only applies within those limits and must be exercised fairly. On top of that, I cannot ignore statutory working-time limits. The basic framework comes from section 106 of the Trade Regulation Act, section 3 of the Working Time Act, section 4, and section 5, Germany, retrieved on 2026-09-30.

As an operator, I therefore do not organise this by gut feeling but by clear rules before the shift even starts. A typical example would be a Saturday evening when two large tables arrive later than planned, the dish pit is running ten minutes behind, and the shift lead asks whether the service team can stay longer. I first check whether overtime is even part of that role’s framework, who is already close to the daily limit, and whether the rest period before the next shift would still be protected. “We’re very busy today” on its own is not enough for me as a justification if I want to run the place fairly and avoid disputes afterwards.

When I can require extra work at all

I can only require extra work properly if the basis in the business is sound. That includes the work actually owed under the contract, a lawful instruction, and the statutory limits. A roster entry by itself does not make every extra half hour mandatory. In hospitality, people often mix up what was planned, what was actually worked, and what was legally owed. If one of our cooks is scheduled until 10:00 pm but the kitchen runs until 10:35 pm because a late menu has to be finished, I check three points: was the extension really operationally necessary, was it instructed or at least clearly prompted by the employer, and is it documented in a way we can later verify.

It also matters that this is different from on-call work. The often-mentioned four-day notice rule in section 12 of the Part-Time and Fixed-Term Employment Act applies by statute to on-call work, not automatically to every normal restaurant roster. So if I ask someone at short notice to step in, that does not automatically create a duty, and it does not automatically make the request unlawful either. The decisive point is the concrete contract situation together with the other rules in the business. For my organisation, that means I separate a published schedule, a voluntary extra request, and a binding instruction very clearly, so the team knows exactly what kind of request is on the table.

The legal limits are not negotiable

Even if extra work can lawfully be instructed, my freedom as an operator ends where the Working Time Act sets boundaries. Under section 3 of the Working Time Act, the basic rule in Germany is eight hours per working day, and up to ten hours is only possible if the statutory averaging requirement is met. Under section 4, breaks must be granted, and under section 5, there must generally be eleven hours of uninterrupted rest between working days. I cannot organise those rules away with a sentence like, “Just help out a bit longer today.”

In practice, I always check the whole chain, not only the single extension. If a server has already been in the building since 2:00 pm, I cannot thoughtlessly keep that person until midnight for breakdown and cleaning if they are due back on breakfast the next morning. Another detail is often missed: anyone who has a second job brings those hours with them. Under section 2 of the Working Time Act, working time from multiple jobs is added together. I therefore ask about such constellations early and record them organisationally instead of discovering in the middle of a conflict that two individually lawful shifts become unlawful when combined.

Working overtime and getting paid for it are two separate questions

The fact that an hour was recorded does not automatically settle the pay question. For overtime pay, what matters is that the time was actually worked and that it was caused by the employer. That is exactly what the Federal Labour Court pointed out: time stamps alone do not replace every element of proof; the duty to record time and the question of remuneration are legally distinct issues. The relevant decision is Federal Labour Court, 5 AZR 359/21, Germany, retrieved on 2026-09-30. And there is no general statutory overtime premium for all hospitality businesses simply flowing from that.

I handle this in the business with one simple principle: if someone works longer than planned, the reason is documented immediately, and the shift lead reviews it promptly. A note such as “Table 14 took 28 minutes longer because of an allergen clarification and a restarted sauce” is understandable; “just stayed longer” is not. That lets me distinguish fairly between genuine operational overtime, voluntary staying without instruction, and a planning mistake on our side. For employees, that matters because they should know what their claim rests on. For me, it matters because I want to decide compensation or time off based on a verifiable process rather than on fading memory after a long service.

How I organise fair decisions in a concrete Saturday shift

Take a realistic example. At 9:20 pm, one service employee drops out sick for the last hour, three tables are still seated, and the bar still has twelve cocktails open. I do not simply demand that everyone stay longer. Instead, I decide in four steps: first, capture the remaining work; second, prioritise the roles actually needed; third, check the legal limits; fourth, ask for volunteers or issue a targeted instruction where that is genuinely justified. Maybe the bar needs another twenty minutes, while the floor only needs one person to close out the final bills and handle the last payments. In that situation, it is unfair to keep four people unnecessarily just because “we all leave together.”

For that organisation, I rely on clear responsibilities and traceable time data. In Bonzumo, I can plan shifts, record actual times via the time clock, handle exceptions, and maintain working-time accounts; roles and permissions also help define who may only view times and who may correct them. For me, that is not an automatic legal verdict but the basis for clean operational organisation. If you want to see that organisational framework in context, start with Give your team a clear start to every working shift and the broader view at Connect the work behind every successful service.

Typical pitfalls I deliberately avoid

The first pitfall is the silent expectation. When managers say, “We’ll see when we get out,” pressure builds quickly even though nothing has been clarified properly in legal or organisational terms. The second pitfall is mixing tips, mood, and extra work. Good tips do not make overtime automatically mandatory, and they do not automatically make it fairly compensated either. The third pitfall is false precision through technology. A recorded clock-out time is useful, but it does not prove by itself why someone stayed longer. That is why I ask shift leads to record reasons, not just collect minutes on a screen.

Another common error is relying on the wrong deadline or on vague habit. The four-day rule in section 12 of the Part-Time and Fixed-Term Employment Act is not a general scheduling deadline for every restaurant. And if there is a works council, the timing and distribution of working time, as well as technical systems used for monitoring conduct or performance, can require co-determination under section 87 of the Works Constitution Act. In practical terms, that means I discuss the rules in advance, not after an argument. Where co-determination matters, the solution belongs at the right table, not in a spontaneous instruction five minutes before the end of a shift.

What you are entitled to ask — and what I must answer

If overtime affects you, three questions are entirely legitimate: on what basis is it being required, how will it be documented, and how will it be compensated or balanced out? That is exactly the transparency I also expect from my managers. A fair message would be: “We need another 25 minutes tonight for the final bills, your rest period before tomorrow remains protected, please clock out normally and we will approve the reason.” An unfair message would be: “Just stay, we’ll sort it out somehow later.” Anyone who leads that way creates mistrust, errors in time data, and unnecessary conflict at the end.

As an operator, I do not owe perfect predictability, but I do owe a decision that can be followed and explained. That is why I distinguish clearly between a genuine emergency, normal guest business, and plain understaffing caused by poor planning. If we notice that the same extra half hour turns up “spontaneously” every Friday, then we no longer have an overtime problem; we have a planning problem. In that case, I adjust staffing, closing routines, or task distribution instead of building the operation around unspoken extra work. That is how I take employees seriously, still look after guests properly, and prevent overtime from turning into a sloppy habit in the restaurant.