Which Documents Restaurants Need for Onboarding

The core set: I do not start anyone with unclear basics

Restaurants do not need “everything that might be useful one day.” They need a tight mandatory core. First, I make sure the essential contractual terms are clearly documented: the agreed role, pay, and working time. In Germany, an employment contract is not automatically invalid just because it is not in writing, but the duty to provide documentary proof still remains. In hospitality, the general easing toward plain text form does not simply cover us, because restaurants belong to the sectors named in section 2a of the Act to Combat Clandestine Employment. That is why I plan around signed proof, not a chat history or an unsigned PDF; the legal basis is the Verification Act.

After that, I collect only the data and documents that are actually necessary for employment and for the specific job. For payroll setup, that can mean a master-data form requested by the tax office or payroll adviser, bank details, and, where relevant, proof of the right to work. I deliberately avoid the reflex of asking every server for an ID copy, a criminal-record certificate, or private health data. My standard is necessity in the employment relationship, not office convenience. That follows section 26 BDSG: employee data may be processed only as far as it is needed for employment purposes. My rule is simple: justify first, request second, file it only after that.

For kitchen, bar, and dish area, hygiene evidence depends on the actual job

As soon as someone works with certain foods or in covered kitchen activities, I do not ask for some vague “health certificate.” I check whether the instruction certificate under section 43 of the Infection Protection Act is required for that role. For a first start in such work, that initial certificate must be no more than three months old. In addition, I as the employer must instruct the employee after work begins and then again every two years; participation has to be documented and the records kept available. That is not a nice extra but a concrete operator duty under the same rule. Someone working only in the office does not automatically need that document, and that distinction prevents lazy one-size-fits-all rules.

In a restaurant with an open kitchen, this can get blurred very quickly. A new team member may officially start in service, but on two evenings she also plates cold dishes. In that case, I do not treat her paperwork like that of a pure host. I look at the real mix of duties. For perishable food, appropriate specialist knowledge may also matter depending on the task and prior training; see section 4 of the German Food Hygiene Regulation. So I do not just note “has instruction certificate.” I also note which activities the person is actually scheduled to perform. That extra line prevents the classic mistake of hiring someone formally for one role and then putting them in a station for which a required document is still missing.

Operational documents are not secondary paperwork; they are part of safety

Clean onboarding, for me, includes more than personnel paperwork. It also includes the operational documents that make the first shift safe. That means role-based instruction, clear station rules, contact persons, access rights, and where needed, equipment guidance. The instruction must relate to the concrete task and happen before the employee first performs it; if needed, it must be repeated. That is not an unwritten hospitality habit but a direct requirement under section 12 of the Occupational Safety and Health Act. So I document when we instructed someone for the dining room, terrace, hot pass, or dish area. A signed contract does not replace that instruction.

In practical terms, a new server in my business does not just hear, “Walk along today and see what happens.” They get a short handover that can be traced later. It states, for example, who has till access, who handles allergen questions, how far their first independent table section goes, and when asking for help is mandatory. For a kitchen assistant, the same handover looks different: walking routes, hygiene points, cutting areas, storage places, and who to speak to immediately after the first mistake. These documents are not a stiff personnel file; they are working tools. If I keep them properly, I reduce not only risk on the first shift but also confusion in the team, because everyone can see what has already been explained and what is still open.

What I do not demand from everyone as a blanket rule

Many onboarding lists online turn into collection boxes. I think that is risky, because they quickly absorb documents that are necessary only in individual cases. An ID copy for every role, a criminal-record check for every mini-job, medical details without a concrete reason, or a routine pile of private records is not a good standard. Instead, I ask three questions every time: What do I really need for this role, who will use the information, and how long must it remain accessible? That keeps me closer to necessity and also lets me give employees an honest explanation if they ask. The result is more respectful onboarding and a filing system I can defend if someone looks at it later.

A good example is residence-status or work-authorization documents. I do not request them symbolically from everyone; I check them where they are relevant to the actual employment. The same applies to hygiene evidence. A host without food contact does not automatically need the same paperwork as someone working the salad station. Even private phone numbers, emergency contacts, or clothing sizes are not “mandatory onboarding documents” to me. They are separate organizational details with a clear purpose. The distinction sounds small, but in daily operations it matters a lot: mandatory documents block a start, convenience data usually should not. If I keep that line clear, I avoid chaotic first shifts and unnecessary data-protection ballast before the employee has even properly started.

How I sort the paperwork into four folders instead of one chaotic list

I organize onboarding documents in four groups: contract evidence, activity-based evidence, operational documents, and ongoing additions. The first group contains the employment contract or the signed proof of essential terms. The second contains only role-related proof such as the section 43 IfSG certificate or, where applicable, work authorization documents. The third contains instructions, role approvals, station rules, and contact persons. The fourth is deliberately secondary: later additions such as updated contact details, new station approvals, or a second instruction for extra duties. This structure helps me more than an alphabetical personnel file, because it prepares the real assignment instead of merely collecting paper.

Take a sample shift in a bistro. Leon starts as a runner in evening service, but after two weeks he is meant to take orders himself. I do not rebuild his whole file. I add very specifically to the third and fourth groups. First comes the new instruction for the till workflow, allergen guidance, and responsibilities, then the role approval. If counter duties are added later, I review again whether further hygiene topics or access restrictions are affected. That way, the documentation grows with the real responsibility. That is exactly why this question is different from a general onboarding checklist. The point is not just whether something was “ticked off,” but which document actually authorizes which kind of work.

How Bonzumo helps me handle document flow without pretending to replace duties

For daily organization, I use digital tools where they genuinely fit. In Bonzumo, employees have a personal document inbox for reading and downloading. That is practical for operational documents such as station notes, instruction sheets, workflow descriptions, or updated house rules, because new colleagues can find the same version in the right place. If I change our service sequence for the first terrace block someone handles alone, I do not have to scatter that update across five chats. Together with roles and permissions in the team area, I can also define clearly who may only read and who may work with personnel or time data. That organizational side is easier to grasp in Give your team a clear start to every working shift.

The limit matters to me just as much: a document inbox does not automatically replace legally required signed proof when that proof has to exist in the necessary form. So I do not use Bonzumo as an excuse for vague personnel records. I use it for clean distribution and findability inside the business. A practical example: a new kitchen assistant receives the station description, contact list, and goods-receiving house rule digitally. The signed employment documentation and the checked section 43 certificate are still managed in the proper personnel filing process alongside that. This combination keeps everyday work lighter without making a false promise that a download link alone settles every formal onboarding requirement.

The best final onboarding question is: may this person do exactly this work today?

Before anyone starts their first shift, I do not ask myself the fuzzy question of whether “everything is there.” I ask the concrete one: may this person do exactly this work today, and can they do it safely? If the answer is yes for a service runner but not yet for taking orders on the POS, I plan the shift accordingly and keep the scope smaller. If the required hygiene certificate is missing for an intended kitchen task, we do not improvise; we change the task or move the start date. That clarity is fairer than a hectic “we will see how it goes.” It protects the employee from overload and the business from avoidable gaps in responsibility, hygiene, and access.

That is why onboarding in my restaurant ends not with a long list of files but with an approval per work area. Only when contract proof, required role-based evidence, instruction, and the right access all fit together does someone receive the intended work framework. Everything else stays visibly open. For the wider view of how team, sales, and handovers belong together operationally, I also use Connect the work behind every successful service. But the actual decision remains mine as the operator: not to collect the maximum number of documents, but to verify exactly the right ones, explain them clearly, and assign them fairly to the real work the person is about to do.