Mise en place — "everything in its place" — is often understood narrowly: chop the prep before service. In reality it's a system for organizing a station so that during service the cook never has to think about where something is, never walks off to fetch an ingredient, and never makes a decision that could have been made ahead of time. The difference between a kitchen with real mise en place and one running "from memory" is hours of labor per week and consistent ticket times during the rush.
A Station Is a Workstation, Not Just a Spot at the Counter
The first step is to stop thinking of a station as "a stretch of counter." A station has structure:
- Reach zone — what you need every few minutes: cutting board, knives, oil, salt, the most-used prep items. Everything within arm's length, no steps, no turning your body.
- Access zone — what you need several times a shift: prep backup stock, equipment for specific dishes. One step or one bend away.
- Restock zone — the reserve in the station's fridge or in shared storage. You go here between waves of guests, not during them.
Arrange items by frequency of use, not by "product logic." If a sauce goes into every other dish, it belongs in the reach zone — even if it "should" logically live with the other sauces.
The test is simple: watch a cook for ten minutes during the rush. Every trip away from the station and every "where do we keep..." is a flaw in the setup, not in the cook.
Two-Stage Prep: Base and Finish
The most underrated mise en place technique is splitting a dish's preparation into two stages.
Stage 1 — base prep (that morning or the day before). Everything that holds up in storage without losing quality: chopping vegetables, portioning meat, blanching, base sauces, dressings, dough. Done in batches, at a calm pace, with no order pressure.
Stage 2 — finishing at service. Only what has to be fresh: searing, plating, fresh herbs, dressing a salad right before it goes out.
Classic examples of this split: a base sauce for eggs is finished ahead and held, while the eggs themselves are cracked to order; salad vegetables are cut in the morning and stored separately in closed containers, then tossed with the dressing minutes before serving so the acid doesn't kill the crunch. The principle is the same either way: the line between the two stages sits exactly where quality would otherwise start to suffer.
Once you map every menu item into "base" and "finish," you get two lists: what can be batched during quiet hours, and what has to happen at the station when an order comes in. It often turns out that half of what cooks scramble to do during the rush can move calmly to the morning.
Batch Prep, Done Right
Batch prep only saves time when paired with two rules:
- Batch size comes from usage, not container size. Prepping a week's worth of dressing when it only keeps for three days means you're planning to throw out a third of it. Start from average consumption over the shelf life, adjusted for day of the week.
- Store components separately. A mixture only keeps as well as its least stable ingredient. Chopped vegetables go in their own containers, dressing in its own, and they only meet right before service.
Keep shelf life in mind: fresh oil-and-vinegar dressings hold up in the fridge for several days; yogurt- or cheese-based versions, noticeably less. Whatever your internal standards are, they only work when they're written on the container.
Labeling and FIFO: Boring, But That's the System
Every prep container gets labeled: what's inside, when it was made, and how long it's good for. No exceptions for "obviously everyone knows" — that's exactly where kitchens lose prep and pick up citations during inspections.
The FIFO rotation rule — first in, first out — works physically: the fresh batch goes to the back, the older one moves to the front. If keeping order requires remembering and thinking, the order won't survive. If the oldest stock simply ends up within reach first, it will.
The Prep List: A Plan Instead of Memory
A kitchen morning without a prep list starts with a "what did we run out of" audit and improvisation. A morning with a prep list starts with a concrete plan: which items, in what quantity, by when, and who's making them.
A working format is simple:
- a list of station prep items with a par level ("parking level");
- the actual count that morning;
- the difference is the prep assignment.
The list gets filled out at closing (the evening team sees the real counts) and checked at opening. This also defuses the perennial shift conflict: "yesterday's crew left nothing" turns from an argument into a line on a document.
Recipe Cards Belong at the Station, Not in a Binder
The standard is captured in a recipe card with exact weights and a photo — and it hangs where the cooking happens, not in an office binder. This matters most for new hires and for delivery orders, where the person plating the dish isn't always the one who created it: a visible card at the station keeps portions and plating consistent without the chef having to check every plate. In Meni, recipe cards with photos live in the same system as the menu, so they're easy to pull up on a tablet right at the station.
Cleaning as You Go Is Part of Mise en Place
The clean-as-you-go rule: tidy up as you work, not at the end. Wipe the board between tasks, rinse a tool right away, put a container back closed. This isn't about looks: a cluttered station breaks the whole zone system — what you need stops being within reach, and the cook is back to searching and walking.
One last touch: the station's "zero state." Photograph a properly set-up station and post the photo nearby. Any shift can bring the station back to that standard in two minutes, and the next shift starts without having to audit it first.
Key takeaways
- Organize the station by frequency of use: reach zone, access zone, restock zone. Every trip away from the station during the rush is a flaw in the system.
- Split every dish into base prep (batched, ahead of time) and finish at service. The line sits wherever quality would start to suffer.
- Size batches based on usage and shelf life; store components separately.
- Labeling every container and physical FIFO are the bare minimum the whole system depends on.
- A prep list with par levels replaces memory and defuses conflicts between shifts.