What training your servers, managers and office staff need

You should not train the whole team the same way

Service staff, management, and admin each need different training. One general walkthrough is usually not enough, because the day-to-day tasks are too different. In service, the focus is on taking orders quickly, handling payments cleanly, and dealing confidently with split bills. Management needs to handle exceptions, review open transactions, and understand the daily closing. Admin usually works more with master data, reports, the cashbook, and preparing exports for accounting. If everyone gets the same training, each person hears a lot they will never use later, while the important parts for their own role stay too shallow.

For your business, role-based onboarding makes much more sense. In BonZumo, roles and permissions can be set up to match real responsibilities. That is exactly where training should begin: what does this person see in the system, what can they change, and which decisions should they be able to make on their own afterward? Then training is not just a software explanation. It becomes a translation of your operating process into concrete actions. That reduces later questions far more effectively than one long presentation for everybody.

Service should master the sales flow with confidence

For service staff, the main learning goal is not administration but a smooth process from table to payment. In training, your team should therefore first understand the table and area plan: where do I find my section, how do I open a table, how do I add follow-up orders, how do I store an order note, and how do I recognize what has already happened at that table? That is the core of the shift. If a server hesitates here, later theory will not help much. Especially in a full dining room, the flow has to work without someone searching menus first or asking about every change.

After that, typical payment situations belong in the practice session. BonZumo supports splitting bills by items or into equal shares, and it handles tips within the payment flow. That is exactly what you should train hands-on, because this is where most uncertainty comes up in real shifts. After onboarding, a service employee should be able to split a group bill on their own, post a partial payment, see what is still open on the table, and close the table only once the remaining amount has been settled. It is also important to understand that sales amount, tip, and open balance are different pieces of information. If someone has only seen that once but never done it themselves, they will almost certainly ask again during evening service.

Train service staff with practical tasks, not a long screen tour

For service, plan short, repeatable drills instead of a broad system tour. A good training package consists of five to seven standard situations that really happen in your venue. That might include a table with an additional order, a reassignment inside the person’s own section, a bill with two payment methods, a split by items, and a guest who needs invoice details. The employee should not just click through it, but also explain what they are seeing: is the table still open, which share has already been paid, where was the tip recorded, and what is still missing before the transaction is complete?

Casual staff and new starters especially benefit from this limit. At the beginning, you do not need to show them article maintenance, the cashbook, or export views if they will not handle those tasks. In fact, too many menus usually increase hesitation. A clear boundary works better. Anyone working in service should know the interface they need in their own shift and feel secure in it. If you assign roles cleanly, the team will only see the areas that fit their work anyway. That makes training easier to understand and avoids unnecessary focus on functions they do not need.

Management needs training for exceptions and control

Shift leaders, restaurant managers, or owners need a different level of depth. For this role, it is not enough to handle only standard sales. Management needs to understand how transactions connect across the day and where to step in when something does not run smoothly. That includes reviewing open tables, handling payment queries, seeing the difference between a sale and a payment, and, when needed, tracing which steps have already happened in a transaction. In BonZumo, the POS, payment overview, receipt, and closing all refer to the same transaction. That connection is exactly what matters for management.

Management training should therefore always ask: which information do I need in order to decide an exception cleanly? If a table was paid partly in cash and partly by card, management does not need to repeat every service click, but they should be able to see what has already been paid, which amount remained open, and whether a tip was recorded separately. Just as important is the view of permitted actions and responsibilities. Management has to recognize which issues the team may resolve on its own and when a higher permission level is needed. In this role, training is not only about operation. It is also about practicing the limits of intervention.

Management should be able to explain daily closing, not just open it

A particularly important training block for management is the daily closing. Anyone with responsibility should not only know where to find it, but also which questions it can answer. BonZumo brings together payment information, cash movements, Z reports, the cashbook, and the archive in the intended process. In training, management should therefore practice how to review a day: which figure comes from sales, which comes from payments, which cash movements belong to them, and where can questions about a single transaction be picked up again?

What matters here is your operating organization. The software shows information, but you decide who prepares the closing, who checks it, and who decides when there is a discrepancy. That handover needs to be part of management training. A shift leader may only need to review the closing of their own shift, while the owner may also review the cashbook and further reports. So do not simply train 'management' as one single role if your responsibilities are layered. Otherwise, you either give too little knowledge or unnecessarily broad permissions.

Admin needs master-data and closing knowledge, not service simulation

In admin, the learning goals are different from those on the restaurant floor. Here, the focus is usually on clean data maintenance, checking closings, and preparing handover to accounting. For this role, it is especially important to understand how items are created and maintained, which information later appears in sales, and what practical consequences a change can have. If items, categories, or location-specific menus are maintained in BonZumo, admin should understand that every change will be felt in sales. That is why this training should not copy the speed of service. It should focus on controlled work with a clear approval process.

Admin should also learn how to work with reports, the cashbook, and the DATEV preview. BonZumo can prepare a DATEV booking batch with a preview. That is useful for handover to your accountant or finance lead, but it does not replace complete accounting training. That boundary should be very clear in training. Admin should recognize which assignments and entries matter for the export, which notices or checks may appear, and when they need to coordinate with your tax advisor or internal responsibility. Someone trained well here asks better questions and changes less based on guesswork.

Treat item maintenance as a risk task, not a side topic

Many businesses underestimate training for item maintenance. In reality, it is sensitive work, because small changes can have a large effect. A wrongly assigned item, an unclear category, or a misleading label will later affect service, kitchen work, and closing at the same time. If admin or management maintains items, the training should always be tied to concrete decisions. What may be changed during live business, what is better changed outside peak hours, and who checks a change before it becomes relevant for everyone? This organizational side is often more important than the pure click path.

It helps to let every role that maintains data complete one full exercise: find an existing item, make a clear change that others can follow, check the effect in the selection, and then clarify whether further adjustments are needed in the business. If you also work with recipes, costing, or location-specific menus, you should discuss which change belongs in which place. Not everyone who understands a sales transaction should automatically be allowed to change master data. Here, training also serves to keep permissions deliberately narrow and to approve substitutes only in a targeted way.

Roles and permissions must be part of training, not just setup

The question of proper training cannot be separated from access permissions. If someone sees functions during training that will not actually be available later in daily work, confusion is inevitable. The reverse is just as risky: if a person can do more in live operation than they were ever taught. In BonZumo, roles and permissions help keep responsibilities in the team clear. Do not use that only as a technical setting. Use it as a training principle too. Always train people in the same view they will really use later. Then they get to know exactly the interface that belongs to their task.

In practice, that means service trains in the sales and payment flow. Management additionally trains control questions and closing questions. Admin works in maintenance, reporting, and export views. Only after that should you check whether someone also needs a backup role. That order matters, because otherwise backup easily turns into hidden full access. If, for example, the office occasionally prepares the daily closing, that person does not automatically need the same intervention options as the operational manager during evening service. Keep core role and exception role clearly separate when preparing your training.

One independent core task per role shows whether training is enough

You can tell whether training was good not by the fact that everyone nods politely, but by whether each role can complete its own core task without help. For service, that might be a split group bill with a tip. For management, it might be reviewing an open transaction and placing it correctly in the daily closing. For admin, it might be controlled item maintenance or preparing an export with the DATEV preview. These tasks are close to daily work and show much faster than any general Q&A where understanding is still missing.

What matters is that the task is complete. A server who only knows where to click 'split' but does not understand why the table remains open is not fully trained yet. The same goes for an admin employee who starts an export but cannot classify the notices in the preview window. So after every training session, plan a short practical final round. Not as a formal exam, but as operational safety: who can really work after the introduction, who needs one more exercise, and whose permissions should remain restricted until then?

Backups and handovers decide whether your training works in real life

The real stress test usually does not come in the first week. It comes when someone is ill, a temporary worker jumps in, or a shift ends differently than planned. That is why backup roles should be an explicit part of your training concept. Think through, for each role, what truly has to be covered in an absence and what can wait. A service backup almost always needs secure access to ordering and payment. A management backup mainly needs orientation for open transactions and for handover into closing. An admin backup usually needs less speed, but more accuracy in maintenance and documents.

Set simple handover rules for this. Who finishes which tasks before the end of the shift, where are open questions documented, and which cases must be passed to the next responsible person? BonZumo makes these decisions easier because transactions, payments, receipts, and closing information belong together instead of being scattered across separate notes. Even so, you still need to define organizationally when someone is only informing the next person and when they may actually intervene. Good training therefore answers not only 'How do I do this?' but also 'When am I responsible, and when do I get help?' That is exactly what turns a software introduction into a reliable operating process.