Coursing a Table in a Restaurant: Fire, Hold, Pace

A good dinner has a rhythm. Starters land, plates clear, mains arrive hot, dessert comes when the table wants it. That rhythm is coursing. This guide explains coursing a table in a restaurant, from the words the line uses to the way you pace a six-top on a Friday night. It covers ringing in, firing, holding, the expo’s role, the common mistakes, and how a point-of-sale sends course markers to the kitchen.

In short: Ring in the whole order with each dish marked by course. Send starters right away and hold the rest. Fire each later course from the floor when the table is ready. Pace by the slowest dish in the course and by the size of the party. Let the expo control the pass. Use a ticket or kitchen screen that shows held and fired courses clearly.

What is coursing a table in a restaurant?

Coursing a table in a restaurant means sending each part of the meal to the kitchen at the right time, so every dish in a course reaches the table together and hot. The server controls the timing from the floor. The kitchen cooks only what has been fired, and holds the rest.

A typical full-service meal has three or four courses:

Course	Typical items	Common timing
Course 1	Drinks, bread, small bites	Right after greeting
Course 2	Starters, soups, salads	Fired on order
Course 3	Mains	Fired when starters are nearly done
Course 4	Dessert, coffee, tea	Fired after mains are cleared

Some menus add more steps, like a pasta course or a shared grill course. The idea stays the same. Each course is a group of plates that must land at the same time for the same table.

The words the kitchen uses

• Ring in: enter the order into the POS.
• Course marker: a label on each item that says which course it belongs to.
• Fire: start cooking now. “Fire table 12 mains.”
• Hold: the kitchen can see it but must not cook it yet.
• Away: an older word for fire in some kitchens. “Mains away on 12.”
• Pick up / walk in: a plate or course is ready at the pass.
• Re-fire: cook a dish again because it was wrong, dropped or died in the window.
• In the window / on the pass: plates waiting to go out.

Use the same words every shift. New staff learn faster, and calls do not get lost in the noise.

Should you ring in all courses at once or course by course?

For most full-service restaurants, ring in the whole order at once, with each item marked by course, and hold the later courses. The kitchen sees what is coming and can prep. The server fires each course when the table is ready. Course-by-course entry fits tasting menus and slow, long meals.

Here is how the two methods compare:

	Ring in all, fire by course	Ring in course by course
Kitchen sees the full order early	Yes	No
Prep and par-cooking	Easier to plan	Harder to plan
Server trips to the POS	One main entry, then quick fire taps	One entry per course
Risk of a forgotten course	Low; held items stay on screen	Higher; server must remember to ring in
Best for	Most à la carte dinner service	Tasting menus, very slow meals

When you ring in all at once, two things must be true. First, held items must look different from fired items, so no cook starts a main early. Second, the fire call must reach the right station fast. If either fails, the method breaks.

How do you pace courses by party size?

Pace each course by the slowest dish in it and by the size of the party. A two-top eats faster than a ten-top. Large parties need more time between courses, and the kitchen needs more lead time to plate many dishes at once. Fire earlier for big parties, and watch the slowest eater.

Use these as starting points, not rules:

Party size	What changes	What to do
2 guests	Eat fast, notice delays	Fire mains as soon as starters are mostly eaten
4 to 6 guests	Mixed pace, more dishes per course	Fire when most plates are done; tell the kitchen it is a 6-top
8 or more	Long plate-up time, many mods	Give the kitchen a heads-up; fire a little earlier; use two runners
Kids at the table	Kids eat earlier and faster	Ask parents; fire kids’ mains with adult starters if they want

Pace by the slowest dish

If one main is a well-done steak and the others are pasta, the steak sets the timing. The grill fires first. The pasta station times its plates to land with the steak. Good tickets and kitchen screens show cook times or ticket age, so the line can stagger starts without guessing.

Read the table, not the clock

Timers help, but the table tells you more. Watch for forks down, plates pushed aside, or guests leaning back. That is when to fire the next course. If a table is talking and in no hurry, hold a little longer. If a guest says they have a show at eight, fire early and tell the kitchen.

What does the expo do during coursing?

The expo, or expeditor, controls the pass. They call fires to stations, check each plate against the ticket, and send a course out only when every plate for that table is ready. They also tell servers about delays. On a busy night, the expo is the link between the floor and the line.

A clear expo routine looks like this:

1. Read the new ticket. Note party size, allergies and any rush notes.
2. Call the fire. When a server fires a course, call it to every station in that course: “Fire 12, two salmon, one steak mid-rare, one risotto.”
3. Track ticket age. Watch which tables have waited longest.
4. Check each plate. Right dish, right mods, clean rim, correct garnish.
5. Hold the course until complete. Do not send three of four plates.
6. Call for runners. “Walking 12.” Send enough hands for the whole course.
7. Mark it served. On a kitchen screen, bump the course so the next one comes forward.

Give the expo authority. If they say a dish must be re-fired, the line re-fires it. That one rule saves many bad plates.

What goes wrong when coursing a table?

The most common problem is mains dying in the window: plates are ready but the table is still on starters. Other problems are forgotten courses, early fires, and a course going out with one plate missing. Most of these come from unclear calls or tickets that do not show what is held and what is fired.

Problem	Usual cause	Fix
Mains dying in the window	Fired too early, or table slowed down	Fire later; server tells expo when the table slows
Main course forgotten	Held and never fired	Held items stay visible; expo checks old tickets
One plate missing from a course	Station not told, or dish re-fired late	Expo holds the whole course; call all stations together
Cook starts a held dish	Held and fired look the same	Clear “HOLD” label or color on ticket or screen
Dessert arrives before mains are cleared	Fired by habit	Fire dessert only after the server confirms
Allergy plate mixed up	Mods lost between stations	Allergy flag on every ticket line; expo checks it

When plates are already up

Decide fast. Some food holds for a short time under the heat lamp: braises, rice dishes, many sauces. Some does not: fried food, fish, steak cooked to temperature, anything with a crisp crust. If the table is not ready and the dish will not hold, the expo should call a re-fire and tell the server. A re-fired dish costs food. A cold plate costs the guest.

How does a POS send course markers to the kitchen?

A POS lets the server mark each item with a course number and send the order with later courses on hold. The kitchen screen or printer shows the full order, but the line cooks only what is fired. When the server taps fire, the next course moves to “cook now” and the expo sees it.

The flow in a typical system:

1. The server opens the table on the floor plan.
2. The server rings in items and sets a course on each one, or lets the menu set it by category.
3. The server sends the order. Course 1 or 2 goes to the kitchen to cook. Later courses show as held.
4. When starters are nearly done, the server taps “Fire course 3” from the table screen.
5. The kitchen screen marks course 3 as fired and starts its ticket timer.
6. The expo bumps the course when it goes out. The status moves from cooked to served.

In Restaurant POS Studio, coursing works this way: each item carries a course, later courses wait on hold, and servers fire from the table. The kitchen display system shows held and fired items differently and tracks order status from cooked to served, so the expo can see which tables are waiting.

Printer or screen?

Coursing works with both, but they behave differently. A printer prints the fire as a new slip, which the cook must match to the first ticket. A screen updates the same ticket in place. If you are choosing between them, read our guide on KDS vs kitchen printer.

How do I train servers to course well?

Train coursing on slow nights, with a written list of calls and a few role-play tables. Teach servers to read the table, to fire with the expo in mind, and to speak up early when a table slows down. New servers should shadow a strong server for a full service before they course alone.

1. Teach the words. Ring in, fire, hold, re-fire, walking. Post them by the POS.
2. Show the menu’s default courses. Starters on course 2, mains on course 3, and so on.
3. Practice on the POS. Ring in a full order, hold, and fire in a training mode or test table.
4. Walk the pass. Let servers stand next to the expo for an hour.
5. Run a pre-shift note. Mention big parties, slow dishes and items the kitchen has run out of.
6. Review one night a week. Look at ticket times by course and talk about the slowest tables.

If your kitchen and floor staff read different languages, the calls and tickets matter even more. Our guide on bilingual kitchen tickets shows how to keep every fire call clear.

Coursing checklist for Friday night

Before service, check five things: course markers on every menu item, a clear look for held items, a single fire call routine, an expo on the pass, and enough runners for your biggest party. If those five are in place, most coursing problems never start.

• Every menu item has a default course.
• Held and fired items look different on the ticket or screen.
• Servers know the fire call and use it the same way.
• One person runs expo during the rush.
• Big parties get a heads-up to the kitchen before they order.
• Ticket timers are on, and someone watches them.