What Site Managers Need to Know

The general manager is the sensor for the entire maintenance programme. What they notice, when they report it, and how they describe it determines everything downstream.

They are not technicians and should not need to be. They need a small, specific set of things.

What to report and when

The daily checks that are also maintenance signals. Temperature logs, sanitiser concentration, rinse temperature. These are food safety requirements and they are the earliest failure indicators available.

The symptoms that mean something. Trained explicitly, because they are counterintuitive:

Equipment running constantly is failing, even though it is working. Ice on an evaporator is a fault, not a normal condition. Dishes coming out wet may mean the rinse is not hot enough. A door that needs lifting to close will be left open. Water on the floor near equipment is urgent. A hood that smokes indicates a ventilation problem, not a busy kitchen. Several appliances underperforming at once is one problem, not several.

When to report immediately versus when to add to the routine queue. The priority definitions, in plain language, on the wall.

How to describe a fault

The single highest-value training item.

Describe what it does, not what is wrong. Managers guess at diagnosis and the guess misdirects the technician. "The freezer is at 15 degrees and should be at zero, there is ice on the fan" is useful. "The compressor is gone" is a guess that sends the wrong part.

Give the asset tag.

Give numbers. Actual temperature, target temperature.

Say when it started and what changed. After a delivery, after a power cut, after cleaning.

Photograph it. The unit, the display, the error code, the damage. Requiring a photograph on the report form does more for first-visit resolution than any other single change.

Say whether it is in use and whether product is at risk.

What they should be able to check themselves

A short list that resolves a real share of reports without a call-out.

Is it powered? Switch, plug, breaker.

Has a control been changed? Thermostats get adjusted.

Is the door closing?

Is anything blocking airflow — product against an evaporator, boxes against a condenser, a blocked intake.

Is a filter obviously blocked?

Is a drain blocked?

Is there an error code displayed?

Five minutes on this list before reporting saves a significant number of unnecessary visits, and managers are happy to do it once they know it is expected rather than being asked to fix things.

What they should not do

Diagnose.

Open equipment, beyond removing an accessible filter.

Reset a safety device repeatedly. A high-limit that trips twice is a fault, not a nuisance.

Bypass anything.

Call a contractor directly outside the defined process, which is how work becomes invisible. This happens when the official route is slower than the unofficial one, which is a process design problem rather than a discipline problem.

Accept a technician leaving without a report.

Managing the visit

Escort the technician. Access, and knowing what was actually done.

Ask what was wrong and what was done, and write it down. Technicians frequently explain more verbally than they write.

Ask whether the fix is permanent.

Check it works before signing.

Sign for what was actually done, not for a blank sheet with a promise to fill it in.

Report anything the technician mentioned in passing. "That other unit's condenser is filthy" is a free inspection nobody logged.

The monthly checklist

Ten items, no more. Realistically:

Walk-in door seals, paper test. Ice build-up check. Condenser coils, visual. Drain check. Filter condition. Fire suppression pull station clear and nozzles unobstructed. Hood filters clean. Thermometer calibration check. Interior release on walk-ins. Any new damage.

Completed with a record, monthly. Ten minutes. It is the cheapest component of the whole programme and the one most likely to lapse, which is why the completion rate is worth tracking by site.

Giving them something back

A programme that only extracts information from sites will be quietly abandoned.

Faster response. Fewer failures. Less time on the phone chasing contractors. Being told when something is fixed.

If the manager's experience is that reporting through the process is slower and less certain than calling the contractor they know, they will call the contractor they know, and no amount of training changes that.

Delivering the training

This is not a course. It is thirty minutes, repeated, with material that stays on the wall.

Thirty minutes at induction for every new manager, covering the reporting form, the priority definitions, the emergency procedures and the monthly checklist.

A one-page card by the phone with priorities and contacts.

A wall poster with the symptoms that mean something.

Refresh annually, and after any process change.

Include it in the manager handover checklist, because this knowledge is exactly what disappears when someone leaves.

Use real examples from your own estate. "Last July the walk-in at site twelve failed; the log had been showing a warm trend for nine days and nobody reported it" teaches more than any general description of preventive maintenance.

Then check it worked by reading the next month's work orders from that site.