Every operator says they run weekly P&L reviews. Almost nobody runs the version that changes behavior. Most weekly reviews become status meetings. The area director walks in, the general manager presents the numbers, everyone confirms things are on track, the meeting ends, the P&L keeps drifting.
The version I run now is 45 minutes, has the same structure every week, and produces one committed action per meeting. It is not glamorous. It is what makes the operating rhythm hold.
Why weekly, not biweekly or monthly
Every operator asks this question. The pull toward biweekly is strong because 21 general managers times a weekly meeting is a lot of time for an area director. The answer is still weekly.
Two reasons. First, food cost and labor variance decay quickly. A miss on labor variance last week is fixable this week. A miss two weeks old is baked into the month. Second, weekly meetings compound. The general manager knows the questions are coming Monday, so they look at the numbers Sunday night. That single behavior change is worth the meeting.
Biweekly meetings lose about half the compounding effect. Monthly meetings lose almost all of it. If you cannot commit to weekly, you have too many direct reports. That is a span-of-control problem, not a meeting problem.
The purpose of the weekly review is not to review. It is to force the general manager to look at their numbers on Sunday night.
The 45-minute agenda
Fig. 1 · Same clock every week.
Minutes 0 to 3: warm up
Two questions, not about the numbers. "How is your team this week?" "Anything I need to know that is not on the agenda?" Ninety seconds each. This is not throat-clearing. It surfaces the people issues that would otherwise interrupt the numbers conversation later.
Minutes 3 to 13: the four numbers
The general manager reads the four numbers from the shared dashboard. Sales versus forecast last week. Labor as a percent of sales last week. Food cost variance week to date. Comps and voids last week. Ten minutes total. No slides. No context yet. Just the numbers.
The point is to put reality on the table before anyone starts telling a story about it.
Minutes 13 to 30: the three variances
The general manager picks the three most meaningful variances from the last week and walks each. Not all variances. The three biggest, or the three most instructive. Why did it move, what did they see, what are they doing about it.
The area director listens, then asks at most two questions per variance. Not five. Two. The point of the questions is to sharpen the general manager's thinking, not to interrogate them. If the general manager cannot answer a question, that is data. Log it. Come back to it next week.
Minutes 30 to 40: the week ahead
Forecast for the coming week. Staffing plan. Any promos or events. Any expected risk (weather, competitor opening, event cancellation, a manager on PTO). Ten minutes to make sure the coming week is set up to be reviewed cleanly seven days from now.
Minutes 40 to 45: one action
The general manager names one specific action they will take this week to move a specific number. "I am going to rebuild the Wednesday dinner schedule to target 27 percent labor instead of 31." Not five actions. Not "focus on labor." One action, one number, one week.
Log it. Come back to it first thing next week. That single discipline is what makes the whole meeting compound.
What is not on the agenda
Equally important. Things that do not go in this meeting:
- Corporate updates. Send those in email. This meeting is not a broadcast channel.
- Personnel decisions. Separate meeting. Different tone.
- Menu debates. Separate meeting with the chef.
- Franchisor or investor updates. Separate meeting.
- Strategy discussions. Not a weekly conversation. That is the monthly regional review.
Every time you add something to the weekly review, something else gets squeezed out, and it will not be the corporate update that gets squeezed. It will be the one action commitment. Guard the format.
The general manager runs it
This is the change that most area directors resist and it is the one that matters most.
The general manager owns the meeting. They present the numbers. They pick the three variances. They name the action. The area director's job is to listen carefully, ask a few sharp questions, and confirm the commitment.
Why. Because ownership sits with the person who prepares. If the area director prepares the meeting, the area director owns the P&L in the general manager's mind. That is exactly backwards. The general manager runs the P&L. The meeting has to reflect that.
General managers who have never run this meeting will be uncomfortable the first three weeks. Coach them into it. First week, the area director walks the format and the general manager watches. Second week, the general manager presents the numbers with the area director prompting. By week four, the general manager runs it end to end. If they cannot by week six, the issue is not the meeting.
The shared log
Every weekly review produces two artifacts. The one action commitment, and a running log of what was discussed. Both live in the same place.
What works: a shared Airtable or Notion page per general manager. Weekly row with four columns: numbers snapshot, top three variances, one action, followup from last week. Takes about three minutes to fill in during or right after the meeting. The area director writes the log, not the general manager. The general manager already ran the meeting.
Six months of these logs is a picture of the general manager's development, the unit's operating pattern, and the quality of the coaching relationship. It is also the receipt for the quarterly and annual reviews.
The escalation rule
If the same variance shows up in three consecutive weekly reviews without moving, escalate. That does not mean fire the general manager. It means the weekly review is not enough to fix the issue. Time for a field visit, a deeper diagnostic, or a peer review from another general manager who solved the same thing.
Escalation is not a punishment. It is an admission that the weekly conversation reached its limit. Most operators avoid the escalation because it feels like they are giving up on the coaching. Refusing to escalate is what actually gives up on the coaching.
Where I got it wrong
Two mistakes worth naming.
I did too much of the talking
In the first six months of running this format, I dominated the meeting. I explained the variance instead of asking about it. I proposed the action instead of hearing it. Predictably the general managers stopped preparing, because I was going to do the work anyway. The meeting became my meeting, which meant the P&L became my P&L in their heads. Painful to unwind.
I let the meeting expand
Every week somebody wanted to add something. A quick note on a promo. A five-minute update on the new online ordering rollout. A brief walk-through of the guest satisfaction scores. Every addition was small. Cumulatively they doubled the meeting length and diluted the format. Now the format is fixed. Additions get their own meetings.
The point
A weekly P&L review that works is boring. Same time, same agenda, same four numbers, same three-variance walk, same one action. Repetition is the whole point. The magic is in the compounding, not in any one meeting.
Run it for six months and your general managers know their numbers cold. Run it for a year and the P&L stops surprising you. Skip it or turn it into a status meeting and the P&L becomes a fire drill at quarter end, every quarter.
Cadence beats charisma. This meeting is where cadence lives.