Should I document my working hours?

Yes — and not just as a precaution

Yes, you should document your working hours. In Germany, the employer must introduce and use a reliable system to record actual working time, specifically the start, end, and duration of daily work. For restaurants and many mini-job arrangements, there are also explicit recording and retention duties. For this article, the legal context is Germany, status 30 September 2026, based on the Federal Ministry of Labour FAQ on time recording, the Federal Labour Court decision of 13 September 2022, and section 17 MiLoG.

When a server asks me this question, my answer is simple: yes, please record the time you actually worked, not just the shift that was planned. In a restaurant, that difference matters every day. A rota may say 5:00 p.m. to 11:00 p.m., but if someone starts at 4:45 p.m. for mise en place and leaves at 11:20 p.m. after closing tasks, the real work is longer than the published schedule. As an operator, I do not want pay, break checks, or overtime discussions to depend on memory, mood, or who speaks up more confidently at the end of the month.

What should actually be recorded

The core record is straightforward: actual start time, actual end time, and actual duration of work. Real breaks must be separated from working time. In hospitality, that sounds easier than it is, because the grey areas are small but constant: setting up before opening, carrying stock downstairs after service, staying longer because a large table pays late, or taking a break that gets interrupted twice by guests asking to settle. If I ignore those transitions, I end up debating minutes later when the real problem was an unclear process.

So I organise the rule in practical terms: what was genuine work, what was a genuine break, and when did each one really begin and end? For example, a bartender clocks in at 3:55 p.m., sets up the station, works through service until 10:10 p.m., and takes a real break from 6:30 to 6:55 p.m. That is what should be recorded. I do not treat quarter-hour rounding, automatic standard breaks, or “we usually do it like this” as a fair substitute for what actually happened. A clean record should reflect the restaurant, not beautify it.

Why this is fairer for employees, not just safer for management

From an employee perspective, time records protect against the classic restaurant phrase: “It was only a few minutes.” A few minutes polishing glasses before service, a few minutes securing the terrace after the last guests leave, a few minutes receiving a delivery between tasks — that adds up quickly. Without documentation, people are left with a vague feeling that extra effort disappears. With documentation, there is at least a traceable timeline. The important limit is this: a time stamp alone does not automatically prove every pay claim. The Federal Labour Court separates the duty to record time from the separate question of overtime pay, as reflected in the decision of 4 May 2022.

That distinction matters in how I run the restaurant. If a shift lead clearly keeps someone longer because the kitchen is still finishing a delayed ten-top, that is a business-caused extension. If someone remains on site after duties are over and chats privately, that is different. Recording time helps me examine the situation fairly instead of making assumptions. I do not use time recording as a weapon against the team, and I do not promise that every stamp settles every legal question. What it does give us is a shared factual base, which is usually the difference between a calm clarification and a frustrating dispute.

How I organise the process in everyday service

In practice, time recording only works if the moments are clear. I define when clock-in begins, who checks exceptions, and how a shared device is used. In Bonzumo, I can organise this with time clock functions, working time accounts, and role-based responsibilities, so exceptions are reviewed by the right people instead of everyone improvising. That only becomes fair if planning and actual hours are considered together, which is why I also look at Give your team a clear start to every working shift when I set up the process for our restaurant.

My operating rule is deliberately simple: clock in when work starts, clock out when work ends, and mark a break only when it is a real break. Shift leads then have three duties. First, they check open or unusual bookings before everyone leaves. Second, they clarify discrepancies on the same day or the next working day, not three weeks later. Third, they note the reason for a correction in plain language. A useful example would be: “Shift ended at 00:18 due to late group settlement, 22-minute break taken, clock-out forgotten.” That prevents the two worst habits: guessing afterwards and making bulk corrections at month end.

What happens if someone forgets to clock out or enters the wrong time

If someone forgets to clock out, I do not treat that as a licence for unlimited working time, but I also do not treat it as proof of dishonesty. The correction should follow the actual work performed. For Germany, status 30 September 2026, the verified baseline is that wrong time entries should be reported promptly with date, actual start or end, break, and activity, and then corrected in a traceable way; personal notes made close to the event can help if there is a dispute. That is the standard I use operationally: report, review, correct, document.

A realistic example is a server who finishes the shift, helps with closing for another ten minutes, gets home, and realises they never clocked out. The right response is not to hope the system somehow “knows,” and not to have the office simply cut the time to the planned rota end. The shift lead should check the context: who else was there, what closing duties were still open, whether a late payment or handover delayed departure, and whether the stated timing fits the evening’s flow. The fair solution is a reasoned correction. Blind approval is weak management, but reflexive reduction is just as unfair.

The mistakes I need to avoid as an operator

The biggest mistake is building time recording as a control tool against the team. Then people clock out too early, take breaks only on paper, or stop recording prep and closing tasks because they expect an argument. The opposite mistake is just as harmful: a loose system with no rules, where everyone “sorts it out later.” That creates month-end lists full of unclear entries, and then nobody can tell planned time, worked time, and guessed time apart. Both versions damage trust. A good system protects employees and reduces pressure on supervisors.

To avoid that, I set clear decision criteria before problems arise. Was the task instructed, tolerated, or objectively necessary for service? Was the break actually taken, or constantly interrupted? In our house, does changing, station setup, or cashing up count as work because it is part of the assigned duty? I do not decide those points ad hoc depending on how busy we are or who is asking. I decide them as restaurant rules for comparable cases. Technology supports this, but it does not replace management. If the organisational rule stays vague, the software just records new arguments more neatly.

My practical conclusion for a fair restaurant

My clear answer is therefore yes: working hours should be documented, and they should be documented according to the time actually worked. For employees, that creates a traceable basis for questions about breaks, shift extensions, and forgotten clock events. For me as the operator, it is the basis for leading fairly instead of deciding from memory or instinct. In hospitality, where preparation, rush periods, interrupted breaks, and late closing tasks are normal, proper time recording is not office decoration. It is part of serious restaurant organisation.

When I set this up in a restaurant, I use four steps. First, I define what counts here as work start, break start, and work end. Second, I name who may review and correct exceptions. Third, I explain to the team the difference between the rota and actual recorded time. Fourth, I keep those records in one shared operational context, not in scattered messages and private notes. If I want that process to fit the rest of the day instead of standing alone, I review it alongside Connect the work behind every successful service. That is how time recording becomes understandable, consistent, and fair.