What happens when there is a dispute about working time?

The short answer: I clarify the specific shift, not just the total

When there is a dispute about working time in my restaurant, I do not let the louder person win. I check the actual shift. The key questions are the real start, the real end, the break that was actually taken, and whether the work in question was required, accepted, or clearly part of the job. If someone reports a discrepancy, I want the date, start and end time, break, and a short description of what they were doing. I do not simply adjust a monthly balance; I correct the specific, supportable event. In Germany, full recording of the start, end, and duration of working time is already mandatory. Even if employees record it themselves, the employer remains responsible, as the Federal Ministry of Labour explains in its working time recording FAQ.

For employees, that means an inconsistent time entry does not just disappear because the shift was hectic. For me as the operator, it also means I cannot brush off a report with “that should be about right” or “that probably did not happen.” In a restaurant, the usual problem is not bad faith but a messy end of shift. Example: a server clocks out, then helps clear and secure the terrace after a sudden rain shower. I then check whether real operational work was done after clock-out, who saw it, and whether that closing work belonged to the shift. That turns frustration into something reviewable instead of a power struggle.

What the dispute is really about: a time error, a break, overtime, or who caused it

Working time disputes often sound similar, but they are not the same issue. Sometimes someone forgot to clock out. Sometimes a break appears in the record although it was never really taken. Sometimes the question is whether staying longer was actual work or just unresolved presence in the building. That distinction matters because a recorded hour does not automatically settle every pay question. In its decision of 4 May 2022, case 5 AZR 359/21, the German Federal Labour Court made clear that, in overtime pay disputes, the employee must present not only the times worked but also that the overtime was caused or accepted by the employer. Time stamps alone are not always enough, as shown in the Federal Labour Court decision.

That mixed situation happens quickly in hospitality. Example: a cook stays 40 minutes after the scheduled end because a delivery arrives late and chilled goods still need to be checked and put away. If the shift lead ordered that or knowingly let it continue, that is different from someone staying on site after work for a private chat and going home later. So I separate two questions every time: what actually happened as working time, and how should that time be treated in organizational or pay terms? That order protects both sides. Otherwise I start arguing about money before the facts are clear, or I end up with time data but no understandable reason for why those extra minutes happened at all.

How I organize the review so nobody has to fight to be heard

I keep the process deliberately simple. First, the person concerned reports the discrepancy promptly with the date, start, end, break, and a short description of the work. Second, the responsible shift lead reviews how the shift actually ran: did prep take longer, did a delivery arrive late, did a large party delay closing? Third, I or the responsible manager decide based on that single shift, not on a vague monthly difference. An 18-minute deviation because of genuine closing work is different from three missing end times in one week. I want every correction or rejection to be explained in a way the team can follow. That gives people confidence and prevents time data from being reconstructed weeks later from memory alone.

It helps me if planned shifts, actual times, exceptions, and permissions are kept together. In Bonzumo, shift planning, time tracking, working time accounts, and roles and permissions are available as team tools, so I can treat time disputes as a defined work process instead of a hallway conversation between the kitchen door and the bar. That is not legal advice, but it creates order: who may report, who may review, and who may correct? That clarity matters in daily practice. The broader team setup behind that is part of Give your team a clear start to every working shift.

A realistic restaurant example: a missed clock-out after a long Saturday

Take a common example. It is Saturday night, the terrace was full, the last table paid late, and the shared device shows no clock-out at the end of the shift. On Monday, a server says she worked not until 11:20 pm but until 12:05 am. I do not solve that by sympathy, and I do not choose the most convenient number. I ask for the sequence of events: which tables were still open, who cleared the glasses, who handed over the cash area, who secured the outside section and entrance? Then I check which tasks were still operational work. In Germany, a forgotten clock-out should be corrected based on the actual work performed, notes, shift coordination, and responsible review. That does not automatically create unlimited working time.

The most common mistake here would be to enter the planned shift end for convenience, or to accept every later time claimed afterwards. Both are unfair. If two colleagues confirm that they were still clearing and securing together, that is a strong indication. If the shift lead already noted that closing was delayed, that also helps. But if the handover was complete at 11:25 pm and the employee then only waited for a ride home, that is not working time. So I only correct what I can plausibly connect to real operational tasks. That protects the team from blanket rejection and the business from unsupported additions.

Where I look especially closely: breaks, daily limits, and rest periods

Working time disputes are not only about missing minutes. They often reveal whether my organization is sound. If breaks exist only on paper but cannot realistically be taken during service, that is a management problem, not just a booking problem. In Germany, the minimum rules are clear: if working time exceeds six and up to nine hours, at least 30 minutes of break are required; above nine hours, at least 45 minutes are required; and no one may work more than six hours in a row without a break. That is set out in section 4 of the Working Time Act. So when someone disputes their hours, I do not only inspect the number. I also ask whether the break was really taken or only existed in the rota.

Daily limits and the rest period between shifts matter just as much. Under section 3 of the Working Time Act, the basic rule is eight hours per working day, with extension to up to ten hours only under the statutory balancing conditions. Under section 5, there is generally an uninterrupted rest period of eleven hours between working days; hospitality may shorten this only within the narrow statutory rule and only with later compensation. So if the same person repeatedly stays longer because staffing is thin, I treat that as a signal to reorganize shifts and responsibilities instead of merely correcting the same time issue again and again.

Handling overtime fairly: document it, approve it, do not romanticize it

I tell my team this openly: heavy business alone does not mean overtime is always compulsory in hospitality. The employment contract, any collective or workplace rules, managerial authority, and statutory limits all matter. At the same time, one extra recorded hour is not automatically a complete answer to the pay question. For overtime pay, it also matters whether that extra work was instructed, caused, or at least knowingly tolerated by the employer. That is why I do not want overtime treated as a heroic silent sacrifice at the end of a chaotic evening. If someone should stay longer, there should ideally be a clear instruction. If the need only arises in the moment, it still has to be reported and reviewed promptly.

Example: the dishwashing area fails unexpectedly, and two servers help with closing for 25 minutes. If the shift lead instructs that or visibly accepts it, that time belongs in the review. If someone regularly arrives far before the shift to drink a coffee in peace, presence alone does not become working time. That is where many misunderstandings start. My mistake would be to let everything run without structure and only debate it weeks later during payroll preparation. A better standard is this: extra work is named concretely, time off or pay is not simply assumed but clarified, and open questions are discussed at the level of the individual shift.

How I prevent disputes so a few minutes do not turn into a principle fight

The best solution starts before the dispute. That is why I plan not only guest-facing service time, but also setup, handover, and closing work. If the rota only shows service hours while the team is still expected to prepare the room beforehand and clean after, I create the discrepancy myself. The same applies to breaks: I do not rely on theory, but organize cover and shift rhythm so that breaks are actually possible. I also define within the team who reports exceptions immediately and who reviews them. Then a five- or twenty-minute deviation stays a manageable case instead of growing into a quiet fairness problem. I keep that wider operational view through Connect the work behind every successful service.

Employees can reasonably expect me to take credible reports seriously and to explain rejections. Guests notice the quality of that approach indirectly: where working time is organized fairly, handovers are calmer, breaks are more realistic, and the atmosphere in service is more stable. Where time disputes are ignored, the result is tense shifts, sloppy closing, and mistrust. So my clear answer is this: when working time is disputed, I review the actual work on the specific shift, the real break, and whether the extra time was caused or accepted; I correct supportable errors transparently; and if the same conflict keeps returning, I change the workflow instead of arguing about it every week. That is how fairness in a restaurant is organized, not just claimed.