One number decides the whole thing
Seconds per guest. Everything else on the form is bookkeeping around it. At the 25 seconds sitting in the field, one flow of a buffet clears 144 guests an hour; at 40 seconds it clears 90. That is the difference between a meal that fits in its slot and a meal that does not, and it is set by how far a guest walks, how many dishes they stop at, and whether anything on the line is being cut, plated or assembled to order.
Nobody measures it. It takes one stopwatch and one event: start when a guest picks up a plate, stop when they turn away from the last dish, and do it fifteen times. The spread will be wide and the average is the number you want. Until you have it, the answer this page gives is exactly as good as the guess you fed it.
What the defaults work out to
180 guests, a quarter of them going back for a second pass, so 225 trips down the line. Two lines served from both sides is four flows, each doing 144 an hour, so 576 an hour altogether. 225 divided by 576 is 23.4 minutes, and the 45 minute window has 21.6 minutes spare.
Now take three of those flows away. One line, one side, 225 trips at 144 an hour is an hour and 34 minutes — more than twice the window, for the same food and the same room. That is the whole reason this page exists. The step from one flow to two saves 46.9 minutes; the step from six to eight saves 3.9. The line is a reciprocal curve and the cheap wins are all at the left hand end of it.
The second side is not a second table
Opening the far side of a buffet table doubles the throughput without taking another square foot of floor, which sounds like the free lunch it partly is. The catch is that a guest on the far side has to be able to reach every dish, so a two sided line is two mirrored sets of the same food. Twelve dishes at two per station is six stations; two sided, that is twelve chafers, twelve sets of serving tools and twelve pans to keep filled. The floor is free and the kitchen is not.
The page prints the servers as stations by sides by lines, so at the defaults that is six stations, two sides, two lines, one server each — 24 people on the line. If that number looks absurd for your event, the honest fix is usually fewer stations with more of each dish rather than fewer servers, because a station nobody is standing at is the one that runs empty and stalls the line.
Waves move the wait, they do not remove it
Three tables of ten is thirty people, and thirty people take 3.1 minutes to get through 576 guests an hour. So the calls go out every three minutes or so, six waves for eighteen tables, the last table called at about 15.6 minutes and off the line at 18.8. Everyone else is sitting down for their wait rather than standing in it.
Call faster than the gap and the queue simply rebuilds at the chafers, which is the same wait with worse scenery. Call slower and the line stands idle between waves and the meal drifts past its window for nothing. The gap the page prints is the rate the line can actually swallow, and it is the one worth setting a timer to.
What beats the arithmetic
A dish running out. The line stops entirely while somebody walks a fresh pan from the kitchen, and a two minute stall in a 23 minute service is nine percent of the whole meal gone. That is a kitchen and a par level problem rather than a layout one, and it is the reason experienced catering staff watch the pans rather than the queue.
The other thing not modelled here is that people do not arrive at a buffet at a steady rate even when you call them in waves. They arrive in a lump at the start, thin out, and lump again at dessert. The page gives you the average, which is the right number for sizing the line and the wrong number for predicting the worst two minutes of it.
Questions people ask
How many buffet lines do 200 guests need?
It depends entirely on how long one guest takes and how long you have. Put 200 guests, 25 seconds and a 45 minute window into the form and it wants three flows, which is two lines served from both sides. Stretch the seconds to 40 because there is a carving station and a made to order pasta pan, and the same 200 guests in the same window want four flows. The guest count on its own does not answer the question and any figure that claims it does is guessing at the seconds for you.
How long does it take 180 people to go through a buffet?
At the values in the form, 23.4 minutes through four flows, and an hour and 34 minutes if you run one line served from one side. The arithmetic is 180 guests plus a quarter going back for seconds, giving 225 trips, divided by the number of flows times 144 an hour. The single biggest lever is the number of flows and the second biggest is the seconds per guest.
Is a double sided buffet really twice as fast?
In throughput terms yes, because two guests are being served at once instead of one, and the page models it that way. What it costs is a second complete set of the food: every dish has to appear on both sides or guests on the far side will cross the line to reach it and the whole benefit evaporates. So it doubles the chafers, the serving tools and the pans while taking no extra floor.
How far apart should tables be called?
At the rate the line can swallow them, which the page prints. Three tables of ten at 576 guests an hour is a call every 3.1 minutes. Calling faster than that just rebuilds the queue at the chafers where it is least pleasant, and calling slower leaves the line standing empty. Nothing about the interval is a rule — it falls straight out of the flow rate you entered.
Does this tell me how many people the room can hold?
No, and it cannot. Legal occupant load is set by the fire marshal and the building official under the code your jurisdiction has adopted, and it is a separate number from anything that fits physically. This page takes a guest count you supply and works out how long a serving line takes to feed it. It issues no occupancy or compliance verdict at all.