For chefs

How Chefs Can Raise Inventory Problems With the Owner

Owners respond to numbers and options. A short weekly brief with three figures, one problem and one ask turns complaints into decisions.

By ChefMind AI Team · · 5 min read

Chefs often feel like they raise the same issue again and again and nothing changes: product is short, the cooler is a mess, the budget is too tight. Owners often hear the same conversation as complaints about money. The gap is rarely about the problem. It is about how the problem arrives. This is practical advice on making it a decision, not an argument. Figures are illustrative.

This article is general guidance. It does not reflect any one chef's or owner's experience.

Bring numbers, not feelings

"We are always running out of chicken" is a feeling. "We ran out of chicken on three of the last four Saturdays, which cost us about 25 covers of the chicken special" is a fact the owner can act on.

The same goes for waste, quality and cost. Wherever you can, attach a number, a date and a dollar amount.

The one-page weekly brief

A short, regular update works better than an occasional big discussion. Keep it to one page:

  1. Three numbers: food cost against target, top waste items this week, and any notable price changes.
  2. One problem: the thing that most needs attention, with evidence.
  3. One ask: a specific decision or resource, such as a new par, a scale at receiving or a supplier change.
  4. One win: something that went well. It builds trust.

Frame the problem in the owner's terms

Owners think in cost, risk and guest experience. Translate the kitchen problem into one of those.

  • Instead of "the walk-in is a disaster", say "we threw out about $60 of product last week because it was behind other stock, and a shelving change would stop most of it."
  • Instead of "we need a better supplier", say "three short deliveries this month cost us about $140 in credits we had to chase, and an emergency run."

Propose a fix and its cost

A problem with no solution invites a defensive reply. Offer one or two options and what each costs in money and time.

OptionCostExpected effect
Add a use-first shelf and weekly date check1 hour setup, 10 minutes a weekLess spoilage
Adjust prep par for the soupNo costLess over-prep
Weigh proteins at receivingA scaleCatch short deliveries

Say what you would do, and what you need from them.

Choose the moment

Not at the pass during service. Not at close after a bad night. Pick a calm, regular time, such as the same slot each week, so it is a routine and not a confrontation.

Some phrasing that helps

  • "Here is what the numbers show, and here is what I would like to try."
  • "I want to hit our food cost target. This is where I see us losing it."
  • "If we do nothing, this probably costs us about this much a month."
  • "What would you need to see to approve this?"

Follow up

After a decision, report back: did it work? A chef who closes the loop earns credibility for the next ask.

Common mistakes

  • Raising issues only when angry.
  • No numbers.
  • Problems without proposals.
  • Blaming people, not systems.
  • Not following up.

Owners and chefs also see cost differently. See why chefs and owners disagree about food cost.

Where software can help

A weekly brief is easier when the numbers are in one place. ChefMind AI keeps ingredient quantities, expiration dates and food cost in a single system; see inventory management. A waste log can supply the waste numbers.

The short version

  • Bring numbers, one problem, one ask and one win, once a week.
  • Translate the problem into cost, risk or guest impact.
  • Propose a fix with its cost, pick a calm moment and follow up.

Frequently asked questions

What should a chef bring to a conversation with the owner?

A few numbers (food cost against target, top waste items, notable price changes), one clear problem, and a proposed fix with its cost.

How often should chef and owner review inventory and costs?

Weekly for a short check-in, with a deeper monthly review. Frequent small conversations beat one tense one.

About the author

ChefMind AI Team

Editorial team

Practical restaurant operations guidance from the ChefMind AI team. Figures marked illustrative are worked examples, not industry benchmarks.

Newsletter

Practical kitchen operations, now and then

New articles on food cost, inventory and purchasing. No spam, and you can unsubscribe at any time.