HR Policy Packages for Multicuisine restaurants
What this looks like in your business
A multicuisine restaurant has more rules than its staff can recall: who may swap a shift, what a cook does when a dish is returned, how a captain handles a drunk guest at the bar, who keeps the tip or service charge, how the banquet team is rostered. Policies that live in the head chef's habits break when he is on leave. GullyHR drafts written policies in three package sizes, each with a plain-language FAQ, a workflow and forms, for your own legal adviser to review before issue. You choose the package that fits where the restaurant stands now.
Where unwritten rules cost a restaurant most
Disputes in a restaurant come from the same few places, and they are rarely about the big rules. A cook is marked absent after leaving early because the head chef agreed, but the manager did not know. Two captains disagree about who keeps the tip pool on a banquet night. A steward is warned for breakage and a cook is not, for the same error, because different supervisors handled them. A bar captain serves a guest who has had too much because no rule told him he could refuse. Heat and long hours make tempers short, and a team drawn from several regions and languages hears the same instruction in different ways. When the rule is not written, each supervisor fills the gap from habit, and staff compare outcomes. Specialist cooks, who are scarce and have other offers, take unequal treatment as a reason to go. A policy pack does not remove disagreement, but it gives every manager the same page to point to, so the answer on Saturday night is the answer on Tuesday morning.
Choosing between Starter, Core and Complete
We do not start by drafting; we start by choosing. The Starter package holds five policies that settle the most frequent arguments. For a restaurant, those are likely to be attendance and shift swaps, leave, conduct on the floor and in the kitchen, notice and exit, and the sharing of any service charge or tips. The Core package holds eleven and adds, for example, uniform and hygiene, a warning and appeal routine, kitchen safety and the handling of cash by cashiers. The Complete package holds all thirty, in three stages. We look at your existing papers, your size, whether you serve alcohol at a bar and whether you run banquets, then recommend the smallest package that covers what you really face. Before drafting, we settle management choices with the owner: what is a first warning, who can approve a swap, how tip sharing is decided, and who may refuse a guest at the bar. Every policy then follows one structure, with an employee FAQ, a workflow and any forms. Packages can grow with the restaurant, so a Starter pack is not a dead end.
Tip sharing and the bar, settled in writing
Take a multicuisine restaurant with a bar and a banquet hall. The owner has argued with her captains three times over how the banquet service charge is split, and a bar captain has served a regular who was clearly drunk. She asks for the Core package. In the choices meeting we ask her to decide, not to describe: does the kitchen share in the banquet charge, on what basis, and who announces the split? She decides that kitchen and floor each receive a share by role, declared on the notice board before each event. For the bar, she decides that any captain may refuse service and must tell the manager, who records it. These choices go into the policies on service charge and on alcohol service. The drafts include an employee FAQ in plain words and a one-page workflow. The manager reads the pages to the captains and the head chef reads the kitchen version. The owner's adviser reviews both before issue, and a small change is made on the adviser's advice.
Who owns a policy once it is issued
A policy is only as good as the person who answers questions about it. We assign an owner to each: the restaurant manager for attendance, shift swaps, conduct on the floor and uniform; the head chef for kitchen safety, hygiene and station discipline; the cashier lead for cash handling; the owner for tip sharing, warnings that end in exit, and every change of rule. Each policy carries its date of issue and its review date, and a signed acknowledgement is kept in the staff file so a captain cannot say he never saw it. Handovers are marked: from drafting to your adviser, from adviser back to the owner, and from owner to the managers who explain it to the teams. Changes go through the owner only, and the old version is kept with its date. What stays with you is the decision to adopt, to apply a rule firmly or to waive it. We do not give legal opinions, and your adviser confirms each policy against local rules before it reaches staff.