Guide
Who owns the broken dishwasher? Keeping equipment faults from getting lost between shifts
How a fault disappears
The lunchtime kitchen porter notices the dishwasher leaking. They tell the sous chef, who mentions it in the handover. The evening team puts a tray under it. The next morning someone asks whether the engineer was called. Everyone assumed someone else did it.
Nobody did anything wrong, exactly. The fault was noticed, mentioned and worked around. What was missing was a single person whose job it was, and a next step with a time on it.
One owner at a time
Every fault needs one named owner. Until someone accepts it, the department’s manager is accountable. When it is passed to someone else, the new owner accepts it, so there is never a moment where it belongs to everybody and therefore nobody.
A next action, not a vague deadline
“Fixed by Friday” is a hope. “Call the engineer by 10am” is a next action. Deadlines should describe the next thing that has to happen, and they should not move quietly: if a deadline changes, record the reason and keep the original, so lateness is visible rather than erased.
Waiting is a state, not an excuse
Plenty of faults are genuinely stuck: waiting on a part, a contractor or a landlord. That is fine, as long as the record says what it is waiting for and when someone will follow it up. Being blocked should never hide a fault that is already overdue.
Check the fix
The engineer leaves and says it is fixed. Is it? For anything important, the person reporting the fix and the person confirming it should both be on the record, and the fault should only be closed once someone has checked. If it fails again, reopen it rather than starting a new report, so the history stays together.
Make reporting quick
If reporting a fault takes longer than working around it, people work around it. A report needs only a short title, the department responsible, a category and a priority. Everything else, such as a photo or a description, is useful but optional.
Priorities that mean something
A priority should change what happens next. In OpenHandover the default next action for each priority is:
- Urgent, an immediate disruption: next action within 30 minutes.
- High, a significant impact on this shift: within 4 hours.
- Normal, a routine repair or follow-up: within 24 hours.
- Low, a non-urgent improvement: within 72 hours.
Urgent means the next step happens fast, not that the repair is promised in half an hour. For immediate danger, follow your site’s emergency procedures first.