Which problems should staff call the owner about?

Separate emergency action from owner approval

A fire, serious injury or immediate threat must follow the relevant emergency procedure. Calling the owner is not a substitute for contacting emergency services or taking trained protective action. Make that clear at the top of any escalation guide.

Below that level, distinguish an issue that could stop today's service from one that can be planned. A broken card terminal during trade and a loose label on a storage box may both need attention, but not the same response time. Avoid using one chat group as the only route for every kind of problem.

Describe observable triggers

Replace 'call if it is serious' with examples the team can recognise. Keep the list tied to your premises, equipment and service. People need enough discretion to raise something unexpected, so state that uncertainty about safety should always be escalated.

HSE's role guidance supports making responsibilities clear and giving people a route to raise conflicts. Your escalation guide should name the role responsible on each shift; an owner's name without a reachable deputy leaves a gap whenever that owner is unavailable.

Further reading: HSE: Management Standards — Role

Ask for the information needed to decide

A message saying 'machine broken' creates a string of follow-up calls. A better message identifies the equipment, what staff observed, what service is affected, any safe steps already taken and what decision is needed. Do not encourage staff to dismantle equipment or repeat unsafe troubleshooting to complete a form.

For example: 'The second till cannot connect. We have moved payments to the working till and the queue is growing. No payment has been taken twice as far as we can verify. Can the duty lead approve the provider support call?' Keep payment details out of general chat.

Issue and time noticed:
Immediate safety concern?:
Effect on service:
Approved action already taken:
Decision or support needed:
Who is responsible now:
Next update due:

Specify what happens when nobody answers

Write the next contact and the permitted fallback. Depending on the problem, that might mean pausing an affected service, contacting an approved contractor or waiting until the scheduled review. Do not leave people choosing between guessing and repeatedly calling an unreachable owner.

Test the chain once with a harmless scenario. Check that the deputy has the necessary authority and information, rather than simply forwarding every query back to you. Keep sensitive access instructions separate from a broadly readable contact sheet.

Review misrouted issues without punishing caution

Look at examples that arrived too late, too often or without enough detail. Adjust the trigger or ownership. An unnecessary safety escalation is usually a better learning opportunity than a reason to make the team hesitant.

Close the loop with whoever reported the issue. Tell them what happened and whether the procedure changed. If ordinary problems remain unanswered until they become urgent, fix the review process; the team cannot follow a 'record for later' rule when later never arrives.