Restaurant shift handover checklist: a usable log and clear ownership

Why a message in the group chat is not a handover

A handover transfers operational responsibility. A chat message only transfers information. The incoming manager must know which issues remain open, what has already been done and what they need to do next. Without acceptance, both shifts can reasonably assume the other person is handling the problem.

Use the chat for urgent notification if that is your team’s normal channel, but keep the current state in one accessible log. Otherwise photographs, voice notes and corrections become scattered across conversations. The goal is not more documentation: it is a short, reliable view of exceptions. Routine work can stay in its checklist; only deviations and unfinished commitments need prominent handover attention.

Record what changed

Use the same structure each day: team availability, reservations, unavailable menu items, equipment issues and open guest requests. Include only information the incoming shift can act on. A long diary is harder to use during service.

Name the next action

For every unresolved issue, record what happened, what has already been done, who takes over and when to check again. Do not rely on a message being read as proof that responsibility has been accepted.

Confirm together

Reserve a short overlap for the outgoing and incoming shift leads. Review exceptions and confirm ownership. If a problem repeats, move it into the weekly process review instead of copying the same note indefinitely.

Seven blocks for the manager’s handover

Use seven blocks: people, reservations, menu availability, equipment, guest commitments, stock exceptions and money-related discrepancies. Under people, record actual coverage and replacements, not unnecessary personal details. Under reservations, include operational requirements and the person responsible for follow-up. Under menu availability, distinguish an item that has run out from an item temporarily paused pending verification.

For equipment, note the operational restriction and authorised next step. Guest commitments should include what was promised and by whom, with access limited to staff who need it. Stock exceptions should reference the inventory record. Money discrepancies belong in a controlled reconciliation process; a handover note should identify the issue and owner without exposing payment-card details.

A sample entry that someone can act on

Weak entry: “Terrace booking problem. Please check.” Usable entry: “18:10, reservation R-104 for six at 20:00. Covered terrace requested; current allocation is indoors. Outgoing manager has explained that terrace confirmation is pending. Incoming manager checks availability by 18:45 and contacts the guest through the booking system. No terrace promise has been made.” This is a fictional example.

The difference is context, status, next action, owner and deadline. Add acknowledgement by the incoming manager and close the entry only when the guest has received the confirmed outcome. If conditions change again, append the update rather than replacing the earlier promise. The record should explain the sequence without forcing staff to reconstruct it from memory.

Urgent issues cannot wait for the next shift

Separate normal follow-up from issues that require immediate escalation under the venue’s procedures. A potentially unsafe product, an equipment hazard or uncertain allergen information is not just a note for tomorrow. Staff need a known escalation contact and authority boundaries, including when to stop the affected activity while a qualified person checks it.

The FDA Food Code is a US model for retail food safety, not Thai law. It is a useful example of why food operations require defined controls, but local requirements and the venue’s approved procedures govern the actual action. Do not replace temperature, hygiene or allergen procedures with a generic management checklist. The handover should reference the relevant control record and show who owns the unresolved issue.

Multilingual teams and remote owners

For a team in Koh Samui with different working languages, use consistent field names and plain sentences. Dates should include the day and local time; “tomorrow evening” becomes ambiguous when a remote owner reads it later. Define statuses such as open, waiting for supplier, accepted by next shift and closed. A translation should preserve operational meaning rather than decorative wording.

The owner does not need every guest interaction. Give them a view of overdue, repeated or high-impact issues. Keep the detailed log available to authorised staff. This lets the owner distinguish an isolated service recovery from a persistent staffing or equipment problem. Use anonymised summaries for broader management discussion whenever the identity of the guest is irrelevant.

How to introduce the checklist without bureaucracy

Pilot the log on one shift pair. Ask the incoming manager which information they actually used and what was missing. Remove fields that no one uses for a decision. Keep the overlap short and focused on exceptions. At the weekly review, inspect unresolved age and repeated issues rather than judging the team by how many notes it produced.

Should the outgoing manager remain until every issue is solved? Not necessarily: acceptance and a clear next step allow work to continue across shifts. Can an AI assistant summarise the log? It can help draft a summary, but a person should verify material commitments and missing context. Who closes a task? The person who verifies the outcome, according to the agreed responsibility rule.

Continue reading