Write Better Shift Handover Notes in a Small Restaurant

Imagine arriving for an evening shift to find a note that says, ‘Busy lunch. Please sort the fridge and call the guest.’ You have no idea which fridge, whether food has been protected, or which guest is waiting for what. It is an uncomfortable way to start work. A thoughtful handover does not need to recount an entire service; it needs to leave the next person feeling informed, able to act and confident about which issues have already been addressed. The best notes respect both the people coming on duty and the customers whose experiences continue across shifts.

Start with what the incoming colleague needs to feel ready

At a shift change, staff may be handling bookings, deliveries, cleaning, customer requests and a queue of new orders. Ask the incoming colleague what decisions they must make within their first ten minutes. Those are usually more important than an account of how stressful lunch felt. For instance, knowing that one table has requested a later arrival matters more than a long explanation of why the dining room was noisy earlier.

Place time-sensitive operational matters at the start: current bookings and agreed changes, unavailable items, equipment restrictions, urgent customer follow-ups and outstanding safety actions. Where the definitive information already lives in the booking or food-safety system, link or refer to that record rather than copying a possibly outdated version. The purpose is orientation, not creating another competing source of truth.

Ask one simple question before adding a line: what could the next team do incorrectly if they did not know this? If there is no convincing answer, it might be useful background for a separate discussion, not an urgent handover.

Give each unresolved issue a little context and a next step

‘Please check drinks stock’ could mean several things. Is a delivery late? Is there an unexpected shortage? Has stock been moved to another storage area? A usable note explains what was observed, what has already been done and what decision remains. It should also say who owns that decision and when it needs attention.

For example: ‘Apple juice delivery short by two cases; quantity logged on supplier discrepancy record R17; shift manager to check supplier reply before tomorrow’s lunch.’ This illustrates a format, not an actual restaurant incident. The next person can find the detailed evidence without searching through a colleague's messages or repeating the receiving work.

For equipment, avoid diagnostic guesses. ‘Cold room not working’ is too vague if the issue was an intermittent alarm, and unsafe if it conceals an unresolved food-storage problem. Record the equipment identifier, observed condition, safety action already taken and the authorised person contacted. Food-safety procedures, not a handover notebook, must govern whether affected equipment or ingredients may be used.

Keep food-safety records authoritative

Some information cannot responsibly be reduced to an informal sentence. The Food Standards Agency's current food-business guidance collection covers food-safety management and allergen information. A handover should direct staff to the restaurant's maintained checks, relevant logs and escalation procedure rather than pretending to replace them.

If a temperature control, cleaning task or equipment inspection has failed, the appropriate response follows the documented food-safety plan and competent management decision. A shift note can say that a matter is unresolved and where the record sits; it cannot declare the affected food safe because the writer hopes the problem will disappear. Similarly, a supplier change or recipe substitution that may affect allergens needs formally updated ingredient information before anyone answers a customer.

Make the handover format easy to complete without inviting false certainty. ‘Action pending, responsible person informed, affected station not in use’ communicates a practical boundary. A tick beside ‘food safety checked’ gives little assurance unless it corresponds to actual required controls.

Protect the guest's trust when a concern crosses shifts

Guests should not have to tell a difficult story three times because colleagues fail to hand over a promised response. A complaint about a missing item, a disputed bill or an accessibility arrangement can be acknowledged with care and carried forward to someone who can resolve it. Record the promise made, the expected follow-up and the authorised contact route, without including unnecessary private detail.

For example, the handover might refer to an incident number in the approved customer-service system and say, ‘Duty manager to contact guest tomorrow about the agreed correction.’ It need not copy the person's full phone number, address and private conversation into a notebook that any passer-by could see. The Information Commissioner's Office guidance on data minimisation explains that personal data should be adequate, relevant and limited to what is necessary.

When a guest has made a time-sensitive arrangement, make the next team aware of what is actually confirmed, not merely what someone intends to arrange. ‘Requested step-free access; awaiting manager confirmation’ is materially different from ‘step-free access confirmed’. That distinction is both considerate and operationally important.

Make stock and menu changes immediately understandable

‘No salmon’ might mean sold out, supplier delay, safety concern, a temporary menu pause or a staff misunderstanding. The incoming team needs to know which. State the affected item, the reason if known, whether the till and online menus have been updated, and who can authorise its return. Otherwise the front-of-house team may promise a dish that the kitchen has already withdrawn.

Use maintained recipe and allergen sources when ingredients change. A short handover cannot reliably contain a complete ingredient declaration, and the next colleague should not interpret a substitute as suitable for an allergic customer without the established checks. Where one sales channel still displays an unavailable dish, record that as an open correction with an owner.

For expected deliveries, note the order reference and any action required on arrival, not just ‘stock coming’. If an item is held because of a supplier dispute or damage, identify its physical holding location so it is not accidentally used. Keep quantity, product identification and stock-system updates consistent.

Choose a format that works for real people on a busy evening

A stable template can have a short shift identifier, the immediate priorities, open actions, customer follow-ups, stock and menu exceptions, equipment or safety references, and the person accepting responsibility. That is enough for many small restaurants. It should not demand a paragraph under every heading if nothing relevant happened. Requiring filler teaches staff to write without thinking.

Paper can work where everyone knows where the current sheet lives and how completed records are stored. Digital notes can help when different teams need controlled access, but only if the system remains usable during interruptions. Agree who may edit entries, when an issue is closed and how older versions remain traceable when necessary. Do not let informal chat threads become an invisible parallel handover that excludes the next colleague.

Where possible, allow a brief verbal exchange for genuinely complex issues. The written record should survive even when colleagues do not overlap, but tone and context sometimes benefit from a careful conversation. The principle is not more paperwork; it is less uncertainty for the people who inherit unfinished work.

Stop old problems being copied forward forever

A repeated note about a broken appliance can become background noise. Give open items a clear owner, an action date or review point and a reference to the formal issue record where appropriate. When resolved, record the closure and remove it from the live list rather than leaving the next shift to investigate again. Do not simply delete evidence of a safety-critical problem to make the handover look clean.

Spend a few minutes after a particularly difficult shift reviewing whether incoming staff knew what mattered. Did they discover a booking change late? Was a product sold despite being unavailable? Was a customer promised a callback that nobody owned? These questions identify gaps better than counting how many lines employees filled in.

Ask for feedback without blame. People may stop reporting uncertainty if every incomplete handover turns into an accusation. A consistent, respectful process should make it easy to say, ‘I noticed this; I have taken these steps; I need help deciding what happens next.’

Test the handover by letting another colleague use it

Before settling on a template, give a realistic example to a colleague who did not write it. Can they find the urgent tasks, identify the responsible person, locate the source record and explain what has been promised to a customer? If they need a lengthy telephone call to reconstruct the situation, edit the note for clarity. If they can act but the writing is long, reduce what does not help.

Review a sample of open and closed items every few weeks. The strongest sign of improvement is not beautiful wording. It is fewer repeated searches, fewer missed commitments and fewer unresolved risks drifting from one shift to the next. Recognise that colleagues need different amounts of context: a new employee may need a reference to a procedure, while an experienced manager may need only the exception and decision owner.

A good handover is a small act of care. It tells the next person, ‘Here is what matters, here is what we know, and here is where help is needed.’ It also gives customers a better chance of receiving the service they were promised, even when the person who made that promise has gone home.