Restaurant Loss Prevention Training: What to Teach and When

Most restaurant loss prevention training happens once, during onboarding, somewhere between the allergen sheet and the uniform policy. Three weeks later nobody can tell you who is allowed to approve a comp.

That is the whole problem. The controls that protect a restaurant’s margin are procedural: count this, log that, never do both jobs yourself. Procedures decay unless somebody keeps teaching them. This guide covers what belongs in the training, who should deliver it, how often to repeat it, and how to tell whether it worked. For the wider picture of where the money goes in the first place, start with our guide to restaurant loss prevention.

Key Takeaways

• Employee theft accounts for roughly 75% of inventory shortages and about 4% of restaurant sales (Restroworks, retrieved 2026-09-29), and most of it runs through procedures staff were never properly taught.
• Onboarding-only training fades within weeks. Build a quarterly refresh cycle and a trigger for policy changes.
• Teach the procedure and the reason behind it. Staff who know why blind drops exist stop treating them as distrust.
• Train on delivery and off-premise scenarios too, because that is where newer losses concentrate and where most programs have nothing to say.
• Measure the training against void rate, comp rate, drawer variance and food-cost gap, not against completion certificates.

What restaurant loss prevention training has to cover

A working program covers five areas. Anything less and you have a cash-handling class, not a loss prevention program.

• Cash handling: drawer counts, blind drops, deposit procedure, what to do when the drawer is short
• POS discipline: unique logins, void and refund procedure, who approves a comp and how it gets recorded
• Inventory and receiving: counting, rotation, waste logging, checking deliveries against the order
• Physical security: key control, alarm codes, safe access, opening and closing security checks
• Off-premise and delivery: recognising fraudulent orders, packing and handoff verification, what to document when a customer claims an order never arrived

The fifth one is the gap in most restaurants. Programs written five years ago cover the dining room thoroughly and say nothing about the third of revenue that now leaves through the back door in a bag. Our guide to restaurant delivery fraud breaks down the individual schemes; the training job is turning those into scenarios your staff can recognise mid-shift.

Who should run loss prevention training

The general manager owns the program, but the person who delivers each piece should be the person who owns that process day to day. The bar manager teaches bar variance. Whoever receives deliveries teaches receiving. The GM teaches cash and POS.

This matters more than it sounds. Training delivered by a manager who does not personally run the procedure gets taught as a rule. Training delivered by the person who lives with it gets taught with the reasons attached, and the reasons are what survive.

Avoid outsourcing the whole thing to a video module. Off-the-shelf compliance video is fine for the legal baseline and useless for the part that actually prevents loss, which is your restaurant’s specific procedure for your specific POS.

Cash handling training for servers and bartenders

Start here because cash is where new staff make honest mistakes that look identical to theft, and because the procedures are short enough to teach in fifteen minutes.

Count the drawer blind. Teach staff to count without looking at the POS total first. Explain why: a known target turns a short drawer into a corrected drawer, and then nobody ever learns that the shortage happened.

Never share a login. The most common well-meaning violation in a restaurant is a busy server borrowing a manager code. Teach the alternative, which is to call the manager over, and make sure managers actually come over, because a control that slows service down gets routed around within a week.

Follow one procedure for shortages. Report it, log it, do not make it up out of tips. Shortages that get quietly covered are shortages you never find the cause of.

Handle the deposit out of sight. Counting money in view of the dining room is both a security risk and a bad habit.

Say the quiet part in the session: these rules exist to protect honest employees as much as the business. A server who follows the procedure has a record that clears them. That framing changes how the room receives the whole program.

Teaching staff to spot POS and comp abuse

Every restaurant’s POS produces exception reports: voids, discounts, refunds, reopened checks, no-sale drawer opens. Managers review them. Staff should understand that they exist and roughly what they show.

That transparency does more work than surveillance does. A team that knows every void carries a name and a timestamp behaves differently from a team that assumes nobody looks.

Teach the specific procedures:

• A void before payment and a void after payment are different events and get handled differently
• Comps get recorded with a reason and a manager name, every time, including the owner’s table
• Refunds go back to the original payment method, never to cash or a different card
• A reopened check needs a stated reason

Then run the scenarios. What do you do when a regular asks you to ring their cocktail as a soft drink? When a coworker asks you to void their mistake on your login? When a manager comps their own meal? Staff who have thought about these once in a training room handle them far better than staff meeting them for the first time on a Friday night.

Training the receiving and inventory side

Kitchen and stock training is usually treated as a food-safety topic and taught nowhere near the loss prevention material, which is why receiving stays the quietest leak in most restaurants.

Teach the receiving crew to check the delivery against the purchase order rather than the invoice that came with it. Teach them to weigh at least one case of anything priced by weight, and to refuse short or substituted product rather than sorting it out later. Teach the waste log, with a reason code on each entry, because the reason is what tells you which process failed.

Make it explicit that the person who orders should not be the person who receives, and explain the reason rather than just assigning it. Duty separation feels arbitrary until someone explains that it removes the single most common opportunity for long-running loss.

Key control, opening and closing security checks

The physical security piece is small, concrete, and frequently skipped.

Every member of staff who holds a key or an alarm code should be able to say who else holds one and what the procedure is when someone leaves the business. Codes should change when a keyholder departs, and staff should know that as a rule rather than discovering it did not happen.

The opening and closing checklists should include security steps, not just operational ones: check the premises for overnight tampering, verify the alarm state, confirm the safe is locked, audit open checks before the close, and secure rear and side doors. Signed by name, because an unsigned checklist is a piece of paper.

How often to run loss prevention refreshers

Onboarding, then quarterly, then on every policy change. That is the cadence that holds.

The onboarding session should be scheduled as its own block rather than folded into a general orientation, because material presented alongside parking instructions gets weighted like parking instructions. Quarterly refreshers can be short: fifteen minutes in a pre-shift meeting, one topic at a time, rotating through the five areas.

Policy changes get their own briefing immediately. A new comp approval rule that arrives by group message will be followed by roughly half the team.

Two things extend the shelf life of all of it. Rotate duties, so no one person settles into unwatched control of a process. And give people a way to raise concerns without putting their name on it. An anonymous channel gets used, and a suggestion that you speak to your manager about your manager does not.