In a restaurant, all day means the total number of one item needed across every active ticket. It is not about the time on the clock. It is a fast way to tell a cook what the station owes the room right now.
Picture a dinner rush. One ticket has two burgers, another has one, and a third has three. Instead of calling each ticket as a separate little problem, expo can call, "Six burgers all day." One number, one clear picture. The grill cook can see the load, pace the pickups, and ask the useful follow-up before the rail gets any louder.
That is why the phrase matters. It turns a pile of paper into a count a station can work with. Cooks hear it hundreds of times because it helps the line stay coordinated when everyone is moving fast.
All day means the total, not the next ticket
When someone says "all day," they are asking for the total quantity of a menu item across the tickets that are currently in play. It can include food that is already cooking, food that needs to be fired, and food that is waiting on another part of the plate. The exact cutoff depends on the kitchen, but the purpose stays the same: give the station the whole count, not one fragment of it.
Restaurant guides from Toast and SpotOn describe the phrase the same way: a total count of one item across open orders. The useful part on a real line is what happens next. A cook can answer, "Four down, two working," or ask, "How many are medium?" That keeps the conversation about the food, not the math.
It is also different from a guest's order. A server rings in one burger for table 24. The grill station does not only need to know that one burger exists. It needs to know how that burger sits inside everything else already called. All day gives the station that wider view.
How an all-day count works during service
The count usually comes from expo, the chef, or the cook running the station. As new tickets arrive, the total changes. If three chicken orders are already working and two more hit the rail, the call becomes "Five chicken all day." If one plate leaves the pass, the active total drops. It is a moving number, not a number someone announces once and forgets.
A good call starts with the item, then the total, then only the details that change how it is cooked. "Eight salmon all day, five medium, three medium-well" gives the fish station a plan. "Eight salmon" gives a useful starting point. A long story about which tables ordered them does not help anyone with a pan in hand.
Some kitchens use the phrase as a question. "How many fries all day?" means stop for a beat, count every fry order that matters, and answer with the total. Others use it as a declarative call. Both versions do the same job: reset the room around one reliable number.
For a new cook, the first skill is not shouting the answer. It is learning what your station counts and when. Does the saute cook include the order already plated? Does the fryer count a side that is waiting for a refire? Ask during a quiet moment, then follow the system the team already trusts.
How to answer an all-day call
Take a quick look at the rail and at the food already in motion before you answer. Count the item across every ticket that belongs to your station. Then count the portions that are down, the ones that need to be fired, and anything being remade. The final number should tell the rest of the line what you actually owe, not what you remember hearing ten seconds ago.
Answer in the same short language the call used. If expo asks, "How many chicken all day?" a useful reply is "Seven: four down, three to fire." If the number has changed because one plate just went out, say that. If you need a detail before you can commit, ask the direct question: "Seven total. How many are gluten-free?" Clear answers let the next person make a decision without translating your update.
Do not bluff a count to sound fast. A two-second recount is cheaper than an extra plate, a missing entree, or a table waiting because the line worked from the wrong number. The point of all day is not to prove you can do mental math in a loud room. It is to give the kitchen a shared answer it can trust.
A simple example: six burgers all day
Say the rail has three active tickets. Table 11 needs two burgers, table 14 needs one, and table 18 needs three. The correct total is six burgers all day. That lets the grill cook see six portions of meat, six buns, six sets of toppings, and the pacing problem in front of them.
Now add the cook temperatures. Two are medium, three are medium-rare, and one is well-done. The full call might be, "Six burgers all day: three medium-rare, two medium, one well." The total comes first because it tells the station how much food it is managing. The temperatures come next because they determine the order of operations.
Then a burger from table 11 walks to the pass. The count is no longer six active burgers. If the other five are still working, the next check becomes five all day. That rhythm is how a station avoids the two classic disasters: realizing too late that it is short, or cooking food nobody needs.
What all day does not mean
All day is not the same as on the fly. On the fly means an item is needed immediately. Maybe a plate was dropped, a server forgot to ring it in, or a guest has been waiting too long. "Fire one salmon on the fly" is urgent. "Four salmon all day" is the total count. A fast kitchen needs both pieces of information, but mixing them up makes a station choose the wrong priority.
It is not the same as "one more." If a cook asks for one more burger, they might mean one additional burger beyond what is already cooking. An all-day call should be the total, so the listener can compare it with what is down. When the language gets loose, cooks either overfire food or discover a missing plate at the worst possible time.
It also does not always mean every item printed anywhere in the building. A bar, pastry station, and grill can have different active counts. A kitchen's system should be specific enough that each station knows what they own. Broad calls are only useful when everybody agrees on the boundary.
Why the count changes so quickly
Restaurant tickets are not a static checklist. A new ticket comes in. A table changes a side. A server adds another entree. A cook calls a refire. A dish gets 86'd. Every one of those moments can change a station's workload. All day is the quick reset that keeps a running total from turning into a guess.
The strongest teams do not wait until there is confusion to count. Expo checks the rail, calls totals before a big pickup, and listens for the station's answer. The cook checks the food in front of them against the total. If the numbers do not match, that is the moment to solve it. Waiting until a server is standing at the pass is too late.
Many restaurant terminology guides group all day with calls such as "heard," "behind," and "in the weeds." The WebstaurantStore kitchen slang guide and the Institute of Culinary Education's restaurant terminology guide are useful introductions. The real lesson is that kitchen language is not decoration. Each phrase exists because it helps a crew move safely and keep the food consistent.
Three ways all-day counts go wrong
Counting the tickets instead of the items. Three tickets can hold one burger or ten. The all-day number is the quantity of the item, not the number of pieces of paper on the rail.
Forgetting food that is already working. A cook may see two new orders and fire two more portions without checking what is already on the grill. The total only works when the station counts the food that is down as well as the food still to fire.
Giving a total without the useful details. "Ten steaks all day" is a start. If those steaks need different temperatures, sides, or pickup times, the station needs that information next. Good calls stay short, but short does not mean incomplete.
The fix for all three is the same: stop for a clean count, say it clearly, and get a response from the person cooking it. A loud kitchen does not need more noise. It needs fewer assumptions.
Why cooks keep saying it
All day is a small phrase that carries a whole shift. It tells the grill how much meat to manage, tells expo whether a pickup is realistic, and tells everyone on the line what part of the rush they are actually in. That is the kind of shorthand people carry with them long after a shift ends.
BOHO's Line Lingo tee is built around that shared vocabulary. It is not a costume for people who watched a kitchen show once. It is a signal for the cooks, chefs, dishwashers, and restaurant lifers who know why "six burgers all day" can change the next ten minutes. For the rest of the language, start with BOHO's guide to what 86 means in a restaurant, then head into the 86 Series.
Frequently asked questions
What does all day mean in a restaurant?
All day means the total number of one item needed across every open ticket. It is a running count, not a time of day. If there are two burgers on one ticket and three on another, the cook may hear "five burgers all day."
Does all day include food already on the grill?
Usually, yes. The point is to give the station a full picture of what is working, what has been fired, and what still needs to go. Each kitchen has its own rhythm, so a new cook should listen for how the chef or expo calls the count.
What is the difference between all day and on the fly?
All day is the total count across active tickets. On the fly is an urgent request for something needed immediately, often because a ticket was missed, dropped, or needs a fast replacement.
Can all day mean more than one menu item?
Yes. An expo might call several totals at once: "Six salmon all day, four medium, two well." The first number gives the full demand, then the rest adds the details a station needs to cook accurately.
