The ACF Certified Executive Chef (CEC) credential is aimed at chefs who run kitchens, so effective preparation shifts from practicing recipes to practicing decisions: how you diagnose a rising food cost, handle a cooling failure on your watch, and correct a recurring attendance problem. This guide teaches named management concepts — menu engineering categories, progressive discipline, HACCP-style oversight — through worked scenarios with a plausible wrong turn and a better decision. Work through each scenario on paper, write your answer first, then compare it against the reasoning here and score yourself with the readiness checks at the end.
Shifting from cook-level answers to executive-level decisions
The CEC scope spans culinary leadership and management, food safety, finance, nutrition, operations, and HR. Scenario questions ask what the executive chef decides and assigns, not how the cook executes the task.
A cook-level answer describes technique: sear, chill, reheat, plate. An executive-level answer owns the system: who is trained, what standard applies, how compliance is verified, and what happens when it fails. When you read a scenario stem, first place it in a domain — finance, safety, operations, HR — then name the management tool that fits, such as a yield test or a documented counseling session. Naming the tool is what separates a justified decision from an opinion.
Practice this translation explicitly. Take a plain task you know well, such as blanching vegetables, and rewrite it as three executive decisions: the standard (quality and safety parameters), the assignment (who checks what and when), and the exception (what triggers stopping production or retraining). Write these out for a dozen tasks from your own kitchen. If your answers still read like instructions to a line cook, redo them until each one names a person, a standard, and a verification step.
Food safety: designing the cooling procedure your team will follow
Advanced food safety at this level means designing and verifying procedures, not just following them. For a cooling failure, the executive decision covers the method, the monitoring, and the corrective action.
Scenario: a 20-liter batch of veal stock finishes at 9 p.m. and your sous chef seals it hot in a deep container in the walk-in. The plausible mistake is treating this as the sous chef's carelessness and moving on. The better decision is procedural: hot stock should be divided into shallow pans, stirred in an ice bath or with an ice paddle, and monitored with a calibrated thermometer as it passes through the danger zone. The executive chef owns writing that standard, training it, and auditing it.
Why it matters: as the supervising chef, both your exam answers and your real kitchen depend on whether the safe method is the default method. A strong answer identifies the immediate corrective action (reheat or discard per your food safety policy if the stock lingered in the danger zone), the root cause (container depth and no assigned check), and the prevention (equipment, training, and a documented shift-close safety checklist). Note the pattern — correction, cause, prevention — and reuse it for every sanitation scenario you write during practice.
Financial management: diagnosing a rising food cost before acting
Cost control questions reward diagnosis before intervention. A rising food cost has several distinct causes — purchasing, yield, portioning, waste, menu mix — and each one points to a different fix.
Worked scenario: your food cost has crept from 30 to 34 percent over two months. The plausible mistake is raising menu prices immediately. Prices are visible to guests and can cut volume, so acting before diagnosis can worsen the very numbers you are trying to fix. The better decision is to work the table below in order: verify standard costing sheets are current, check purchase price variance, run yield tests on the biggest movers, watch portioning on the line, and review the waste log.
If costing and purchasing check out and you observe oversized portions on two stations, the correct action is targeted: recalibrate scales and portioning tools, retrain those stations, and re-check costs over the next several ordering cycles. Only then consider price or specification changes, and weigh them against menu mix data. The exam-relevant habit is sequencing: verify the standard, measure against it, fix the deviation, re-measure — rather than jumping to the most visible lever.
Read the table left to right: a signal triggers one diagnostic step, and the result determines the response. Practicing this chain with your own numbers builds exactly the reasoning a written scenario demands.
| Signal | First diagnostic step | What the result tells you |
|---|---|---|
| Food cost up over several weeks | Compare invoice prices against standard cost sheets | Purchasing or price drift; revisit specifications or suppliers |
| Costs up only on some items | Run yield tests on those items | Trim loss or a changed product spec; adjust specs or prep method |
| Volume-corrected cost still up | Observe portioning during service | Portion control failure; recalibrate tools and retrain those stations |
| Costs up alongside returns and waste | Review the waste log and production records | Overproduction; revise forecasts and par levels |
Menu development: balancing nutrition, margins, and menu mix
Menu decisions weigh three constraints at once: guest appeal and nutrition, contribution margin, and operational fit with your stations. Menu engineering categories let you judge each item against data, not taste alone.
Learn the menu engineering vocabulary and use it precisely: stars (high popularity, high margin), plowhorses (high popularity, low margin), puzzles (low popularity, high margin), and dogs (low on both). Pair that with nutrition reasoning — a menu claim such as a light designation or a dietary accommodation changes the recipe's cost structure and prep flow. In a scenario, the executive-level answer states which item you would re-engineer, how (portion size, garnish, cross-utilized ingredients), and which data you would check first: sales mix and plate cost.
Scenario: the owner wants a health-focused entrée added. The plausible mistake is designing the dish first and costing it later. The better sequence is to define the nutritional target and price point, cost a draft recipe, confirm ingredients cross-utilize existing inventory, and position it where it can lift a puzzle item's appeal or replace a dog. Run the numbers in a written exercise: cost a draft at three portion sizes and observe how contribution margin and prep complexity move together. That trade-off, not the recipe itself, is the decision you are rehearsing.
Operations and production: a plan that survives a busy shift
Production planning converts sales forecasts into par levels, station assignments, and prep timelines. A workable plan cross-utilizes ingredients, sequences prep around equipment, and states who verifies quality at each step.
At executive level, production reasoning runs from forecast to workload. Trace the chain: forecast covers by daypart, translate them into par levels per item, group prep tasks by station and equipment (oven time, fryer, chill time), and build a timeline so batch-cooked and par-prepped items are ready before peak. Cross-utilization matters here too — an ingredient cut three ways for three dishes lowers both waste and prep hours. Write one complete plan for your own menu rather than skimming many generic examples.
The scenario connection is that operations stems describe symptoms — items running out, uneven quality between shifts, prep finishing late — and expect a management fix: forecasting method, par levels, station balance, and verification steps. When you answer, name the record you would keep (production log, waste log) and the check you would assign (a sous chef sign-off before service). Avoid answers that only add labor; adjusting the plan is the stronger decision in a written scenario because it is sustainable.
- Exercise — audit one week of your dinner production plan against service reality. Each night, record forecast versus actual covers and whether par levels ran short or excessive.
- Log any 86'd item with its cause: demand, prep, or supply.
- Log one wasted ingredient and whether it could cross-utilize into another dish.
- Note whether the prep timeline finished before peak, and what slipped.
- Self-check rubric: after five services, a workable plan shows forecasts within a band you can state, no unexplained 86s, and a timeline where the last bottleneck is identified and fixed. If prep consistently finishes late, your plan assigns too much to one station — rebalance and repeat the week.
HR decisions: correcting behavior with documentation, not anger
Personnel scenarios test progressive, documented correction: state the standard, counsel privately, record the conversation, follow up on a timeline, and escalate per policy only if the behavior continues.
Worked scenario: a dependable line cook has arrived late three times in two weeks. The plausible mistake is an informal 'knock it off' in the kitchen — or the opposite, skipping toward termination because you are frustrated. The better decision is a private, documented counseling session: restate the schedule expectation, ask about causes (transport, second job, a scheduling conflict), set a clear review date, and note the conversation. This preserves a strong employee if the cause is fixable and builds the record that policy requires if it is not.
Why it matters: documentation is what makes later decisions defensible — to your owner, to your team's sense of fairness, and under your organization's policies. Contrast this with a performance problem such as inconsistent plating: the same structure applies, but the content is coaching and a skill check rather than an attendance expectation. In practice answers, distinguish conduct issues (addressed through discipline) from skill issues (addressed through training); mixing the two is a common reasoning error when writing scenarios. Always name who conducts the conversation and where the record lives.
A preparation sequence and readiness checks for CEC study
Rotate through the six scope areas in weekly cycles, writing one scenario answer per area each cycle. Treat scenario-writing volume and your rubric scores — not hours logged — as the progress markers.
Readiness checks: you can name the management tool that fits a stem within seconds; your written scenario answers always identify a standard, an owner, and a verification step; your costing exercise produced a defensible re-engineering decision; and your rubric scores on practice scenarios are stable rather than fluctuating. These are learning milestones, not predictions of a result — treat a weak domain as a signal to write more scenarios in it, not to reread notes passively.
For current certification requirements, eligibility pathways, and administrative details, rely on the American Culinary Federation at acfchefs.org; those requirements are credential-specific and are deliberately not restated here. Pair this guide with the free practice questions and other study guides on Ace ServFood so you keep rehearsing decisions rather than memorizing definitions.
- Weeks 1–2: Map the six domains onto your own kitchen. Write one executive-level decision (standard, assignment, verification) for a real task in each domain.
- Weeks 3–4: Run the financial and menu exercises above with your actual data: cost sheets, a yield test, sales mix, and one re-engineering proposal.
- Weeks 5–6: Drill safety and HR scenarios on paper — correction, cause, prevention for safety; standard, counseling, follow-up for HR — and score each against the patterns in this guide.
- Final stretch: Complete full practice sets under time limits, then sort every miss by domain to find which reasoning step you skipped: diagnosis, tool, or verification.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.