A restaurant refrigeration maintenance program works best when units are ranked by what a failure would cost you, then visited at a frequency and depth that matches the rank. Walk-in freezers and coolers get the closest attention, reach-ins and prep tables a lighter routine, ice and beverage equipment a sanitation-focused one. Every visit should log the same readings against the same unit record, so trends show up before breakdowns do.
- Start with criticality, not equipment type. A walk-in holding a week of protein deserves more attention than a prep table that can be emptied into another unit in minutes.
- Visit tasks should change by unit type. A freezer needs defrost testing every visit, a reach-in mostly needs gaskets, drains and coil access, and an ice machine needs sanitation and water-side checks.
- Frequency follows exposure. Condensing units behind a kitchen or in a grease-laden alley need coil cleaning more often than units on a clean roof.
- The same short list of readings, taken the same way each visit, is worth more than a long checklist that varies by technician.
- A program is only as good as the unit inventory behind it. Every visit, reading and repair should attach to a specific, labeled unit.
Start with what a failure costs you
Most restaurants maintain refrigeration the way they maintain smallwares: when it breaks. A program changes the order of operations. You decide in advance which units can never be allowed to fail on a Friday night, which ones can fail with an annoying but survivable day, and which ones are simply replaceable on a slow Tuesday. Then you spend attention accordingly.
That ranking is the backbone of everything else on this page. If you have not built it yet, the inventory and risk ranking page walks through how to count units and score them. The program described here assumes you have at least a rough list: unit, location in the building, type, refrigerant if known, and what depends on it.
Two questions sort most units quickly. First, how much product is inside, and how fast does it become unsafe if the unit stops? Second, can the product be moved somewhere else without disrupting service? A walk-in cooler with a full receiving day inside fails both tests. A single-door reach-in on the line passes the second, because a cook can move a few pans.
Three tiers that work for most kitchens
You can use more tiers, but three is enough for most single restaurants and keeps a multi-location template readable. Adjust the names to match how your team talks.
| Tier | Typical units | Why they sit here | Program intent |
|---|---|---|---|
| 1: Protect the inventory | Walk-in coolers, walk-in freezers, any unit holding bulk product | Loss is large, recovery is slow, product cannot be relocated quickly | Closest attention, defrost and airflow verification, trend review |
| 2: Protect the line | Reach-ins, undercounter units, sandwich and pizza prep tables, bar refrigeration | Failure disrupts service but product can usually move | Routine inspection, gasket and drain care, coil access |
| 3: Protect quality and sanitation | Ice machines, beverage dispensers, display and merchandising coolers | Failure affects quality, guest experience or cleanliness before it affects safety | Sanitation cycle, water-side checks, scheduled cleaning |
Notice that tier is not the same as value. A cheap walk-in compressor that cooks a week of inventory is a tier 1 problem. A very expensive display case with a short product turn may belong in tier 3. Rank by consequence.
What each visit should cover, by unit type
The task list below is a reasonable starting point to adapt, not a universal standard. Manufacturer instructions and the specific system govern. What matters is that the tasks are written down per unit type, so a different technician can arrive and do the same job.
| Unit type | Core tasks each visit | Added tasks on a longer cycle |
|---|---|---|
| Walk-in freezer | Run a defrost cycle and watch termination; check drain line and heater; look at evaporator for ice pattern; test door heater and closer; inspect gaskets | Refrigerant circuit review, contactor and capacitor check, fan motor current, controller and alarm test |
| Walk-in cooler | Inspect evaporator and drain pan; confirm fan operation; check gaskets, strip curtains and door closer; verify box temperature against a calibrated reference | Condenser coil cleaning, electrical connections, controller accuracy |
| Reach-in and undercounter | Gaskets, hinges, drain, lower coil access; confirm the unit is not starved for ventilation | Condenser coil cleaning, fan motors, thermostat accuracy |
| Prep tables | Top rail and pan lid condition, drain, ventilation behind the unit, temperature at the pan line | Condenser cleaning, fan motors, thermostat accuracy |
| Ice machine | Check water supply, filter condition and harvest pattern; inspect for scale or biofilm | Descaling and sanitizing per the manufacturer cycle, condenser cleaning, water-quality review |
| Remote condensing unit or rack tie-in | Visual on the condenser, fan operation, oil and sight-glass observations where present, pressure readings | Leak inspection, electrical check, controls review |
Pair this with the refrigeration PM guidance for walk-ins, reach-ins and prep tables if you want the detailed checklist. For ice, see the commercial ice machine guide.
Setting frequency without guessing
Frequency is where programs get either wasteful or thin. A rigid quarterly schedule for every unit overspends on clean, lightly loaded equipment and underspends on the stuff that sits in the worst conditions. Build frequency from three inputs instead.
- Tier. Tier 1 units generally justify more visits or deeper visits than tier 3.
- Exposure. A condensing unit near the exhaust discharge of a fryer line, or in an alley with cooking grease and dust in the air, loads up its coil faster than a unit on a clean roof. Coil cleaning frequency should reflect what you see, not a calendar default.
- History. A box with a pattern of repeat calls earns extra attention until the root cause is found. If a unit has needed three visits for the same complaint, the program should call for diagnosis, not another reset.
In practice many kitchens land on a rhythm where tier 1 units are inspected every visit, with condenser cleaning on a shorter cycle than the rest of the checklist. Tier 2 and 3 units may be covered on alternating or semi-annual passes. Your mix will differ; the point is that the logic is written down and you can defend it.
Heat is the stress test for condensing units. Late summer and early fall are when marginal airflow, dirty coils and weak fan motors become service calls. A pre-summer visit that confirms condenser condition and walk-in door sealing often matters more than any other in the year. The seasonal calendar shows how to place it.
The readings worth logging every time
A long list of measurements that nobody compares is theater. A short list taken consistently becomes a trend line. For refrigeration, the following are usually enough to spot slow decline.
- Box air temperature at a consistent location, with the reading instrument noted.
- Suction and discharge pressure, with ambient condition noted.
- Superheat and subcooling where the system allows it.
- Compressor and fan motor amperage compared with nameplate.
- Defrost behavior on freezers: did it terminate normally, was there residual ice, was the drain clear.
- Condenser coil condition before and after cleaning, with a photo.
- Anything done to refrigerant: type, quantity, and the reason.
Trends matter more than any single value. A compressor drawing slightly more current each visit, or a freezer whose defrost keeps running long, is telling you something months before it fails. That is the difference between a planned repair during a slow afternoon and an emergency during dinner service.
How the program ties back to the unit inventory
The inventory is the spine, and each visit adds to it. If readings are recorded on a technician's invoice and nowhere else, you will not be able to see a pattern across visits or sites. If they are recorded against a unit ID, you can.
- Label each unit with a unique ID, ideally physically on the unit. A QR tag works well because anyone can scan it.
- Record type, location, tier, age if known, refrigerant if known, and electrical and condensing configuration.
- At each visit, attach the readings, the tasks completed, photos and any recommendations to that unit's record.
- Review the records with your service provider at a set interval, and move units between tiers when conditions change.
- Use the history when deciding repair versus replacement. The replacement planning page covers that logic.
The DaVinci Portal is built around this model: QR-coded asset records with service history, readings and photos, included with service and programs. Whether you use that or your own system, insist on unit-level records.
What a program does not cover
Be clear about boundaries when comparing proposals. A maintenance program reduces the chance of failure; it does not eliminate it, and product loss, food waste and lost sales are generally outside what any service provider covers. Parts and repairs found during a visit are usually quoted separately unless the agreement says otherwise. Read the exclusions the same way you would read a lease.
Work that crosses into other trades, such as dedicated electrical circuits, panel or feeder work, and building structure, needs to name who performs it. Davinci's refrigeration and controls work is done by its own UA Local 250 crew, and the proposal should state which party handles anything outside that. For help weighing proposals, see how to compare commercial maintenance proposals and the broader maintenance contracts for restaurants and food service page.