The pre-shift meeting, also called a lineup or huddle, is one of the shortest parts of a restaurant's day and, when it's done well, one of the most valuable. When it's done badly, it's the opposite: a rushed list of specials that staff stopped listening to after the first sentence, taking up time without changing anything about the shift.

Why These Few Minutes Matter So Much

Pre-shift is usually the only time the whole team is together, focused, and not yet busy. Once doors open, information travels in fragments: a quick word at the pass, a note on the POS, a shout across the floor. Anything important that doesn't get said before service has to compete with everything else happening during it.

Used well, pre-shift gets everyone aligned on what matters for this particular shift: a large party at 7:30, a dish the kitchen is still dialing in, an item that's about to run out, or a service issue from last night that needs fixing tonight.

What Separates a Useful Pre-Shift From a Wasted One

Length isn't the difference. A good pre-shift can run five to ten minutes. The difference is focus. A meeting that repeats the same generic reminders every day teaches staff to tune out. A meeting that always contains something specific and useful for that shift earns attention, because people learn it's worth listening to.

Here's a simple ten-minute structure:

  • Minute 0 to 2, the shift at a glance: covers expected, large parties, VIPs or regulars, and any notes handed over from the previous shift.
  • Minute 2 to 4, from the kitchen: the chef or sous covers specials, 86'd items, low-stock items, and anything the line needs from the floor tonight.
  • Minute 4 to 7, one focus point: a single thing to get better at, such as a wine to recommend, a natural upsell, or a step of service that slipped last night. One point, not five.
  • Minute 7 to 9, a taste or a quick drill: let the team taste the special, or role-play a common guest question.
  • Minute 9 to 10, recognition and close: call out something specific someone did well, then open the doors.

A few principles hold it together:

  • Focus on what's different or important about this shift, not a repeated script
  • Include the kitchen so the whole team shares the same picture of the night
  • Use it as a short, low-pressure training moment, not only logistics
  • End on something human, such as recognition, a quick question, or a laugh, rather than an administrative note

Looking to Build Your Restaurant Management System?

EatlyPOS is a modern, responsive frontend template built with Next.js that provides a solid foundation for developing a complete restaurant management system. Visit our homepage to explore the interactive demo, check available licenses, and kickstart your development with a professional codebase.

Learn More

Use Pre-Shift for Culture, Not Just Logistics

Beyond passing on information, pre-shift is a chance to build culture in small, steady doses. That might mean thanking the server who calmly handled a difficult table last night, celebrating a great review that named a team member, or simply setting an upbeat tone before a demanding Saturday.

It doesn't need to feel forced. Specific recognition works better than generic praise. "Maya, the way you handled the birthday table that got the wrong cake was exactly right" means more than "great job last night, everyone." Over weeks and months, these moments add up and feed into the kind of culture that reduces turnover.

Keep It From Becoming a Chore

If the manager running pre-shift clearly isn't invested, rushing through it while checking their phone, the team learns not to care either. Managers who spend five minutes preparing beforehand get a much more engaged team.

A few habits that help:

  • Write the day's three or four points down before the meeting starts
  • Use your POS data: yesterday's sales mix, a slow-moving special, or how long tickets took during the rush
  • Rotate who leads parts of it, letting a senior server, bartender, or cook run the focus point
  • Start on time, every time, so the meeting feels like part of the shift instead of an optional extra

Adapt the Format, Keep the Purpose

Different shifts need different formats. A 20-person brunch team might need a full huddle in the dining room, while a three-person weekday lunch crew can cover everything in two minutes at the bar. Some restaurants run separate front-of-house and kitchen lineups and then bring everyone together for one final minute.

Whatever the format, the purpose stays the same: a short, focused moment that gets the team aligned before service begins, rather than leaving each person to start the shift with whatever they happened to pick up on the way in.