Operations
No line cook sets out to sabotage a recipe. Consistency erodes in smaller moves than that, a heavier pour because the bottle was almost empty, a portion that grew because the scale wasn't handy, a substitution made under pressure during a Friday rush and never mentioned again. None of it looks like a problem in the moment. All of it is the same problem, repeating.
Recipe drift is quiet. That's what makes it expensive.
How a recipe drifts without anyone deciding to change it
Inconsistency rarely starts as a decision. It starts as an accumulation:
Portion creep. A scoop that's "close enough" today is a different close enough tomorrow, and six months later the recipe's actual portion size bears no relationship to what it was costed against.
Substitution without documentation. An ingredient runs out, someone swaps it, service continues — and the recipe never reflects what actually went out the door.
Technique variation across shifts and staff. The recipe says "reduce until nappe consistency," and five different cooks interpret that five different ways, especially without a reference photo or a trained eye checking it.
Equipment differences between stations or locations. The same recipe cooked on different equipment doesn't behave the same way, and a recipe that doesn't account for that will drift by definition.
No feedback loop. If nothing catches the drift, it doesn't correct itself. It just becomes the new normal — until someone eventually asks why this dish doesn't taste like it used to.
Where the cost actually shows up
Recipe inconsistency doesn't show up as a single bad number. It shows up as several smaller ones, in different departments, that rarely get connected back to the same root cause:
Food cost. A portion that's crept up 10% is a food cost that's crept up right alongside it — invisible until the monthly numbers come in high and nobody can say exactly why.
Guest experience. Regulars notice inconsistency before management does. A dish that's better some nights than others reads as unreliable, and unreliable is a hard reputation to shake, especially in a review-driven market.
Training cost. Every inconsistent recipe becomes harder to train against, because there's no single correct version to teach. New hires are trained on whichever version the person training them happens to make.
Waste. Inconsistent yields and portions make inventory and prep planning a guessing game, which tends to resolve toward over-ordering and over-prepping — waste with no clean line back to a cause.
Multi-location brand risk. A dish that's excellent at the flagship and mediocre at location four isn't a minor variance. It's two different guest experiences under the same name.
Catching drift before it becomes the new baseline
Recipe consistency isn't maintained by writing a good recipe once. It's maintained by a system that keeps checking the recipe against reality:
Recipes specific enough to remove guesswork — exact weights, named techniques, plating references, not ranges and approximations.
A single current version, so there's no ambiguity about which recipe is the correct one on any given night.
Cost tied to the recipe, so a portion or ingredient drift shows up as a margin change immediately, not three months later.
Visibility across locations, so a manager can see that location four's version has quietly diverged from the standard — before a guest does.
A record of what changed and when, so drift can be traced back to a cause instead of discovered as an unexplained trend.
Consistency is a system, not a discipline problem
It's tempting to treat recipe drift as a staffing or training issue — tighten up, retrain, remind people to use the scale. That helps, but it doesn't hold, because the underlying problem is that the recipe itself isn't specific enough, current enough, or visible enough to catch drift when it happens. Discipline fades under a Friday-night rush. A system doesn't.
This is the core of what Yes, Chef! is built to do: keep every recipe precise, current, and costed, with the visibility to catch drift across every station and every location before it becomes the new normal — so the dish a guest orders in October tastes like the one they loved in June.
The kitchens with a reputation for consistency aren't the ones with the strictest managers. They're the ones whose recipes don't leave room for drift to begin with.
