An equipment fault report that gets more than 'it's broken' across

Identify the machine before describing the fault

A message saying 'the fridge' is ambiguous when you have several. Give each important unit a simple internal label and record its make, model, location and service contact where the team can find them. Keep the serial number in the equipment record if it can be collected safely, so staff do not have to reach behind a faulty machine during service.

An operator on Reddit described ringing random firms after breakdowns, struggling to get a response. A prepared equipment record will not guarantee an available engineer, but it can make the first conversation more useful and reduce requests for basic information.

Further reading: Restaurant owner asks how to arrange reliable equipment repairs

Describe observations, not guesses

Use plain facts: 'Display shows code E3', 'water visible beneath the front left corner', or 'machine stopped during the usual cycle'. Record when the symptom started and whether it has happened before. Avoid writing 'compressor failed' unless a competent person has actually diagnosed that fault.

HSE advises having a procedure for reporting damaged or faulty equipment and using competent people for maintenance. Keep staff within their training and the approved operating procedure. Do not ask them to remove panels, bypass guards or repeatedly restart a machine to produce a better video.

Further reading: HSE: maintenance of work equipment

Use a short report the caller can read aloud

Make the report usable on a phone. Put the identity and current status first, followed by the symptom and effect on service. Record any food or other stock affected separately under your relevant procedure; do not let equipment administration delay an immediate safety action.

This example is for collecting information, not for deciding whether a machine is safe. The person receiving it still needs to assess the issue and arrange the correct response.

Equipment label and location:
Make/model/serial, if already recorded:
Observed symptom or error code:
First noticed at:
What was happening at the time:
Current status and safe action taken:
Effect on service:
Previous related report/reference:
Photo available, if safely obtained:
Reported by and contact:
Person notified, time and acknowledgement:

Follow the report through to a verified outcome

Choose one person to own the follow-up. They record the repair reference, appointment, interim restrictions and the next update due. If the expected acknowledgement does not arrive, use the agreed escalation contact. A message sent to a group chat is not the same as a request accepted by a responsible person.

When someone says the machine is fixed, keep the service findings and confirmation of return to use with the original report. If the symptom returns, reopen the issue with the previous reference rather than starting a disconnected conversation. Review repeated faults with the appropriate engineer and decision-maker. That gives you a useful maintenance history without turning staff into technicians.