How to Set Up a Restaurant Staff Meal Policy That Doesn't Wreck Food Cost
Last updated: August 20, 2026
A staff meal policy should cap the value at $6–$10 per shift, limit it to a defined list of items (not full menu access), and require it to be rung into the POS at zero dollars so it shows up in your reporting. Do those three things and staff meals cost you 1–2% of food sales, which is normal and expected. Skip any one of them and that number creeps to 3–4% without anyone noticing until the P&L comes back wrong.
Here's the thing nobody tells new owners: staff meals aren't a line item most restaurants track on purpose. They're a byproduct of goodwill — you feed your people because it's the right thing to do, because a hungry line cook makes mistakes, and because it's basically free advertising for retention. But "free" and "untracked" are two different words, and kitchens that don't separate them end up with a food cost percentage that doesn't match their recipe costing no matter how many times they re-run the numbers. I've watched a GM burn an entire Sunday trying to find a 3-point food cost variance that turned out to be four line cooks ordering off the regular menu every night because nobody ever told them not to.
The fix isn't complicated, but it has to be specific. A real policy names who gets a meal, when, what they're allowed to order, what it's worth, and how it gets rung in. Vague policies ("staff can eat whatever, just be reasonable") always drift toward the most expensive interpretation over time, because nobody wants to be the manager who tells a good employee no over a $4 difference. Written caps take that argument out of the room entirely.
This post covers how to set the dollar cap, what to put on a limited staff menu, how to ring it into your POS so it actually shows up in reporting, the legal side of counting meals as wages, and what a real policy looks like on paper so you're not starting from a blank page.
What should a restaurant's staff meal policy include?
A workable policy sets a dollar cap per shift ($6–$10 is standard), restricts orders to a defined staff menu rather than the full menu, requires the item to be rung into the POS as a $0 comp for tracking, and states clearly whether the meal counts toward minimum wage compliance under IRS de minimis fringe benefit rules.
Why staff meals blow up food cost when nobody's watching
It's not one bad decision. It's a hundred small ones that never get corrected. A dishwasher grabs a to-go container of the $22 ribeye special because nobody told them the staff menu was different from the guest menu. A line cook takes a "family meal" portion that's actually three portions because he's cooking for his ride home too. A manager comps a meal for a friend who stopped by and calls it a staff meal because it's easier than explaining a guest comp. None of these people are stealing. They're operating without a rule, and people default to generosity when there's no rule.
The accounting problem compounds it. If staff meals get punched in as regular sales that are then voided, or worse, never rung in at all, your recipe costing and your actual plate costs stop lining up. You'll see it show up as a food cost percentage that runs high every single week even though your invoices, your waste log, and your portioning all check out. Restaurant Business has covered this exact accounting gap — the fix is treating staff meals as a distinct cost category, not folding them into either sales or waste.
Setting the dollar cap
Most full-service and fast-casual operators land between $6 and $10 per shift per employee, scaled to their average plate cost. A quick-service concept with a $3.50 average food cost per item might cap at $5. A full-service kitchen running $8–$12 plate costs might cap at $10. The number matters less than having one — write it down, post it in the kitchen, and put it in the employee handbook so there's no ambiguity when a new hire asks what they can order.
| Meal Policy Model | How It Works | Best For | Rating |
|---|---|---|---|
| Fixed staff menu | 3–5 pre-set items, no substitutions, capped value | Full-service, high check average | Best Control |
| Dollar cap, any item | Employee can order anything up to a set dollar value | Fast-casual, limited menu | Good, Needs POS Discipline |
| Family meal only | One shared pre-shift meal, no individual ordering | Smaller kitchens, tight-margin concepts | Lowest Cost |
| Unwritten / "use judgment" | No cap, no menu, no tracking | Nobody — this is how variance happens | Avoid |
Building and rolling out the policy
Once you know your cap and your model, the rollout is mechanical. The mistake most owners make is writing the policy and never training on it, which means it lives in a binder nobody reads.
Choose lower-cost, high-margin items you already prep in volume — a burger without the specialty bun, a bowl, a family-style pasta. Know the exact plate cost of each so your cap is grounded in reality, not a guess.
Every meal gets rung in under this code, even though it's free to the employee. This is the single most important step — most platforms including Toast support a dedicated comp category that reports separately from voids and discounts.
Under IRS rules, meals furnished on the employer's premises for the employer's convenience — feeding staff during a working shift — are generally excludable from wages as a de minimis fringe benefit. Confirm your setup qualifies before assuming it's automatic. See IRS Publication 15-B for the specific tests.
"Staff meal is off the staff menu, rung in as a comp, one per shift." Say it in pre-shift for the first two weeks. Policies fail because they're announced once and enforced never.
If staff meal comps run above 2% of food sales, someone's either ordering off-menu or the cap isn't being enforced at the pass. Catch it monthly, not at year-end.
What goes wrong even with a written policy
A policy on paper isn't a policy in practice if the person running the pass doesn't enforce it. The most common failure points: new hires who never got trained on the staff menu because onboarding skipped it, managers who quietly let their own comps slide because they don't want the confrontation, and multi-unit operators who write one policy for headquarters and never adapt it per location, so a $10 cap that's reasonable in one market is way under the average plate cost in another.
- Post the staff menu and dollar cap somewhere visible on the line, not just in a binder
- Include the staff meal policy in new hire onboarding, not just the handbook signature page
- Require every meal — including manager meals — to go through the $0 comp code
- Set a monthly threshold (2% of food sales is a reasonable ceiling) and review actuals against it
- Reprice the staff menu items whenever core ingredient costs shift more than 10%
Real Kitchen Example
A 90-seat gastropub outside Columbus, Ohio was running food cost 3.8 points over its recipe-costed target for four straight months. The GM assumed it was portioning drift on the fryer line and spent two weeks re-training cooks on scoop sizes with no change. When they finally pulled comp reports, staff meals weren't showing up as a separate category at all — the previous manager had trained the team to ring staff meals as 100%-off discounts on regular menu items, which meant a cook grabbing a $19 steak frites showed as a $19 discount, not a $6 staff meal. Once they built a dedicated staff menu (five items, capped at $8, priced off actual plate cost) and moved everyone to a $0 comp code, food cost dropped 2.6 points in the first full month and stayed there. The other 1.2 points, it turned out, actually was fryer oil — they hadn't been filtering consistently on double shifts, which run down usable oil life faster than the schedule accounted for. Worth checking both; they're often tangled together on a P&L. If oil life on a busy line is part of your cost picture too, this breakdown on extending frying oil life and Purimax's cost calculator are useful for running your own numbers the same way this GM eventually did.
Should staff meals count toward an employee's minimum wage?
Under federal rules, employer-provided meals during a shift, for the employer's convenience, are generally treated as a de minimis fringe benefit and excluded from wages — not counted as a wage credit. Some states have their own meal-credit rules for tipped employees, so check your state labor department before assuming federal treatment applies everywhere you operate.
What's a reasonable food cost percentage impact for staff meals?
1–2% of total food sales is the range most managed programs land in. Above 3% usually means either the dollar cap isn't enforced, the staff menu includes high-cost items, or meals aren't being rung into the POS separately from regular sales and discounts.
