Halfway through the third quarter, the guests are finished eating. The attendant knows some of the dishes are ready to go. The runner, waiting in the pantry, does not.

So the attendant waits, or walks into the corridor looking for a runner. Or the attendant texts or radios a captain who is in the middle of something else. Meanwhile the dishes sit where the guests can see them. This part matters because nobody buys a premium suite for the view of their own dirty dishes.

Seasoned attendants accept the waiting for runners as normal. It is easy to miss from an office and impossible to miss on the floor. The wait time is invisible, but very important. There is no record of when the dishes became ready, so there is no record of how long they sat. Ask anyone how long dishes or beverages wait for a runner and you will get an honest guess that nobody can check. Beverages behave the same way, and they carry the inventory count with them, so a wide gap there costs you twice.

What premium suite operations do record is the finish. Dishes were cleared. Beverages were picked up. Closeout completed. So the report says everything happened. A report made only of completions cannot show you a bottleneck. It can only tell you the night ended.

Two numbers change that. How many suites are ready and how many have been cleared. The difference between them is the count of suites with something sitting out waiting on a runner, a KPI that did not exist until now. It is not the runners' fault. They must go suite to suite to ask whether dishes or beverages are ready for pickup.

Underneath it is a communication and routing problem. An attendant calls or texts their captain, the captain radios or texts the pantry, and the pantry sends a runner. Every step waits on the one before it. So most operations are running on memory, personal texts, and radio traffic, and the resulting bottlenecks never show up as trackable data.

Now there is a better way than memory and serial communication. LUXOPS signals when each suite is ready for dish and beverage pickup, and when each suite has been cleared. Runners go straight to where they are needed instead of checking suite to suite. LUXOPS also quantifies the wait, in real time, so captains and supervisors can respond. Those KPI numbers can be compared across venues, which allows corporate to set operational standards to improve the guest experience everywhere.

In your operation, are runners sent directly where they are needed, or do they go suite to suite to find out?

A suite orders for 22 people. The attendant checks the received food and beverage items against the event order, item by item, and records the result on a sheet of paper. Somewhere between the kitchen, the pantry and the suite, an item on that order does not arrive. Maybe a dip. Maybe the second bottle of red.

What happens next depends entirely on the venue. Some require the attendant to text or call the captain immediately. The captain, usually busy with something else, then contacts the pantry or the kitchen depending on whether the missing item is cold or hot. That serial communication takes time and relies on the captain's memory and ability to multitask. Some operations also require attendants to fill out a paper form recording what was late or missing and when everything was finally received. The form is not collected until the end of the event, so another real-time data point is buried.

Most guests do not complain. They make a mental note, enjoy the rest of the game, and bring it up on a satisfaction survey or in six months when the suite renewal is on the table.

Ask a premium operation what share of suites received everything the guest ordered on a given night. You will get a range, usually wide, usually optimistic. Not because anyone is being dishonest, but because the answer is buried on paper.

LUXOPS broadcasts the live status of every suite and signals everyone at once when an item is missing, without relying on texts or radio calls. The data is collected per section, per event and per venue. You could discover that one pantry runs a few points behind the others every single event, which is fixable as soon as it is visible. You could compare an NFL, NBA, MLB or college game to the one before it, or to a similar event at another venue.

Does your operation know the share of suites that received everything the host ordered and can compare it to previous events?

By the time the last guest leaves, a suite attendant has been on their feet for nine or ten hours. What remains is the closeout, which means waiting for a captain to come verify that all dishes are cleaned or removed, all perishable food items are gone, ice is disposed of, and the fridge and alcohol safe are locked.

Captains are not slow. They must verify 10 to 20 suites on foot, one at a time, in an order set by whoever texted or radioed first or flagged them down in the corridor. Some attendants get verified in 3 minutes. Some wait 30. From inside the suite those two situations look identical, because attendants have no way to know where they are in the queue.

Closeout has the same shape as the dish and beverage problem from the previous article. The completion gets recorded. The interval between ready and verified does not, so it cannot be managed, and everyone involved assumes the delay is normal.

Now there is a way to see closeout progress in real time. LUXOPS captures numbers that did not exist before: how many suites are ready to close, which ones were ready first, how many the captain has verified, and the average wait between the two. From those it calculates closeout efficiency, the share of suites verified within a set target after signaling ready. Once that gap is visible by suite, by section and by venue, closeout stops being a guess. You find out where the queue backs up, whether the same section finishes last every event, and where the stress on staff is actually coming from.

What number(s) would you want to see for closeout?

At too many premium venues, suite attendants fill out paper inventory forms listing every beverage and disposable in the suite. By then the attendant has been on their feet for ten hours, and inventory is the last task standing between them and the parking lot. Handwriting suffers, because the priority is getting into the queue for closeout.

Those forms are collected by captains, stacked, and carried up the chain to supervisors who total them by hand or key them into a spreadsheet. Every transfer is another chance for a miscalculation, or for illegible handwriting to be read wrong.

That total becomes the basis for the next order. Undercount beverages, and excess product arrives to sit in pantries and storage rooms until it is thrown away at its expiration date. Overcount, and not enough is ordered, so suites run short during an event and pantries start swapping items.

Accuracy is only half of what paper costs. Buried in those same forms is the difference between one event's count and the next, and that difference is the only true measure of what a suite actually consumes. A 12-person suite hosting the same law firm every event does not consume like a 22-person suite that rotates corporate hosts, and neither consumes the same for an NFL game as for a concert night. That number is buried on paper at most venues, so every cabinet in the building gets stocked to the same par. Per-suite consumption history changes that, and what it recovers is the excess inventory sitting in every one of those cabinets.

Now there is a better way. LUXOPS captures the count digitally in the suite, at the moment the attendant is looking at the shelf. Pack and sleeve sizes are stored in the system, so nobody converts from memory. Section and venue totals calculate themselves with no transcription in between, and every count is kept, so the difference between the start and end of an event becomes a per-suite, per-event consumption rate instead of a number buried in a stack of paper.

If you had a per-suite consumption number for every type of event, how would you use it?