Back to Mise

From Mise’s kitchen

Chef Tips

Practical kitchen guidance for repeatable recipes and a more deliberate service.

Quantity · yield · service

Field notes for the working kitchen.

Use these independent kitchen practices to make recipes repeatable and organize prep around the pace of service. Adapt each method to your menu, staffing, and workflow.

A working kitchen guide

Recipe Standardization, from Batch to Service

The goal is a clear starting batch, a defined finished yield, and serving notes a teammate can follow without filling in missing details from memory.

1. Write quantities so they can be repeated

Choose a base batch and record each ingredient with a measured quantity and unit. Use weights where they suit the ingredient and your process; keep units consistent within the recipe. Describe the ingredient’s state as it enters the recipe—such as drained, finely chopped, or room temperature—and say whether a quantity is purchased or prepared weight.

Replace vague directions like “one bunch” with the amount your kitchen has tested. If a substitution is acceptable, name it and specify how much to use. For seasoning that is adjusted during cooking, record a starting amount and the tasting point or cue for the final adjustment.

2. Define the yield and portion

State what the base recipe makes: for example, a finished batch weight or volume, plus the number of portions it is intended to serve. Note when the yield is measured—such as after draining, trimming, or reducing—so cooks compare the same stage. Give a portion weight, count, or volume and the tool used to portion it when that matters.

For a first scaling pass, use target yield ÷ base yield as the scale factor and multiply the ingredient quantities by that number. As an illustrative example, scaling a 12-portion base recipe to 30 portions gives a factor of 2.5. Treat the result as a calculation to check in the kitchen: equipment, cooking time, seasoning, and some ingredients may need a separate test at the new batch size.

3. Make serving notes usable at the pass

Describe the finished portion in service terms: the vessel, amount of each component, garnish, and order of assembly. Add the details that change the result, such as a finishing sauce added to order or a garnish held back until plating. Keep the notes brief enough to scan during service, and link them to the relevant prep step when a component is made separately.

Document holding, cooling, reheating, and allergen procedures only as approved by your kitchen’s food-safety process. If an instruction changes, update the shared spec and its version so the team can tell which procedure is current.

Recipe standardization checklist

  • Name the recipe, version, and base batch yield.
  • Record measured amounts, units, ingredient state, and any approved substitutions.
  • Define the finished yield, measurement stage, portion size, and portioning tool.
  • Write the production steps and service notes that affect the finished plate.
  • Test a batch at the intended scale, note corrections, and update the spec.

Start with the details your team needs for production. Keep the spec focused on tested instructions, and leave out assumptions that have not been checked.

Kitchen practice · service planning

Mise en Place Planning: A Field Note for Service

Treat mise en place as a sequence of decisions that carries a menu from prep to the pass. Build a timeline your team can scan, assign each task to a station or person, and adjust the timing to fit your own service.

Before the prep shift: map the work

Start with the menu and expected covers, then list the components each dish needs. Group shared work—such as a base sauce used across several dishes—so it is made and checked once. Mark tasks that need a long lead time, a particular piece of equipment, or a handoff between stations. Give every task an owner and a latest useful finish time, based on your kitchen’s staffing and workflow.

At the start of prep: set useful pars

Turn the cover estimate into starting quantities for each component. Use recent sales, reservations, menu mix, and your own service buffer rather than applying one blanket number to every dish. Write down the unit that matters at the station—portions, containers, or batch size—and flag ingredients or components that need a second check before they are replenished.

Sequence the work around the menu and the people available: begin with tasks that need cooling, resting, or a long cook, then fit shorter jobs around shared equipment and station handoffs. Follow your kitchen’s approved food-safety procedures for handling, cooling, storage, and labeling.

Before doors: stage and check each station

Ask each station to verify its own mise against the menu: portions and backups are present, tools and equipment are ready, and components are staged in the order they will be used. Taste and check the items your kitchen normally verifies before service. Make shortages visible while there is still time to reassign prep or agree on a substitution with the team.

In the final check: agree on the handoff

Bring the stations together for a short verbal check. Confirm who is covering each position, what is limited or unavailable, which components need close attention, and how a low par or delay should be called to the pass. Keep the plan specific enough that a teammate can act on it without stopping service to ask what comes next.

During service: replenish from what you see

Watch the pace of orders and compare it with the remaining portions at each station. Replenish in manageable batches that suit the component and your approved holding process. Call out a change in pace early, keep the pass informed about shortages, and reset a station when a wave eases so the next push starts organized.

At close: use the service to improve the next plan

Note what ran short, what remained, where work backed up, and which handoffs caused rework. Compare those observations with covers and actual sales, then adjust the next prep list, par, or task owner. A brief record from each service is more useful than a fixed plan that never reflects what the kitchen learns.

Keep the timeline visible to the people doing the work, review it after service, and change only the steps that your team’s experience shows need changing.

Menu planning · cross-course prep

Build a Cross-Course Prep Map for Service

Plan the menu as connected work, not as a separate prep list for every plate. A cross-course map shows what each course needs, which components can be produced together, and what has to happen first so stations can finish dishes at the right time.

1. Map each course backward from pickup

Make one row for each course, in the order you plan to fire them. List its plate components, the station that finishes them, and the order of work at the pass. Then work backward: note what must be portioned, cooked, cooled, rested, or assembled before that pickup. Give each task an owner and a latest useful finish time based on your covers, staffing, and service pace.

2. Combine shared components across the menu

Scan all the course rows for the same ready-to-use component, not just the same raw ingredient. Add its planned portions across the dishes, account for the yield your kitchen actually gets, and mark where each portion will go. For example, if one lemon-herb dressing is used on both a starter and the greens with a main, plan the combined batch once, then portion and label what each station needs. Lemons used in different preparations still need their own task and yield notes.

3. Mark dependencies and shared bottlenecks

Connect tasks that depend on one another: greens need to be washed and dried before they are dressed; a tart shell needs to bake and cool before it is filled. Also mark constraints that determine where or when work can happen, such as one oven serving several courses, limited chilling space, or a blender shared by two stations. Put each task after its prerequisite and reserve constrained equipment or storage for the window it needs. Follow your kitchen’s approved food-safety and holding procedures.

4. Turn the map into a station-ready sequence

Schedule long cooks and tasks with resting or cooling time early enough to create useful work windows for other prep. Batch shared components once, then identify their labeled containers, destinations, and handoff time. Fit shorter jobs around equipment use, and keep final seasoning, garnishing, and other last-minute work close to the station that will pick up the dish. Put the owner, work location, and finish time beside every task.

5. Check the whole menu before doors

Walk the sequence with the stations. Confirm the shared batch covers its planned uses, each course has its own labeled mise, and no task is waiting on equipment or a handoff that is already booked. Call out shortages or changed timing while there is room to adjust. After service, note what ran short, remained unused, or held up another task; use those observations to update the next map.

  • Course and pickup order, with each plate’s components.
  • Shared ready-to-use components, combined target, yield, and station destinations.
  • Task dependencies, owners, finish times, and equipment or space constraints.

Menu planning · course-by-course service

Prep Timing Between Courses

Work backward from the order you plan to serve each course, then separate work that can be completed and held appropriately from the finishes that belong close to pickup. Let the menu, team, equipment, and pace of the room shape the plan.

Map the service sequence before setting times

List courses in their planned firing order. For each one, note its components, the station and person responsible, any equipment or handoff it depends on, and the cue that means it is ready to fire. Work backward from that pickup to place its prep and finishing tasks. Base durations on your kitchen’s own tested process, and leave room for the staffing, covers, and service pace you expect that day.

Prepare ahead what suits the component

Complete suitable batch work before service: measure dry ingredients, portion components, prepare sauces or dressings that hold well under your procedure, and wash and thoroughly dry produce when that fits the recipe and food-safety plan. Label each item with its course, station, intended use, and required storage or holding instructions. Shared components can be made together, then divided and staged for the courses that need them.

Decide what can be prepared ahead by checking the recipe, desired texture, and your kitchen’s approved food-safety process. Do not assume every component can wait at room temperature or be held for the same length of time.

Before service, stage the next steps

Arrange labeled mise in course order and make tools, pans, plates, and shared equipment easy to find. Mark components that lose quality while waiting—such as dressed greens or crisp garnishes—and keep their final preparation on the live sequence. Confirm who owns each pickup and how the pass will communicate a delay, change in pace, or unavailable item.

Between courses, follow the pass

As one course leaves, check with the pass about the next pickup and the pace of orders. Use that signal to start work that needs a longer lead, while keeping an eye on shared burners, oven space, and staff who may still be finishing the previous course. If a table or service wave runs early or late, re-sequence flexible tasks and communicate the change instead of relying on a clock time that no longer fits.

Keep quality-sensitive finishes near pickup

Finish the tasks most affected by waiting close to their planned pickup: cook delicate items, crisp or fry elements, dress salads, bring sauces together, adjust final seasoning, and add fragile garnishes as the dish is assembled. Coordinate the final check and plate handoff with the pass. The exact sequence depends on the dish, its safe holding requirements, and how quickly your kitchen can finish it consistently.

Review the map after service

Note where a component waited too long, a station ran short, or a dependency delayed a course. Compare those observations with the actual service sequence and adjust the next prep list, owner, or pickup cue. Use timings your team has observed and tested; there is no single number of minutes between courses that fits every menu or service.

  • Course order, pickup cue, station, and task owner.
  • Components that can be prepared ahead under your storage and safety procedures.
  • Finishing work that should stay close to pickup for quality.
  • Dependencies, shared equipment, and a plan for a change in service pace.

Before service · repeatable kitchen check

Service-Day Prep Checklist

Run through this with the stations before doors. Adjust quantities and timing to the menu and your kitchen’s workflow.

  • Planned dishes: Review today’s menu, list each dish’s service components, and confirm the portion target for each.
  • Ingredients and shortages: Check that required ingredients are on hand in the quantities needed. Flag gaps and agree on an approved substitute or mark the item unavailable before service.
  • Outstanding prep: Mark each remaining task, give it one clear owner, and set a useful finish time before the component is needed.

During service · course handoff

Managing Course Transitions

A smooth interval between courses depends on a shared handoff: the room confirms a table is ready, the dining area resets for what is next, and the pass fires against the table’s actual pace. Give each step a clear owner and communicate status as it changes.

1. Agree on the release cue

Before service, decide who confirms that a table has finished and how that person signals the pass. Use the table number and the expected cover count so the kitchen knows which order is moving. Some guests may finish early, but confirm that the whole table is ready; flag split pacing or a requested pause before anyone fires the next course.

2. Clear the completed course deliberately

Once the server confirms the table is ready, clear used plates, cutlery, and shared pieces in an agreed order. Check for a guest who is still eating, a plate that needs to stay, or a note the next course depends on. Keep dirty items moving away from the clean reset area, then tell the floor lead when the table is clear or when something is holding it up.

3. Reset for the next course

Remove crumbs and used settings, then place clean cutlery, glassware, serving pieces, or other settings the next course requires. Follow the restaurant’s table and sanitation standards. Check that the table is complete before marking it ready, and tell the pass if a missing setting, guest request, or delayed reset changes the pickup plan.

4. Stage and call the next pickup

At the pass, reconfirm the table, cover count, course, and any order changes. Each station checks its own components and calls when ready; the pass checks the assembled plates and coordinates the handoff to the floor. Keep final cooking and finishes that lose quality while waiting close to that call. Follow the kitchen’s procedures for holding and food safety. If the table or a station is not ready, communicate the hold and reset the sequence together instead of firing on an assumed interval.

5. Track status and service pace

Use one shared pass board or service log with a simple status for each table, such as eating, clearing, resetting, firing, and served. Assign one person to update it when the floor or pass confirms a change. Mark holds, split pacing, and delays where both sides can see them; the pass can then call the next pickup against the room’s current pace. After service, note where a handoff stalled and agree on one cue or ownership change to try next time.

  • Confirm the table and cover count before releasing the next course.
  • Clear used items and report anything that keeps the table from resetting.
  • Set clean pieces for the next course and confirm the table is ready.
  • Stage and check the pickup at the pass before coordinating the fire.
  • Update shared table status when confirmed; call out holds and pace changes.

During service · station coordination

Coordinate Station Ownership Across Courses

Multi-course service runs more smoothly when each task has a clear owner and every station knows how to report its status to the pass. Use the role names and call format that fit your kitchen, then keep them consistent through the shift.

Give each task one accountable owner

Before service, assign each course component, shared piece of equipment, and station-to-station transfer to a named person or role. One lead can coordinate the station while another cook completes a task, but make clear who confirms it is finished. Name a backup or escalation path for breaks and simultaneous pickups; avoid leaving ownership with a vague “kitchen” or “team.”

Use a short, shared readiness call

Agree on simple status calls such as ready, working, and hold. The station lead reports the course and item to the pass. For a hold, say what is delayed, what is needed, and when the pass should expect the next update. The pass acknowledges the call and coordinates any change to the pickup; neither side has to guess from silence.

Close one course, then hand off the next

As plates leave, the pass names the next course or pickup and calls out changes in pace, covers, or priority. Each station lead confirms what is ready, what remains in progress, and any component or equipment another station is waiting on. The receiving owner repeats back a changed assignment, and the pass updates the shared board or ticket status. If a hold changes the sequence, agree on the revised order before firing dependent work.

  • Give every task one accountable owner and a clear backup or escalation path.
  • Have station leads call readiness, active work, and holds directly to the pass.
  • At each course change, confirm the next pickup and repeat back changed handoffs.

Menu planning · ingredient costing

Compare Ingredient Costs by Usable Yield

A purchase price is only a useful menu-planning comparison when each option is measured in the same recipe-ready state. Account for what your kitchen can actually use after trimming, peeling, draining, boning, or other preparation.

Start with the same unit and condition

For each candidate ingredient, record the amount paid and the amount received in a consistent unit. Note the state that matters to the recipe: whole or trimmed, bone-in or boneless, dry or drained, and any quality or size specification that affects how it cooks or portions. Compare alternatives at that same stage rather than comparing a case price with a ready-to-use portion.

Use your kitchen’s actual prep yield

When prep removes trim or leaves liquid behind, weigh or measure what remains usable for the dish. Calculate cost per usable unit = purchase cost ÷ usable quantity, keeping the units consistent. Use yields recorded by your own team for that product and preparation method; do not assume another supplier’s pack or a general yield estimate behaves the same way.

If the yield changes with the cut, batch, or prep method, keep those notes with the costing record. Recheck after a supplier or specification changes, or when the team sees more trim or waste than usual.

Apply the usable cost to each recipe

Check that the recipe quantity is written in the same usable state as your cost. Multiply the amount the recipe uses by its cost per usable unit, then compare the ingredient contribution across menu items or candidate suppliers. If one recipe records purchased weight and another records prepared weight, make that difference explicit before you compare them.

Review the kitchen trade-offs

Ingredient cost is one planning input. Also consider whether an option changes prep work, storage needs, consistency, shelf life, or the chance of unused product. Keep those operational notes alongside the cost so the menu decision reflects how the ingredient works in your kitchen, not only its listed price.

A quick comparison checklist

  • Record the paid amount, received quantity, unit, and product specification.
  • Measure usable yield after the preparation step that affects the recipe.
  • Compare recipe quantities and costs in the same prepared state.
  • Keep prep, storage, and waste observations with the costing notes.
  • Refresh the comparison when the product or observed yield changes.

Use measured kitchen records to make the comparison repeatable. Where a yield or cost has not been checked, label it as an estimate and verify it before relying on it for menu planning.

Kitchen practice · prep review

Track Usable Trim and Recurring Kitchen Waste

A short, consistent prep record can show which trim is useful to another planned preparation and which waste keeps returning. Use those observations to review the next prep list, recipe spec, or purchasing quantity with your own team’s experience.

Record the same details each prep

For each ingredient and comparable prep batch, note the date, item, starting quantity and unit, recipe-ready yield, and the weight of trim. Separate trim your kitchen has approved for another use from material that is discarded. For each amount, record its destination or a plain reason—such as an unusable cut, spoilage, over-prep, or an order that did not sell. Follow your kitchen’s food-safety rules for evaluating, handling, labeling, and storing anything retained for another preparation.

Add the service context that helps explain a change: covers or sales, menu mix, supplier or product specification, and any unusual prep conditions. Use the same units and weighing point from one record to the next so the team is comparing like with like.

A simple recordkeeping example

Illustrative sample only; replace with measured kitchen data. A short review of three comparable prep shifts could be recorded like this:

  • Ingredient and starting amount: Carrots, 10 lb per shift.
  • One shift’s result: 8 lb recipe-ready, 1 lb clean trim set aside for planned stock under the kitchen’s approved process, and 1 lb discarded.
  • Recurring observation: The saved trim remained unused on two of the three shifts.
  • Next prep decision: Check planned stock demand before holding additional trim, then review the next comparable shifts.

Keep the quantities, destination, reason, and follow-up decision together. This example shows a record format; it is not a savings estimate or a promised result.

Turn a repeated observation into a prep question

Review records over several comparable services rather than changing a par from one unusual shift. Look for recurring patterns: a trim container that is rarely used, a prep quantity that regularly remains after close, or the same ingredient being discarded for the same reason. Check those notes against sales, covers, recipe portions, and any supplier or process change before choosing what to adjust.

The follow-up may be to change a prep par, clarify a recipe’s usable-yield quantity, review a cut or handoff with the team, plan an approved use for suitable trim, or leave the current process in place and collect more observations. Write down the decision and when to review it, then compare the next set of records to what the kitchen expected.

Quick trim and waste log checklist

  • Record the item, date, batch, starting quantity, unit, and recipe-ready yield.
  • Weigh trim and separate approved retained trim from discarded waste.
  • Note where retained trim went, or why material was discarded or left unused.
  • Add relevant service, sales, menu, or supplier context.
  • Review comparable records, write the next prep decision, and set a follow-up point.

Treat the log as a way to ask better prep questions. Let repeated, measured kitchen observations guide the next decision, and keep assumptions labeled until your team has checked them.

During service · contingency planning

When a Course Is Delayed or an Ingredient Runs Out

A missing component can affect more than one plate. Use the course map, station calls, and pass to identify the impact, agree on one response, and give every affected person the same current plan.

1. Map the disruption to the courses and tickets

Name the delayed or unavailable component, then check the menu, tickets, and prep map for every course that uses it—including shared sauces, garnishes, or other components prepared for several dishes. At the pass, identify the affected dishes and tables or tickets, the station responsible, what is ready, and what is still needed. If the scope is uncertain, say so and verify it with the relevant station before changing a pickup.

2. For a delay, call the status and next update

The station lead should tell the pass which component is delayed, which course or tickets it affects, the work still in progress, and an estimate only when the team has a useful one. Give a time or service cue for the next update. The pass and affected stations can then decide whether to hold that pickup, adjust the order, or continue another course when the table’s pace and the rest of the service plan allow. Keep quality-sensitive finishing work aligned with the revised pickup.

3. For an unavailable ingredient, confirm before substituting

Check which dishes rely on the ingredient and whether the kitchen has a substitution already approved for those recipes. Before anyone handles or substitutes a component, follow the kitchen’s established food-safety and allergen procedures, including the process for checking guest requirements and preventing cross-contact. Have the responsible chef or service lead confirm the response. If there is no suitable, approved option, mark the affected item unavailable and give the floor only the confirmed information to share with guests.

4. State one plan across stations and the pass

Use a short call with the course or dish, affected tickets, component, decision, owner, and next update. Example wording—replace each bracketed field with the current service details: “[course] on [tickets]: [component] is delayed; hold those pickups, [station/owner] is checking timing, and we’ll update the pass at [time or cue].” Ask the receiving station or pass to repeat back a changed assignment. Update the shared board or tickets, notify any station that uses the component, and tell the floor lead when guest-facing timing or availability changes. Keep the current plan visible so an earlier call does not continue to guide the service.

  • Identify every affected dish, course, ticket, and station.
  • Agree who can decide the response and name an owner for the next action.
  • Follow established food-safety and allergen procedures before handling or substituting.
  • Call the decision, hold, and next update to the pass and affected stations.
  • Update tickets or the shared board and pass confirmed guest-facing changes to the floor.

If the team cannot confirm a safe, workable response, hold the affected pickup and involve the responsible chef or service lead before it proceeds. Clear, repeated communication helps everyone work from the same plan.

Household preferences · meal service

Turn Meal Feedback into Future Menu Notes

A brief, meal-specific conversation can help a chef plan the next menu with more care. Capture what people liked or would change, then turn that feedback into one practical food or service adjustment.

Ask while the meal is still fresh

Choose a relaxed moment after the meal or a short follow-up. Start with a neutral, optional question such as, “What should we keep or change for next time?” If a little more detail would help, ask about a specific part of the meal: flavor, texture, portion, temperature, or how the courses arrived. A short answer is enough; avoid turning dinner into a survey.

Keep the note about food and service

Name the dish or course and record the preference in plain, neutral language. Add a service observation—such as timing, temperature, or pacing—only when it helps shape the next meal. Keep the wording close to what the household said, and distinguish a direct preference from your own interpretation.

Treat one reaction as useful context, not a permanent rule. Look for the same preference across later meals and check in before making it a standing menu choice. Update the note when the household’s feedback changes.

Turn a comment into a next-menu action

A useful note links a dish, a specific preference, and a clear next step. Keep it concise enough to scan while planning the next menu.

Sample feedback: “Roasted carrots were a favorite; mains arrived before the salad was finished.”
Future-menu note: “Repeat roasted carrots; wait for the salad course to finish before sending mains.”

Keep records limited to food preferences and the meal or service experience. Do not ask for or add personal details unrelated to the meal.

Interested in Mise’s recipe workspace or Founding Chef membership?

Talk with Mise