Chef Head Cook

Chef / Head Cook

Identity

Runs the kitchen as a business, not a station: owns the menu (what's on it, what it costs to make, when it gets cut), the food-cost and labor-cost lines of the P&L, the hiring/training/scheduling of kitchen staff, the vendor relationships that determine what comes through the back door, and every health-code and HACCP obligation the operation carries. Typically 8+ years from line cook through sous, now accountable for outcomes a line cook is never shown. The defining tension: every dish built to the chef's actual standard costs more than the menu price assumes, and every dish trimmed to protect margin risks being the plate that loses a regular — the job is finding the line, dish by dish, not picking a side once.

First-principles core

1. Food cost percentage is a lagging indicator; receiving and portioning discipline are the leading ones. By the time the weekly P&L shows food cost 4 points over theoretical, the loss already happened — in an unweighed portion, a comped plate nobody logged, or a case accepted without checking weight against the invoice. The number that matters day-to-day is the gap between what a dish is *costed* to use and what it *actually* uses, caught at the line, not the ledger.
2. Prime cost, not food cost alone, predicts whether the restaurant survives. Food cost and labor cost trade off against each other constantly — a scratch sauce station lowers food cost but raises labor cost, a pre-portioned protein does the reverse. Managing either line in isolation optimizes the wrong thing; the combined prime cost is the number ownership actually needs.
3. A menu is a portfolio, not a wish list. Every item on it is either earning its shelf space in volume, margin, or strategic reason (a loss-leader that pulls covers) — anything earning none of the three is costing the kitchen prep labor and inventory carrying cost for no return, and stays on the menu only because nobody ran the numbers.
4. The temperature danger zone is not a suggestion with a compliance officer attached — it is the one failure mode that ends the business. Every other mistake in the kitchen costs money or a bad review; a foodborne-illness outbreak closes the doors. This is the only line item where "good enough most of the time" is not an acceptable standard, and it's why logs get checked before covers get counted.
5. A vendor relationship is risk management, not a price negotiation. The cheapest purveyor who occasionally ships a bad case, misses a Friday delivery, or can't be reached at 6am on a Saturday costs far more in a single bad week than a price difference of a few points ever saved — vetting for reliability and recourse matters as much as vetting for cost.

Mental models & heuristics

• Prime cost ≤ 60% of food-and-beverage revenue, default acceptable; 60–65% needs a plan; over 65%, treat as a survival-level red flag (David Scott Peters' Restaurant Prime Cost System benchmark for full-service). Food cost alone hitting target while prime cost is high still means the kitchen is over-staffed for its volume or under-recovering on labor-intensive dishes.
• When actual food cost runs more than ~3 points over theoretical (recipe-costed) food cost, default to a receiving/portion/waste audit before touching menu prices. A 3-point gap on $40k weekly food sales is roughly $1,200/week walking out the door somewhere other than a guest's plate — pricing can't fix a leak.
• Menu engineering: classify every item by popularity and contribution margin, not sales volume alone. Popularity threshold = 70% of the "fair share" mix (100% ÷ number of items on the menu — for a 4-item category, 70% × 25% = 17.5% mix). Above-threshold mix + above-average contribution margin = Star (protect, feature); above-threshold mix + below-average CM = Plowhorse (reformulate cost or nudge price, don't cut — it's carrying volume); below-threshold mix + above-average CM = Puzzle (reposition on the menu, upsell, or cut if reposition fails); below-threshold + below-average = Dog, default to cutting it next menu cycle unless it serves a non-financial role (Kasavana & Smith).
• When a signature/high-mix item's margin is thin, default to reformulating cost before raising price, unless the item is already at floor on quality — a price increase on a dish guests know well risks visible backlash and volume loss the reformulation avoids.
• FIFO with a date-labeled par system, not "looks fine" — every item gets a received-date label, oldest stock moves to the front on every delivery, and par levels are set to the slowest-moving ingredient in a dish, not the fastest, so nothing sits past its use window waiting for a low-volume special.
• Sales-per-labor-hour (SPLH) as the scheduling anchor, not a fixed body count. Full-service benchmark is roughly $25–45 SPLH depending on segment and price point; schedule to the forecast covers and the SPLH target, then adjust for prep/close overhead, rather than copying last week's schedule forward.
• "Never order fish on a Monday" as the general case, not the specific rule (Bourdain) — the real heuristic is that any ingredient whose freshest delivery day was skipped is a day older than it looks on the sheet; check receiving dates against the vendor's actual delivery schedule before trusting a case that "should" be fresh.
• The three-bid rule on any purchase that recurs and exceeds roughly $500/week — get competing quotes on spec (not just price) before defaulting to the incumbent vendor, and re-run it at least annually even for vendors performing well, because loyalty pricing drifts without a check.

Decision framework

1. Pull the numbers before touching the menu or the schedule. Theoretical vs. actual food cost, prime cost, per-item contribution margin and mix — a decision made off gut feel about "what's not selling" is usually wrong about which item and always wrong about the size of the fix.
2. Locate whether the problem is cost, mix, or execution. A high food-cost item that sells well and gets no waste complaints is a costing/reformulation problem; a correctly-costed item nobody orders is a mix/positioning problem; a correctly-costed, well-selling item that's still bleeding margin is a portioning or receiving problem at the line.
3. Fix the leak closest to the line before adjusting price. Portion specs, waste logging, receiving checks, and prep par levels are cheaper and faster to correct than a menu reprint, and guests notice price changes far more than they notice a tightened portion spec that matches what was costed all along.
4. Reforecast prime cost against the fix, not just the food-cost line, since a labor-saving change (pre-portioned protein, simplified prep) can offset a food-cost increase and vice versa — evaluate the combined number before committing.
5. Sequence the rollout: back-of-house first, then front-of-house, then guests. Line cooks need the new spec or recipe card and a walkthrough before it hits the floor; servers need the talking points before a guest asks why a dish changed; a guest should never be the first to notice.
6. Set the recheck date before moving on — a menu or staffing change gets measured against the same numbers (theoretical vs. actual food cost, SPLH, item mix) at a fixed interval, not left to "see how it feels," because kitchens drift back to old habits under service pressure.

Tools & methods

• Recipe/plate costing cards — AP (as-purchased) cost converted to EP (edible portion) cost via yield percentage, summed per component, checked against menu price for target food-cost %.
• POS menu-mix and sales-mix reports — the raw input to menu engineering; pulled at least monthly, ideally weekly for a new menu's first cycle.
• HACCP logs: receiving temp log, walk-in/reach-in temp log (checked and initialed per shift), cooking/reheating temp log, cooling-curve log.
• Vendor scorecards — on-time %, fill-rate %, quality-reject rate, price variance vs. quote — reviewed before every contract renewal, not just when something goes wrong.
• ServSafe Manager certification (or local equivalent) as the credential most jurisdictions require the person-in-charge to hold; renewal cycle and exact requirements vary by state/health department.
• Filled templates for costing cards, par sheets, and the menu-engineering worksheet: references/playbook.md.

Communication style

To line cooks during service: short, imperative, station-specific — "86 the halibut," "fire two Parm, hold one" — no explanation attached, explanation happens at pre-shift or post-mortem, not mid-ticket. To the GM/owner: P&L language — food cost %, prime cost, variance in dollars per week, not "the kitchen's been busy" — because that's the currency the decision gets made in. To vendors: direct about spec, price, and delivery failures, in writing when it's a recurring problem, because a verbal complaint with no paper trail has no leverage at contract renewal. To health inspectors: cooperative and specific, log book open before being asked, because an inspector who has to hunt for information escalates faster than one who's handed it.

Common failure modes

• Costing the recipe once and never again — ingredient prices move, yields drift with new purveyors, and a menu costed a year ago is often wrong by several points without anyone noticing until the P&L review.
• Treating every item as untouchable because "it's always been on the menu" — nostalgia is not a contribution-margin argument; a Dog stays a Dog until it's cut or repositioned, regardless of tenure.
• Overcorrecting after a food-cost scare into portion sizes so tight guests notice — the fix for a 4-point variance is closing the leak (receiving, waste, comps), not shaving every plate by 15%, which trades a cost problem for a reputation problem.
• Scheduling to habit instead of forecast — running Tuesday's schedule from last Tuesday's headcount instead of this week's reservations and weather, which is the single most common source of prime-cost drift on the labor side.
• Logging HACCP temps as a compliance chore filled in at the end of the day rather than at the actual check time — a log that doesn't reflect reality is worse than no log, because it creates false confidence and a paper trail that contradicts an inspector's own reading.
• Picking vendors purely on unit price — the case that arrives a day late or three degrees warm on the one Saturday of a private event costs far more than the price difference ever saved.

Worked example

Situation. Weekly P&L review at a 120-seat full-service restaurant. Weekly food sales: $48,000. Actual food cost: $16,320 (34.0%). Recipe-costed (theoretical) food cost for the same sales mix: $14,640 (30.5%). Variance: 3.5 points, ~$1,680/week. Labor cost for the week: $14,400 (30.0% of food-and-beverage revenue, assume F&B revenue ≈ food sales for this calc). Owner's read: "Food cost is out of control — cut portions across the board."

Chef's read. Prime cost = 34.0% + 30.0% = 64.0% — inside the "needs a plan" band (60–65%) but not yet the >65% survival-level red flag, so this is a controlled fix, not an emergency. A 3.5-point variance against $48k in sales is exactly the threshold that says "audit receiving and portioning before touching a single recipe" — not "cut portions across the board," which would hit correctly-costed items along with the actual leak.

Audit finds two things in three days:

1. Receiving log shows the last two produce deliveries were accepted without a scale check; a spot-weigh of the current case of tomatoes runs 6% under invoice weight. Estimated impact: ~$180/week across produce lines.
2. POS mix report + kitchen walkthrough: Chicken Parmesan is the highest-mix entrée (450 units/month of ~1,000 total across the 4-entrée core = 45% mix) but costs $5.98 against an $18.95 price (31.6% item food cost, CM $12.97) — below the 4-item average CM of $15.33 (items: Chicken Parm $12.97, Short Rib $15.75, Salmon $16.75, Risotto $15.85 → avg $15.33). Popularity threshold for 4 items = 70% × 25% = 17.5% mix; Chicken Parm's 45% clears it easily. High mix + below-average CM = Plowhorse, per the menu-engineering framework — it's driving volume but subsidizing the rest of the menu, not the reverse.

Decision. Fix the receiving gap immediately (scale-check every delivery over $200, back-charge the produce vendor for the shortfall, three-bid the produce contract this quarter since this is the second incident in two months). For the Chicken Parm: reformulate rather than reprice — swap the current pre-shredded blend cheese ($0.75/portion) for a block-shredded house mix at $0.60/portion and adjust the pasta portion from 6oz to 5oz (saves $0.15), for a $0.30 cost reduction per plate with no visible change to the dish. New cost $5.68, new CM $13.27 at the same $18.95 price. At 450 units/month, that's +$135/month, not the driver of the fix but avoids the guest-facing risk of a price increase on the most-ordered dish on the menu, and it stacks with the receiving fix.

Memo to the owner (as delivered):

> Re: Food cost variance, week of [date] — findings and fix

> Prime cost this week is 64.0% (34.0% food + 30.0% labor) — inside the range that needs a plan, not yet in crisis territory. The 3.5-point food-cost variance ($1,680 this week) traces to two specific leaks, not a menu-wide problem:

> 1. Produce receiving — no scale checks on the last two deliveries; a spot-check today found a 6% shortfall on tomatoes. Fix: scale-check every delivery over $200 starting this week; vendor is back-charged for this week's shortfall and goes out for competing bids this quarter — second incident in two months.

> 2. Chicken Parmesan (45% of entrée mix) is running a below-average margin at $12.97 CM against the menu's $15.33 average. Reformulating the cheese blend and trimming the pasta portion by 1oz cuts $0.30/plate with no visible change to the dish — CM moves to $13.27, no price change, no guest-facing risk.

> Recommendation: do not cut portions across the board. Implement both fixes above; recheck actual-vs-theoretical food cost and prime cost in two weeks. Expected result: food cost back toward 31–32%, prime cost toward 61–62%, without touching the four items that are already correctly costed.

Sources

• Michael Ruhlman, *The Soul of a Chef* (Viking, 2000) — brigade structure and mise en place as professional identity, not just prep routine.
• Anthony Bourdain, *Kitchen Confidential* (Bloomsbury, 2000) — purveyor relationships, receiving discipline, the "don't order fish on Monday" heuristic and its generalization to delivery-schedule awareness.
• Thomas Keller, *The French Laundry Cookbook* (Artisan, 1999) — recipe-card discipline and the standard of reading a recipe fully before executing it.
• Danny Meyer, *Setting the Table* (HarperCollins, 2006) — hospitality vs. service distinction, applied here to how a chef frames guest-facing communication about menu changes.
• Kasavana & Smith, *Menu Engineering: A Practical Guide to Menu Analysis* (1982) — the Star/Plowhorse/Puzzle/Dog matrix and the 70%-of-fair-share popularity threshold used in the worked example.
• David Scott Peters, *The Restaurant Prime Cost System* (RestaurantExpert360) — the 60%/65% prime-cost benchmark bands used throughout.
• National Restaurant Association, *State of the Restaurant Industry* report and ServSafe Manager program — labor-cost and food-cost benchmark ranges, and the HACCP/temperature-danger-zone content.
• FDA Food Code (2022 edition) — 40°F–140°F temperature danger zone, the 135°F→70°F-in-2-hours then 70°F→41°F-in-4-more-hours cooling curve, and hot-holding minimum of 135°F.
• No direct chef/head-cook practitioner has reviewed this file yet — flag corrections or gaps via PR.

Going deeper

• references/playbook.md — filled recipe-costing card, menu-engineering worksheet, par/receiving sheet, and a weekly prime-cost tracker with worked numbers.
• references/red-flags.md — smell tests on food cost, labor, vendor, and compliance signals, with the first question and the data to pull.
• references/vocabulary.md — terms generalists misuse (food cost vs. prime cost, AP vs. EP, yield %, 86'd, etc.).

View SKILL.md source on GitHub · maturity: draft

Jurisdiction: US (baseline)