Operations & tasks
How to Run a Restaurant Shift Meeting
A pre-shift meeting is not a lecture. It is a quick alignment ritual that prevents expensive mistakes during rush. The best huddles answer four questions in plain language. What is different tonight versus a normal Tuesday: events, large parties, promos, staffing gaps, or equipment issues. What must not break: allergen communication, time and temperature rules, steps of service for VIPs, and any cash or security quirks. Who needs help: a green cook on saute, a server covering an extra section, or a bartender running a new build. What does success look like by close: sell-through targets, table turn goals, and cleanliness minimums.
Keep it standing and time boxed. Ten minutes is a ceiling for most full service teams. One voice leads, usually the manager on duty or expo on heavy kitchen nights. Rotate micro teachable moments, but do not turn the circle into ten minutes of storytelling.
Close the loop in systems, not memory. If the fryer is flaky, if a guest recovery needs a follow up, if prep fell short on a key item, create tasks with owners and due times before the first guest walks in.
Restaurant Codex connects those priorities to one-off Operational assignments while analytics show whether follow through happened. Pair the huddle with Knowledge Base micro references for builds or allergy scripts when the team needs a refresher.
Related question
What are restaurant shift handoff best practices?One source of truth: cold chain status, 86s, equipment, guest recovery, cash exceptions, and open work with owners. Verbal only fails.