A handover that survives a busy shift.
A practical guide for cafés, restaurants and hospitality businesses: make the next responsibility clear before the shift changes.
Published . Updated .
The next shift inherits a promise, not just a list.
A customer waiting for a reply does not experience a shift boundary. Neither does an order already accepted or an unavailable item still visible to the person taking orders. The handover needs to carry the unresolved promise and the authority to deal with it.
This is a practical hospitality guide, not a report of observed client work, a food-safety standard or a substitute for your existing specialist procedures. Every situation and time in the worked example is fictional. It illustrates operating responsibility, not a guaranteed service outcome.
Begin with what the incoming person must do next. “Customer issue pending” leaves too much unanswered. What was promised? Where is the authorised record? Who owns the reply? When is it due? Which decision can that person make, and which must be escalated?
An illustrative 15:00 shift change.
Imagine a café changes shifts at 15:00. A takeaway customer has reported a missing item and was promised a reply by 15:15. The existing order record contains the information needed to check the matter. The incoming person handling customer enquiries takes ownership of the reply.
A second issue concerns an item shown as available although the team has confirmed there is no stock for the next service period. The person responsible for the next service needs to update availability in the channels they are authorised to manage and tell the person taking orders. Any already accepted order needs its own customer follow-up.
These are separate responsibilities. The customer issue is not closed because somebody checked stock. The stock issue is not closed because somebody put a note in a chat. The incoming team confirms each owner and the next action before treating the transfer as complete.
| Open matter | Owner and next action | Follow-up and escalation boundary |
|---|---|---|
| Missing-item report; reply promised by 15:15. | Incoming customer-enquiry owner checks the existing order record and contacts the customer. | If the record cannot be resolved by 15:10, involve the person authorised to decide the remedy. Do not promise a refund outside existing authority. |
| An unavailable item is still offered for the next service period. | Person responsible for the next service updates authorised availability channels and informs the person taking orders. | Check completion before the next order is accepted. Escalate any channel they cannot change or any accepted order needing a remedy. |
- Open matter
- Missing-item report; reply promised by 15:15.
- Owner and next action
- Incoming customer-enquiry owner checks the existing order record and contacts the customer.
- Follow-up and escalation boundary
- If the record cannot be resolved by 15:10, involve the person authorised to decide the remedy. Do not promise a refund outside existing authority.
- Open matter
- An unavailable item is still offered for the next service period.
- Owner and next action
- Person responsible for the next service updates authorised availability channels and informs the person taking orders.
- Follow-up and escalation boundary
- Check completion before the next order is accepted. Escalate any channel they cannot change or any accepted order needing a remedy.
Fictional operating example. The times are chosen to demonstrate a boundary, not a response-time promise. Keep customer identifiers in the appropriate order record, not in this public example or a casual handover message.
A usable format has six answers.
The shift record should identify the open matter, what has already been promised, the next action, the incoming owner, the review time and the escalation boundary. Add a reference to the authorised record rather than copying its full contents.
For each entry, ask the incoming person to confirm that they can act. A name on a list is not evidence that responsibility has been accepted. If nobody present has the necessary authority, say that clearly and identify who can decide.
Use the routine and system the operation already has. A short conversation supported by a written record may be enough. The purpose is continuity during service, not an elaborate document that nobody has time to maintain.
| Field | Useful entry | Avoid |
|---|---|---|
| Open matter | The unresolved order, customer promise or operating exception. | A vague “pending” label. |
| Commitment already made | What was promised, and by whom, with a record reference. | A new promise made without checking the earlier one. |
| Next action | One specific action the receiving person can take. | “Look into it” with no defined next step. |
| Incoming owner | The actual person accepting responsibility on this shift. | A department name nobody has accepted. |
| Review time | When to confirm completion or revisit the matter. | An invented response guarantee. |
| Escalation boundary | What requires the authorised decision-maker or specialist process. | Assuming ownership gives unlimited authority. |
- Field
- Open matter
- Useful entry
- The unresolved order, customer promise or operating exception.
- Avoid
- A vague “pending” label.
- Field
- Commitment already made
- Useful entry
- What was promised, and by whom, with a record reference.
- Avoid
- A new promise made without checking the earlier one.
- Field
- Next action
- Useful entry
- One specific action the receiving person can take.
- Avoid
- “Look into it” with no defined next step.
- Field
- Incoming owner
- Useful entry
- The actual person accepting responsibility on this shift.
- Avoid
- A department name nobody has accepted.
- Field
- Review time
- Useful entry
- When to confirm completion or revisit the matter.
- Avoid
- An invented response guarantee.
- Field
- Escalation boundary
- Useful entry
- What requires the authorised decision-maker or specialist process.
- Avoid
- Assuming ownership gives unlimited authority.
Keep access limited to the people who need the record. Do not duplicate payment details, personal contact information or personnel records into informal shift notes.
Operating clarity does not replace specialist controls.
Food safety, temperature control, allergen information and legally required procedures stay within the operation’s established specialist controls. A shift note is not an authorisation to serve an item, improvise an allergen answer or bypass a required check.
If an open matter concerns a potential safety issue, use the existing escalation procedure immediately. Do not wait for the convenient review time in a general handover list. The example above deliberately concerns service continuity and availability, not a decision about food safety.
Personnel welfare, illness, injury and confidential staff matters also need their appropriate procedures and access boundaries. Record only the operating information the next person is entitled to receive. Do not turn a shared shift record into a medical, disciplinary or personnel file.
The person leading the shift may not be the person authorised to approve refunds, repair equipment or change commercial terms. State the limit alongside the responsibility so the team can act without guessing.
Review a normal shift and a busy one.
Observe one ordinary changeover and one busier changeover where feasible. Ask outgoing and incoming people which open matters were difficult to carry. Use records you are entitled to examine. You do not need a customer’s private history to establish whether responsibility was clear.
Test one change within the existing routine. For example, ask the incoming person to confirm the owner and next action for each unresolved promise. Check whether the format is short enough to use during service and whether both sides understand what completion means.
Review missed replies, unresolved availability changes and questions that still returned to you. Do not blame the person automatically. Missing authority, inaccessible records or conflicting instructions can require different changes.
ScaleOn’s method is Diagnose, Design, Enable, Govern, Transfer. Applied here, the useful output is a handover your team can use and own, with necessary founder judgement and specialist controls kept in their proper place.