Should I Have an Employment Contract in Hospitality?

Yes, your working conditions should be clear and in writing

Yes, in hospitality you should have an employment contract, or at least a clear written record of your essential working conditions. In Germany, an employment relationship can exist even if it was agreed verbally, but in restaurants that quickly creates disputes about duties, pay, working time, or probation. One point matters especially for restaurants and accommodation businesses: the simplified text-form option under the Written Terms Act does not broadly apply here, because the sector is among the industries listed in section 2a of the Act to Combat Undeclared Work. That follows from the current Written Terms Act, Germany, status 30 September 2026.

So when a new server asks me whether they can “just start now” and sort out the contract later, my honest answer is no. I do not organize onboarding by hearsay when the shift may already be hectic by Friday evening. A typical example: someone starts as a runner and assumes that only means carrying drinks, while I expect clearing tables and polishing cutlery as well. Without a written description, misunderstanding is almost guaranteed. It is fairer for both sides to define the role, pay, agreed hours, and start date before the first stressful service begins. That is not bureaucracy for its own sake; it is reliability in a business where plans can change minute by minute.

What I insist on before the first real shift

If you start in my restaurant, at least these points must be unambiguous: what job you are doing, how you will be paid, when you start, and what working time has been agreed. Those core terms should be clearly recorded; that is the practical heart of the employer’s documentation duty. I deliberately avoid friendly but vague wording that leaves everything open in daily service, such as “mostly front of house, helping everywhere if needed.” A better version is specific: table service in the restaurant, occasional support at reception, no kitchen production. That way you know what you signed up for, and I can assign shifts that actually match the role instead of improvising later.

A concrete example helps. If I hire a part-time employee for three fixed evening shifts per week, I do not only note the hourly wage. I also record whether prep time before opening is part of the shift, who explains the house tipping rules, and whether different work areas are planned during probation. In hospitality, small assumptions become expensive very quickly. The employee may think they are needed from opening time onward, while I have already scheduled thirty minutes of mise en place beforehand. That kind of friction damages trust before someone has even settled in. A clean contract or written record will not prevent every conflict, but it removes the avoidable ones.

Why verbal agreements fail so often in restaurants

Verbal agreements in hospitality usually fail not because anyone means badly, but because the pace is fast, shifts change, and responsibility moves between different people. Today the restaurant manager conducts the interview, tomorrow a shift lead allocates sections, and on Sunday somebody fills in for both terrace and bar. If it exists only in someone’s memory that an employee “should not really be scheduled past midnight” or “is only available on weekends for now,” the reliable basis is missing exactly when it matters. The problem rarely appears during a quiet lunch. It shows up on a full Saturday night, when nobody has time to reconstruct earlier conversations properly.

As an operator, I therefore need more than a signed contract; I need to organize it so the agreement still matters in daily practice. Otherwise the document exists, but it does not help anyone when building the rota. In BonZumo, I can support that through the team area with roles, shift planning, and a personal document inbox. That does not replace the legal agreement itself. What it does is help me schedule according to the agreed role, assign access according to responsibility, and keep documents findable for the employee instead of buried in chats. The practical benefit is simple: the server sees planned shifts, the shift lead works within the right permissions, and fewer questions end up in chaotic messenger threads. See also Give your team a clear start to every working shift.

Which documents I ask for, and which I do not ask for by default

I do not collect everything that some businesses routinely copy just because “everyone does it.” I only ask for data and documents that are necessary for the employment and the actual job. In Germany, one legal benchmark for that is section 26 of the Federal Data Protection Act, status 30 September 2026. For food-related work, I also check whether instruction under section 43 of the Infection Protection Act is required. Residence or work authorization documents must be checked case by case when relevant. What I do not demand across the board are broad health records, a criminal record certificate for every restaurant role, or an ID copy without a clear purpose.

A useful distinction is the difference between a kitchen assistant and an office temp in the same business. For the kitchen assistant, I check the hygiene-related records that are actually needed and I document the required instructions. For purely administrative work, other documents may matter instead. The common pitfall is the catch-all request: “Just send everything.” That creates piles of data, but not good staff organization. A structured process is more sensible than random messenger messages. In BonZumo, employees have a personal document inbox where documents can be read and downloaded. The fair part is not the digital tool by itself. The fair part is that each person works only with the documents that are genuinely needed for their role.

How I connect the contract with actual shift planning

A contract only becomes useful when it matches the way shifts are planned. If I agree on 20 hours per week, my rota cannot quietly rely on full-time availability. If I hire someone for service, I should not suddenly place them alone behind the bar without a conversation just because somebody called in sick. This is where many real conflicts in restaurants begin, not at the moment of signing. So I check every new schedule against the agreed role, the discussed availability, and the person’s current training level. That is what operational fairness looks like to me. It is not just administration; it is keeping daily decisions aligned with what was actually agreed.

In practice, that means I set up shifts with the intended staffing, avoid publishing half-finished rota drafts, and keep responsibilities separate. For example, a newly promoted shift lead does not automatically need access to every personnel area just because they run Friday dinner. The practical benefit of roles and permissions is very concrete: that person can handle operational tasks without unnecessarily seeing contract details or time-balance data of other employees. If I want my team to work from one shared structure instead of scattered side lists, the wider workflow matters too, which is why I value Connect the work behind every successful service. The employment contract remains the foundation; the software helps prevent operations from drifting away from it.

What staff should know about notice periods, probation, and confusion

People who ask about starting a job often also worry about how it can end. For Germany, the current baseline under section 622 of the Civil Code, status 30 September 2026, is a statutory notice period of four weeks to the 15th or to the end of a calendar month; during an agreed probation period of no more than six months, the basic notice period is generally two weeks. Another important point is form: termination and termination agreements require written form, not just email or a messenger message, see section 623 of the Civil Code. If I run my business properly, I explain that early instead of discovering it in the middle of a conflict.

The trap for employees is often the relaxed tone that hospitality businesses sometimes adopt. A realistic example: after two stressful weeks, a manager says in passing, “Then maybe we should leave it here.” That alone is not a valid termination in the legally required written form. The reverse is true as well: as an operator, I cannot rely on a shouted remark that somebody is “not coming back tomorrow.” Clean personnel organization protects both sides most when the mood is already bad. If a written dismissal is received and someone wants to challenge it, the general rule is a three-week period for bringing an unfair dismissal claim under section 4 of the Dismissal Protection Act. And no, severance pay does not arise automatically in every termination case.

My fair standard for new employees in the restaurant

My standard is therefore clear: nobody starts in my restaurant on the basis of a vague handshake if the conditions are still open. Before the first real shift, the role, pay, working time, responsibility, and required records must be organized in a way the employee can understand. After that, I structure the start so those agreed points are visible again in daily operations: in the rota, in permissions, in accessible documents, and in an induction that does not promise more than the team can realistically support on shift. That turns the employment contract from a paper file into a dependable framework for cooperation. Even in a busy house, that extra clarity pays back quickly.

So if you ask whether you should have an employment contract in hospitality, my answer as an operator and from an employee’s point of view is clearly yes, in a form that is documented and understandable. Not because every shift starts with legal theory, but because without a clear basis, small uncertainties become real unfairness very quickly. A restaurant can survive one messy evening; it should not build its staffing on permanent ambiguity. Good organization helps, software can support the workflow, and managers need to take the question seriously. But the decisive point remains simple: only when the essential terms are clearly agreed can a shift be planned fairly for everyone involved.