Techniques
Firing / Timing Orders

Prep & Assembly

Firing / Timing Orders

Coordinating when each dish starts cooking so a table's plates finish together.

Firing, or timing orders, is the kitchen-line discipline of starting each component at the right moment so every dish for a table reaches the pass hot and at the same time. The expediter calls fires based on cook times, course pacing, and ticket order to keep service flowing. Good firing prevents one plate sitting under heat lamps while another is still cooking.

Firing is the act of beginning to cook a dish on command; timing orders is the working-backward calculation that tells you exactly when to fire each component so an entire table's plates land together. They are the planning and execution halves of the same skill, and together they separate a kitchen that feels calm from one that feels chaotic. Every plate on a ticket moves on its own clock — a braise that needs ninety minutes, a fish that needs six, a sauce that holds for three — and the cook's job is to make those clocks meet at the pass at the same moment.

The technique rests on three things: a settled mise en place, an honest read of every cook and rest time on the ticket, and clear communication between stations. Miss any one of them and the failure is visible on the plate — cold protein, wilted herbs, sauce that broke while it waited. The discipline scales: a two-person dinner party uses it informally with an index card and a kitchen timer, while a 200-cover banquet runs it with timestamps on a Kitchen Display System. The math is identical; only the tools change.

At its heart, firing is anchored on the longest lead-time item on the order. That single dish sets the clock for everything else, and every other component is fired later by the exact number of minutes it needs less. Once that anchor is set, the rest is execution, call-outs, and the discipline to reset the station before the next ticket lands.

Difficulty
Hard

Types & varieties

À la carte firing

Tables ordered at different moments; the expediter sequences dishes so a single table's plates land together while protecting the pass from bottlenecks.

Table-wide firing

An entire table's order is held and fired as one unit so everyone eats simultaneously — standard in fine dining.

Course-by-course firing

Tasting menus and prix fixe: first course fires and clears, then the second, on a set rhythm (often 12–18 minutes between courses).

Banquet / party firing

Dozens to hundreds of identical plates hit the pass within a tight window (often 90–180 seconds). Relies on batch cooking, finishing pans, and pre-plated components.

Same-time (simultaneous) firing

All components of a single plate are fired so they finish together — typical for steak frites, where protein, sauce, and fries must meet at the pass at once.

How to do it

  1. 1

    Read the full order end to end

    Before touching a pan, read every dish on the ticket (or every course on the menu). Note modifiers, allergies, and shared plates. You cannot sequence what you have not seen.

  2. 2

    Identify the longest lead-time item

    Find the component that takes the most time from pan to plate — a braised short rib, a risotto, roasted root vegetables. This sets the clock; everything else is relative to it.

  3. 3

    Calculate 'fire by' times working backward

    For each dish, subtract its cook time, rest time, and plating time from the desired service moment. Write these as call-back times on the ticket or set timers in a KDS.

  4. 4

    Group items by cooking station

    Cluster dishes by where they cook (sauté, grill, pantry, pastry). Parallel stations work simultaneously; you only sequence within a single station's workload.

  5. 5

    Confirm mise en place for every component

    Verify portions, sauces, garnishes, and warmed plates are ready. Pull or thaw anything missing before firing — running out mid-fire is the most common timing failure.

  6. 6

    Fire long items first and call out clearly

    Begin with the longest lead-time dish and call it to the relevant station by name and time. Speak so the whole line hears; it prevents duplicate work.

  7. 7

    Fire short items at their calculated times

    Hold vegetables, quick-seared fish, and sauces until their call-back arrives. Heat lamps and warmers bridge a 1–3 minute gap if things slip.

  8. 8

    Plate each dish as it finishes

    Build plates in the order components become ready — base, protein, sauce, garnish — keeping hot elements hot. Sauce and fresh garnish go on at the last moment.

  9. 9

    Hand to the pass for expediter check

    The expediter (or at home, the cook) confirms every plate against the ticket — garnishes, doneness, allergens — before it leaves the kitchen.

  10. 10

    Reset, and reset fast

    The moment a dish is called, the station begins resetting for the next ticket: wiping pans, re-portioning, refreshing sauces. A 30-second reset keeps the next fire on time.

Working backward: the firing math

Every firing plan is the same equation, written once per dish: service time minus cook time minus rest time minus plating time equals fire time. The cook who learns to run that equation in their head — or, better, writes it on the ticket — has removed most of the chaos from a multi-plate order.

  • Anchor the ticket on the longest lead-time item. If the short rib needs 90 minutes and the salad needs 4, the short rib fires first; the salad fires at minute 86.
  • Account for rest time before service time, not after. A steak cooked in 8 minutes and rested for 7 must leave the pan 15 minutes before the plate hits the table.
  • Plate time is real time. A composed dish that takes 90 seconds to build across two stations must be plated before service, not during.
  • Sauces, herbs, and quick finishes go on at the very end — fired last, often at the pass, to preserve color, gloss, and freshness.
  • Subtract a 1–2 minute pass buffer for the expediter's check, final garnish, and the walk from kitchen to dining room.

Communication on the line

Timing fails before it starts if the line cannot hear what is coming. Every fire is announced by name, count, table, and time so the receiving station knows both what to begin and how to pace the rest of its workload.

  • Call format: item, count, table, fire time — 'Beef, two, table 12, fire now, six-top.' The whole line hears; no one duplicates work.
  • Reverse-order calling during a rush: newest fire first, oldest items checked, so nothing is forgotten mid-ticket.
  • Modifiers and allergies are read aloud and confirmed at the pass — an allergy that travels only on paper is a disaster waiting to fire.
  • At home, the equivalent is a single index card on the counter with each dish's 'start cooking at' time. One cook, one voice, no one to call out to — just the card.

Common uses

Coordinating multi-course tasting menus where each course must arrive on cueHoliday meals (Thanksgiving, Christmas) where turkey, sides, and gravy need to finish togetherWine-pairing dinners with timed service intervalsDinner parties of four or more where plates must leave the kitchen togetherRestaurant service during the rush when six to ten tables are mid-orderBanquets, weddings, and catering where dozens of identical plates must hit the pass

Tips & pitfalls

  • Read the entire ticket (or full menu) before firing anything — the longest item dictates when the shortest ones must start.
  • Build your firing plan around rest and hold times: a steak needing 8 minutes on the heat and 5 minutes resting should leave the pan 13 minutes before service, not 8.
  • Group by station, not by dish: proteins to the sauté cook, starches to the pantry, sauces to the saucier — fired in parallel.
  • Call items out in reverse order during a rush — newest fire first, oldest items checked — so nothing is forgotten.
  • Use a physical timer or KDS countdown for every long-cook item (braises, roasts, stock reductions); mental timing drifts under pressure.
  • Keep a 1–2 minute buffer for the pass — plating, final garnishes, and the expediter's check all eat time.
  • Pre-portion and pre-heat: portioned proteins, warmed plates, and hot pans cut seconds that add up across a ticket.
  • Walk the pass: visually confirm plates before they leave; a fired dish that sits under a heat lamp too long is worse than one fired a minute late.
  • For home cooks, write the firing plan on an index card next to the stove with each dish's 'start cooking at' time — it prevents the classic 'everything went cold while I finished the gravy' failure.

Good to know

Term origin
'Firing' comes from professional restaurant kitchens; to 'fire' a dish means to begin cooking it on command. The practice is formalized in the Escoffier-style brigade system.
Related discipline
Built on rigorous mise en place — every component prepped, portioned, and accessible so cooking can begin instantly on call.
Core calculation
Each dish is worked backward from the moment it must hit the table; the longest lead-time item sets the firing clock for the rest of the ticket.
Critical tool
A reliable timing system — paper tickets with handwritten call-backs, kitchen printers with timestamps, or a Kitchen Display System (KDS).
Holding buffer
Most plated dishes tolerate 30–90 seconds under heat lamps or on warm surfaces; sauces and garnishes are fired last so they arrive vivid.
Skill level
An advanced kitchen skill, usually learned on the line after competence in individual techniques.
Home equivalent
Holiday dinners, multi-course dinner parties, and tasting menus — anywhere several dishes must reach the table simultaneously.
Common failure
Forgetting that proteins rest 5–15 minutes after cooking; the protein often needs to leave the pan before its actual 'done' time on the ticket.

Also called

Firing · Timing · Coursing

Dishes that rely on it

Related