A trader takes a pitch at an event expecting four hundred people. The menu has six items, three of them cooked to order, and one person is taking payment.
By eight o'clock the queue is forty minutes long, half of it gives up, and the organiser watches people walk away hungry.
Why throughput is the whole thing
Because an event has a fixed window and a fixed crowd. Everything about profitability is how many of them you can serve before it ends, and quality matters only to the ones who reach the hatch.
Know your actual rate
Timed, from a real service, per hour with a given number of staff. Most traders have never measured it and cannot plan around a guess.
Shorten the menu for volume
Two or three items rather than eight. It is the single most effective change and the hardest for traders to accept.
Separate cooking from assembly
Prepare components ahead, assemble to order. It is what turns a three minute item into a forty second one.
Take payment separately
A dedicated person or a second point, because payment is frequently the bottleneck rather than the cooking.
Take orders down the queue
So food is being prepared while people are still waiting, which removes the dead time entirely.
Add staff rather than equipment
Beyond a point the constraint is hands rather than heat, and traders buy another griddle when they needed another person.
Ask the organiser the right questions
Expected attendance, the peak window, how many other food traders, whether there is a headline act that empties the site and what happened last year.
Calculate your share honestly
Four hundred people and four traders is not four hundred customers. Working out a realistic share prevents both under and over preparation.
Prepare for the peak rather than the total
Because everybody arrives in the same forty minutes, and a rate that works across four hours fails in the one that matters.
Explain your capacity to the organiser
Plainly, at booking, with what you can serve per hour. An organiser who knows can book a second trader rather than blaming you afterwards, which is the site planning in power, pitch and site requirement questions.
Manage the queue visibly
Where it forms, whether it blocks anything, whether people can see a menu while waiting and whether anybody is talking to them. Perceived waits are shorter than measured ones.
Handle dietary requests without stopping service
Because one complicated order can halt a queue, which is the preparation in menu and dietary questions from organisers.
Plan the stock around the rate
A trader who can serve a hundred and twenty an hour needs stock for the peak rather than for the day, and running out at seven is as damaging as a long queue. Working backwards from throughput gives a realistic order quantity instead of the optimistic one that ends in waste or the cautious one that ends in a closed hatch.
Decide what happens when the queue is too long
A visible cut off, a sign, or somebody walking the line telling people the wait. Managing the end of a queue honestly keeps people from standing for forty minutes and leaving angry, and it protects the organiser's event as much as your own takings.
Publish your capacity and coverage
So organisers book appropriately and enquiries arrive qualified, as in answering service area questions and the timing pressures in food service and kitchen hours questions.
Getting started
Measure your actual hourly rate, publish it and ask organisers about peaks, then capture event details at any hour. SpideyChat for food businesses answers from your published pages, plans are on the pricing page, and the chatbot ROI calculator works through the numbers.