Equipment Uptime: A Preventive Maintenance Playbook for Venue Operators

Every operator has a version of this story. Second quarter, a sold-out house, and the draft system in the busiest stand stops pouring. A supervisor gets on the radio. Somebody goes to find the technician. The technician is on the other side of the building dealing with something else. Forty minutes later it is fixed, and the stand has lost the single highest-volume period of the night.

Nobody logs that as a maintenance failure. It gets logged, if at all, as a slow night in stand 12. Which is exactly why the problem persists: the cost lands in the revenue report and the cause lives in the maintenance one, and nothing connects them.

This is a playbook for closing that gap. It is written for venues specifically, because venue maintenance has a constraint that industrial maintenance does not, and most of the available guidance ignores it.

What Reactive Maintenance Actually Costs

The case for preventive maintenance is well established outside hospitality, and the numbers are worth borrowing because they come from a rigorous source rather than a vendor.

The Department of Energy's Federal Energy Management Program, through Pacific Northwest National Laboratory, estimates that a preventive maintenance program delivers 12 to 18 percent cost savings over a reactive one. Predictive maintenance, meaning condition monitoring rather than fixed intervals, adds a further 8 to 12 percent on top of preventive. And for organisations heavily reliant on reactive work, the total savings opportunity can exceed 30 to 40 percent.

Their framing of why is the useful part. During the period an organisation believes it is saving money by only fixing things when they break, it is in fact spending more than it would have under a planned approach. Reactive work carries emergency labour rates, expedited parts, collateral damage from running equipment to failure, and shortened asset life.

The Constraint Nobody Writes About: Your Maintenance Window

Industrial maintenance planning assumes you can schedule a shutdown. Venue maintenance planning has to fit between events, and in a busy building that window can be a single overnight.

This changes the whole design of a program. Three consequences follow.

Work has to be grouped by location, not by asset type

A technician sent to service every ice machine in the building walks miles and clears one category. A technician assigned to clear everything in the club level in one pass finishes an area. When your window is four hours, travel time is a material share of your capacity.

Anything requiring a shutdown goes on the dark-day calendar

Draft line cleaning, hood cleaning, deep refrigeration service and electrical work belong on days with no event, planned against the season calendar months out. Trying to fit these into a between-events window is how they get deferred indefinitely.

Frontline staff become your inspection layer

You cannot inspect a 20,000-seat building with a maintenance team of six. What you can do is make it trivially easy for the person who noticed to report it, at the moment they noticed, from where they are standing. A concession worker who can log a fault in ten seconds gives you coverage no inspection round can match.

Rank Assets by Revenue Exposure, Not Replacement Cost

Most asset registers are ordered by value, which is an accounting view rather than an operating one. The question that matters is: if this fails at the busiest moment, what stops earning?

Notice that the two highest priorities are among the cheapest assets in the building. A 400 dollar card reader can block more revenue in two hours than a 40,000 dollar chiller. Registers ordered by capital value systematically under-protect exactly the equipment that matters most on event day.

Building the Program in Five Steps

1. Inventory with locations, not just assets - Every asset needs a physical location string that matches how your staff describe the building. "Stand 14, back line" beats an asset tag nobody can read in the dark.
2. Set intervals from the manufacturer, then adjust from your own failure history - Start with the manual. After two seasons your own data will tell you which intervals are too generous and which are wasteful.
3. Turn intervals into recurring scheduled tasks - The work should appear in someone's queue automatically. A maintenance calendar that lives in a spreadsheet depends on a person opening the spreadsheet, which is the single most common point of failure in these programs. Listo supports scheduled task requests and messages so recurring work is generated rather than remembered.
4. Give every staff member a ten-second fault path - QR codes at the equipment, or a location-based request from a shared device, routing straight to the maintenance queue rather than through a supervisor. Every hop you remove is time the asset is not producing.
5. Review repeat offenders quarterly - Pull failures by asset over a rolling quarter. The same three pieces of equipment will usually account for a disproportionate share, and that is your replacement business case written from your own data.

Why Repeat Offenders Are the Whole Game

If there is one argument for having a system rather than a process, it is this. In a venue running on radios and verbal reports, nobody knows that the same ice machine has been fixed eleven times this season. Each individual repair was small, handled, forgotten. In aggregate it is a capital replacement that has been paid for twice over in labour and lost sales.

The pattern shows up immediately once failures are logged against an asset with a timestamp. Two things become possible. You can make a replacement case with evidence rather than instinct, which is a very different conversation with finance. And you can spot the failures that are actually a training or process issue rather than an equipment one, because those cluster by shift and by person rather than by asset.

This is where equipment management stops being a maintenance function and starts being an operating one. We wrote about the platform side of this in our piece on maximising venue revenue and uptime through equipment management.

What Good Uptime Looks Like

The clearest result we can point to comes from American Family Field, where Delaware North deployed Listo across food and beverage operations. The team reduced downtime by 70 percent, largely by keeping concession stands stocked and running rather than discovering problems after they had already stopped a stand trading. The consequence was fewer lost sales, lower operating cost and a better experience for fans who did not spend the third inning in a queue that was not moving. The full write-up is on our American Family Field case study.

Two mechanisms drive a result like that, and neither is exotic. Faults get reported in seconds by whoever noticed rather than minutes later by a supervisor with a radio. And the request goes to an available technician directly, rather than to a dispatcher who then has to find one. Across its venues Listo reports an average 15 percent reduction in monthly labour hours, and maintenance travel and search time is a meaningful part of that. As with any average, your building will differ.

Refrigeration, Food Safety and the Failure You Find Too Late

Refrigeration deserves separate treatment because it is the one category where the maintenance failure and the compliance failure are the same event, and where you can lose the product without anyone noticing at the time.

A walk-in that drifts from 38 to 46 degrees over a Saturday does not announce itself. Nothing stops working, no guest complains, and the crew closing down has no reason to check. The discovery happens the next morning, or worse, it does not happen at all and the product goes out. In a venue with dozens of cold-holding points spread across concourses, suites and commissary space, the number of places this can happen quietly is the problem.

Two practical measures close most of the exposure. First, put temperature checks on a scheduled recurring task rather than a clipboard, with a specific person assigned per zone and a completion record. A log that is filled in from memory at the end of a shift is worse than no log, because it creates a document asserting something nobody verified. Second, make the out-of-range path a routed request rather than a note, so a reading outside tolerance goes straight to a technician with the asset and location attached.

The reason to run this through the same system as everything else is that it puts temperature failures in the same asset history as mechanical ones. A walk-in that has drifted three times this quarter and been reset each time is telling you something a repair log alone will not.

Coordinating Contractors Without Losing the Thread

Most venues do not employ the specialists for their highest-risk systems. Draft, refrigeration, HVAC, elevators and fire systems typically sit with outside contractors on service agreements, which introduces a coordination problem that internal maintenance does not have.

The failure pattern is consistent. A fault gets reported internally, someone calls the contractor, the contractor arrives on Tuesday, and the internal record never gets updated because the work was not done by anyone with access to the system. Six weeks later nobody can say whether it was fixed, what was replaced, or whether the same fault has recurred.

The fix does not require giving contractors licences. It requires that the internal request stays open until somebody internal confirms the work and closes it, with a note of what the contractor did. That sounds administrative and it is, but it is the difference between an asset history you can plan from and a folder of invoices.

One practical detail worth building in: capture the contractor visit date and the parts replaced on the closing note. When the same asset fails again, that record is what turns a service call into a warranty conversation.

The Four Numbers Worth Reporting

• Time to acknowledge. Fault reported to fault accepted by a named technician. This is the number that most directly reflects whether your routing works.
• Time to resolve. Accepted to complete. Read it separately from acknowledge, because they have different causes and different fixes.
• Repeat failures per asset. Rolling quarter, ranked. Your capital plan should be built from this list.
• Planned share of total maintenance work. If less than half your maintenance activity is scheduled, you have a reactive operation with a preventive policy document, which is a common and expensive place to be.

Read the first two by location and by hour rather than as building averages. A four-minute median across the building can comfortably conceal a stand that waits twenty minutes every time, and that stand is where your money is going.

Where to Start This Season

Do not attempt a full asset register in one go. Take the ten pieces of equipment whose failure would stop a point of sale from trading, give each one a location, a manufacturer interval and a QR code, and run those ten as scheduled recurring work for a full event cycle.

Then read the failure log. In our experience the first month of honest data changes what operators thought their problem was in about half of buildings. The failures cluster somewhere nobody expected, usually in a category that had been treated as routine, and that is worth far more than a comprehensive register nobody maintains.