What should the first working week in a restaurant look like?

The week should begin in stages, not as a stress test

The first working week in a restaurant should be structured in stages: first orientation, then supervised practice, then a small area of independent responsibility. I do not throw new employees straight into a busy evening and expect them to “just join in” as if every rule were obvious. If someone has to carry full service, taking payment, guest questions and closing duties all at once on day one, they make avoidable mistakes and lose confidence for no good reason. A good first week makes the pace of the business visible, but deliberately limits responsibility. That is fairer for new colleagues and noticeably better for guests, because uncertainty does not have to be solved in front of the table.

I plan that week with a clear rhythm, not with a symbolic welcome talk. One example would be this: Monday starts outside peak service, Tuesday brings a short first service route with support, Wednesday repeats the same station, Thursday adds a slightly fuller section with a defined contact person, and Friday only becomes more independent if the first four days were stable. That separates getting familiar from being put under pressure. In that example, if someone begins with drinks in a small terrace section, they learn routes, table logic and guest communication without also having to handle every complaint, split bill and last-minute change on their own.

Day one needs orientation, documents and real questions

On the first day, I am not trying to dump as much information as possible onto a new person. I want to make the business understandable. I show the site in a fixed order: entrance and changing area, team structure, dining room, pass and pick-up points, storage access, waste routes, break area, hand-washing stations and the sequence before a shift begins. After that, I explain who is responsible for which question. New employees often ask more confidently when they know exactly where to go: person A for the rota and recorded hours, person B for guest-facing routines, person C for kitchen coordination and allergen questions. That clarity prevents awkward shouted questions later in front of guests.

I do not treat mandatory briefings and necessary onboarding as unpaid spare time. In Germany, occupational safety instruction must happen before the work starts and during paid working time under Section 12 of the Occupational Safety and Health Act. Food-handling instruction under the Infection Protection Act is a separate requirement and is not replaced by a quick till explanation; the core rule is set out in Section 43 of the Infection Protection Act. In Bonzumo, I can keep documents and team information accessible through team management and a personal document inbox, so shift leads do not have to search through private chats when a record or instruction needs to be found again.

From day two onward, a limited first service route matters most

Day two should not mean “now work properly.” It should mean: repeat one small task, this time with more of your own action. I might assign three to five tables in a quiet edge section, or only drink service in one clearly defined zone. The experienced colleague stays reachable, but does not have to speak every sentence for the new person. That lets me see quickly whether someone can find their way, understand priorities and stay friendly with guests while something is also waiting at the pass. The big mistake many restaurants make is moving a new employee too early between bar, terrace, till and clearing. Then nobody learns cleanly; they only learn to be hectic.

At that stage, a clear view of tables and expected guests helps more than an abstract training script. When reservations, areas and responsibilities are visible, I can show a new colleague why table 12 matters first and why a group of four cannot simply be placed at any free table for two. That is exactly where I use a well-prepared service starts with a clear table plan, not instead of personal training, but as a shared picture of guest count, section and handover. The practical benefit is simple: the new person understands the room faster, the trainer explains less from memory, and guests see less searching at reception or in the service paths.

Till work, kitchen flow and first guest contact should not be crammed together

In the first week, I deliberately separate three learning fields: speaking to guests, order and service logic, and payment handling. If someone can already welcome guests warmly, that does not mean they must also be able to manage every split bill or special request at the till on the same day. A typical week-one mistake looks like this: the new employee takes orders half-confidently, runs towards the kitchen with doubts, and then freezes in the evening at the first group payment. It is better to show payment flows first, then do them together, and only after that let the person handle a small, controlled case alone. Guests notice immediately whether someone is being guided or is improvising in the system.

The kitchen should also be explained from the start as a rhythm, not just as a handover point. I show which orders go where, which questions the kitchen truly needs answered, and when it is better to record a short note properly instead of shouting something while passing by. In Bonzumo, that practical process can be supported because the order remains one connected transaction across table, service, kitchen and payment, and service notes have a defined place in the order flow. The aim in week one is not completeness but reliable basic behaviour. For example, a new server must know that an unclear special request gets clarified immediately before the next course moves forward. That prevents frustration for guests, kitchen and the new team member alike.

Shift planning, roles and recorded time need to be fair from the start

The first week often fails not during service itself, but in the organisation behind it. If a new employee does not know when they are really expected, where the shift begins or who is responsible for closing, every working day starts with uncertainty. I therefore only publish shifts that are prepared in substance: start time, work area, accompanying colleague and the one new task added that day. In Bonzumo, I can organise shifts, absences and publication status in one place, and that matters especially when several managers take turns onboarding. Without that structure, each of them quietly expects something different and the employee has to guess whose version applies.

It is just as important that a new employee does not receive the same system rights as an experienced shift lead. In the first week, read access, observation and one limited working area are often enough. Roles and permissions help me reflect those responsibilities properly instead of saying verbally, “please do not click anywhere.” The same logic applies to working time: start, end and exceptions need to be traceable. That is why I rely on clear shift organisation and access for the team, so a forgotten clock-out does not turn into a trust problem. The concrete benefit for the team is fewer misunderstandings, cleaner handovers and a start that is not built on improvisation.

Feedback should be small and daily, not one big verdict at the end

I do not wait until Sunday to give one broad judgement about the whole first week. Short feedback after each shift works better: what felt safe today, where did things stall, and which one point are we repeating tomorrow? Those talks often take five minutes, but they do far more than vague praise or a late comment such as “you need to be more independent.” Suppose someone is friendly with guests but still carries trays insecurely. I do not rewrite the whole rota. The next day I shorten the walking route but keep the guest contact practice in place. That keeps feedback concrete, solvable and far less personal.

The other direction matters just as much. I actively ask new employees where they still feel unsure. Many will otherwise say “it’s fine” out of politeness, even though they still have not understood the difference between order tickets, table numbers or production points. If I discover that gap only on a packed Friday evening, it is too late. Organising fairly means uncertainty can be spoken aloud without being treated as weakness. Restaurants with a fast tempo easily drift into a culture where new people would rather guess than ask. That is neither professional nor guest-friendly. A good first week makes questions cheaper than mistakes.

By the end of the week, the goal is a reliable release, not perfection

After the first week, nobody needs to be able to do everything. What matters is whether the person can handle one clearly defined area reliably. I do not decide that by instinct alone. I look at observable criteria: punctual start, safe handling of their own section, understandable communication with guests, asking for help in time, clean handover and calm behaviour when small mistakes happen. If that foundation is there, I expand responsibility in week two. If something is still shaky, I do not repeat the entire week from scratch; I repeat only the missing parts. That keeps onboarding fair while the operation stays stable.

A realistic end-of-week target in the example above would be this: the new colleague can independently handle drinks service in a small area, greet guests warmly, knows the internal contact people, records working time properly and understands when a question has to be escalated immediately. Not yet released would be complicated complaints, large group settlements or running a full solo section on a peak Friday. That limited release protects everyone involved. Employees feel real progress instead of overload, and guests meet someone who does not need to know everything yet, but who can already manage their part of the evening reliably.