Course firing: mains away when the starters clear

A table of four orders starters and mains together. The starters arrive, and eleven minutes later, with half the starters still on the plates, the mains appear at the pass. The server either rushes them to a table that is not ready, or leaves them under the lights while the steak goes grey. Either way, the meal has lost its rhythm, and the kitchen has done its job perfectly to the wrong timetable.

Course firing is how a restaurant stops that happening. The mains are ordered at the start, but they are not cooked until someone tells the kitchen the table is ready for them. That call, the fire, is one of the most important moments in a sit-down service, and in many venues it is left to habit, memory and shouting.

This guide covers what course firing is, the two signals the kitchen needs before it starts a main, who should fire and when, how cook times change the call, and how to measure whether your fires land at the right moment. Every venue and figure in it is an example.

Course firing means sending each course of a meal to the kitchen to be cooked at the moment the table is ready for it, rather than all at once when the order is taken. The order is taken in one go, so the kitchen knows what is coming, but the later courses are held until they are fired.

Most restaurants fire the starters straight away. The mains are held, and fired when the starters are nearly finished, so they arrive a few minutes after the starter plates are cleared. Desserts are usually ordered later, so they are fired as soon as they are ordered.

The practice of managing the order and timing of courses is often called coursing. It is the reason a good meal feels unhurried even in a busy room: each course arrives when the guests are ready for it, not when the kitchen happens to be free.

A kitchen working without fire calls has two choices, and both are bad. It can cook each order as soon as it arrives, which sends mains out while starters are still being eaten. Or it can guess when each table will be ready, which depends on how fast four strangers eat their soup, something the kitchen cannot see.

The floor can see it. The server knows when a table has slowed down, when one guest has barely started, when a bottle of wine has opened a long conversation. The kitchen knows how long each dish takes. Course firing joins those two pieces of knowledge: the floor says when, and the kitchen knows how long.

That is why course firing is a system, not a habit. It needs a clear way for the floor to tell the kitchen, and a clear way for the kitchen to show what is waiting and what is cooking.

Before a main is started, two signals must reach the kitchen. The first says what is coming: the full order for the course, with every choice, change and allergy, so the station can plan and prepare. The second says when: the fire, which tells the station to start cooking now.

Many problems with coursing come from mixing the two up. If the first signal is missing, the fire arrives with an order the station has never seen, and cooking starts from cold. If the second signal is missing, the station either starts too early, because the order looked active, or waits too long, because nobody called it.

Good coursing keeps the two signals separate and clear. The kitchen sees the held course early, plainly marked as waiting, and starts it only when it is fired.

The held course is the first signal. When the order is taken, the mains go to the kitchen marked as held. The station can see that a table of four is having two steaks, a sea bass and a risotto, can check it has what it needs, and can do any preparation that does not commit the dish.

The held course must look different from active work. On paper, kitchens often use a separate rail or a different coloured ticket. On a screen, the held ticket should be greyed out, placed in its own area or marked held in a way that cannot be mistaken for a ticket to start. Our guide to kitchen tickets that never need a shout covers how held courses should appear.

A held course also gives the kitchen a forecast. A grill cook who can see eight steaks held across four tables knows the next twenty minutes will be busy, and can prepare for it before the fires arrive.

The fire is the second signal. It tells the station that the table is ready for the course, and that cooking should start now. On paper, it is often a separate fire ticket, or the server calling it at the pass. On a screen, the held ticket changes state and becomes active.

The fire must be quick to send and impossible to miss. A server who has to walk to the pass, find the chef and wait for a nod will fire late, or not at all on a busy night. A fire that changes a ticket quietly on a screen at the far end of the kitchen may be missed by the cook who needs it.

The best fire is one action from the floor, which changes the ticket visibly at every station that cooks a part of the course, with no shouting required.

In most restaurants, the server fires the course, because the server can see the table. That works well when servers are trained, attentive and have a quick way to fire. It works poorly when a server is stretched across too many tables and forgets.

In some kitchens, the pass fires the courses. The head chef or expeditor watches the room, or asks the floor, and calls each table's mains in turn. That gives the kitchen more control over its own pace, and works well in kitchens with a strong pass and a clear view of the dining room.

In the classic brigade de cuisine, the aboyeur at the pass called the orders to each station, a role many kitchens still fill today. Whoever fires, the rule is the same: one person is responsible for each table's fire, and everyone knows who that is.

The right moment to fire depends on the table, the dishes and the kitchen. A common starting point is to fire the mains when most guests at the table are about two thirds of the way through their starters. That gives the kitchen time to cook, and the floor time to clear the starter plates before the mains arrive.

The server should look at the slowest eater, not the fastest. A table where three guests have finished and one has barely started is not ready, however empty most of the plates look. Firing on the fastest eater means mains arrive while one guest is still on their starter.

Some tables want a pause between courses: a long conversation, a celebration or a second bottle of wine. A good server notices and holds the fire for a few minutes. A good kitchen accepts that a held course will sometimes wait longer than expected.

The fire should also reflect how long the course takes to cook. A table having four quick pasta dishes can be fired later than a table having a whole roast chicken that needs twenty-five minutes. If the floor fires both at the same point in the starters, one table will wait too long for its mains.

Kitchens can help by telling the floor which dishes are slow. A simple note in the service briefing, such as "the chicken for two takes twenty-five minutes, fire it as the starters arrive", turns the server's judgement into a reliable timing.

Your own ticket times show which dishes are slow. Our guide to ticket times: the only kitchen metric that moves covers how to measure them, so the slow dishes are known, not guessed.

A single table often orders mains with very different cook times: a well-done steak that takes eighteen minutes, a piece of fish that takes eight and a salad that takes three. All four plates must arrive together.

The fire starts the course, but the stations must time their own parts. The grill starts the steak at once; the fish station waits ten minutes; the cold section plates the salad at the end. The person running the pass coordinates them, so the plates come together at the same moment.

That coordination is easier when every station knows what the rest of the table is having, not only its own part. Our guide to kitchen screen layout for four stations covers how to give each station its own work while keeping the table in view.

Large tables make course firing harder. A table of fourteen takes longer to eat its starters, has more variety in pace and orders more dishes. If its mains are fired as one block, a single station can be overwhelmed while the rest of the kitchen waits.

Fire large tables slightly earlier than small ones, because more plates take longer to cook and assemble. Tell the kitchen when a large table's fire is coming, so stations can clear space. For very large parties, consider a set menu, which makes the course predictable and lets the kitchen prepare in advance.

Avoid firing two large tables at the same moment. If two parties of twelve are on their starters together, stagger their fires by a few minutes, even if one waits slightly longer.

On a tasting menu, every guest has the same courses in the same order, and the kitchen knows them all in advance. Coursing becomes a rhythm: each course is fired when the table finishes the one before, and the kitchen can prepare each course's parts ahead.

The risk is the opposite of an à la carte service. With many small courses, a few minutes' delay on each one adds up to a long evening, and a table that expected two and a half hours leaves after four. Agree a target gap between courses, perhaps eight to twelve minutes, and have the floor fire each course as the previous plates are cleared.

The pass should watch the whole room, because a tasting menu kitchen often has several tables at different courses at once, and two tables reaching the same course together can stretch one station.

Desserts are usually ordered after the mains are cleared, so they are fired as soon as they are ordered. The timing question is when to offer the dessert menu: too soon and guests feel hurried, too late and the table waits with empty plates and an evening that has gone flat.

A good rule is to clear the mains, give the table a minute, then offer desserts and drinks together. That keeps the meal moving without pushing it.

Some desserts take time, such as a soufflé or a fondant baked to order. Those are often ordered with the mains, held, and fired when the mains are cleared. They are course firing in miniature, and the same two signals apply: the kitchen needs to know the dessert is coming, and when to start it.

Course firing is one table at a time, but the kitchen feels the whole room. If several tables are seated together, their starters finish together and their fires arrive together, and the kitchen faces a wave of mains it cannot cook at once.

Pacing covers means spreading the arrivals and orders across the evening, so the fires are spread too. That starts at the booking stage: staggering booking times, limiting how many tables arrive in each slot and seating walk-ins with the kitchen in mind. Our guide to pacing covers so the kitchen never drowns covers it in detail.

On the floor, the host and servers can help by not seating and ordering four tables at the same moment, and our guide to table pacing: stopping four tables ordering at once covers how.

Kitchen tickets must make the state of each course obvious at a glance. A held course should be visibly different from an active one, and a fired course should look like work to start now, so no station has to ask which is which.

The ticket should also carry everything needed to cook the course: every dish, every change, every allergy and the table number. A fire that arrives with incomplete information forces the cook to stop and ask, which wastes the minutes the fire was meant to save.

When a course is fired, the change should reach every station that cooks part of it at the same time. A steak fired at the grill while the sides are still held at the fryer will arrive alone.

Even good systems go wrong sometimes. A course fired too early arrives while the table is still eating. The fix is to hold the plates briefly if the dish allows, or to tell the table honestly that the mains are ready and ask if they would like a few more minutes. Note it, so the server learns.

A course fired too late leaves the table waiting with empty plates. Apologise, tell the kitchen, and see whether any part of the course can be brought forward. Then look at why the fire was late: a stretched server, a missed table or a fire sent but missed in the kitchen.

A course never fired at all is the worst case. The table waits, the server assumes the kitchen is slow, and the kitchen never saw the fire. Every held course should be visible to someone whose job is to notice when it has waited too long.

Ticket times show how long each ticket takes from arrival in the kitchen to completion. For fired courses, they show how long the kitchen took after the fire, which tells you whether the kitchen is cooking at the pace the floor expects.

Look at ticket times by station and by hour. If tickets regularly take far longer than planned at certain hours, the fires may be bunching, or a station may be the bottleneck. If they are completed quickly but tables still wait between courses, the fires may be late.

Also look at remakes. A dish sent back because it was cold, overcooked or wrong may point to a course that waited too long at the pass, which is often a sign that the fire and the cooking were out of step.

Course firing needs training on both sides. Servers need to know when to fire, how to read the table, which dishes are slow and how to send the fire quickly. The kitchen needs to know what a held course looks like, what changes when it is fired and how to coordinate the stations.

Practise with real scenarios: a table that slows down, a large party, a table with very different cook times, a fire that arrives at the same moment as three others. Walk through each one before service, so the team knows what to do when it happens.

Review course firing after busy services. Which tables waited? Which fires were early or late? A short conversation after service builds better habits than any rule.

An invented bistro with sixty covers has a recurring problem on busy nights: mains arrive while starters are still on the table, or tables wait twenty minutes with empty plates. The kitchen cooks orders as they arrive, and servers sometimes call fires at the pass when they remember.

The bistro introduces clear course firing. Mains are always entered with the starters, held. Servers fire each table's mains when most guests are two thirds of the way through their starters, looking at the slowest eater, with a single action from the till. Slow dishes, such as the chicken for two, are fired as the starters arrive. The pass watches for held courses that have waited more than twenty minutes.

After a month, the bistro compares ticket times and remakes on busy nights with the month before. Fewer mains wait at the pass, and fewer are sent back cold. The servers say the evening feels calmer, because they no longer have to rush mains to tables that are not ready.

In servearound, the server decides what goes to the kitchen now and what waits. On the till, a dish can be set to hold before the round is sent, or the whole round can be sent held, and held dishes reach the station that cooks them as tickets marked held: on the board, so the station can see what is coming, but plainly not to be started. Each ticket carries the table, every dish with its options and notes, and the guest's allergies at its head.

When the table is ready, a single button on the till, showing how many held tickets are waiting, fires every held ticket at the table at once, or the kitchen fires a held order from its own board with a second tap on its ticket. If guests order from the table's QR code, the venue chooses whether their orders start in the kitchen at once or wait, held, for staff to fire them. A dish sent back is re-fired from the check as a remake, with a reason, and the guest is not charged again.

Kitchen analytics show ticket times day by day, by station and by day and hour, where the minutes go between the queue, prep and the pass, and the remake rate. Bookings are paced by the times each shift offers and how long each booking lasts, as there is no automatic cap on covers per slot. See Order Fulfillment.

Sending each course to the kitchen to be cooked when the table is ready for it, rather than all at once when the order is taken.

Usually the server, who can see the table. Some kitchens have the pass fire instead. Either way, one person is responsible for each table.

A common starting point is when most guests are two thirds of the way through their starters, judged by the slowest eater and adjusted for slow dishes.

What is coming, through a held course with every detail, and when to start, through the fire.

Plainly different from active work: in its own area, greyed out or marked held, so no station starts it early.

The fire starts the course, and each station times its own part so the plates arrive together, coordinated by the pass.

Spreading arrivals spreads the fires, so the kitchen does not face every table's mains at once.

Look at ticket times by station and hour, at remakes and at how long tables wait between courses.

Course firing means ordering every course at the start but cooking each one when the table is ready for it. The kitchen needs two signals before it starts a main: the held course, which shows what is coming with every detail, and the fire, which says start now. Keep them separate and clear, with held courses plainly marked and fires sent in one action from the floor.

Make one person responsible for each table's fire, read the slowest eater, work back from cook times and stagger large tables. Pace covers across the room so fires do not bunch, and measure ticket times and remakes to see whether your coursing works.