OPERATIONAL FRAMEWORKS
KITCHEN DESIGN ADVISORY
Optimizing flow and functionality for high-volume output. I consult on spatial layout, equipment specification, and ergonomic station design to reduce friction and improve line speed.
STANDARD OPERATING PROCEDURES
I develop the full suite of kitchen SOPs: opening and closing procedures, station setup standards, prep specifications, cleaning protocols, and service checklists. Written, formatted, and ready for implementation — not generic templates.
RECIPE & PRODUCTION SYSTEMS
Scaling culinary creative into operational consistency. I build production logs, sub-recipe costing, and yield testing frameworks that protect margins without sacrificing culinary integrity.
TRAINING FRAMEWORKS
Systems only work if the team understands and applies them. I build training structures for new hires and existing teams — position-specific, practical, and tied directly to the operational standards of the concept.
PRE-OPENING KITCHEN SETUP
For new openings, I manage the kitchen setup process: equipment commissioning, station buildout, mise en place systems, and service simulations before the first real cover. A kitchen that opens organized opens better.
WHO THIS IS FOR
- Hotels and independent restaurants in pre-opening or concept transition
- Operations building a kitchen from the ground up or undertaking significant renovation
- Restaurants that have grown without formalizing their back-of-house systems
- Executive Chefs and F&B Directors who need an external systems partner
FREQUENTLY ASKED QUESTIONS
What are kitchen systems, and why do they matter more than recipes?
Kitchen systems are the defined, repeatable structures that govern how a kitchen produces food: how prep is planned and assigned, how recipes are documented and costed, how stations are set and checked, how ordering and receiving work, how new cooks are trained, and how standards are verified. A recipe describes one dish. A system determines whether that dish arrives identically on a Tuesday lunch with two cooks and on a Saturday night with a full brigade. Kitchens that run on individual talent perform brilliantly until the person carrying them leaves. Kitchens that run on systems perform consistently and can be scaled, staffed, and handed over. Recipes are content. Systems are infrastructure.
What should a commercial kitchen SOP actually contain?
Enough to be executed by a competent cook who has never worked in your kitchen, and no more. A usable SOP defines the task, the standard it must meet, who owns it, when it happens, what equipment and product it requires, and how completion is verified. It should be readable in under a minute at the station. Most SOP binders fail for the opposite reasons: they are either so vague that they restate the obvious, or so exhaustive that no one opens them after week one. The other common failure is that they document the ideal kitchen rather than the real one. An SOP describing a mise en place that has never actually been achieved simply teaches the team that documentation can be ignored.
How do you design a commercial kitchen layout for real production volume?
By working backward from the menu and the covers, not forward from an equipment list. Design begins with what the kitchen must produce at peak, item by item, by daypart, and translates that into the production steps, equipment capacity, and station structure required to deliver it. From there the layout is organized around flow: receiving to storage to prep to production to plating to pass, with as little backtracking and cross-traffic as possible. The failures that are expensive to correct are almost always dimensional and structural, insufficient refrigeration near the line, undersized ventilation, a pass that cannot hold the covers, a single aisle carrying prep traffic through the hot line during service. Equipment can be replaced later. Circulation and infrastructure cannot.
Our kitchen is already built. Can systems fix a bad layout?
Systems cannot move a wall, but they can substantially reduce what a bad layout costs you. Most kitchens I assess are losing far more to poor sequencing than to poor architecture. If prep is scheduled so that two stations compete for the same equipment at the same hour, if product is stored where it generates unnecessary trips during service, or if the plating sequence forces cooks across the aisle at peak, those are scheduling and organization problems solvable without construction. The approach is to identify which constraints are genuinely physical and which are habitual, fix the second category immediately, and stage the first into a capital plan with a realistic priority order rather than a wholesale rebuild.
How do you build a prep and production system that survives staff turnover?
By removing the dependency on memory. A durable production system consists of documented recipes with yields and specifications, par levels tied to forecast rather than intuition, prep lists generated from those pars rather than written from scratch each morning, clear ownership of each task by station and shift, and a verification step so that gaps are caught before service rather than during it. The test is straightforward: if your strongest sous chef does not arrive tomorrow, does the kitchen still know what to produce, in what quantity, to what standard? In most operations the honest answer is no, which is why turnover in one position causes weeks of disruption. The objective is a kitchen where competence is transferable.
What training frameworks keep standards consistent across shifts?
Structured onboarding with defined competencies, station certification, and a verification cycle. New cooks should progress through a documented sequence with a stated standard at each stage, rather than absorbing the job by proximity to whoever is nearby. Station certification means a cook is signed off on a station by someone accountable, against explicit criteria, before they run it unsupervised. Verification means a recurring check, line checks, tasting, spec review, that catches drift early, because standards do not collapse suddenly, they erode. The framework also has to define who owns training. When it belongs to everyone in general it belongs to no one, and the standard becomes whatever the busiest person had time to demonstrate.
How do you set up a kitchen for a new opening?
In a defined sequence tied to the construction and licensing calendar. Equipment specification and layout are settled first, because they constrain everything downstream. Recipes, yields, costing, and plate specifications are completed before hiring, so the kitchen is being staffed against a known production requirement. Par levels, prep structure, and ordering systems are built and populated with forecast data before the first delivery. Then the brigade is hired, trained against those documented standards, and run through production rehearsals under simulated volume. Only then does the kitchen meet guests. Openings that reverse this order, hire first, formalize later, spend their first three months building in public, which is the most expensive place to do it.
How do kitchen systems reduce food cost and waste?
Through control at each point where product is lost, most of which sit outside the recipe. Accurate par levels reduce over-ordering and spoilage. Documented yields make purchasing decisions comparable across vendors and specifications. Portion control and plate specifications remove the silent variance between one cook's plate and another's. Structured receiving catches short deliveries, substitutions, and price changes at the door rather than at month end. Production planning aligned to forecast keeps prep from outrunning demand, which is where most usable product is lost. And inventory discipline makes theoretical versus actual variance visible early enough to investigate. Each contributes a modest amount. Together they typically account for the several points of food cost that no single change ever explains.
How do you get an experienced brigade to adopt new systems?
By involving them in building the systems and by proving the systems reduce their workload rather than add to it. Experienced cooks resist new documentation for a rational reason: they have usually seen initiatives arrive, add administrative burden, and disappear. The approach is to start with the pain points the team already complains about, deliver a visible improvement there first, and expand from that credibility. Standards should be built with the people who will run them and reflect how the kitchen actually works. It also requires consistent reinforcement from the executive chef and the general manager, because a system that leadership does not follow is a suggestion. Adoption is an operational outcome, not a matter of enthusiasm.
How long before kitchen systems show measurable results?
Waste and ordering discipline usually move within two to four weeks, because par levels and receiving controls take effect immediately. Food cost variance typically tightens over one to two full inventory cycles, which means six to eight weeks before the numbers are trustworthy. Consistency and ticket times improve on a longer curve, generally three months, because they depend on training penetrating every shift rather than only the strong ones. Cultural durability, systems holding without the chef enforcing them daily, takes closer to six months. Anyone promising a transformed kitchen in three weeks is describing a temporary improvement produced by attention, which reverses as soon as the attention leaves.
Do you help with equipment specification and vendor selection?
Yes, as part of design advisory and pre-opening work. Specification is driven by the production requirement rather than by catalog tier: what the menu demands at peak, in what quantity, within what footprint, service capability, and budget. That analysis frequently reveals both over-specification, expensive equipment bought for volume the operation will never reach, and the under-specification that causes daily pain, usually refrigeration and ventilation. I work with your chosen dealers and vendors rather than carrying commercial relationships with them, because specification advice should not be influenced by who is selling the equipment. Service coverage, parts availability, and realistic replacement cycles are part of the evaluation, not afterthoughts.
RELATED SERVICES
Systems exist to produce a menu. When the menu is rewritten, recipe architecture, prep structure, and par levels have to be rebuilt with it or the new dishes drift immediately.
The most efficient time to build kitchen systems is before the kitchen opens, when standards can be established rather than retrofitted onto existing habits.
A diagnostic determines which problems are genuinely systemic and which are physical, so investment goes to the constraint that is actually limiting the kitchen.
Kitchen systems usually sit inside a broader operational structure covering leadership, cost control, and multi-outlet alignment.
Documented kitchen rebuilds and systems implementations, with the operating conditions before and the measurable outcomes after.