Most restaurants either run too many meetings or none at all. Owners who feel burned by endless, unproductive sit-downs stop scheduling them altogether, and then wonder why nothing improves between shifts. The fix is not more meetings or fewer meetings. It is the right three, run for the right reason.
What meetings should a restaurant actually run?
A restaurant should run exactly three recurring meetings: a Daily Huddle at the start of every shift, a Weekly Sync on the same day and time each week, and a Monthly Review in the first week of the month.
Each one has a different job. The Huddle aligns the team on today. The Sync rolls daily data up into weekly patterns. The Review steps back and looks at trends and strategy. Running more than this turns management into a calendar full of overlapping check-ins. Running fewer than this means the team is guessing instead of executing against a plan.
The common thread across all three is simple: they exist to teach, coach, and solve problems. If a meeting is only there to deliver information one way, it should be a memo instead.
What happens in the Daily Huddle?
The Daily Huddle is a five to ten minute launch sequence at the start of every shift that sets the revenue target, the operational focus, the feature item, and any alerts the team needs before service starts.
It is not a meeting in the traditional sense. It is a short sequence that makes sure every person on the floor knows the same three things before the doors open: the number they are working toward, the one priority for the shift, and the item they are pushing, along with a short script for how to sell it. It also covers anything 86'd, any reservations or VIPs the team needs to know about, and any alerts that matter that day.
- Today's revenue target, covered in about thirty seconds
- Today's single operational focus, covered in about thirty seconds
- Today's feature item and selling script, covered in about a minute
- 86'd items, reservations, VIPs, and alerts, covered in about a minute
- One teaching moment, a short coaching point of about two minutes
The temptation is to skip it on the busiest days. That is backward. A few minutes of alignment before the shift prevents confusion once service starts, and the busier the restaurant is, the more that alignment matters.
What happens in the Weekly Sync?
The Weekly Sync is a thirty minute meeting where each manager presents their team's performance patterns from the week and the action plan for the week ahead.
This is where daily scorecard data, the kind of information a manager collects shift by shift, rolls up into something an owner can actually act on. Each manager presents a summary of how their team is performing, the top patterns from the week, and what they plan to do differently next week. The owner's job is to coach on those patterns, not to relitigate individual employee incidents.
- Each manager presents team patterns and next steps
- Blockers and support needed are raised and addressed
- Next week's focus areas are agreed on
- Quick wins and recognition are called out
Without the daily documentation feeding it, the Weekly Sync turns into a complaint session built on feelings instead of data. The rule is simple: no venting without data behind it. For a deeper look at how daily discipline is supposed to feed this meeting, see the four levels of restaurant management.
Results are not typical and will vary with your business, your market, your team and how much of the work you actually do. Client figures on this site come from recorded interviews and are dated. Nothing here is a guarantee of revenue, profit or growth.
What happens in the Monthly Review?
The Monthly Review is a sixty minute meeting in the first week of each month that walks through the full P&L, reviews trends, assesses team development, and sets the strategic focus for the month ahead.
This is the meeting where the owner stops looking at today or this week and looks at direction. It covers the full profit and loss statement, what improved and what declined and why, who on the team is growing versus who needs coaching or is at risk, and what the strategic priority is for the next month. It closes with an open floor, specifically to surface anything that is not working that nobody has raised yet.
- Full P&L walkthrough
- Trend analysis: what improved, what declined, and why
- Team development: who is growing, who needs coaching, who is at risk
- Strategic focus for the next month
- Open floor for unraised problems
Restaurants that install this kind of structure tend to find problems before they compound. One Founders Board member installed KPIs on every line of his P&L within ninety days of starting this work. See his story in the Pizza Pizzazz case study.
Why does the CEO have to teach in every meeting?
The CEO's actions account for the large majority of the outcome, so a meeting that does not teach, coach, or connect work back to profit wastes the leverage every other person in the company depends on.
The framing behind this lesson is blunt: the CEO is 95% of success, and everybody else, even in a company of thousands, is the remaining 5%. That does not mean the team does not matter. It means that if the person running the meeting is not using it to teach, the other 5% has nothing to connect to.
“The CEO is 95% of success. Everybody else, even 10,000 people in the company, they are 5%. CEO, 95%, everybody else, 5%.”
In practice, that means an owner reviewing a manager's P&L should not simply report the numbers. The job is to teach the manager the order the metrics follow: profit first, then sales and expense, then what drives sales, then what drives expense. Once a manager understands that order, they stop reacting to numbers and start thinking like an owner.
What goes wrong when restaurants skip this rhythm?
Without the Huddle, the team loses alignment before service starts. Without the Sync, daily data never turns into a pattern anyone acts on. Without the Review, small declines go unnoticed until they become large ones.
The most common failure is treating meetings as reporting sessions instead of teaching sessions. A manager who leaves a meeting knowing exactly what they knew walking in did not get anything out of it, and neither did the owner. The rule worth repeating is that if nobody learned something, the meeting was a waste.
The second most common failure is disconnecting daily work from the main goal. Teams keep doing today what they did yesterday, without anyone asking whether it still connects to profit. Sports teams never make a move without connecting it to the score. Restaurants, left unmanaged, tend to drift the other way.
This meeting rhythm is one piece of a larger operating system that the Founders Board gives members a license to install, covering how managers are organized, how scorecards feed into reviews, and how ownership of the P&L moves down the org chart. For more on how that structure scales with headcount, see the restaurant org chart by size.
Owners who want to see how this kind of structure changes day-to-day operations can look at how Temakasi moved from being every role to rarely needing to be there.
How does a restaurant start running this meeting rhythm?
It starts by scheduling the three meetings on a fixed cadence, even before every system behind them is built, and treating each one as a teaching opportunity rather than a status update.
The Huddle can start the same day a restaurant decides to run it. The Sync needs a manager who is already documenting daily patterns, since without that input the meeting has nothing real to discuss. The Review needs a P&L that is current enough to walk through line by line. None of this requires new software or a new hire. It requires an owner willing to show up every time as the teacher, not the auditor.
Restaurants that want help installing this rhythm alongside the rest of an operating system can look at the Founders Board or apply to discuss fit.
